Hi Aki,
your statement that it should not do this made me check things again,
and it turned out that one of the scripts piping spam (or ham) into
spamassassin was misconfigured. That caused the same behaviour as I
have seen it when trying to manually pipe an encrypted mail into
spamassassin (timeo
> On 06/06/2023 04:10 EEST Robert Senger
> wrote:
>
>
> Hi there,
>
> I was using imap_sieve for many years now to pipe mails upon user
> action (moving mails to the SPAM folder) into spamassassin to train
> spam detection. This worked fine all the time.
>
> Now we're moving to encrypted m
Hi there,
I was using imap_sieve for many years now to pipe mails upon user
action (moving mails to the SPAM folder) into spamassassin to train
spam detection. This worked fine all the time.
Now we're moving to encrypted mail storage on per user basis, with
encrypted private keys. This works well
