comcast blocking smtp25

[Jack Coats]

I found at one time many rejections were because there was not the proper 
reverse DNS entry made so when a message is sent the senders domain needs to 
match the IP address it was sent from.  And yes, this lookup really happens 
on the receiving side, not the sending side.

-- 
*NIX is User Friendly ... It is just picky about who its friends are!

---------- Original Message -----------
From: Jerry Feldman <gaf at blu.org>
To: discuss at blu.org
Sent: Fri, 15 Jul 2005 06:38:27 -0400
Subject: Re: comcast blocking smtp25

> --Signature_Fri__15_Jul_2005_06_38_27_-0400_mDFycIe2zDqEE4.q
> Content-Type: text/plain; charset=US-ASCII
> Content-Transfer-Encoding: quoted-printable
> 
> On Thu, 14 Jul 2005 23:48:09 -0400
> David Hummel <dhml at comcast.net> wrote:
> 
> > Right, starting with the whole AOL fiasco a while back.  Nonetheless,
> > Comcast does selectively block SMTP out, which is even worse.  I don't
> > see any reason not to use the smart host, which solves both problems.
> It's not that comcast blocks port 25, it does not, many recipients,
> such as AOL will reject Comcast dynaic addresses causing you to use
> another SMTP host.
> 
> --=20
> Jerry Feldman <gaf at blu.org>
> Boston Linux and Unix user group
> http://www.blu.org PGP key id:C5061EA9
> PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
> 
> --Signature_Fri__15_Jul_2005_06_38_27_-0400_mDFycIe2zDqEE4.q
> Content-Type: application/pgp-signature
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.0 (GNU/Linux)
> 
> iD8DBQFC15Ij+wA+1cUGHqkRAjJLAJsEwdXfSOWB1xZn+5uV7EuEOsy6JACfTUXu
> HH08JRSh+GvpGjf7GAy/4jg=
> =tFO0
> -----END PGP SIGNATURE-----
> 
> --Signature_Fri__15_Jul_2005_06_38_27_-0400_mDFycIe2zDqEE4.q--
------- End of Original Message -------