Just tried using Client tools 8.3 and on sending an email the date has an offset of 0000 not +0000, this returns as invalid by some strict SMTP servers.
Any suggestions for a work around?
Thanks
Are you using the .NET mode (nMailMode=0 the default)? If so no - there's no workaround as the date headers are provided through the core .NET libraries. I'd be surprised if the date headers it creates have a problem - I'm using that in various apps with no issues. Is it possible there's a proxy or something else in between that tweaks the headers?
The old mechanism using native code is deprecated as it doesn't support encryption.
+++ Rick ---
No I’m still using mode 2.
If I use the wwSMTP sample form within the wwClient sample folder.
I always relay email to my local SMTP server which then does all the secure and DKIM-Signature stuff.
Sending via Classic mode: Date: Wed, 28 Oct 2026 15:38:56 0000
Sending via .NET mode: Date: 28 Oct 2026 15:40:30 +0000
The .Net mode adds the + on the offset but looses the Day from the start of the date.
According to the RFC 5322 format standard, this is still incorrect.
I get this on some emails:
host mx01.mail.com[74.208.114.68] said: 554-Transaction failed 554-Reject due to policy restrictions. 554 For explanation visit https://postmaster.mail.com/en/case?c=r0704&i=ip&v=&r=1MQ5CI-1wz2Di3zxg-00M659
Hope this helps
James
Day of the week is optional per spec...
As to the +0000 for the legacy native mode - turns out that's a pretty simple fix, so I've fixed that even though I haven't touched that SMTP code in many years. It'll be in the next update.
+++ Rick ---
Excellent thank you Rick