You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mails having utf8(e|)smtps received headers are marked with symbol RCVD_NO_TLS_LAST, or lacking RCVD_TLS_ALL, as rspamd does not seem to understand what protocol this is. Exim compiled with SUPPORT_I18N and libidn2, and gmail (at least) adds the string utf8 (lower or upper case) before the protocol in the received headers if client uses SMTPUTF8.
Motivation
Clearly labeling emails received with TLS as such, even when it's made with SMTPUTF8, would be nice for correctly rating email.
Describe alternatives you've considered
A custom protocol checker could probably do away with the issue, but as this feels like something more of a core feature (correctly categorizing the protocol), I feel it's better to fix this in the "correct" end.
Summary
Mails having utf8(e|)smtps received headers are marked with symbol RCVD_NO_TLS_LAST, or lacking RCVD_TLS_ALL, as rspamd does not seem to understand what protocol this is. Exim compiled with SUPPORT_I18N and libidn2, and gmail (at least) adds the string utf8 (lower or upper case) before the protocol in the received headers if client uses SMTPUTF8.
Motivation
Clearly labeling emails received with TLS as such, even when it's made with SMTPUTF8, would be nice for correctly rating email.
Describe alternatives you've considered
A custom protocol checker could probably do away with the issue, but as this feels like something more of a core feature (correctly categorizing the protocol), I feel it's better to fix this in the "correct" end.
manual page for exim and their handling of this case: https://www.exim.org/exim-html-current/doc/html/spec_html/ch-internationalisation.html
A couple of examples of such received headers, as a result of using the go-smtp library to send a mail:
This mail was marked with RCVD_NO_TLS_LAST after first step "with utf8esmtpsa (TLS1.3)"
The text was updated successfully, but these errors were encountered: