• 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!
  • 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.

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