Re: Spamassassin goes to folder spam

2021-04-21 Thread mauric
>> Hello

>>

>> Asking for litle help.. Doevecot and sieve are running fine.. One

>> thing now, if receiving mail from Users-spamassassin

>>

>> This mail will by forwarding from sieve to folder spam. I didn't see

>> why this will transfer there.



>You have two conflicting X-Spam-flag headers. This isn't why your email
wasn't filtered into the list folder, but it's the more serious problem.

>Ordinarily SA will strip any pre-existing X-Spam-* headers, which suggests
some other software is calling SA as a library and writing its own headers.

>If possible configure a header with a different and unique name.





disable now the content_filter in master.cf



smtp  inet  n   -   y   -   1   postscreen

## Disable  -o content_filter=spamassassin



and add here to main.cf following entry:



smtpd_milters = unix:spamass/spamass.sock,

   unix:opendkim/opendkim.sock,

   unix:opendmarc/opendmarc.sock,

   unix:private/clamav/clamav-milter.ctl

non_smtpd_milters = $smtpd_milters



but still the double flag appair running with Debain 10 and installed
cpan Spamassassin.



X-Spam-Flag: YES

X-Spam-Flag: NO

X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on nmail.caloro.ch

X-Virus-Scanned: clamav-milter 0.102.4 at nmail.caloro.ch

X-Virus-Status: Clean



thanks for possible update









Re: Spamassassin goes to folder spam

2021-04-20 Thread RW
On Tue, 20 Apr 2021 01:12:18 +0200
mau...@gmx.ch wrote:

> Hello
> 
> Asking for litle help.. Doevecot and sieve are running fine.. One
> thing now, if receiving mail from Users-spamassassin
> 
> This mail will by forwarding from sieve to folder spam. I didn't see
> why this will transfer there.

You have two conflicting X-Spam-flag headers. This isn't why your email
wasn't filtered into the list folder, but it's the more serious problem.

Ordinarily SA will strip any pre-existing X-Spam-* headers, which
suggests some other software is calling SA as a library and writing its
own headers. If possible configure a header with a different and unique name.  


Re: Spamassassin goes to folder spam

2021-04-19 Thread John Hardin

On Tue, 20 Apr 2021, mau...@gmx.ch wrote:


if header :contains "To" users@spamassassin.apache.org
  {


This header might be a better check:

   List-Id: 


--
 John Hardin KA7OHZhttp://www.impsec.org/~jhardin/
 jhar...@impsec.org pgpk -a jhar...@impsec.org
 key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
---
  Our politicians should bear in mind the fact that
  the American Revolution was touched off by the then-current
  government attempting to confiscate firearms from the people.
---
 Today: the 246th anniversary of The Shot Heard 'Round The World


Re: Spamassassin goes to folder spam

2021-04-19 Thread Benny Pedersen

On 2021-04-20 01:12, mau...@gmx.ch wrote:

Hello

Asking for litle help…. Doevecot and sieve are running fine…. One
thing now, if receiving mail from Users-spamassassin

This mail will by forwarding from sieve to folder spam. I didn't see
why this will transfer there.

Dovecot 2.3.4.1 (f79e8e7e4) - Debain 10

Sieve

if header :contains "To" users@spamassassin.apache.org {

  fileinto "INBOX.Spamassassin";


  stop;



}

if header :contains "X-Spam-Flag" "Yes" {

  fileinto :create "Junk";

  stop;

}




X-Spam-Flag: YES



X-Spam-Flag: NO


multiple spamassassin versions or not same add header can make this

but easy fix in sieve, see above


Re: Spamassassin goes to folder spam

2021-04-19 Thread Arne Jensen

Den 20-04-2021 kl. 01:12 skrev mau...@gmx.ch:
>
> Hello
>
> Asking for litle help…. Doevecot and sieve are running fine…. One
> thing now, if receiving mail from Users-spamassassin
>
> This mail will by forwarding from sieve to folder spam. I didn’t see
> why this will transfer there.
>
Your message has two X-Spam-Flag's, one with YES, and another one with
NO, and then you aren't stopping the Sieve parsing.

>  
>
> Dovecot 2.3.4.1 (f79e8e7e4) - Debain 10
>
>  
>
> Sieve
>
>  
>
> if header :contains "To" users@spamassassin.apache.org
>  {
>
>   fileinto "INBOX.Spamassassin";
>
> }
>
> if header :contains "X-Spam-Flag" "Yes" {
>
>   fileinto :create "Junk";
>
>   stop;
>
> }
>
You could add "stop;" to the first one, where you file the message into
INBOX.Spamassassin, which means if it moves the message for you due to a
match, it won't go further with the check on the spam flag for that
particular message.

> --
>
> [...]
>
> Envelope-To: mau...@gmx.ch 
>
> X-GMX-Antispam: 5 (nemesis mail header analyzer); Detail=V3;
>
> X-Spam-Flag: YES
>
> X-UI-Filterresults: junk:10;V03:K0:oQ58xS3PZ3o=:ui
>
> X-UI-Loop:V01:NQ+uvMhGdNE=:SW
>
> X-Spam-Flag: NO
>
From your own snippet of headers, as you can see above, it appears like
you are having two different X-Spam-Flag's to match against, which will
cause some complications and potentially unpredictable results...

-- 
Med venlig hilsen / Kind regards,
Arne Jensen