Mail to some lists works, bounces for others
Hello,
We have a number of mailing lists that are member-only. On most of the lists, users can post successfully.
But on others, even though people attempting to post are members, or in one case the list owner, their mail is rejected. "550 5.1.1 Recipient address rejected: User unknown"
There are no lock files for a particular list.
The only files in /var/lib/mailman/locks are master-qrunner and master-qrunner.mailman.2502 (The dates on those two files are more than 24 hours into the future - is that normal?)
The /var/lib/mailman/data/aliases shows the relevant aliases for that particular list.
Mailman version: 2.1.13 OS: Ubuntu 10.04.2 MTA: Postfix 2.7.0
thanks,
Luke
Luke Tymowski wrote:
Locks are not relevant to this issue as Mailman never sees the attempted posts.
The only files in /var/lib/mailman/locks are master-qrunner and master-qrunner.mailman.2502 (The dates on those two files are more than 24 hours into the future - is that normal?)
Yes, the timestamps on the master-qrunner locks are in the future. That is the time at which the lock expires.
The /var/lib/mailman/data/aliases shows the relevant aliases for that particular list.
And has the /var/lib/mailman/data/aliases.db file been updated since those aliases were added?
In fact does Postfix even use those aliases?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hello,
And has the /var/lib/mailman/data/aliases.db file been updated since those aliases were added?
What confused me was that these are all lists that have been around for the last 6-7 years.
I moved the lists to a new server 2 weeks ago. Most of the lists worked just fine.
So, yes, the aliases.db exists and was regenerated when I moved the lists to the new server.
In fact does Postfix even use those aliases?
Well, most of the lists worked, but some didn't. I'd think if Postfix didn't know about those aliases, none of the lists would work (it's the only place where the list handlers are kept).
I fixed the issue by editing /etc/mailman/mm_cfg and changing: MTA=none to MTA='Postfix'
Then running /var/lib/mailman/bin/genaliases
Mailman/Postfix were installed from apt-get.
Luke
Luke Tymowski wrote:
So there was some problem with the aliases. Either they weren't in /var/lib/mailman/data/aliases or /var/lib/mailman/data/aliases.db was not properly synced with /var/lib/mailman/data/aliases, because, assuming virtual mappings are not involved, that's the only thing that would be affected by the things above.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
So Mailman on the new server has been installed using apt-get.
Then you moved your list files/directories from the old server to the new server?
My Sysadmin-sense[tm] is tingling. I get the feeling that either the permissions of some of the files/directories are not correct or, and this is a biggie when moving servers, the "ownership" of those files/directories may no longer be correct.
Are there any warnings about access permissions showing up in the systems logfiles?
Try running the bin/check_perms scripts to check that your files and directories have the right permissions.
Alternatively, login to your Mailman server, change to the mailman directory and try something like:
ls -lR | grep -v MAILMAN-UNAME | less
replacing MAILMAN-UNAME with your Mailman username (probably 'mailman' but not guaranteed).
Check an eye open for any files that have ended up in there that are not owned by your mailman software.
Good luck, Steff
Luke Tymowski wrote:
Locks are not relevant to this issue as Mailman never sees the attempted posts.
The only files in /var/lib/mailman/locks are master-qrunner and master-qrunner.mailman.2502 (The dates on those two files are more than 24 hours into the future - is that normal?)
Yes, the timestamps on the master-qrunner locks are in the future. That is the time at which the lock expires.
The /var/lib/mailman/data/aliases shows the relevant aliases for that particular list.
And has the /var/lib/mailman/data/aliases.db file been updated since those aliases were added?
In fact does Postfix even use those aliases?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hello,
And has the /var/lib/mailman/data/aliases.db file been updated since those aliases were added?
What confused me was that these are all lists that have been around for the last 6-7 years.
I moved the lists to a new server 2 weeks ago. Most of the lists worked just fine.
So, yes, the aliases.db exists and was regenerated when I moved the lists to the new server.
In fact does Postfix even use those aliases?
Well, most of the lists worked, but some didn't. I'd think if Postfix didn't know about those aliases, none of the lists would work (it's the only place where the list handlers are kept).
I fixed the issue by editing /etc/mailman/mm_cfg and changing: MTA=none to MTA='Postfix'
Then running /var/lib/mailman/bin/genaliases
Mailman/Postfix were installed from apt-get.
Luke
Luke Tymowski wrote:
So there was some problem with the aliases. Either they weren't in /var/lib/mailman/data/aliases or /var/lib/mailman/data/aliases.db was not properly synced with /var/lib/mailman/data/aliases, because, assuming virtual mappings are not involved, that's the only thing that would be affected by the things above.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
So Mailman on the new server has been installed using apt-get.
Then you moved your list files/directories from the old server to the new server?
My Sysadmin-sense[tm] is tingling. I get the feeling that either the permissions of some of the files/directories are not correct or, and this is a biggie when moving servers, the "ownership" of those files/directories may no longer be correct.
Are there any warnings about access permissions showing up in the systems logfiles?
Try running the bin/check_perms scripts to check that your files and directories have the right permissions.
Alternatively, login to your Mailman server, change to the mailman directory and try something like:
ls -lR | grep -v MAILMAN-UNAME | less
replacing MAILMAN-UNAME with your Mailman username (probably 'mailman' but not guaranteed).
Check an eye open for any files that have ended up in there that are not owned by your mailman software.
Good luck, Steff
participants (3)
-
Luke Tymowski -
Mark Sapiro -
Steff Watkins