Spam to "mailmain" list oddity
Mailman version 2.1.8
I administer mailman on a few domains, and on one I receive a lot of spam seemingly sent to the mailman@ list. I can work on my spam filters, but I'm trying to understand the path the mail is taking through mailman.
The mailman@ list has only me as the admin and NO members.
I have just a handful of lists on this machine: users@, dev@, svn@, etc.
When mail is sent to mailman@ I get a message with the following headers:
Return-path: mailman-bounces@
Envelope-to: <my email address>
X-Original-To: mailman@
Delivered-To: users-owner@The body of the message is simply the sender's body only -- it's not a mailman-generated message (e.g. approval message).
In my sender filters I have:
generic_nonmember_action: holdMy question is why is mail to mailmain@ seemingly getting delivered to users-owner@?
Another thing I'm finding curious: I have RFC2369 headers enabled on all lists (including the "mailman" site list). And indeed messages on the other (e.g. users@) lists include these headers. But mail sent to mailman@ does not include these headers. Why is that? Because List-Post, List-Subscribe, etc. have no uses for the mailman list?
-- Bill Moseley moseley@hank.org Sent from my iMutt
Bill Moseley wrote:
Mailman version 2.1.8
I administer mailman on a few domains, and on one I receive a lot of spam seemingly sent to the mailman@ list. I can work on my spam filters, but I'm trying to understand the path the mail is taking through mailman.
The mailman@ list has only me as the admin and NO members.
Then posts to the list won't be delivered to anyone.
I have just a handful of lists on this machine: users@, dev@, svn@, etc.
When mail is sent to mailman@ I get a message with the following headers:
Return-path: mailman-bounces@ Envelope-to: <my email address> X-Original-To: mailman@ Delivered-To: users-owner@
The body of the message is simply the sender's body only -- it's not a mailman-generated message (e.g. approval message).
In my sender filters I have:
generic_nonmember_action: hold
My question is why is mail to mailmain@ seemingly getting delivered to users-owner@?
My first guess, assuming you've verified the above by actually sending your own message to mailman@..., is that your MTA aliases or whatever are piping mail sent to mailman@... to
"/path/to/mail/mailman owner users"
instead of
"/path/to/mail/mailman post mailman"
Another thing I'm finding curious: I have RFC2369 headers enabled on all lists (including the "mailman" site list). And indeed messages on the other (e.g. users@) lists include these headers. But mail sent to mailman@ does not include these headers. Why is that? Because List-Post, List-Subscribe, etc. have no uses for the mailman list?
The List-* headers are included in mail actually delivered from the mailman list unless the list attribute include_rfc2369_headers is set to No as is also the case for other lists. So if include_rfc2369_headers is set to Yes for the mailman list, this is additional evidence that the mail is not coming from the list.
What do you see in Mailman's 'post' and 'smtp' logs for one of these messages?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro wrote:
Bill Moseley wrote:
My question is why is mail to mailmain@ seemingly getting delivered to users-owner@?
My first guess, assuming you've verified the above by actually sending your own message to mailman@..., is that your MTA aliases or whatever are piping mail sent to mailman@... to
"/path/to/mail/mailman owner users"
instead of
"/path/to/mail/mailman post mailman"
Actually, that specific alias wouldn't account for the (Postfix ?)
Delivered-To: users-owner@
header, but I still think it is some alias or whatever in the MTA that is redirecting the mail from mailman@... to users-owner@...
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Mon, Oct 27, 2008 at 02:25:41PM -0700, Mark Sapiro wrote:
Actually, that specific alias wouldn't account for the (Postfix ?)
Delivered-To: users-owner@
Perhaps, I'm an Exim user not Postfix, so not familiar with it. The alias file was delivering the mail to users-owner@ so it would make sense, though.
Removing the alias did resolve my issue. But once I removed the alias I had a ton of mail in "defer" status in the mailmain list. So, I ended up with more junk! I set the "mailman" list to discard all non-member postings (which is everything).
I hope that doesn't break anything? I can never remember what exactly IS the purpose of that "mailman" list, anyway. What's it used for?
-- Bill Moseley moseley@hank.org Sent from my iMutt
Bill Moseley wrote:
I hope that doesn't break anything? I can never remember what exactly IS the purpose of that "mailman" list, anyway. What's it used for?
See FAQ 4.25 at <http://wiki.list.org/pages/viewpage.action?pageId=4030591>.
-- Brad Knowles <brad@shub-internet.org> LinkedIn Profile: <http://tinyurl.com/y8kpxu>
On Mon, Oct 27, 2008 at 02:10:40PM -0700, Mark Sapiro wrote:
My question is why is mail to mailmain@ seemingly getting delivered to users-owner@?
My first guess, assuming you've verified the above by actually sending your own message to mailman@..., is that your MTA aliases or whatever are piping mail sent to mailman@... to
"/path/to/mail/mailman owner users"
Nice guess. And it's worse than that.
And this also explains why the List-* headers are not added to the email as well. /etc/aliases includes:
mailman: users-owner@<list domain>It's not even hitting mailman.
Postfix is used on that machine and it has two alias files:
alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliasesso it's matching in /etc/aliases first.
Why that's in /etc/aliase I'm not sure. Have to track that down.
Thanks for pointing me in the right direction.
-- Bill Moseley moseley@hank.org Sent from my iMutt
participants (3)
-
Bill Moseley -
Brad Knowles -
Mark Sapiro