http://bugzilla.spamassassin.org/show_bug.cgi?id=3454
Summary: New rule form for de-obfuscation rules
Product: Spamassassin
Version: 2.63
Platform: Other
OS/Version: other
Status: NEW
Severity: enhancement
Priority: P3
Component: Rules
AssignedTo: spamassassin-dev@incubator.apache.org
ReportedBy: lwilton@earthlink.net
Currently we are writing some incredibly large and virtually unreadable REs for
rules to deal with obfuscation. If rules had the ability to run a s// type
substitution on the selected message part before running the =~ or !~ part many
of these rules could be vastly simplified.
I don't know what the exact syntax would have to look like, but I envision
something possibly like the following. Correct any parts of this that don't
actually make sense in perl; I'm a C++ programmer:
header SW_SALES Subject (s/[0-9]//) =~ /Software (?:sales|deals|bargans)/i
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
Summary: New rule form for de-obfuscation rules
Product: Spamassassin
Version: 2.63
Platform: Other
OS/Version: other
Status: NEW
Severity: enhancement
Priority: P3
Component: Rules
AssignedTo: spamassassin-dev@incubator.apache.org
ReportedBy: lwilton@earthlink.net
Currently we are writing some incredibly large and virtually unreadable REs for
rules to deal with obfuscation. If rules had the ability to run a s// type
substitution on the selected message part before running the =~ or !~ part many
of these rules could be vastly simplified.
I don't know what the exact syntax would have to look like, but I envision
something possibly like the following. Correct any parts of this that don't
actually make sense in perl; I'm a C++ programmer:
header SW_SALES Subject (s/[0-9]//) =~ /Software (?:sales|deals|bargans)/i
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.