similar to: pigeonhole + spamprobe

Ubuntu 20.04, Dovecot 2.3.7.2, SpamProbe v1.4d. For the past weeks my sieve filters that call spamprobe have been crashing out for some users. I have a dozen similar server setups and this is not happening on any of the other servers and it was working just fine for a year up until recently. This particular server is quite busy. There is plenty of disk space and inode usage is about 2.5%.

FWIW this took me days to get right, and still needs tinkering, but it might make for a good starting point for anyone else needing something similar (ie; I don't use or need the overhead of spamassassin or rspamd). https://gist.github.com/markc/eeeb66ce30ea805af62631656cf86c4d Any comments or corrections on that page would be appreciated.

There were some non-compatible changes in 2.2.27 that makes older versions of pigeonhole incompatible, when external programs are used. We moved the program-client code from pigeonhole to dovecot core and made some changes to it to facilitate other uses for it. Aki > On January 8, 2017 at 3:33 PM Tobi <tobster at brain-force.ch> wrote: > > > Hi Stephan > > thanks for

Hello Dovecot gurus, I've set up SPF checking on my postfix gateway and have confirmed that messages from domains set with hard fails that don't come from a good sender are rejected outright. Messages from domains set with a softfail that come from bad sources are tagged in the message header with "Softfail (domain owner discourages use of this host)", but end up in the

I currently use Ubuntu 20.04 with Dovecot 2.3.7.2 and OpenSSL 1.1.1f. A few months ago there was an update to all these systems and since then I've had to talk W7 and old Mac clients through disabling ports 993/995 with TLS enabled back to ports 143/110 without SSL or they could not pick up email. Thunderbird users (ie; me) were unaffected. Could anyone share a set of port 993/995 SSL

Hi Stephan thanks for insisting on the pigeonhole version. That seems to be the reason. With 0.4.16 I built the rpms again and after yum install on my mailbox servers the script "terminated normally" Just one thing that does not go in my brain so far: in 1 out of maybe 20 cases the script worked with 0.4.14 without an error. But thats not important as with 0.4.16 it works in 100% of

I want to supply separate Letsencrypt certificates for each virtual domain and seeing that SNI does not work I need to allocate separate IPs. Could anyone give some pointers, or keywords to search for, on... a) how to make dovecot listen for different domains on different IPs? b) how to configure separate SSL certs for each of these IPs?

Hello Dovecot users, RC2 had one more important bug caused by the new sieve_default_name feature. To prevent causing more of such rather stupid bugs in the future, I created an external shell-based test suite to test dovecot-lda delivery, the doveadm sieve tools and ManageSieve. These kind of tests aren't possible with the current Sieve-based test suite that is included in the Pigeonhole

Hello Dovecot users, RC2 had one more important bug caused by the new sieve_default_name feature. To prevent causing more of such rather stupid bugs in the future, I created an external shell-based test suite to test dovecot-lda delivery, the doveadm sieve tools and ManageSieve. These kind of tests aren't possible with the current Sieve-based test suite that is included in the Pigeonhole

Hello Dovecot users, I finally release the first version of Pigeonhole v0.4 for Dovecot v2.2. The main reason for the delay was that some unexpected (design) problems occurred with the new doveadm-sieve plugin, which allows synchronizing sieve scripts using doveadm sync. One important change is that I incorporated the extprograms plugin into the main Pigeonhole release. With this plugin it

Hello Dovecot users, I finally release the first version of Pigeonhole v0.4 for Dovecot v2.2. The main reason for the delay was that some unexpected (design) problems occurred with the new doveadm-sieve plugin, which allows synchronizing sieve scripts using doveadm sync. One important change is that I incorporated the extprograms plugin into the main Pigeonhole release. With this plugin it

On 5/31/20 11:54 AM, Aki Tuomi wrote: > >> On 31/05/2020 07:36 Mark Constable <markc at renta.net >> <mailto:markc at renta.net>> wrote: >> >> >> I currently use Ubuntu 20.04 with Dovecot 2.3.7.2 and OpenSSL 1.1.1f. >> >> A few months ago there was an update to all these systems and since >> then I've had to talk W7 and old Mac

On Tue Jul 07 2020 02:07:08 GMT-0400 (Eastern Standard Time), Mark Constable <markc at renta.net> wrote: > FWIW I meant if the client is Windows7/old-Outlook then changing either > 993/SSL or 143/STARTTLS to 143/NONE could help pick up the mail. We had > to do this for a 100 or so clients a few months ago after upgrading to > Ubuntu 20.04. Really, really bad idea. You just

Hello, did an test Install on my system get some nice SEGFAULT wich backtrace here: https://dominikbreu.de/Stikked/view/8b6b7e5b version is following: aptitude versions dovecot-sieve i 2:2.2.17~rc1-1~auto+4 best regards dominik Am Montag, den 11.05.2015, 00:42 +0200 schrieb Stephan Bosch: > Hello Dovecot users, > > Here's the Pigeonhole RC that goes with the Dovecot RC. It

On 06 Jul 2020, at 20:30, Mark Constable <markc at renta.net> wrote: > you could try disabling SSL/STARTTLS on port 143. What? I?ve never seen SSL/StARTTLS on port 143,a dn I doubt that would work? -- Rumour is information distilled so finely that it can filter through anything. It does not need doors and windows -- sometimes it does not need people. It can exist free and wild, running

Hello Dovecot users, Here's the Pigeonhole release that goes with Dovecot v2.3.1. You will need this release for Dovecot v2.3.1, because the previous v0.5.0.1 release will not work. Apart from compatibility changes, it only contains bugfixes. Changelog v0.5.1: - Explicitly disallow UTF-8 in localpart in addresses parsed from Sieve script. - editheader extension: Corrected the stream

Hello Dovecot users, Here's the Pigeonhole release that goes with Dovecot v2.3.1. You will need this release for Dovecot v2.3.1, because the previous v0.5.0.1 release will not work. Apart from compatibility changes, it only contains bugfixes. Changelog v0.5.1: - Explicitly disallow UTF-8 in localpart in addresses parsed from Sieve script. - editheader extension: Corrected the stream

On 5/11/2015 9:26 AM, Dominik Breu wrote: > Hello, > > did an test Install on my system get some nice SEGFAULT > wich backtrace here: https://dominikbreu.de/Stikked/view/8b6b7e5b > version is following: > aptitude versions dovecot-sieve i 2:2.2.17~rc1-1~auto+4 I cannot view that URL (some broken SSL error). You can just put the backtrace in the email itself. Regards,

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> <br> </div> <blockquote type="cite"> <div> On 31/05/2020 07:36 Mark Constable <<a href="mailto:markc@renta.net">markc@renta.net</a>> wrote: </div> <div> <br>

On 2019-02-05 13:07, Stephan Bosch via dovecot wrote: > Hi, > > Here is the associated release for Pigeonhole: > > https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.24.1.tar.gz > https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.24.1.tar.gz.sig > Binary packages included in https://repo.dovecot.org/ > > + imapsieve: Added