https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7910
Bug ID: 7910
Summary: Incorrect Thread-index in zimbra formed messages
Product: Spamassassin
Version: 3.4.6
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: Rules
Assignee: dev@spamassassin.apache.org
Reporter: informatique@qc.bzh
Target Milestone: Undefined
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.
--
You are receiving this mail because:
You are the assignee for the bug.
Bug ID: 7910
Summary: Incorrect Thread-index in zimbra formed messages
Product: Spamassassin
Version: 3.4.6
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: Rules
Assignee: dev@spamassassin.apache.org
Reporter: informatique@qc.bzh
Target Milestone: Undefined
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.
--
You are receiving this mail because:
You are the assignee for the bug.