SA Bugzilla – Bug 7910
Incorrect Thread-index in zimbra formed messages
Last modified: 2023-01-18 23:40:44 UTC
Hello, Our sended mails trigger the PDS_BAD_THREAD_QP_64 rule. It seems that the header Thread-Index is malformed. As far I know, the rule is correct for exchange servers sending messages. But it seems that zimbra is using the header in an other way. The current definition in 72_active.cf is : header __THREAD_INDEX_GOOD Thread-Index =~ m,^A[a-z0-9][A-Za-z0-9+/]{27}(?:[A-Za-z0-9+/]{20})?(?:[AQgw]==|[A-Za-z0-9+/]{7}|[A-Za-z0-9+/]{13}[AEIMQUYcgkosw048]=)$, Here is an example header our server is generating : Thread-Index: TBTkM9019y9w+zdGmptIaSuZKsAA7g== I can find such "malformed" headers in official zimbra documentation, so I presume it is not due to a bad configuration. Thank you for checking.
Hello, We have the similar issue with our Zimbra mail server. We already contacted the support and they said to us that the issue was related here. No issue on Zimbra side. Our sent mails still trigger the PDS_BAD_THREAD_QP_64 rule. The header is still malformed. We tested our mails with the tool called mail-tester : https://www.mail-tester.com/ All of us mails trigger this rule and we lost rate because of it. As the bug is open since almost 2 years now, do you have some updates / advice for us ? Thank you.
PDS_BAD_THREAD_QP_64 is not in the current SpamAssassin ruleset. mail-tester.com is not part of the ASF SpamAssassin project and they are known to be using an obsolete version with rules and scores that do not match the current SA default ruleset. Take any problems they claim to exist in your mail to them. We cannot answer for their failure to provide accurate results.
remember to get support one need to use sa-update, no support if this is not runned in cron installation of zimbra precompiled problems same goes for mail-tester