smerritt wrote:
TLS and authentication all take place after making the initial connection. If TCP to port 25 is blocked by the ISP, there's nothing any server configuration change can do about it.
Not necessarily. In Mozilla, for instance, you can choose to use an all-SSL connection on port 465. Port 25 is never touched in this case. One of my co-workers uses this to get around port 25 blocking on his Verizon DSL connection and use the company Linode for outgoing mail.
(Edit: OE can also be configured to use SSL as well.)