Folks
You may recall over the weekend I was lamenting the fact that my lists are getting spammed with with replies going back to somewhere (and being determined as spam by some of the over zealous spam detectors).
So Paul Tomblin, suggested setting the system to discard the messages, and for the most part that really did the trick..
Well, I am still getting some more, and I know why and hence this question and comments
I used to run 3 of the lists on a separate RH 7.3 box that also hosted another sub-domained system connecting via UUCP Yep UUCP
And that system was getting some much spam that I moved the mailling lists to my main system and a new virtual hosted domain And subsequently moved the offending spam related subdomained system to my main system. (So that is has to macch a user name in liue of just passing thru the system) With me so far ?? I am not.
The lists that are getting the bogus messages have new domain names, but spammers are sending spam to the lists using the old domain. And hence failing.
The list name that I am tinkering with is rrdiana@railnet.org, but it used to be rrdiana@nshore.org, railnet.org and nshore.org are now virtual hosted on my system.
So, is this "legal" in the sense of Mailman on the "General options page
Example host_name (general): Host name this list prefers for email. Railnet.org
To also add nshore.org so that both valid domain names are there.
host_name (general): Host name this list prefers for email. Railnet.org, nshore.org
Rrdiana.railnet.org is valid, but rrdiana.nshore.org is also valid to a point, but.. ???
THANKS
Dave
-- Dave Foran Internet ONLY: dave@hamnet.org
Cruise Missile Coordinates 41.36.46N 81.25.53W
Quoting Dave Foran (dave@hamnet.org):
When I moved my lists from my home machine (xcski.com) to a virtual private server (list.xcski.com), I used postfix's "/etc/postfix/relocated" to cause requests for the old list names to bounce with a message giving the new list names. Spammers never read those bounce messages, but real people might. You could use that to make sure if people are requesting the old list address that they get told of the new list address.
Or if you just want the list to be available at both locations, I imagine you could just make your own entries in the aliases file (the main one, not the one mailman manages) for the old location.
-- Paul Tomblin <ptomblin@xcski.com> http://blog.xcski.com/ "The ideals we uphold during a crisis define who we are." - Bruce Scheier http://www.schneier.com/crypto-gram-0109.html
Quoting Dave Foran (dave@hamnet.org):
When I moved my lists from my home machine (xcski.com) to a virtual private server (list.xcski.com), I used postfix's "/etc/postfix/relocated"
Hmm Wonder if an option like this is available in sendmail..
The users have the correct domain names, Tis the spammers still using the
to cause requests for the old list names to bounce with a message giving the new list names. Spammers never read those bounce messages, but real people might. You could use that to make sure if people are requesting the old list address that they get told of the new list address. old name
Or if you just want the list to be available at both locations, I imagine you could just make your own entries in the aliases file (the main one, not the one mailman manages) for the old location.
Something tinker with..
Dave
-- Paul Tomblin <ptomblin@xcski.com> http://blog.xcski.com/ "The ideals we uphold during a crisis define who we are." - Bruce Scheier http://www.schneier.com/crypto-gram-0109.html
Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/dave%40hamnet.org
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Dave Foran wrote:
I didn't see this answered in the other replies in this thread.
No it is not legal. It needs to be a single host name which is the name which will be exposed in email addresses generated by mailman. I.e., Mailman will advertise the list posting address as listname@host_name, the request address as listname-request@host_name, etc, so it should be the single host name you prefer to use for the list.
Mailman also sends certain owner notices to listname-owner@host_name, and it expects to receive those back as messages for the 'owner' which it resends to the actual owners and moderators. Thus, host_name must also be a host that the outgoing MTA knows how to route back to Mailman.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Quoting Dave Foran (dave@hamnet.org):
When I moved my lists from my home machine (xcski.com) to a virtual private server (list.xcski.com), I used postfix's "/etc/postfix/relocated" to cause requests for the old list names to bounce with a message giving the new list names. Spammers never read those bounce messages, but real people might. You could use that to make sure if people are requesting the old list address that they get told of the new list address.
Or if you just want the list to be available at both locations, I imagine you could just make your own entries in the aliases file (the main one, not the one mailman manages) for the old location.
-- Paul Tomblin <ptomblin@xcski.com> http://blog.xcski.com/ "The ideals we uphold during a crisis define who we are." - Bruce Scheier http://www.schneier.com/crypto-gram-0109.html
Quoting Dave Foran (dave@hamnet.org):
When I moved my lists from my home machine (xcski.com) to a virtual private server (list.xcski.com), I used postfix's "/etc/postfix/relocated"
Hmm Wonder if an option like this is available in sendmail..
The users have the correct domain names, Tis the spammers still using the
to cause requests for the old list names to bounce with a message giving the new list names. Spammers never read those bounce messages, but real people might. You could use that to make sure if people are requesting the old list address that they get told of the new list address. old name
Or if you just want the list to be available at both locations, I imagine you could just make your own entries in the aliases file (the main one, not the one mailman manages) for the old location.
Something tinker with..
Dave
-- Paul Tomblin <ptomblin@xcski.com> http://blog.xcski.com/ "The ideals we uphold during a crisis define who we are." - Bruce Scheier http://www.schneier.com/crypto-gram-0109.html
Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/dave%40hamnet.org
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Dave Foran wrote:
I didn't see this answered in the other replies in this thread.
No it is not legal. It needs to be a single host name which is the name which will be exposed in email addresses generated by mailman. I.e., Mailman will advertise the list posting address as listname@host_name, the request address as listname-request@host_name, etc, so it should be the single host name you prefer to use for the list.
Mailman also sends certain owner notices to listname-owner@host_name, and it expects to receive those back as messages for the 'owner' which it resends to the actual owners and moderators. Thus, host_name must also be a host that the outgoing MTA knows how to route back to Mailman.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Dave Foran -
Mark Sapiro -
Paul Tomblin