On 2021-11-15 at 05:53:43 UTC-0500 (Mon, 15 Nov 2021 11:53:43 +0100)
Philipp Ewald <philipp.ew...@digionline.de>
is rumored to have said:
I cannot make that line of text into a coherent English sentence.
May I pray for pardon my Lord. My english is not nativ.....
We work with what we have. My German would be far worse.
I suspect that the only problem here is one of unclear language.
Here you can test it....
I have no clue what to test. I do not understand what you think is not
working as intended.
Mail with:
Content-Type: text/html;
charset="us-ascii"
getting "MIME_BASE64_TEXT=1.741"
Which is correct, if the charset is actually us-ascii and Base64
encoding is used anyway. There is no circumstance where a formally
correct text/html document that is strictly us-ascii (i.e. all entities
HTML-encoded) must be Base64-encoded. MIME_BASE64_TEXT exists because it
is unusual to base64-encode pure us-ascii AND it is strong (albeit
imperfect) indicator of the message being spam.
Base64 generate with site:
https://www.base64encode.org/
Or /usr/bin/base64 or 'openssl enc' :)
Kind regards
On 11/12/21 10:16 PM, Bill Cole wrote:
On 2021-11-12 at 04:33:34 UTC-0500 (Fri, 12 Nov 2021 10:33:34 +0100)
Philipp Ewald <philipp.ew...@digionline.de>
is rumored to have said:
Hi folks,
it's seems to be that spamassins dont check non ASCII Base64 decodes
Mails.
I cannot make that line of text into a coherent English sentence.
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64
[BAYES_99=3.5, BAYES_999=5, HTML_FONT_LOW_CONTRAST=0.001,
HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723,
RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_RP_RNBL=1.31]
Mails with:
Content-Type: text/html;
charset="us-ascii"
would get "MIME_BASE64_TEXT"
[BAYES_99=3.5, BAYES_999=5, CK_HELO_GENERIC=0.001,
HELO_DYNAMIC_DHCP=0.206, HTML_IMAGE_ONLY_28=1.404,
HTML_MESSAGE=0.001,
HTTP_EXCESSIVE_ESCAPES=1.572, KHOP_DYNAMIC=0.001,
MIME_BASE64_TEXT=1.741, MIME_HTML_ONLY=0.723,
RAZOR2_CF_RANGE_51_100=1.886, RAZOR2_CHECK=0.922,
RCVD_IN_RP_RNBL=1.31, T_REMOTE_IMAGE=0.01]
Is this a Bug?
Not until it's reproducible and described in a coherent manner.
If you can provide valid email messages (perhaps artificially
constructed) that do (or don't) hit the rules that you believe they
should (or should not,) please do so.
The purpose of MIME_BASE64_TEXT is to identify messages where a text
part (or the whole message) with pure US-ASCII content has been
Base64-encoded instead of being sent unencoded (or just QP-encoded to
protect overlong lines.)
--
Philipp Ewald
Administrator
DigiOnline GmbH, Probsteigasse 15 - 19, 50670 Köln
Fax: +49 221 6500-690, E-Mail: philipp.ew...@digionline.de
AG Köln HRB 27711, St.-Nr. 5215 5811 0640
Geschäftsführer: Werner Grafenhain
Informationen zum Datenschutz: www.digionline.de/ds
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
