Question Force same domain emails to use MX records

[jenjohn]

Server operating system version

Ubuntu 22.04..4

Plesk version and microupdate number

18.0.63 Update #4

I have setup MX records to use both Google SMTP server [1st priority] and Plesk Mail Server. I have a few email accounts that use Google Workspace and a quite a few other email accounts that use Plesk Mail server. The setup works perfectly - email sent to the user at Google SMTP server is received. Other email accounts are able to use Plesk email server to receive and send emails.

However, biggest caveat is when a Plesk email server user sends to a Google SMTP server user, it does NOT go to Google SMTP server. It is received locally i.e. Plesk does not lookup MX records to recognize that this should be sent to Google SMTP server.

Is there a setting where you can force Plesk to lookup MX records everytime irrespective of sender/receiver being in the same domain?

 

[Martin Dias]

https://support.plesk.com/hc/en-us/articles/12377846922775-Emails-sent-to-a-domain-with-external-mail-service-are-delivered-locally-to-the-Plesk-server

 

[jenjohn]

I tried that but it disabled ALL emails to Plesk email accounts. Please note that I have email accounts in Plesk AND in Google Workspace/Gmail. I cannot disable Plesk email completely, they are live accounts. I will need Plesk to check MX records even if I am sending to the same domain.

 

[Martin Dias]

This would be per domain, or do you have some domain with mailboxes on both sides?

 

[jenjohn]

Yes, I have a domain that has some mailboxes in Plesk and some in Google. So, cannot really disable emails in Plesk.

 

[Kaspar]

This use case is currently not supported by Plesk. When the email service is enabled for a domain in Plesk, email is always delivered locally rather than routed externally via MX records.

 

[jenjohn]

Ok. Thx. will submit as a feedback.

 

[kokobine]

Unbelievable i cant believe there is no solution for this

 

[Raul A.]

Unfortunately, this is how the mail service works.

The email addresses should be created on only one system. Each system considers all the email addresses to be hosted on that system.

You could use a subdomain with Google mail and configure the Golgle hosted addresses to check/use the corresponding Plesk hosted email addresses.

 

[jenjohn]

This feature request should be considered by Plesk. It doesn't make sense to pay Google for 25 email accounts when only 2 or 3 actually need the Google Workspace features. Google themselves encourage this split delivery feature...

Send email to two email systems with split delivery - Google Workspace Admin Help

As an administrator, you can customize how email is routed and stored to meet your organization's requirements. Gmail split delivery lets you deliver incoming email messages to 2 different email syst

support.google.com

Raul, can you give more details on your approach? TIA.

 

[jenjohn]

This is also causing another unintended effect. The gmail users have created an alias and some groups. Unfortunately, the email users in the local server CANNOT send to these alias and groups because local email server FIRST checks the existence of alias/groups and it cannot find it and throws an error. All of this can be avoided if Plesk follows its own rules - use MX records to route the email instead of sending it internally first!!

 

[ChristophRo]

Plesk follows its own rules - use MX records to route the email instead of sending it internally first!

Nobody and nothing does and should ever prioritize email routing based on MX over local authority!
That would break all rules and regulation regarding email delivery.

"split" domain scenarios can be achieved with manual re-routing rules for unknown addresses (i.e. "catchall" box) or the use of subdomains.
But then again, you may get this up and running, just to then get f**ked over by DKIM and DMARC