1
DKIM issue after upgrading
Problem reported by Scot Desort - 3/1/2024 at 11:03 AM
Submitted
Hello

We just upgraded from 15.x to 100.0.8818.16520. We are receiving these DKIM errors in the logs for most if not all outbound domains:

[2024.03.01] 00:59:25.741 [57969140] Exception getting DKIM signature System.NullReferenceException: Object reference not set to an instance of an object.
[2024.03.01]    at MailService.RelayServer.RemoteDeliverySession.<>c.<TryDoArcSigning>b__63_0(Header x)   at System.Linq.Enumerable.WhereEnumerableIterator`1.ToList()   at MailService.RelayServer.RemoteDeliverySession.TryDoArcSigning(MimeMessage mimeMessage, InheritedRecipientSettings recipientSettings, String& arcSet, String& dkimSign)00:59:25.741 [57969140] MXRecord count: '5' for domain 

Since the error doesn't refer to a specific field. and is more of a code issue, any ideas to a resolution?

THanks.

10 Replies

Reply to Thread
0
Brian Bjerring-Jensen Replied
Try build 8825.

Are you using an outbound gateway?
0
Scot Desort Replied
No... outbound email is directly delivered without a gateway. 
0
Brian Bjerring-Jensen Replied
Upgrade. Its should be solved.
0
Employee Replied
Employee Post
Hi Scot,

I'm sorry you're having trouble with your DKIM signing after upgrading. I started a support ticket for you so we can look into this problem more. 

Thank you,
0
Scot Desort Replied
The issue may be isolated to domains that have DKIM keys that are 2048 bits long. 2 domains that have keys of 1024 bits appear to be working. 
0
Brian Bjerring-Jensen Replied
8825... has anybody seen where to configure DKIM?

I cant find it.....
0
Brian Bjerring-Jensen Replied
I configured a 4096 bit key on 8825 and its working.
1
Kyle Kerst Replied
Employee Post
I have a SmarterMail v15 test server I maintain checkpoints of for this kind of testing, so I reverted it and set up a 768, 1024, and 2048 bit key on three separate domains before verifying they passed DKIM when sending emails. I then upgraded to our latest SmarterMail public release and saw no DKIM issues on signing or in validation on the remote end in my testing. Because we supported custom selectors in previous versions I also tested with and without this involved in the test but couldn't replicate the behaviors you're noting in those tests. I've reached out on a ticket to see if we can collect some diagnostic details from your environment and hope to get to the bottom of this soon!
Kyle Kerst IT Coordinator SmarterTools Inc. www.smartertools.com
1
Scot Desort Replied
I am going to try to get this customer to find out who can modify their dns records, and gen a new key in SM. The challenge will be them finding the person who can do that. Thanks to everyone so far 
0
Scot Desort Replied
For anyone else this may help, the DKIM key from v15x did not convert properly. We generated a new 2048 bit key, updated DNS (getting GoDaddy credentials was a whole other problem), and all seems well now. Thanks everyone. We also didn't need to move up to 8825 but will probably do so soon.

Reply to Thread