• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

SMTP authentication for 3rd party domains

K

kuhle

Guest
I have a customer whose domain is not currently hosted by us. They have to change their outgoing SMTP server address when they want to send emails from other places as they travel.

I would like to be able to offer them SMTP authentication if that is possible. Could I set up a sub-domain (e.g. relay.mydomain.com), set up an email address with any username and password and give this to them to use in the settings for "My Server Requires Authentication"?

Grateful for any view on how best this could be done.
 
Thank you for this response. Our servers are set up to carry out authentication for both POP3 and SMTP. We would not change this server-wide.

It would seem that a sub-domain would be the obvious way to achieve this, creating a single mail account with a username/password that will be used for SMTP authentication, and each user will have to put these details on their mail settings.

If everybody is given the same one then there is the problem about it being given to "undesirables". Otherwise, each person would have to be given their own one.
 
Well yes. You could set up a subdomain as a domain from plesk, create that mailname and you are good to go for sending.

If you make a proper dns set-up you can even recieve mails and later these can be synced with the "real" email from webmails fetch-mail.

Anyway this setup seems a bit strange and does not permit a good mail flow-- my opinion.
 
I TOTALLY agree with you regarding it not permitting a good mail flow. However, without this (and while keeping SMTP authentication), I can see little other option if we want to offer customers the SMTP authentication when they are not hosting their domain with us. I guess the answer is "swap host to us!!".
 
Back
Top