>doveconf -d >/tmp/default
>doveconf -n >/dmp/changed
>
>diff -urp /tmp/default /tmp/changed | less
>
>try :=)
Thanks for that! I know the options, but I was hoping that there was a simple,
straightforward way to disable an option that the maintainers had enabled. If I
had known what would come
> so you edit something ?
Nope - not in the original files! I created a "local.conf" where I put in every
configuration. And there I want to overrule the "auth-system.conf.ext",
activated by default in the " conf.d/10-auth.conf".
> edit conf.d/10-auth.conf change line with auth-system.conf.ext s
Hello,
I want to deactivate the auth-system.conf.ext because it slows down the system
and makes no sense because I utilize passwdfile.conf.ext.
I have put all my configurations into the local.conf file, and all the original
configuration files remain untouched. I want to stay on this path be
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
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) triggers BOTH scripts while the APPEND (move
from junk to elsewhere)
Gotcha
It looks like you nailed it John! (Log and config attached)
The log looks now very different and my log entry is also shown.
Now I can continue working at this point. Adjusting the events i.e.
The reason was actually simple - but I spent a few evenings searching and was
bl
Hi John!
You are of course absolutely right - wild experimentation is rarely a good
approach. But you are surely familiar with the situation when you have done
everything logical and then, in your desperation, you start to change things
that you would not otherwise change ;)
I've actually gott
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 scripts are little different. I spend the time to raise a Debian
10 wi
r=(none)
imap(info@demo.example)<1503>: Debug: imapsieve: mailbox
INBOX: FLAG event (changed flags: \Seen)
Regards
Jens
-Ursprüngliche Nachricht-
Von: Christian Kivalo via dovecot
Gesendet: Sonntag, 30. Juni 2024 22:07
An: dovecot@dovecot.org
Betreff: Re: IMAPSieve plugin will not
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
Host: VMware Workstation 14.1.8
OS: Debian 12 (Bookworm)
Dovecot: 2.3.19.1
Postfix: 3.7.10
Mailclient: Outlook 2016
Hello,
I am currently working on a new mail server to replace my Debian 10 mail
server. For preparation, I use VMware Workstation to learn and test the
installation steps. W
11 matches
Mail list logo