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

Email Issue when hosting just MX Record

B

bhelmick

Guest
I have a client who I host a website through my Plesk 8.4 Linux server; I also host their nameserver record and therefore the MX entry. The client uses their own mail server in their office and I provide mail aliases on the primary domain that forward mail to their external domain.

So here's how the setup looks:

Domain A: Local to my server with aliases that point to Domain B
Domain B: Only the DNS is setup through Plesk. Hosting and email are disabled.

Here's the problem:

If someone external to my server sends an email to their domain it hits my box properly, resolves the MX record, and the email is properly directed to their mail server. However, if anyone local to my server sends email (such as myself) Qmail ignores the MX record entirely and attempts to deliver the email locally. The emails languish in the queue for 7 days then bounce back undeliverable.

Does anyone know of a way to force QMail to take the correct action in this situation?
 
MX record

If you get this error for a domain that is hosted on the Plesk server, but has external MX, you have to disable 'Mail' service for this domain. Because it will try to send the mail locally first.

It is also an advice to check the domain name in the MX record whether it is resolvable by your server.
I also added an A record to my zone with the MX domain.

I hope it will help! :)
 
Thanks for the response.

You are correct and I have other domains where that works fine. The problem is that I supply a mail alises on the web hosted domain so I cannot simply disable email.

Domain A has aliases that point to Domain B. Domain B is not on my server, Domain A is.

If I disable mail on Domain A, the alises will also cease to function. Or am I incorrect in that assessment?
 
Back
Top