Now I'll confuse you further. OR maybe not; maybe this will make sense to you.
I setup an account to use postfix to send via 127.0.0.1. I sent a message to myself at my Earthlink address, from a completely different address. It went out...and it came back, delivered to the Earthlink address. Is that because I am on Earthlink? I am going to send another quick Test message to you, Remo, using the postfix account. Let me know in the morning if you have received it or not. The subject will be "Postfix text to Remo". On or near 11/8/03 5:55 PM, Remo Del Bello at [EMAIL PROTECTED] observed: > On 11/8/03 12:43 PM, Allen Watson deftly typed out: > >> What seems odd to me is that, when I set up postfix and set 127.0.0.1 as my >> outgoing mail server, the message DOES go out. It just never comes back (and >> I am sending it to myself). >> >> Is that consistent with the scenario where port 25 is blocked? Wouldn't I >> get an error message, as I do when I try using port 2025? (I realize it is >> highly unlikely that Earthlink has 2025 enabled, but I used that just as a >> test to see what a blocked port would return.) And, if port 25 is not >> blocked, then why is the message being "sent" but never received? Any ideas? > > That is because the postfix mail server you are running locally isn't able > to communicate with anybody except for Entourage on your computer. Here's > the flow of communication in your scenario (I'm assuming in the flow below > that you are sending from an Earthlink address): > > 1. Entourage 127.0.0.1:25 ---> postfix 127.0.0.1:25 > Entourage delivers message to assigned SMTP server. Delivery is > successful because the transmission happens internally. > 2. Postfix ip.assigned.by.ELN:25 ---> mx01.earthlink.net: > Blocked. The mail server you are running locally looks up the MX record > in DNS for the account you are trying to send to and tries to deliver the > message there. Unfortunately, Earthlink's firewall blocks the connection. > 3. Postfix ip.assigned.by.ELN:25 ---> mx01.earthlink.net:25 > Blocked. Your local mail server then tries to deliver a delivery failure > notification to the address that sent the message. But to do so it has to > communicate with Earthlink's MX and therefore fails. > > Running a mail server on Earthlink's network...anywhere on Earthlink's > network...won't work, because at some point the server is going to try to > communicate with a server in the outside world and it will need to do so on > port 25 (Because that is the port everyone else is listening to). The > workaround I mentioned involves running a mail server *outside* of > Earthlink's network that accepts connections on a port other than 25 (i.e. > 2025, or 8025 is popular as well). > > -Remo Del Bello -- Microsoft MVP for Entourage/OE/Word (MVPs are volunteers) Allen Watson <[EMAIL PROTECTED]> Entourage FAQ site: <http://www.entourage.mvps.org/> AppleScripts for Outlook Express and Entourage: <http://members.thinkaccess.net/[EMAIL PROTECTED]/Scripts/> Entourage Help Pages: <http://www.entourage.mvps.org/> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> archives: <http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/> old-archive: <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
