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

Resolved DKIM issue - Route email from Exchange via Plesk VPS

George Thalassinos

New Pleskian
Hi, I have a Linux VPS which serves 20 some domains and Plesk Onyx to manage it. I have set up DKIM on my VPS which works ok for all but one, which uses an SBS2011 server with Exchange 2010.

They have a problem because Exchange sends emails directly via a smarthost and the IPs of the receiving mail server (on the VPS) and that of the sending mail server (SBS2011) are different. Therefore DKIM fails.

I need to route their emails via my VPS so that they appear as being sent from the DKIM verifiable server.

At the moment I have set up my Plesk as such :
Plesk Onyx 17.8.11
Installed Mail Server : Postfix
Outgoing Mail Mode : Send from Domain IP addresses
Relaying : Authorization Required / SMTP
DKIM : Allow signing outgoing mail

Exchange last attempt was to create a Send Connector as such (without success) :
FQDN this connector will provide in response to HELO or EHLO : remote.domain.gr (resolves to the Exchange static public IP)
Address space : SMTP * 1
Route Mail through the following Smart Hosts : [VPS Public IP]
Basic Authentication : Username = info@domain.gr (TLS not checked), Password = the corresponding Password (verified), Exchange Server Authentication = No, Externally Secured = No

Any ideas as to how to tackle this?
Thanks in advance
 
Actually, the options I included in my question were the ones I tried out last night, so they were not "without success" at the time of writing.

I had tried other options without success the previous days, but this morning I received an email reply from the users of the relevant domain that their emails were being delivered correctly.

Now, if the DKIM reports come back as PASS, the issue will have been resolved. I will post back when they come in.
 
Back
Top