search for: 5ebc6aae4d7c

...ovecot? I turned on everything I found (also using mail_log for imap protocol): # doveconf -n|egrep -e '(verbose|debug)' auth_debug = yes auth_verbose = yes mail_debug = yes verbose_ssl = yes Is there anybody out there who use Dovecot 2.2.7 with antispam plugin? Antispam plugin revision 5ebc6aae4d7c<http://hg.dovecot.org/dovecot-antispam-plugin/rev/5ebc6aae4d7c>

Is there anywhere a collection of folder names for the antispam_trash and antispam_spam configuration? Our problem is that in academia, you have a vast amount of different clients, and some, like Microsoft, use language-specific folder names *on the server*. So we're now collecting folder names to better handle the rare cases. Two more problems: 1. We needed to fix UTF-8 handling in the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear Eugene, patch 49 breaks compilation with Dovecot v2.1. Attached patch encloses the change in a #if. To feed the #if the actual Dovecot version, I've introduced an extra variable in extra.mk, but I cannot help with making the GNU configure stuff doing it right away. There will be numerous other ways to get the Dovecot version into the

Den 12. feb. 2017 21:44, skrev ebroch at whitehorsetc.com: > > > Any opinion on dspam's interoperability with this? > > Just follow the wiki and replace sa-learn scripts with calling dspam. Dspam direct pipe needs mail-line-endings (\r\n) translated into unix line-endings (\r). like so: ----- learn-spam.sh --------- #!/bin/sh sed -e 's/\r$//' | /usr/bin/dspam

...5 instance. I have configured and installed anavisd-new to use Spamassassin. I want to train the filter. For that i choose dovecot's antispam plugin using mailtrain backend. I compiled and installed the latest version of the antispam plugin from http://hg.dovecot.org/dovecot-antispam-plugin/rev/5ebc6aae4d7c The configuration is below. Whenever I receive an email, the LMTP process segfaults. If I comment out the antispam plugin part in the config files, all works good. THis leads me to believe the issue is with antispam plugin, or its configuration. Here is what i see in /var/log/mailllog Aug 28 23...