• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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