https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8329
Bug ID: 8329
Summary: Adjust header parsing to cope with Communigate rebrand
in 2024
Product: Spamassassin
Version: 4.0.1
Hardware: PC
OS: FreeBSD
Status: NEW
Severity: normal
Priority: P2
Component: Libraries
Assignee: dev@spamassassin.apache.org
Reporter: ch...@threeprong.com
Target Milestone: Undefined
Communigate mail server's parent organization(s) seemed to have forked or some
such thing and now the product has been slightly rebranded. See
https://www.mailspec.com/communigate-spec
Headers that used match regex for a pattern like...
CommuniGate Pro SMTP 7.1.2
now need to match a pattern like...
CommuniGate SPEC SMTP 8.0.7
I noticed this when every message was flagging RDNS_NONE
I found two patterns in Message/Metadata/Received.pm that I was able to just
duplicate to match "SPEC" in addition to Pro. That solved my symptom.
Someone more skilled could probably refine DRY regex and maybe check other
modules also impacted. As best I can tell everything that previously emitted
"CommuniGate Pro" is "CommuniGate SPEC" going forward.
Example anonymized received header...
Received: from mail-pl1-x636.google.com ([2607:f8b0:4864:20::636] verified)
by companyalpha.dom (CommuniGate SPEC SMTP 8.0.7)
with ESMTPS id 9876543 for john...@companybeta.dom; Tue, 15 Apr 2025 22:51:40
+0000
--
You are receiving this mail because:
You are the assignee for the bug.
