similar to: changed behavior for dovecot-lda in 2.3.x

Hi, Since updating to 2.3.1 on my FreeBSD mailserver mail delivery using lda is broken if I have sieve enabled. (Before updating this was 2.2 and pigeonhole 0.4) FreeBSD 11.1-p8 amd64 Dovecot 2.3.1 Pigeonhole 0.5.1 Mailflow is OpenSMTPd as MTA, using mda delivery to rspamc which utlimately delivers using dovecot-lda. smtpd.conf deliver to mda "rspamc -h scan --mime -e

> >> Messages are being sent to dovecot LMTP by postfix. If I change this email > >> to another server with dovecot 2.2.x the same message are delivered > >> immediately. > > Confirmed. Starts to fail here around 30Mb. Tested with Swaks. > > > > Working on a fix... > > Problem found. It is an explicit limit of 40Mb (for the 30Mb I saw in my >

On 17.04.2018 2:21, Stephan Bosch wrote: > Op 16/04/2018 om 19:57 schreef Michael Tratz: >>>>> Messages are being sent to dovecot LMTP by postfix. If I change >>>>> this email >>>>> to another server with dovecot 2.2.x the same message are delivered >>>>> immediately. >>>> Confirmed. Starts to fail here around 30Mb. Tested

Hi all, Reverted back to 2.2.34 and pigeonhole 0.4.22 and (after reverting config changes) it's working again including Sieve. I was notified of commit https://github.com/stephanbosch/dovecot-core/commit/6553f20bb31b5f0eebb73a0db526f00816b47d71 which I'll try. It's in a different option -f (not -d) but will try. Cheers, Bernard. 2018-04-08 20:10 GMT+02:00 Bernard Spil <brnrd at

Is there a way to get this as a patchset against 2.3.8? On Tue, Oct 8, 2019 at 12:03 PM Stephan Bosch via dovecot < dovecot at dovecot.org> wrote: > > > On 08/10/2019 02:52, Stephan Bosch via dovecot wrote: > > > > > > On 07/10/2019 15:13, Fabian Kuran via dovecot wrote: > >> Hi, > >> > >>> Am 23.09.2019 um 09:36 schrieb Filip Hanes

Okay, to convince myself that quota handling was working okay with Dovecot 1.0-rc27 on Solaris 10, I tested sending a message to an account that was purposely over-quota. The account in question had a vacation message set up. For the first test, there was no $HOME/.imap directory at all. I received the vacation message, but the message which was supposed to be delivered locally queued in Postfix

On 31/03/18 09:29, Stephan Bosch wrote: > Op 3/31/2018 om 9:27 AM schreef Andr? Rodier: >> Hello, >> >> I am using a custom directory for sieve logs and trace and it apparently >> generate an error, in some corner case. >> >> - I have an IMAP global sieve script, that is run when appending emails >> into the "Archives" folder. >> - I

Hi, I wonder if someone could give me a little help bringing the sieve-extdata plugin up to date to be usable with latest Dovecot/pigeonhole Trying to use both together at present I get an error: ? managesieve: Fatal: Couldn't load required plugin /usr/lib/dovecot/sieve/lib90_sieve_extdata_plugin.so: dlopen() failed: /usr/lib/dovecot/sieve/lib90_sieve_extdata_plugin.so: undefined symbol:

Any news on this getting into a release? On Sun, Oct 13, 2019 at 2:24 AM Stephan Bosch <stephan at rename-it.nl> wrote: > > > On 10/10/2019 04:05, Larry Rosenman via dovecot wrote: > > Is there a way to get this as a patchset against 2.3.8? > > > > https://github.com/stephanbosch/dovecot-core/tree/fix-solr-xml-parser-2.3.8 > > This hasn't seen any QA

Hello, I am using a custom directory for sieve logs and trace and it apparently generate an error, in some corner case. - I have an IMAP global sieve script, that is run when appending emails into the "Archives" folder. - I have Thunderbird configured to archive emails by year When archiving an email, for instance in "Archives/2018", I often have an error message like this:

I am a little confused here. I have been running 2.2.34 which I installed in /opt/dovecot2.2 I installed 2.3.0.1 to /opt/dovecot23 I then used config files from /opt/dovecot2.2/etc/dovecot to /opt/dovecot2.3/etc/dovecot and all I did was sed -i.BAK 's/dovecot2.2/dovecot2.3/g'. Dovecot started and was running file. Next, I manually crafted config files for 2.3.0.1 based on the example

Hi all, I have the following situation: On a qmail toaster I am running (with dovecot 1.2.12 as the IMAP server), spam mail gets automatically put into a 'this might be spam' folder (per user). Now, every user has the opportunity to move that mail into either a 'learn as spam' or a 'this was ham' folder and the mail items will be treated accordingly. As a cronjob, I run

Op 16/12/2018 om 10:06 schreef Tributh via dovecot: > > Am 16.12.18 um 09:42 schrieb Aki Tuomi: >>> On 16 December 2018 at 10:27 Tributh via dovecot <dovecot at dovecot.org> wrote: >>> >>> >>> Hi, >>> is that here the right place to make feature requests? >>> >>> dovecot supports as authentication mechanism >>>

On 07/10/2019 15:13, Fabian Kuran via dovecot wrote: > Hi, > >> Am 23.09.2019 um 09:36 schrieb Filip Hanes <filip.hanes at ringier.sk >> <mailto:filip.hanes at ringier.sk>>: >> >> >> ?t 19. 9. 2019 o?15:30 Fabian via dovecot <dovecot at dovecot.org >> <mailto:dovecot at dovecot.org>> nap?sal(a): >> >> Are there any

In https://wiki.dovecot.org/HowTo/Fail2Ban, for a current (I know for a fact in 2.2.36) I believe it should be filter = dovecot instead of filter = dovecot-pop3imap [root at mail ~]# ls -l /etc/fail2ban/filter.d/doveco* -rw-r--r-- 1 root root 1875 May 11 2017 /etc/fail2ban/filter.d/dovecot.conf [root at mail ~]#

Hi again, On 24/12/2017 7:11 am, Stephan Bosch wrote: > Op 12/23/2017 om 7:18 AM schreef Reuben Farrelly: >> Hi, >> >> With latest 2.3 -git (and 2.3.0 release), I'm running into this error >> with Thunderbird: >> >> "An error occurred while sending mail. The mail server responded: >> 5.5.4 Unsupported mail BODY type. Please verify that your

Trying to build Dovecot 2.2.34 on OpenBSD fails. This seems to have been introduced by this commit.. https://github.com/dovecot/core/commit/4a9020ed888caf03fd3132a30a7818b01daa4b9d Fairly -current.. /usr/bin/libtool --tag=CC --mode=link cc -std=gnu99 -O2 -pipe -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast

For dovecot 2.1 as per wiki2, is this still valid? noticed a problem before and saw it does seem to be triggering, I use: maxretry = 6 findtime = 600 bantime = 3600 and there was like, 2400 hits in 4 minutes, it is pointing to the correct log file, but I am no expert with fail2ban, so not sure if the log format of today is compatible with the wiki2 entry filter.d/dovecot.conf [Definition]

Hi all. My dovecot setup: pf at vulcan:~ ? dovecot --version 2.3.0 (c8b89eb) on Arch Linux, x86_64 (full config here: [0]) uses sieve plugin to train rspamd system as described in the wiki [1]. It used to work fine prior to 2.3.0/0.5.0 update, but now "imap" process crashes when I move spam letters from the inbox to the junk folder. I've recompiled both dovecot and pigeonhole

On Saturday, November 2, 2019 10:40:45 PM EET Stephan Bosch <stephan at rename-it.nl> wrote: > I think we already know about this issue (tracked as DOP-942). It > apparently happens because qmail masks the SIGCHLD signal while Dovecot > doesn't unmask it before waiting for children. You're right. Isn't this a simple fix - a call to sigprocmask ? This should not be a