https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6202
Summary: Poor address parsing by $pms->get("from:addr")
Product: Spamassassin
Version: 3.3.0
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P5
Component: Libraries
AssignedTo: [email protected]
ReportedBy: [email protected]
While investigating why a junk string like
"u?.%a_<%k_(b_ <[email protected]"
ends up in AWL database:
dbg: auto-whitelist: sql-based get_addr_entry:
found entry for u?.%a_<%k_(b_ <[email protected]|190.74
it turns out the PerMsgStatus::get does a poor job in obtaining
an address from a valid From header field. Here is the original
valid header field which resulted in the above junk:
From: "=?ISO-2022-JP?B?GyRCIiEhfjx1Py4lYSE8JWsbKEI=?=" <[email protected]>
The decoded display name is: "_$B"!!~<u?.%a!<%k_(B". The root of the problem
seems to be that $pms->get("from:addr") does the decoding before extracting
(or discarding) address, display name and comments. So any strange characters
in a decoded display name throws further parsing off-balance.
Don't know what is the proper solution. Perhaps :addr should imply :raw ?
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
