After getting sick of dealing with this (I run my own few machines for personal/professional use, and travel a lot consulting with small businesses, who frequently use retarded consumer-grade bandwidth), I just started using ssh port forwarding on a nonstandard port.

But try explaining this to someone who doesn’t geek about for a living.

Without taking a stand on the whole NN thing (which is really meaningless, without defining terms), filtering and/or monitoring my traffic based on port numbers is evil. It may make the pointy hairs happy. It may be that from a pure utility perspective, it cuts down on spam, or P2P, or whatever the current evil is. But if I want to spam from a client site or a hotel network, you’re not going to stop me, at least that way. (Note: I don’t want to.) It just drives an arms race, complicates networks, confuses consumers, and makes everyone’s life hell.

I’m also aware of at least one, non-US, residential DSL ISP which was (and still is, to the best of my knowledge) spoofing port 25 in the same way.

So far, I haven’t come across any bit-pusher that has attempted to block port 587, and I only use SSL/TLS over that anyway. I also have access to a SMTP server with a custom port.

I’m also aware of at least one, non-US, residential DSL ISP which was (and still is, to the best of my knowledge) spoofing port 25 in the same way.

So far, I haven’t come across any bit-pusher that has attempted to block port 587, and I only use SSL/TLS over that anyway. I also have access to a SMTP server with a custom port.

A good ISP will support sending mail on the submission port (587), using SMTP AUTH. If you configure your mail clients this way, then you should be able to send mail without reconfiguring, regardless of what WiFi system you’re using.

http://wiki.dreamhost.com/KB_/Email/_POP3/IMAP/SMTP_Servers#Does_my_ISP_block_port_25.3F

Cheers.

Chuck