Hi everyone,
Our SpamAssassin rules have not gotten any recent updates (looks like
past 2 days). When investigating, sa-update tries to connect to:
2.4.3.updates.spamassassin.org
When doing a DNS lookup on this hostname it appears to be a CNAME which
points to: 3.3.3.updates.spamassassin.or
Hi Charles,
Yes, it was an incorrectly escaped forward slash in a subject rule.
On 2019/06/24 16:12, Charles Amstutz wrote:
Hi Charles,
My apologies, I forgot to provide feedback to the mailing list. Bad regex was
the cause of this problem for us, too. As soon as the custom rule was fixed,
the
Hi Charles,
My apologies, I forgot to provide feedback to the mailing list. Bad
regex was the cause of this problem for us, too. As soon as the custom
rule was fixed, the problem went away.
Kind Regards,
Stephan
On 2019/06/24 15:58, Charles Amstutz wrote:
But as has already been pointed o
55, Matus UHLAR - fantomas wrote:
On 3 Jun 2019, at 2:20, Stephan Fourie wrote:
> We're currently seeing the rule MISSING_SUBJECT sporadically
> hitting on emails that have a subject. This issue seems to have
> started during last week, which is when clients started complaining
>
Hi,
We're currently seeing the rule MISSING_SUBJECT sporadically hitting on
emails that have a subject. This issue seems to have started during last
week, which is when clients started complaining about false positive
detections. Please see example headers at the following link:
https://past
