The main reason I ask, is because I do not have port 587 open on any of our servers. I know a lot of ISPs are starting to block access for their customers to remote port 25 SMTP servers. My stance with this has always been that if you are affected by this then you should use your ISP's outgoing mail server or consider this an issue between the affected client and their ISP. I actually consider this to be a more ideal set up. Using your ISP's outgoing mail server does not offer any negative side-effects and its less traffic going through our servers. However, if port 587 is suppose to be open and accept mail, then perhaps users really should be allowed to use this port to send mail from our server.
I am reluctant to open just some arbitrary port, such as port 26, just to allow customers whose ISP is blocking remote SMTP servers to send out mail from our servers. To my knowledge, port 26 does not have any standards in place in regards to sending mail. If port 587 is suppose to be opened, is there a way to enforce some type of authentication on this port. When I originally read the RFC, that's what I thought was suppose to happen. I thought port 587 was used for message submission, which required some form of SMTP authentication to accept mail. I know you can open an additional port for exim to run on on cPanel servers, but this was basically just a copy of port 25. Apparently it is just a message submission port, and can be used just like regular port 25 acceptance. I'm just really interested to see other people's take of this. I like to stay as standards compliant as I can, within reason. And if blocking port 587 is breaking a type of standard, then perhaps I should have it open.
0 kommentar(er)
