List Distribution Sequence Confusion
I am having a problem when mailman (2.1.9) tries to distribute mail. My main problem is that I do not understand what it is doing. I do not have a static IP and I have to relay outgoing mail through my ISP's server. Thus there was a lot of fudging of the configuration to make it work thanks to help from this list. When I try to send mail to a list it seems to be trying to mail it to listname-bounces@fakehost.mydomain.com. As result I get this this message from my ISP's server, not unexpectedly:
550 [PERMFAIL] destination not valid within DNS (in reply to RCPT TO command))
I don't understand why it is sending mail there instead of to the members of the list. What am I doing wrong?
FWIW, this was a working system prior to upgrading my Mandriva OS to 2008.1 so lots of things were changed. I can't say what specifically so this is almost like starting from scratch even though I copied all the config files from the working system.
Thanks.
Dennis Putnam wrote:
Mailman is not sending mail to that address (SMTP RCPT TO). Mailman is sending mail with an envelope from that address (SMTP MAIL FROM). This is so bounced mail will be returned to that address for automated bounce processing.
We need more detail. What is the failing address?. are you saying that "fakehost" is the problem? If that is not in the list's host_name attribute, it is being added outside of Mailman.
Is Mailman delivering directly to the ISPs MTA (SMTPHOST in mm_cfg.py) or is it delivering to a local MTA which is relaying to the ISP's MTA.
It is possible that the ISP requires a valid domain in the MAIL FROM address and doesn't complain until the RCPT TO.
If your Python is 2.4 or later, see the FAQ at <http://wiki.list.org/x/-IA9> for a way to enable low level SMTP debugging and see the actual SMTP messages in Mailman's error log.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
I have more information on this that explains why I was confused about the sequence of events for processing mail to a list. It is not going to listname-bounces but rather going to mailman-bounces. The message is addressed to listname@mydomain.com but winds up going to mailman@mydomain.com instead. Why is the wrong list processing the incoming mail? How do I debug this? TIA.
Dennis Putnam wrote:
Dennis Putnam wrote:
How does incoming mail get to Mailman? Are you using something like DynDNS to route incoming mail to an MTA on your box? If so, look in the MTA's logs to see what it says about the misdirected message.
If not, what MTA(s), Aliases, fetchmail, procmail recipes, etc. are involved?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Dennis Putnam wrote:
Mailman is not sending mail to that address (SMTP RCPT TO). Mailman is sending mail with an envelope from that address (SMTP MAIL FROM). This is so bounced mail will be returned to that address for automated bounce processing.
We need more detail. What is the failing address?. are you saying that "fakehost" is the problem? If that is not in the list's host_name attribute, it is being added outside of Mailman.
Is Mailman delivering directly to the ISPs MTA (SMTPHOST in mm_cfg.py) or is it delivering to a local MTA which is relaying to the ISP's MTA.
It is possible that the ISP requires a valid domain in the MAIL FROM address and doesn't complain until the RCPT TO.
If your Python is 2.4 or later, see the FAQ at <http://wiki.list.org/x/-IA9> for a way to enable low level SMTP debugging and see the actual SMTP messages in Mailman's error log.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
I have more information on this that explains why I was confused about the sequence of events for processing mail to a list. It is not going to listname-bounces but rather going to mailman-bounces. The message is addressed to listname@mydomain.com but winds up going to mailman@mydomain.com instead. Why is the wrong list processing the incoming mail? How do I debug this? TIA.
Dennis Putnam wrote:
Dennis Putnam wrote:
How does incoming mail get to Mailman? Are you using something like DynDNS to route incoming mail to an MTA on your box? If so, look in the MTA's logs to see what it says about the misdirected message.
If not, what MTA(s), Aliases, fetchmail, procmail recipes, etc. are involved?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Dennis Putnam -
Mark Sapiro