

And if blocking port 587 is breaking a type of standard, then perhaps I should have it open.

I like to stay as standards compliant as I can, within reason. I'm just really interested to see other people's take of this. Apparently it is just a message submission port, and can be used just like regular port 25 acceptance. 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.
I thought port 587 was used for message submission, which required some form of SMTP authentication to accept mail. When I originally read the RFC, that's what I thought was suppose to happen. If port 587 is suppose to be opened, is there a way to enforce some type of authentication on this port. To my knowledge, port 26 does not have any standards in place in regards to sending mail. 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. 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. Using your ISP's outgoing mail server does not offer any negative side-effects and its less traffic going through our servers. I actually consider this to be a more ideal set up. 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 know a lot of ISPs are starting to block access for their customers to remote port 25 SMTP servers. The main reason I ask, is because I do not have port 587 open on any of our servers. Is that correct? If so, I'm somewhat puzzled, what advantage does this cause? So instead of using port 25, your using port 587? Perhaps I am reading this wrong, but it seems to me that you are suppose to be using port 587 for connecting to your outgoing mail server to send out mail, and then mail servers use port 25 to talk back and forth to each other. I'm wondering how many people have their e-mail systems set up to accept SMTP connections on port 587. I did some searches, and found this mentioned, but never really fully discussed. Hope this helps someone with the same problem which i faced.Forgive me if this has been discussed before. Back in the shell type sudo vi /etc/postfix/sasl_passwd and enter the following (substitute your gmail address and gmail password): :587 press :wq to save and quit the file, and run the following command sudo postmap /etc/postfix/sasl_passwd Smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd Smtp_tls_session_cache_database = btree:/var/run/smtp_tls_session_cache #smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt In main.cf append this settings relayhost = :587
SURGEMAIL PORT 587 PASSWORD
you need to configure Postfix to use Gmail as a relay hostĪ) Open MAMP and in postfix change the domain of outgoing mail to ī) open terminal and type sudo vi /etc/postfix/main.cf this will ask for your admin password enter it and it will open main.cf in vi editorĬ) press ctrl+f and come to the end of the file and bring the cursor one line down from the end and press a, the editor will now switch to insert mode to edit the file. as OSX uses postfix to send mails and if you plan to use external smtp server like which i used here is what you should be doing. You see it is still trying to connect via port 25? how do i change it in mac?įor those of you using MAMP and not able to send the mail from php mail() function because of port 25 being blocked by ISP (in my case) here is some information for you to solve it. May 6 20:32:25 Ibrahim-Armars-MacBook-Pro postfix/smtp: connect to .:25: Operation timed out
SURGEMAIL PORT 587 UPDATE
UPDATE : i tried changing the settings in php.ini to this Īs i am on mac i don't think this can be the solution for me, and it is not working after i tried.
SURGEMAIL PORT 587 PRO
how do i force php mail function to use port 587 instead of default 25? BTW : i am on OSX 10.6.6 using MAMP PRO My ISP have blocked port 25 for sending mails from PHP, and instead have allowed port 587 or 465 to be used.
