[123393] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Problem from Comcast Network to The Planet

daemon@ATHENA.MIT.EDU (Brian Keefer)
Fri Mar 5 19:24:21 2010

From: Brian Keefer <chort@smtps.net>
In-Reply-To: <9805C6F4-6E91-4F47-9458-2005774D7C87@gmail.com>
Date: Fri, 5 Mar 2010 16:23:49 -0800
To: Zachary Frederick <zcfrederick@gmail.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org


On Mar 5, 2010, at 1:33 PM, Zachary Frederick wrote:

> We have been having a problem emailing to a customer whose server is =
hosted by The Planet (http://www.theplanet.com/). Our mail server is =
hosted in-house on a comcast business connection.
>=20
> IP address of our server is: 173.13.45.23
>=20
> Customers mail server is: 69.93.203.243
>=20

I can get there from Comcast Business

[chort@abydos ~]$ nc  69.93.203.243 25
220 =
**************************************************************************=
******************
ehlo smtps.net
250-securemail.insurancewebsitebuilder.com Hello smtps.net =
[173.11.102.7], pleased to meet you.
250-ENHANCEDSTATUSCODES
250-SIZE
250-XXXA
250-ETRN
250-XXXB
250-DSN
250-CHECKPOINT
250-8BITMIME
250-AUTH CRAM-MD5 PLAIN LOGIN DIGEST-MD5
250-XXXXXXXC
250 XXXD
quit
221 2.0.0 securemail.insurancewebsitebuilder.com closing connection

That's almost certainly a PIX/ASA with fixup enabled (like Jay said).  =
It's been known to cause many interoperability problems.  The solution =
is pretty simple:
no fixup protocol smtp 25

--
bk



home help back first fref pref prev next nref lref last post