www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tony Stevenson (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (INFRA-8514) heavy spam uptick into moderation queues - spamassassin config change?
Date Sat, 15 Nov 2014 00:42:34 GMT

     [ https://issues.apache.org/jira/browse/INFRA-8514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Tony Stevenson resolved INFRA-8514.

> heavy spam uptick into moderation queues - spamassassin config change?
> ----------------------------------------------------------------------
>                 Key: INFRA-8514
>                 URL: https://issues.apache.org/jira/browse/INFRA-8514
>             Project: Infrastructure
>          Issue Type: Bug
>            Reporter: Hoss Man
>            Assignee: Tony Stevenson
>         Attachments: extreme.spam.wrapped.by.ezmlm.txt
> in the last ~48 hours, we've noticed a large uptick in the amount of spam making it's
way into the moderatation queue for several of the lucene lists (but there is no indication
that it's something specific to jsut the lucene lists)
> these messages are all wrapped up in a SpamAssassin wrapper with a detailed report --
something completely new that we've never seen prior to Oct 21st.
> my best guess, is that something changed recently in the way spam assassin is configured
on the apache mail servers, so that instead of automatically rejecting emails with extremeely
high spam assissin scores, they are getting wraped & flaged like this and propogated through.
> It would be helpul to know if this change was intentional or not -- if it was intentional,
is it possible for us to "opt in" to a new filter to suppress mails above a certain score
*before* they land in the moderation queue? 
> (I'm not even sure if/how i would go about configuring a filter for these in my client,
since the email we recieve as moderators doesn't even contain the spam score info as a header
-- it's wraped up in the moderation request)

This message was sent by Atlassian JIRA

View raw message