Perhaps this is a misunderstanding. By "same" I mean "this server". The mail
was originally received by my server via TLS, processed by mailman and then
delivered with the ***SPAM*** subject line to the recipients of the mailing
list, but not to the Quarantine. One of the recipients is my own
On 2018-05-09 13:08, Eggert Ehmke wrote:
> > Wild stab - maybe they're entering the system already with
> > ***SPAM*** in the subject?
> The mail also originated from the same server.
All the more reason to suspect the "wild stab" is correct.
In my experience this is quite common on some poorly
The mail also originated from the same server.
Ok, I look into the amavisd config.
Thanks,
Eggert
Am Mittwoch, 9. Mai 2018, 14:06:08 CEST schrieb Reio Remma:
> Wild stab - maybe they're entering the system already with ***SPAM*** in
> the subject?
>
> With amavisd-new it's amavisd that modifies
Wild stab - maybe they're entering the system already with ***SPAM*** in
the subject?
With amavisd-new it's amavisd that modifies the subject, local.cf
shouldn't have an effect on that.
Good luck,
Reio
On 09.05.18 14:02, Eggert Ehmke wrote:
Hello,
I have spamassassin 3.4.1 / amavisd / pos
Hello,
I have spamassassin 3.4.1 / amavisd / postfix / dovecot installed on my Debian
9.4 server. I
also run a mailman mailing list. Most of the time, all runs very well, but
occasionally I get
mails marked ***SPAM*** in my inbox. These are indeed no spam, but valid mails
forwarded by mailma
