On Tue, Feb 12, 2008 at 02:42:30PM -0800, Jeroen van Aart wrote: > 2008-02-12 14:32:11 1JP3bc-0006qp-7U Remote host mail.electrochem.org > [205.161.180.250] closed connection in response to EHLO g2.atypon.com > 2008-02-12 14:32:11 1JP3bc-0006qp-7U == [EMAIL PROTECTED] > R=dnslookup T=remote_smtp defer (-18): Remote host mail.electrochem.org > [205.161.180.250] closed connection in response to EHLO g2.atypon.com > > I would think that if a server reports itself as "esmtp" it should > understand an ehlo, or am I wrong? Is the remote server at fault? What > should I tell their admin?
Try using a HELO/EHLO name (i.e. helo_data) which doesn't resolve to a private IP address (g2.atypon.com => 10.1.1.2). Ideally of course (RFC1123) your public IP address will have a PTR record giving your hostname, and that hostname will forward-resolve to your IP address, and your helo_data will be that hostname. -- Dave Evans http://djce.org.uk/ http://djce.org.uk/pgpkey
signature.asc
Description: Digital signature
-- ## List details at http://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
