It appears that the Sourceforge mailing list server apparently tries to connect back to the host or MX for the host listed in the Return-Path header. My network is setup like this: miami -----> santiago (smarthost) -----> Internet Now, miami runs postfix, but it is not accessible from the outside. Now, when I am using mutt on miami, sending a message to the Sourceforge mailing lists generates a reply like this to santiago (which acts as the smarthost) since the Return-Path is set to roberto@miami.connexer.com: Aug 7 20:28:50 santiago postfix/smtp[11711]: 778272403E: to=<courier-imap@lists.sourceforge.net>, relay=externalmx-1.sourceforge.net[12.152.184.25], delay=92, status=deferred (host externalmx-1.sourceforge.net[12.152.184.25] said: 451-could not connect to miami.connexer.com [66.93.22.253]: Connection timed out 451-Could not complete sender verify callout for <roberto@miami.connexer.com>. 451-The mail server(s) for the domain may be temporarily unreachable, or 451-they may be permanently unreachable from this server. In the latter case, 451-you need to change the address or create an MX record for its domain 451-if it is supposed to be generally accessible from the Internet. 451 Talk to your mail administrator for details. (in reply to RCPT TO command)) When I send from thunderbird from any machine, it works as it is connecting directly to santiago. If I use mutt on santiago, it works fine there as well since it is running an instance of Postfix which can be reached from the public internet. My question is this, is my setup broken (mutt/postfix/smarthost) or is sourceforge's setup broken? Regards, -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~roberto
Attachment:
signature.asc
Description: Digital signature