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

Issue Split Domain Name Routing, Hosted Exchange, DMARC

Terence Channon

Terence Channon

New Pleskian
We have a sender, call it @xyzdomain.com and their emails are not getting through to exchange-user@abcdomain.com that are using Hosted Exchange via a split domain name environment. Here is what happens.

1. @xyzdomain.com sends to exchange-user@abcdomain.com
2. Email first gets to linux server
3. Email then gets forwarded to exchange-user@forward.abcdomain.com (this is what we use for the split domain name alias. - So in PLESK we have the user exchange-user@abcdomain.com set to forward to the exchange-user@forward.abcdomain.com
4. The email never gets to the exchange user - there is a 'no signing table match for" error that is generated.

When we send emails to regular-user@abcdomain.com, everything gets through ok.

The 'forward' seems to be messing with the DMARC policy for the sender, @xyzdomain.com. Any ideas on how we can fix this in PLESK? Any configuration suggestions? Questions about the set-up? Is this a potential bug in PLESK and how it sends out emails/forwards?

FYI - emails sent from @yahoo, @aol, @gmail for instance are able to get delivered to the end-user/exchange-user box without issue.
 
You must log in or register to reply here.

Similar threads

F
Issue SOGo - emails sent from webmail, both manually created and autoresponder/vacation/out-of-office, are rejected. They miss spf, dkim, dmarc, everything
Replies
1
Views
406
Farfalk
F
A
Issue DKIM and DMARC issue, emails not sending
Replies
4
Views
3K
danami
danami
M
Question DKIM fails with plesk server as relay
Replies
6
Views
2K
m4xp
M
C
Issue DKIM and SPF do not align with RFC5322. Then DMARC result is fail.
Replies
2
Views
3K
cmartinez127
C
mapodec
Resolved Emails sent from Plesk accounts are not delivering only to Google Workspace
Replies
2
Views
688
mapodec
mapodec
Back
Top