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.
It does keep spam down. Usually the policy is to allow relays from anyone within the ISP network and block outgoing port 25 connection attempts to prevent the abuse of victimized servers. This is generally a good thing.
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.
Changing ports on a remote SMTP server that is outside the ISP domain _would_ work. Are you saying that they do not allow SMTP relay from inside their network?
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 am fairly certain that most ISP policies around email is to allow SMTP relay from _within_ their network. Not allowing _ANY_ SMTP (port 25) outbound connections would be absolutely ridiculous, as no one using comcast services would be able to send email without a bit of indirection. ;)
_k
--
"All movements go too far."
-- Bertrand Russell--
- keith.hassen - - software.engineer - - red.iron.technologies -
"All movements go too far."
-- Bertrand Russell-- [email protected] mailing list
