Success. It's always the simple permissions issues! Considering that
most who run mailman with postfix would face this, I'm suprised that a 0 B
aliases file and db were included with the fedora rpm - it would prevent
users from getting the perms wrong on a system where you, by default,
cannot su to mailman.
Thanks again to everyone (and sorry it turned out to be such a trivial
# If I had only known, I would have been a locksmith.
# -- Albert Einstein
Well, I rmlist'd the list and tried again with the new aliases db line in
my main.cf for postfix. No dice. However, I did encounter an error page
that might help. What happens is I enter the info on the create list
page. When I submit, I get a popup asking what user's password I'm trying
to change, so I select <>. Next page is an error (below). If I again try
the process, I'm told the list exists already (an error page indicates as
much). FWIW, I also double-checked and I cannot get mail at
mail.nekophile.com in general (same error).
That error page:
Bug in Mailman version 2.1.2
We're sorry, we hit a bug!
If you would like to help us identify the problem, please email a copy of
this page to the webmaster for this site with a description of what
Traceback (most recent call last):
File "/var/mailman/scripts/driver", line 87, in run_main
File "/var/mailman/Mailman/Cgi/create.py", line 55, in main
File "/var/mailman/Mailman/Cgi/create.py", line 217, in process_request
File "/var/mailman/Mailman/MTA/Postfix.py", line 232, in create
File "/var/mailman/Mailman/MTA/Postfix.py", line 53, in _update_maps
raise RuntimeError, msg % (acmd, status, errstr)
RuntimeError: command failed: /usr/sbin/postalias
/var/mailman/data/aliases (status: 1, Operation not permitted)
sys.version 2.2.3 (#1, Oct 15 2003, 23:33:35) [GCC 3.3.1 20030930 (Red
Hat Linux 3.3.1-6)]
SERVER_SOFTWARE Apache/2.0.47 (Fedora)
Apache/2.0.47 (Fedora) Server at www.nekophile.com Port 80
HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5)
The file perms:
root@twiggy $ ls -la
drwxrwsr-x 2 root mailman 4096 Nov 29 17:20 .
drwxrwsr-x 19 root mailman 4096 Nov 20 12:56 ..
-rw-rw---- 1 root mailman 4278 Nov 29 17:20 aliases
-rw-r----- 1 mailman mailman 12288 Nov 29 17:20 aliases.db
Thank you again!
Is there any alternative to running qrunner via cron?
I am used to Majordomo which just sends outgoing mail straight through to
Sendmail and it gets sent out automatically as and when necessary.
Can I get Mailman to do this?
What I would like to do is avoid mail from being queued, or at least
process it as soon as it has arrived in the qfiles directory. Is there any
option for doing this?
I just upgraded from MDK9.1 to 9.2. I now have Mailman 2.1
I know that the aliases have a problem, so I created a new list
"testlist" and added one address, myself.
I had some permission problems (seen in the mail log) but solved those
with check-perm -f
I now cannot find any new errors in the logs. the mail log info shows
that the massage was sent:
Nov 29 09:21:58 aargau postfix/pickup: 9201C415F3: uid=501
Nov 29 09:21:58 aargau postfix/cleanup: 9201C415F3:
Nov 29 09:21:58 aargau postfix/nqmgr: 9201C415F3:
from=<thomas(a)btspuhler.com>, size=1111, nrcpt=1 (queue active)
Nov 29 09:21:59 aargau postfix/local: 9201C415F3:
to=<testlist(a)btspuhler.com>, relay=local, delay=1, status=sent
("|/usr/lib/mailman/mail/mailman post testlist")
I only see one hint from lst night, but no new after the last message:
Nov 28 20:18:00 2003 mailmanctl(8406): Is qrunner even running?
Nov 28 21:32:40 2003 mailmanctl(8822): PID unreadable in:
Nov 28 21:32:40 2003 mailmanctl(8822): [Errno 2] No such file or
Nov 28 21:32:40 2003 mailmanctl(8822): Is qrunner even running?
Nov 28 22:17:29 2003 mailmanctl(3681): Site list is missing: mailman
Nov 28 22:17:29 2003 (3681) Site list is missing: mailman
Nov 28 22:44:27 2003 mailmanctl(4297): PID unreadable in:
Nov 28 22:44:27 2003 mailmanctl(4297): [Errno 2] No such file or
Nov 28 22:44:27 2003 mailmanctl(4297): Is qrunner even running?
bash-2.05b$ grep mailman /etc/aliases
# Added by the mailman rpm
## created: 11-Jul-2003 mailman
spuhlerfam: "|/usr/lib/mailman/mail/wrapper post
spuhlerfam-admin: "|/usr/lib/mailman/mail/wrapper mailowner
spuhlerfam-request: "|/usr/lib/mailman/mail/wrapper mailcmd
tmwchorale: "|/var/lib/mailman/mail/wrapper post
tmwchorale-admin: "|/var/lib/mailman/mail/wrapper mailowner
tmwchorale-request: "|/var/lib/mailman/mail/wrapper mailcmd
tmcboard: "|/var/lib/mailman/mail/wrapper post tmcboard"
tmcboard-admin: "|/var/lib/mailman/mail/wrapper mailowner
tmcboard-request: "|/var/lib/mailman/mail/wrapper mailcmd
No aliases show up for testlist!
Unfortunately there is not much literature available about MM version
All e-mails from this location have been scanned for viruses
This e-mail has been digitally signed
I am trying to setup a mailing list for an orchestra. We have about 750
subscribers. When I was testing the mailman with 4-10 people it worked fine,
when I transferred everybody to the list and tried to post a message, only
5-10% received it, the rest got bounce score of 1.0. Even those who had no
problems in testing mode. Did anybody have a similar problem? Support of my
hosting company says that everything is fine on their side and mailman is
Thanks in advance.
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
Rod Neep wrote:
>List members can all post OK to the list
>The messages all appear in the archives for each list.
>User A receives mail from some lists, but not from others
>User B ditto (but not the same lists necessarily).
>Therefore there is nothing wrong with the user's address or ISP.
>The problem exists with hundreds of users, (but not all).
What ISP's are affected? ISP's and on-line mail systems like HotMail
and Yahoo are all adding and changing systems to deal with spam, and
Mailman list mail will get flagged as spam by many of these systems. I
know that by default both HotMail and Yahoo will direct list mail to the
bulk or junk folder. To make matters worse Yahoo's system has a bad habit
of "forgetting" that a list has been identified as wanted mail.
As far as I know all major systems will not block of move something
like a password reminder, so have the users request such a reminder from
any list they do not get mail from. If they get that, it's probably a spam
For Yahoo the best bet is to set up a filter rather than using their
spam marking system. Users who belong to more than one of your lists can
set up to receive anything from your server and be done with it.
A really strange problem.... I wonder if anyone has seen anything
similar, or can offer any clues.
I have over a hundred mailing lists.
List members can all post OK to the list
The messages all appear in the archives for each list.
User A receives mail from some lists, but not from others
User B ditto (but not the same lists necessarily).
Therefore there is nothing wrong with the user's address or ISP.
The problem exists with hundreds of users, (but not all).
Some lists post messages out to all users
Some lists post messages out to *some* users
Some lists do not appear to post out any messages
There seems to be no reason, and no logic to the thing?
When a user doesn't receive list mail, unsubscribing, and then
subscribing again doesn't make any difference.
Nothing has been changed in any configuration in MailMan, and no new
lists have been added for a few months. Hard disks are nowhere near
full. The problem began about a week ago.
Does anyone have any ideas??
Archive CD Books : http://www.archivecdbooks.org