https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7901
Bug ID: 7901
Summary: Direct usage of UTF-8 in subject triggering
SUBJ_ILLEGAL_CHARS and SUBJECT_NEEDS_ENCODING rules
Product: Spamassassin
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: Rules
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: Undefined
Hi there.
Since almost 10 years we have RFC 6532 [1] available, that allows direct usage
of UTF-8 in email subject.
It's 2021 now, but SpamAssassing still increases scoring for fully valid and
compliant with IETF standards email messages, basically punishing people who
just want to write emails in their own language - in my cases it's Polish.
I don't like when someone tries to block my ability to write in Polish, yet
today I had to fight with mailing team in my company - they refused to send
valid message using Polish language, because it triggered SUBJ_ILLEGAL_CHARS
(1.1) and SUBJECT_NEEDS_ENCODING (0.1) rules. Why? Because I wanted to send an
email with "Security" word ("Bezpieczeństwo") in the subject.
Could you please look into this and update those rules? People out of US
deserve to feel like first class citizens, too - it's one of the basic reasons
why we have UTF-8 available.
[1] https://tools.ietf.org/html/rfc6532
--
You are receiving this mail because:
You are the assignee for the bug.
