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

DomainKeys Identified Mail (DKIM) with different POP3 and SMTP servers

PaulS8

New Pleskian
Hello everybody,

I am using DomainKeys email signing system (under Mail Settings). It works fine if we use the same POP3 and SMTP servers. But if the POP3 server is different, it doesn't sign anything. Obviously the SMTP server is the same one as we set up DomainKeys .

How can I fix it? Are there any settings controlling the signing system and allowing it to sign messages with a different POP3 server?

Pls advise.

Thanks
 
Last edited:
What exactly do you mean by "if the POP3 server is different"?

I mean that when sending emails from Outlook we use different servers:

POP3 server mail.xxx.com.
SMTP server mail.yyy.com --- this is the one we enable the DomainKeys option.

The sender details are as for the POP3, i.e.

Return-Receipt-To: "My Name" <name@xxx.com>
From: "My Name" <name@xxx.com>
 
But if the POP3 server is different, it doesn't sign anything.
Signatures are made at the SMTP level! While the receiving server just decrypts the signature and then verifies the validity of the sender's server ..
 
Signatures are made at the SMTP level! While the receiving server just decrypts the signature and then verifies the validity of the sender's server ..

Yes, this is what I was thinking also, but it seems to be not the case. I am testing two email accounts:

1. SMTP and POP3 are the same server => DomainKeys okey, messages are signed

2. SMTP and POP3 are different. SMTP is the same as (1). Nothing is signed.

Any suggestions?
 
2. SMTP and POP3 are different..
That is a bit confusing ..However, on the assumption in both cases you are using the same SMTP server, then I see no reason why the same SMTP server shouldn't sign again if it signed the first time ...

If you are using different SMTP servers, then make sure both SMTP servers have domain keys enabled on them ...Sorry if I mis-understood your query!
 
That is a bit confusing ..However, on the assumption in both cases you are using the same SMTP server, then I see no reason why the same SMTP server shouldn't sign again if it signed the first time ...

If you are using different SMTP servers, then make sure both SMTP servers have domain keys enabled on them ...Sorry if I mis-understood your query!

The SMTP server is the same for both accounts. One thing I have noticed, but still cannot figure out why it happens. It is using different SMTP IP addresses for a/c (1) and (2). The http://www.mail-tester.com/ shows:

1. 184.107.nn.nnn is authorized to use "myEmail1" - SMTP login email. This is a dedicated IP of the site.

2. 174.142.nn.nnn is authorized to use "myEmail2" - POP3 login email. This is the primary server IP.

I think the problem is that the 2nd IP is not associated with any SMTP servers and there is no DomainKeys enabled option here.
 
Back
Top