Today we received a complaint from someone saying that Astaro's spam filtering is breaking an RFC.
What we were told is that our Astaro firewall is adding an "X-Spam-Report:" line to the header - however, that line's length is way over what the RFC calls for.
Example from the header from one of the messages which originated from our systems behind our firewall and was sent to an external email address:
X-Spam-Score: -2.4 (--)
X-Spam-Report: Spam detection software, running on the system "{yourAstaroFirewall}", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: I am trying to determine which {CENSORED} of the {CENSORED} are already members of the {CENSORED}. Please respond if you are a member of the {CENSORED}, or you attended the {CENSORED} {CENSORED}{CENSORED} [...] Content analysis details: (-2.4 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.1 HTML_50_60 BODY: Message is 50% to 60% HTML -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] 0.0 HTML_MESSAGE BODY: HTML included in message 0.1 AWL AWL: From: address is in the auto white-list
I googled a bit to find any matching RFC information. Haven't had much luck with it yet. The complaint states that "According to RFC the X header can only be 998 characters on one line.".
According to the documentation in the web-admin:
"X-Spam-Report: If the proxy has flagged a message as spam, it will add this multiline header which contains a full human-readable antispam report."
However that doesn't mention any type of byte-limit.
Any help appreciated. Using Astaro Release 5.207.
This thread was automatically locked due to age.
