I am not a networking expert. If they are blocking smtp as a protocol - dont know. If they are blocking inbound/outbound traffic to/form port 25 - simply changing the port may work. You may also try to use ssmtp ( smtp over ssl ) which uses port 465 , not 25. If you do ssmtp over a nonstandard port I don't think your ISP can stop you in any way. Since the communication is encrypted they can't really know if it smtp or just some random encrypted stream of data.
On Thu, 2005-01-20 at 05:52 +0000, Nick Smith wrote: > my ISP just started blocking smtp from any domain not theirs, as per a > supervisor @ comcast they are blocking all mail sent from their clients > that are running a mail server and their outgoing email address is not a > comcast.net address, they say this keeps the spam down. ha. as you can > see they haven't shut me down as of yet, but they did shut down one of > my clients a legit non-profit organization, we are having to look into > alternate methods to get their email out asap. my question is, is there > any way around this? i don't think just changing the ports could work. > the way we had it set up before was that the smtp address was just > relaying through smtp.comcast.net, that is what they are blocking, they > can receive mail fine but anything they send is blocked and it doesn't > come back to them either as not recieved. am i just screwed and stuck > with another "feature" of comcast? i swear if there was ANYTHING else as > fast around here for the same price i would switch, they keep getting > worse and worse. > > any info would be appreciated thanks. > > nick > > > -- > [email protected] mailing list > > -- [email protected] mailing list
