On 5/14/2011 4:01 AM, Ralf Hildebrandt wrote: > I can connect to you mailserver: > > # telnet mail.kasdivi.com 25 > Trying 209.160.65.133... > Connected to mail.kasdivi.com. > Escape character is '^]'. > 220 tuna.theoceanwindow-bv.com
Same here, from my Postfix host at 65.41.216.221: ~$ telnet mail.kasdivi.com 25 Trying 209.160.65.133... Connected to mail.kasdivi.com. Escape character is '^]'. 220 tuna.theoceanwindow-bv.com Now, this is interesting: ~$ host mail.kasdivi.com mail.kasdivi.com has address 209.160.65.133 ~$ host tuna.theoceanwindow-bv.com tuna.theoceanwindow-bv.com has address 209.160.68.112 If that banner host name matches the IP in DNS, then connections to your MX are being redirected to another host on a different /24 subnet, 209.160.68.112. Jason, who/what is tuna.theoceanwindow-bv.com/209.160.68.112? It certainly appears connections to your MX are being redirected to 209.160.68.112. What do the logs on the host at 209.160.68.112 tell you about the Gmail connection timeout problem? Would you mind showing us some random log snippets of mail that is successfully delivered to your Postfix server? I'm guessing it is all relayed through the host at 209.160.68.112 to your server, and that the Gmail connections are timing out while hitting 209.160.68.112. Notice that the Gmail error mentions only a hostname, mail.kasdivi.com, NOT an IP address. The Gmail outbound is listing the host it is attempting to connect to. It can't determine if the connection is rerouted to another host or not, which appears to be the case. Thus, the timeout occurs when the server at 209.160.68.112 doesn't respond to the Gmail server, and your server never sees these connection attempts. Please provide some Postfix logging of successful inbound delivery from multiple external domains, such as cloud9.net. This will tell us if (any) of your inbound mail is being rerouted before being relayed to your Postfix MX host. -- Stan
