• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx

  • We are developing a new feature in Plesk that will help you promote your websites or business on social media. We want to conduct a one-hour online UX test to present the prototype and collect feedback. If you are interested in the feature, please book a meeting via this link.
    Thank you in advance!
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Question SmartHost Configurations via API and not a Port

nmdpa3

Basic Pleskian
Server operating system version
Ubuntu 24.04
Plesk version and microupdate number
18.0.65 #2
Looking to try the new smarthost option in Plesk and noticed it only accepts connections to the relay service by port number. Many relay services will accept the mail to be sent via an API.

Will there be support going forward for using port or api connection when configuring the relay service used with a Plesk smarhost configuration?
 
Many relay services will accept the mail to be sent via an API.
Could you please specify the exact mail services you are interested in? Do they accept emails only by API and do not accept them via standard mail protocols?

Mail protocols ("via a port") are standardized. As far as I know, sending mail "via API" is not standardized; each vendor implements it in its own way. This means it is impossible to start supporting all mail gateways simultaneously; every time, it is a custom development.
 
mailgun has an option to use an API, which they indicate is faster and more efficient than using SMTP. Additionally, this eliminates the need when using cloud services like AWS or Digital Ocean to unblock outbound mail ports, which they block by default. Fortunately mailgun allows the SMTP connection on 2525, however the API option caught my attention as an even better option.
 
Back
Top