Error comfirming subscription from Mailman

After I installed Mailman on my FreeBSD server, I created a test list and sent a subscription to it, the server returned the folowing error message. What causes this problem? Any help will be appreciated. Jeffrey
The original message was received at Tue, 7 Jan 2003 16:16:41 -0800 (PST) from localhost [127.0.0.1]
----- The following addresses had permanent fatal errors ----- <test-request@listserv1.whittier.edu> (reason: 550 5.1.1 <test-request@listserv1.whittier.edu>... User unknown)
----- Transcript of session follows ----- ... while talking to listserv1.whittier.edu.:

Feng Jeffrey wrote:
Did you add the aliases to your MTA's alias file?
-- W | I haven't lost my mind; it's backed up on tape somewhere. +-------------------------------------------------------------------- Ashley M. Kirchner <mailto:ashley@pcraft.com> . 303.442.6410 x130 IT Director / SysAdmin / WebSmith . 800.441.3873 x130 Photo Craft Laboratories, Inc. . 3550 Arapahoe Ave. #6 http://www.pcraft.com ..... . . . Boulder, CO 80303, U.S.A.

Make sure you setup the alias file for your mail server, you skipped that step. Its different for each mail server.
- Feng Jeffrey (yfeng@whittier.edu) wrote:
| Matthew Davis /\ http://dogpound.vnet.net/ | |--------------------------------------------| | Tuesday, January 07, 2003 / 09:59PM |
Modern man is the missing link between apes and human beings.

Hello - I'm new to Mailman.
I have just recently installed mailman 2.0.12 on a FreeBSD 4.7 system using the pkg_add feature.
I believe I have successfully configured the majority of the software package, but ever since I ran the '/usr/local/mailman/cron/crontab.in' I have been receiving the following e-mail message every minute:
Traceback (most recent call last): File "/usr/local/mailman/cron/qrunner", line 276, in ? lock.lock(timeout=0.5) File "/usr/local/mailman/Mailman/LockFile.py", line 219, in lock self.__write() File "/usr/local/mailman/Mailman/LockFile.py", line 350, in __write fp = open(self.__tmpfname, 'w') IOError: [Errno 13] Permission denied: '/usr/local/mailman/locks/qrunner.lock.devilbear.kumacommunications.net. 14720'
/usr/local/ mailman dir entry reads as:
drwxrwsr-x 18 root mailman 512 <date> mailman
Almost everything under /usr/local/mailman reads: (only expection is number of links in ls -l listing of some items)
drwxrwsr-x 2 root 91 512 <date> <dirname>
I apologize that if this has been addressed on this list before, but I have been so far unable to find a searchable archive of the Mailman-Users list.
Any help / guidance to solve the issue above would be most appreciated.
Regards, Chris

On Tuesday, January 7, 2003, at 10:55 PM, C Burchell wrote:
I have just recently installed mailman 2.0.12 on a FreeBSD 4.7 system using the pkg_add feature.
Did you manually add the mailman user and group before installing Mailman, or let the port add them? The port expects a certain UID and GID to be mapped to the Mailman user/group, specifically 91/91. If you're using some other UID/GID it'll be confused.
Bryan

I originally added the user and group mailman, but had the wrong GIDs, I subsequently removed the pkg, changed the uid and gid to 91/91 then reinstalled the package. Then I added the crontab.in file and there were no problems...
However, I have now noted the following error:
After I successfully create my first test list 'test-list', add the aliases, do the Postfix postmap & reload, I get the subscription confirmation message from the test list creation. However, when I try to send a post to the new test-list, I get the following error from Postfix:
The Postfix program
<Test-list@devilbear.kumacommunications.net>: Command died with status 2: "/usr/local/mailman/mail/wrapper post test-list". Command output: Failure to exec script. WANTED gid 26, GOT gid 65534. (Reconfigure to take 65534?)
Is there something Mailman-related that I can do to fix this error?
Regards, Chris

Feng Jeffrey wrote:
Did you add the aliases to your MTA's alias file?
-- W | I haven't lost my mind; it's backed up on tape somewhere. +-------------------------------------------------------------------- Ashley M. Kirchner <mailto:ashley@pcraft.com> . 303.442.6410 x130 IT Director / SysAdmin / WebSmith . 800.441.3873 x130 Photo Craft Laboratories, Inc. . 3550 Arapahoe Ave. #6 http://www.pcraft.com ..... . . . Boulder, CO 80303, U.S.A.

Make sure you setup the alias file for your mail server, you skipped that step. Its different for each mail server.
- Feng Jeffrey (yfeng@whittier.edu) wrote:
| Matthew Davis /\ http://dogpound.vnet.net/ | |--------------------------------------------| | Tuesday, January 07, 2003 / 09:59PM |
Modern man is the missing link between apes and human beings.

Hello - I'm new to Mailman.
I have just recently installed mailman 2.0.12 on a FreeBSD 4.7 system using the pkg_add feature.
I believe I have successfully configured the majority of the software package, but ever since I ran the '/usr/local/mailman/cron/crontab.in' I have been receiving the following e-mail message every minute:
Traceback (most recent call last): File "/usr/local/mailman/cron/qrunner", line 276, in ? lock.lock(timeout=0.5) File "/usr/local/mailman/Mailman/LockFile.py", line 219, in lock self.__write() File "/usr/local/mailman/Mailman/LockFile.py", line 350, in __write fp = open(self.__tmpfname, 'w') IOError: [Errno 13] Permission denied: '/usr/local/mailman/locks/qrunner.lock.devilbear.kumacommunications.net. 14720'
/usr/local/ mailman dir entry reads as:
drwxrwsr-x 18 root mailman 512 <date> mailman
Almost everything under /usr/local/mailman reads: (only expection is number of links in ls -l listing of some items)
drwxrwsr-x 2 root 91 512 <date> <dirname>
I apologize that if this has been addressed on this list before, but I have been so far unable to find a searchable archive of the Mailman-Users list.
Any help / guidance to solve the issue above would be most appreciated.
Regards, Chris

On Tuesday, January 7, 2003, at 10:55 PM, C Burchell wrote:
I have just recently installed mailman 2.0.12 on a FreeBSD 4.7 system using the pkg_add feature.
Did you manually add the mailman user and group before installing Mailman, or let the port add them? The port expects a certain UID and GID to be mapped to the Mailman user/group, specifically 91/91. If you're using some other UID/GID it'll be confused.
Bryan

I originally added the user and group mailman, but had the wrong GIDs, I subsequently removed the pkg, changed the uid and gid to 91/91 then reinstalled the package. Then I added the crontab.in file and there were no problems...
However, I have now noted the following error:
After I successfully create my first test list 'test-list', add the aliases, do the Postfix postmap & reload, I get the subscription confirmation message from the test list creation. However, when I try to send a post to the new test-list, I get the following error from Postfix:
The Postfix program
<Test-list@devilbear.kumacommunications.net>: Command died with status 2: "/usr/local/mailman/mail/wrapper post test-list". Command output: Failure to exec script. WANTED gid 26, GOT gid 65534. (Reconfigure to take 65534?)
Is there something Mailman-related that I can do to fix this error?
Regards, Chris
participants (5)
-
Ashley M. Kirchner
-
Bryan Fullerton
-
C Burchell
-
Feng Jeffrey
-
Matthew Davis