Frequent Visitor
•
6 Messages
Instructions for All Filter Conditions
I am trying to write a filter to send all email with non-ascii and/or formatted characters to a SPAM folder.
To do this, the filter has to recognize the string '=?UTF-8?B' in either the From header and/or the Subject header. I tried From and Subject conditions but they dont seem to work. I am assumed they worked on raw header but it may be they see the =? and then encode it or skip it altogether.
I am looking at the "String" filter condition but don't know if this will work since I cannot find ANY documentation on filters other than "Sender/From" - which appears all over.
Anyone else trying to get rid of these advertising spammers ? None of my normal emails (bank, comcast, verizon, friends, etc) have either of these headers encoded. Only adverts.
Does anyone have current documentation for the filter conditions (e.g., without deprecated Regex rule) ?
Responses
BruceW
Gold Problem Solver
•
22.3K Messages
2 m ago
Please see https://forums.xfinity.com/t5/Email-Web-Browsing/Filtering-spam-by-subject-need-help-please/m-p/3393175#M222352.
You might try a "Header 'Subject' Contains 'UTF-8' " condition, but my guess is that won't work either, for the same reason. Unfortunately, as best I can tell neither Comcast nor Open-Xchange (the company that supplied the "Appsuite" webmail) bothered to document their email filters.
0
0
lawn
Frequent Visitor
•
6 Messages
2 m ago
Thanks @BruceW
They enabled this stuff back 1992 (rfc 1342) as a way to support non-english character sets. After 30 years, you would think there would be a trivial way to recognize & handle the delimiter/escape characters BEFORE they are interpreted. ugh.
...and NO documentation is inexcusable on Comcast's part. They really dont want to support an email platform because its a cost with little benefit to them. aarrrggg.
I have been procrastinating moving my mbox for years ...but where am I going to go ? yahoo stinks now, dont want googlers mail, ....guess i will relook mail.com, zoho, gmx
0
0
BruceW
Gold Problem Solver
•
22.3K Messages
2 m ago
Nope, doesn't work. An email that arrived today had this Subject line:
That's a Base64 encoding of "The All-New Peacock Original – Punky Brewster".
Neither "Header 'Subject' Contains 'UTF-8' " nor "Subject Contains 'UTF-8' " caught it. Worse, webmail seems to convert "Header 'Subject' Contains 'UTF-8' " to "Subject Contains 'UTF-8' " overnight. Bleah!
0
0