Re: Spamassassin not capturing obvious Spam

[Reindl Harald]

Am 31.05.2016 um 19:55 schrieb Shivram Krishnan:

There will a point where the decision to drop the mail is made based on
the headers. Cant we log it there?

SA don't make any decisions of drop / reject
the glue does - spamass-milter, amavis or whatever

and even if - i would find it pervert to make logging in the glue instead have "spamd: result:" log-lines already present which gives you a lot of informations (hitted rules, score, message-id if avalaibale) extended with the envelope-informations not bothering about your usecase - just the fact that you have two different loglines cover each a small piece or a lot of noise where most information is redundant IMHO it is a major bug not include the envelopes (which are known to spamd anyways) in the existing logging

On Tue, May 31, 2016 at 10:30 AM, Reindl Harald <h.rei...@thelounge.net
<mailto:h.rei...@thelounge.net>> wrote:



    Am 31.05.2016 um 19:25 schrieb Shivram Krishnan:

        Thanks guys.

        What I am going to ask might be a longshot.

        But is it possible for anyone who is running a mailserver to
        give a list
        of source of SPAM (recent , anytime this year)and the SA score
        associated? It will be extremely useful for my research and
        credit would
        be given. Example:-
        efetunisie.org <http://efetunisie.org> ,6.3
        abcxcf.com <http://abcxcf.com> ,5.7


    problem is that SpamAssassin don't log envelope-adresses at all in
    the "spamd: result:" lines and so you even have no point to anything
    else than this line in case of mails with a missing message-ID

    discussed this here - nobody cares "use a glue with it's own logging
    - bla"

signature.asc
Description: OpenPGP digital signature