Please use more commonly supported ports for email

[snow99as]

port 25 is used for email submission to other servers. This isn't the 90s and it shouldn't be used for normal email clients to submit emails. Port 587 and 465 should be used instead for clients to submit emails that need to be sent. I would also like to add Port 25 is normally blocked for security reasons by server providers so expecting every server to be able to send out on port 25 is a security concern. Port 25 should only be opened on the email server

[uhlhosting]

Postal isn't intended to act as a mail submission service for end users like Outlook, Apple Mail, or Thunderbird. It's a transactional MTA designed for applications to send email and to deliver that mail directly to recipient mail servers.

Port 587 (submission) and 465 (submissions over implicit TLS) are intended for mail clients submitting messages to an MSA, whereas SMTP delivery between MTAs is standardized on port 25. If Postal couldn't send outbound mail on port 25, it wouldn't be able to deliver email to the vast majority of recipient domains.

You're absolutely right that many cloud providers block outbound port 25 by default to reduce spam. That's an infrastructure policy rather than an SMTP protocol issue. The usual solutions are:

• Request port 25 to be unblocked by the provider.
• Use a provider that allows outbound SMTP.
• Relay outbound mail through a smart host or SMTP relay if direct delivery isn't possible.

Supporting ports 587/465 for inbound message submission (for authenticated clients or applications) could certainly be a useful feature, but it wouldn't replace the need for outbound delivery over port 25.

[snow99as]

@uhlhosting You completely ignored what I said. Port 587 and 465 are used to send mail from an application. Postal is to be used for programmic sending from my understanding. Why are we using port 25 for apps to be sending over to postal. We should be using 587 and 465 for normal mail submission to have postal then send it out to other email servers over port 25. For example if I'm hosting my app on Digitalocean they won't open up port 25 ever and they'll redirect you to use a service like mailgun. If postal is supposed to work like programmic email providers like Mailgun why aren't we using the same standard ports like they use for apps to send mail through them. This would allow postal to be used like any other programmic email provider. Also expecting port 25 To be open on every server for an app to just use postal for sending out emails is bad security practice port 25 should only be open on the email server not the app server wanting to utilize postal

[uhlhosting]

@snow-of-the-mountain I can say the same if my explanation made you write all that gibberish you did now, I am not reading it! Enjoy!

[snow99as]

@uhlhosting Let me dumb it down so you can understand since clearly reading is hard for you

Port 25 is for email server to email server communication not for app to email server communication. This isn't the 80s anymore we shouldn't be using it as the standard email submission for apps. Should really be left for server to server communication

Port 465 and 587 is better suited for apps to submit emails to the email server so it can be sent out Is that better for you to understand or are you gonna continue to be an asshole?

Mailgun uses 465 and 587. Zeptomail uses the same ports and the list goes on.....

[uhlhosting]

Read my message again then! And do not push your limits! No one used any holes here, you keep your opinions when thats the best you got to! What I wrote is not disproving your point, yet guess you do not get plain English or you just ignorant by design. I end with this comment this sharade that will lead nowhere and is not needed. You do you!

[snow99as]

Clearly reading is hard for you. You make a thing to be like zeptomail and mailgun but refuse to use standard ports like them.... My time is wasted. Have fun with your shitty email server that can only use port 25 and can't be used with apps like Pterodactyl and Bitwarden