Deatils: RedHat 4.2, kernel 2.0.33, maj 1.94.4, sendmail 8.8.5-4.
I have five lists working just dandy under two virtual domains. I can add new
lists at will and they work on the first try.
Recently added a list for a host for which I am actually an alias. Nessus.org
is somewhere out there, 'I' am list.nessus.org. DNS works, ping etc, and httpd
virtualhost all work.
So I'm trying to move the firstname.lastname@example.org list to email@example.com.
The commands 'lists' or 'help' sent to firstname.lastname@example.org returns:
MAJORDOMO ABORT (mj_majordomo)!!
While running with an effective uid of 509 and an effective gid of 2 12,
Majordomo ran into the following problems: Unable to write to list directory
$listdir, check permissions on /maj/lists
Things sure look right to me:
drwxr-xr-x 3 majordom daemon 1024 Aug 3 14:20 lists.fidonews.org
drwxr-xr-x 5 majordom daemon 1024 Aug 4 20:09 lists.jbarchuk.com
drwxr-xr-x 3 majordom daemon 1024 Aug 1 12:10 lists.list.nessus.org
And here's a couple of typical directories:
-rw-r--r-- 1 majordom daemon 2573 Aug 4 14:09 nessus
drwxr-xr-x 2 majordom daemon 1024 Aug 4 20:11 nessus.archive
-rwxr-xr-x 1 majordom daemon 16081 Aug 1 10:39 nessus.config
-rw-r--r-- 1 majordom daemon 712 May 7 11:16 nessus.info
-rw-r--r-- 1 majordom daemon 0 Aug 1 09:05 aetest
drwxr-xr-x 2 majordom daemon 1024 Aug 1 08:04 aetest.archive
-rwxr-xr-x 1 majordom daemon 16158 Aug 1 08:15 aetest.config
-rw-r--r-- 1 majordom daemon 13 Aug 1 08:04 aetest.info
('aetest' is the new list I'm getting running first before moving nessus into
All the majordomo.aliases and virtusertable entries for email@example.com
are set up identical to firstname.lastname@example.org, I just copy/paste and edit to suit.
And why should it care anyway if it can't 'write to list directory' if all I'm
sending it a 'help' command? But that doesn't matter, it's not the 'problem',
just a 'symptom', it's the error message that's not intuitive.
Any clues? Need to see any config detritus?
Related to this, can anyone recommend how to make this transition as smooth as
possible, moving an active list from one domain to the other? My intuitive
guess is to shut off sendmail, move the files, and restart sendmail. Will this
have any effect on msgs already in the outbound queue? Obviously I'll need to
immediately post a message to the 'new' list about the change, and I expect a
few 'huh?' queries if someone sends something that bounces, I just want to make
things as easy and transparent as possible for the users. Yes, the user's
filters will break, but that's the price of progress. :)
I have this -very- strange karma thing happening too. I used to read this list
a lot when having difficulties initially getting maj running. Found most
answers in list archives. Later the volume got to be too much I shut it off,
and -then- maj started acting up. Turned the list back on, didn't even ask a
question about it, and fixed it myself. Recently shut the list off again and
-then- this new problem happens. So it appears the majordomo program itself
-knows- whether or not I am subbed to this list, prefers that I be subbed, and
throws a fit when I unsub. Must be some backdoor/sidedoor/screendoor thing
going on. :)
Thanks much. Have a :) day!