RARPSL
join:1999-12-08
Suffern, NY
| said by n2jtx  :I used port 587 myself to get around OOL's port 25 outbound block as I run my own external mail server. The newer versions of sendmail have 587 enabled by default. I am a OOL connectivity user and I feel that they (and most other Outgoing Port25 ISPs) are Hypocrites. I say this since OOL (and I assume the other ISPs blocking outgoing Port25) has a FAQ that explains that this is being done for SPAM Control reasons/etc. They say if you want/need to use some other ISPs SMTP (ie: MSA) Servers to submit your Email, then to find out what Non-Port25 Port that Remote ISP Supports. IOW, because OOL blocks your attempt to connect to the Remote ISP's MSA Servers on Port25 it is, OOL claims, that ISP's responsibility to supply a non-Port25 for use by that ISP's customers when submitting Email to the MSA Server. The Hypocrisy comes into play due to OOL's (and I assume other Outgoing-Port25 Blocking ISPs) refusal to follow their own requirements (when a "Remote" ISP) to support a Non-Port25 Port (such as the aforementioned up-thread 465 [SSL-SMTP] and/or 587 [official MSA] Ports) on THEIR Internet Facing (and LAN) MSA Servers.
IOW: If I am currently connected to ISP2 (which blocks Outgoing Port25) I can not connect to OOL's MSA Servers to send my "From OOL-Address" Email EVEN THOUGH OOL expects ISP2 to accept my "From ISP2-Address" on a non-Port25 Port.
IMO: If an ISP wants to block Outgoing Port25 Connections and require other ISPs to offer some Non-Port25 Port to accept mail submission, then that ISP should comply with this requirement by having a Non-Port25 Port for submission use by their customers on THEIR Servers. |
