New blocking measures by MSN/Comcast/Cox

MSN/Comcast/Cox have started blocking the smtp port for all their customers.

This mean that you need to change your outgoing servers to your ISP's smtp server.

[NetPublicist]

I had a client on MSN who found this out after she was no longer able to send email. We found that MSN only allows her to send emails with the @msn.com domain through their SMTP so she couldn't use MSN to send her email at all. She switched to a real ISP and can use her domain's smtp just fine now.

[Allergy]

Here is possible way for Matrix to help customers- open custom port to access to SMTP server.

[admin]

Not sure if we can run 2 ports in Qmail but I can look. Thats kind of a secrity risk for us as we have them locked down kind of tight.

[Allergy]

For example: Pair Networks support it:
http://www.pair.com/pair/support/lib...mail/smtp.html

Most hosting companies will not open a custom port for SMTP for numerous reasons, one of them security.

[Allergy]

If your SMTP port 25 is enough secured - you may apply the same securety rules to second port.
The only one reason i may se so far - it is more work for SMTP server - because more customer will start use it.

Allergy, also there can be conflicts with ISPs, some include wording in their TOS like "not authorized to circumvent our security measures" and they consider blocking SMTP a security measure, but, not sure how it would be enforced, I don't believe any ISP or web host has tested it yet.

[cleonard]

Hey Hostnet,

Just to make sure I have this correct. If my customers are using MSN/Comcast/Cox as their ISP. Then they cannot utilize mail.theirdomain.com as their SMTP server. They have to send any mail from their hosted accounts like mailbox me@theirdomain.com using their ISP's SMTP?

Just want to make sure I have it down right before I tell them.

Thanks so much

Chris

[mresell]

I think custom smtp port is worth considering. Obviously you need to look at risk. If you can secure 1 port, you can secure 1 more. From a legal standpoint(not a lawyer), I donot see this as being a way around their security. This would only work with your service, if it worked at all. ISP's are getting too much control like the phone companies are getting all over again. Tho, I sympathize with their SPAM problems. I use Comcast in richmond, va and I can tell you that I have not had a problem....YET! I checked comcast info and couldnot find a statement regarding this.

With the exception of MSN, Cox and Comcast I believe have some "regional" office/headquarters that might make some policy on their own, that might be the reason for the difference, and if it is, I say hurray for them!

[jmbeach]

Originally posted by cleonard
Hey Hostnet,

Just to make sure I have this correct. If my customers are using MSN/Comcast/Cox as their ISP. Then they cannot utilize mail.theirdomain.com as their SMTP server. They have to send any mail from their hosted accounts like mailbox me@theirdomain.com using their ISP's SMTP?

Just want to make sure I have it down right before I tell them.

Thanks so much

Chris

Locally, San Diego, I have a couple of clients that had to switch over to Cox's SMTP server in the past several days. I tried the authentication - pop before smtp - as was suggested, but this didn't work for them. Only changing the SMTP settings did the trick.

Bummer that Cox didn't at least announce the change, as I can only imagine how many will be affected by this.

Anyhow, that's my experience with Cox

[mresell]

It could change here at anytime...who knows. NONE of these ISP's let people know this when it happens which puts you in a bad position. Why should you be the one telling them this. As a tech I can't tell you how many times people look at you like your a "liar" or "crazy" when you have to tell them things like that. They think you have conspiracy theories or something, LoL. You know what they say... Just because you are paranoid doesn't mean someone isn't out to get you!

mrseller, I experienced that first hand here on the forums, but it all worked out great in the end (well except they had to use Cox SMTP)