}
}
service lmtp {
inet_listener lmtp {
address = 127.0.0.1 ::1
port = 24
}
}
ssl_cert =
-Ursprüngliche Nachricht-
Von: John Fawcett via dovecot
Gesendet: Dienstag, 2. Juli 2024 12:34
An:dovecot@dovecot.org
Betreff: Re: AW: AW: AW: AW: IMAPSie
support!
Jens
-Ursprüngliche Nachricht-
Von: John Fawcett via dovecot
Gesendet: Mittwoch, 3. Juli 2024 22:25
An: dovecot@dovecot.org
Betreff: Re: AW: AW: AW: AW: AW: AW: IMAPSieve plugin will not run rspamd script
On 03/07/2024 20:53, postfix_dovecot--- via dovecot wrote:
> Hi J
On 03/07/2024 20:53, postfix_dovecot--- via dovecot wrote:
Hi John,
again you're hitting the point!
I put a "report-spam.sieve fired!" and "report-ham.sieve fired!" debug message in the
scripts and monitored with "journalctl -u dovecot -f | grep fired".
The APPEND event (move to junk) trigge
---Ursprüngliche Nachricht-
Von: John Fawcett via dovecot
Gesendet: Dienstag, 2. Juli 2024 16:21
An: dovecot@dovecot.org
Betreff: Re: AW: AW: AW: AW: AW: IMAPSieve plugin will not run rspamd script
(Resending because of size limit exceeded on previous post)
Hi Jens
that looks much better, tho
(Resending because of size limit exceeded on previous post)
Hi Jens
that looks much better, though not yet completely solved. What you're
now getting is both rules firing when you move a message to Junk,
whereas you only want the first one firing. I guess you will have no
rules firing when yo
vice auth {
unix_listener /var/spool/postfix/private/auth {
mode = 0666
}
}
service lmtp {
inet_listener lmtp {
address = 127.0.0.1 ::1
port = 24
}
}
ssl_cert =
Gesendet: Dienstag, 2. Juli 2024 12:34
An: dovecot@dovecot.org
Betreff: Re: AW: AW: AW: AW: IMAPSieve plugin
sieve_pipe_bin_dir = /usr/lib/dovecot/sieve
sieve_plugins = sieve_imapsieve sieve_extprograms
}
protocols = imap lmtp sieve
service auth {
unix_listener /var/spool/postfix/private/auth {
mode = 0666
}
}
service lmtp {
inet_listener lmtp {
address = 127.0.0.1 ::1
port =
usr/lib/dovecot/sieve
sieve_plugins = sieve_imapsieve sieve_extprograms
}
protocols = imap lmtp sieve
service auth {
unix_listener /var/spool/postfix/private/auth {
mode = 0666
}
}
service lmtp {
inet_listener lmtp {
address = 127.0.0.1 ::1
port = 24
}
}
ssl_cert = Von:
rvice auth {
unix_listener /var/spool/postfix/private/auth {
mode = 0666
}
}
service lmtp {
inet_listener lmtp {
address = 127.0.0.1 ::1
port = 24
}
}
ssl_cert =
Gesendet: Montag, 1. Juli 2024 23:16
An: dovecot@dovecot.org
Betreff: Re: AW: AW: AW: IMAPSieve plugin will not run rspa
On 01/07/2024 22:09, postfix_dovecot--- via dovecot wrote:
Hi John,
the prefix is just a sign of my desperation - I tried all sorts of variations
yesterday and now forgot to undo it.
There’s a very detailed tutorial available (German language) with Debian 10.
Just the sieve scrip
Betreff: Re: AW: AW: IMAPSieve plugin will not run rspamd script
On 01/07/2024 18:08, postfix_dove...@gmx.de <mailto:postfix_dove...@gmx.de>
wrote:
Hi John,
is there any other log than system?
Jens
Hi Jens
I meant the same type of logging you already posted (i.e. as belo
Hi Christian,
yes, it's from the genuine Dovecot documentation. But I tried also a lot of
other tutorials. They're almost the same except the external scrips for rspamd.
The result was every time the same: Nothing noticeable in the log.
>Have you checked that your .sieve files have been compile
On 30/06/2024 19:57, postfix_dovecot--- via dovecot wrote:
Tried it now in every known combination. Nothing changes. It's my 7th evening
about this and I'm starting to despair :(
Hi Jens
any chance of posting the debugging from that test in case it gives any
clues.
John
Tried it now in every known combination. Nothing changes. It's my 7th evening
about this and I'm starting to despair :(
-Ursprüngliche Nachricht-
Von: John Fawcett via dovecot
Gesendet: Samstag, 29. Juni 2024 11:50
An: dovecot@dovecot.org
Betreff: Re: IMAPSieve plugin will not run rspam
14 matches
Mail list logo
