I noticed that the mail gem generates the MIME version header capitalized as Mime-Version as opposed to MIME-Version mentioned in the RFC 2045.
While this spelling is technically perfectly correct, it is specifically matched by an rspamd antispam rule called MV_CASE which effectively raises the spam score by 0.5 for all emails with such header. I traced down the original commit in rspamd, it has been there for years and seems to be included in the default configuration, but other than that I found no info about why this rule was added.
I briefly checked a few mail service providers and found that the header capitalization varies a lot:
GMail uses "MIME-Version"
FastMail uses "Mime-Version"
HEY uses "Mime-Version" (but, being a Rails app, perhaps it uses this gem to generate emails :) )
I'll be glad to open a PR if you're interested, thanks!
I noticed that the mail gem generates the MIME version header capitalized as
Mime-Version
as opposed toMIME-Version
mentioned in the RFC 2045.While this spelling is technically perfectly correct, it is specifically matched by an rspamd antispam rule called
MV_CASE
which effectively raises the spam score by 0.5 for all emails with such header. I traced down the original commit in rspamd, it has been there for years and seems to be included in the default configuration, but other than that I found no info about why this rule was added.I briefly checked a few mail service providers and found that the header capitalization varies a lot:
I'll be glad to open a PR if you're interested, thanks!