Re: dovecot-lda without starting dovecot?

On 7 Nov 2017, at 9.15, Stephan von Krawczynski wrote: > > On Tue, 07 Nov 2017 13:19:12 +1000 > Noel Butler wrote: > >> mail_location Optionally disable indexes using :INDEX=MEMORY >> >> don't use this on IMAP boxes, but is safe to use on SMTP and POP3's >> boxes though >> >> eg: >>

Re: dovecot-lda without starting dovecot?

On 7 Nov 2017, at 21.33, Stephan von Krawczynski wrote: > > > Me again have to stress that our former implementation of the lda process did > do exactly nothing to all the dovecot files, and everything worked pretty > well. We had no problems in years. So I really wonder if it wouldn't be the >

Re: Plugin virtual, Horde BAD IMAP QRESYNC not enabled

> On 17 Nov 2017, at 21.36, Aki Tuomi wrote: > > >> On November 16, 2017 at 9:59 AM wertsto...@nurfuerspam.de wrote: >> >> >> > > Hi! > > Thanks for the sample, we were able to identify the problem! Fixed: https://github.com/dovecot/core/commit/489af46c6c1ee32fe6a6ff96a8281f2ef5870c8d <

Re: Dovecots header files not optimized for external plugins

On 19 Nov 2017, at 0.40, Jan Engelhardt wrote: > > > Making third-party plugins for Dovecot is really hard and frustrating. > Using dovecot 2.2.33.2 and the following sources, the compile errors keep > coming. The use of g++ is mandated as the underlying backend this plugin > will access only ha

Re: Error: stat no such file or directory with 2.2.33.2

On 13 Dec 2017, at 9.55, María Arrea wrote: > > > We have upgraded today from Dovecot 2.2.31 to Dovecot 2.2.33.2 and > modified our config to include ITERINDEX in mail_location and we are > detecting some errors like this: > > > /Dec 13 08:17:31 buzon_rhel7 dovecot: imap(rboloix): Error:

v2.3.0 release candidate released

https://dovecot.org/releases/2.3/rc/dovecot-2.3.0.rc1.tar.gz https://dovecot.org/releases/2.3/rc/dovecot-2.3.0.rc1.tar.gz.sig It's finally time for v2.3 release branch! There are several new and exciting features in it. I'm especially happy about the new logging and statistics code, which will

Re: v2.3.0 release candidate released

On 18 Dec 2017, at 23.16, Mark Moseley wrote: > > doveadm(test1-sha...@test.com): Panic: file buffer.c: line 97 > (buffer_check_limits): assertion failed: (buf->used <= buf->alloc) .. > /usr/lib/dovecot/modules/doveadm/lib10_doveadm_sieve_plugin.so(+0x43fe) > [0x6ba6997c33fe] -> Since the panic

v2.3.0 released

https://dovecot.org/releases/2.3/dovecot-2.3.0.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.0.tar.gz.sig Some random notes: - This release is signed with a new PGP key 0x18A348AEED409DA1 (which is signed by the old key). - This fixes several compiling issues reported for the 2.3 release

Re: New Dovecot service: SMTP Submission (RFC6409)

On 22 Dec 2017, at 15.28, Tanstaafl wrote: > > On 12/22/2017, 1:19:45 AM, Aki Tuomi wrote: >> Tanstaafl, maybe you could explain what you think the BURL/URLAUTH >> stuff is for, or do you have some particular use case you would be using >> it? Client support already is not required, and yes, it

Re: Dovecot 2.3 - using doveadm as non-root?

On 3 Jan 2018, at 11.38, Rob Hoelz wrote: > > Hi dovecot developers and users, > > I recently upgraded my server running Arch Linux to dovecot 2.3.0, and I > noticed some of my cron jobs started issuing me error messages. These > cron jobs run as a non-root user associated with my mail account,

Re: zlib plugin producing errors on 2.3.0

On 5 Jan 2018, at 18.33, Carsten Uppenbrink wrote: > > On 24.12.2017 15:58, Adam Weinberger wrote: >> Hello, >> I use the zlib and imap_zlib plugins on FreeBSD. As of 2.3.0, my logs >> are producing these errors every so often, but AFAICT the messages >> themselves aren't getting corrupted. >> Pa

Mailing list content filtering changes

I've now disabled all content filtering in Mailman, because of the failing DKIM/DMARC issues. Hopefully that solves them for now.. Although this will mean that we'll probably start getting HTML mails to this list, which isn't ideal. I guess an alternative could be to reject any mails with text/h

Re: Get parts from username variable

On 7 Jan 2018, at 20.16, Matt . wrote: > > Hi Guys, > > When I have a username like foo-bar-candy can I get/seperate foo, bar > and candy as single variables for my storagepath of the usermail ? If there aren't any @ characters, I think you can kludge this by converting '-' into '@': auth_use

Re: Dovecot 2.3.0 imap-login using 100% CPU

On 10 Jan 2018, at 17.28, Jason Kiniry wrote: > > When in the process of testing out the 2.3.0 version of Dovecot, we noticed > that on a busy server, imap-login can sometimes take 100% CPU and remain > there indefinitely. We grabbed a gdb trace while it was happening: > > dovenull 36053 31.2

v2.2.34 released

https://dovecot.org/releases/2.2/dovecot-2.2.34.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.34.tar.gz.sig * CVE-2017-15130: TLS SNI config lookups may lead to excessive memory usage, causing imap-login/pop3-login VSZ limit to be reached and the process restarted. This happens only

v2.3.0.1 released

https://dovecot.org/releases/2.3/dovecot-2.3.0.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.0.1.tar.gz.sig Small patch release to fix the worst bugs in v2.3.0. v2.3.1 is coming in about a month with a lot more changes. * CVE-2017-15130: TLS SNI config lookups may lead to excessive

Re: v2.2.34 released

On 1 Mar 2018, at 11.17, Alessio Cecchi wrote: > > Il 01/03/2018 07:11, A.L.E.C ha scritto: >> On 02/28/2018 10:20 PM, Timo Sirainen wrote: >>> + mail_attachment_detection_options setting controls when >>>$HasAttachment and $HasNoAttachment keywords are s

v2.2.36 release candidate released

https://dovecot.org/releases/2.2/rc/dovecot-2.2.36.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.36.rc1.tar.gz.sig v2.2.36 is hopefully going to be the last v2.2.x release. Please test this RC well, so we'll have a good final release! v2.3.2 is still going to take a couple of month

Re: v2.2.36 release candidate released

On 2 May 2018, at 12.52, John van der Kamp wrote: > > There seems to be a problem with new user directories and the imapc backend. > On a test setup I get the following error in the log: > > May 02 10:09:58 imap(us...@domain.com): Error: Couldn't create mailbox list > lock /tmp/tmp0Y5TMn/dovec

Re: Upgrading dovecot 2.2 to 2.3 without downtime when using proxy/director?

> On 6 May 2018, at 8.46, Niels Kobschätzki wrote: > > Hi, > > I have a setup with several dovecot-servers (2.2.35) and I use dovecot > proxy. I upgraded one server to 2.3.1 and got the configs fixed so far > that it started again. But when I tried to add it into the proxying > again with "dove

Re: Upgrading dovecot 2.2 to 2.3 without downtime when using proxy/director?

On 15 May 2018, at 12.06, Timo Sirainen wrote: > > If you look at .176's error log, do you see an error about > "director_consistent_hashing settings differ between directors"? Have you set > director_consistent_hashing=yes in the old directors? That is needed

v2.2.36 released

https://dovecot.org/releases/2.2/dovecot-2.2.36.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.36.tar.gz.sig This is the last planned v2.2.x release. We didn't fix everything reported (especially build changes) to try to minimize any unexpected breakages. v2.3.2 will be out with a lot of f

Re: Bug: Dovecot index loosing sync with FTS despite "fts_autoindex = yes"

On 21 May 2018, at 14.11, kada...@gmail.com wrote: > > Le 21/05/2018 à 12:38, Aki Tuomi a écrit : >> can you try turning on pluign { fts_enforced = yes } and repeat your test? > > Same (wrong) result: > 1. Send an email with "too6Ouka" in the body > > 2. Search against "too6Ouka": > # doveadm se

Re: Bug: subscriptions file

I'd rather not add RFC-breaking settings. But there's IMAP4rev2 discussion going on in https://www.ietf.org/mailman/listinfo/extra . Someone motivated enough could perhaps try to suggest changing this behavior in there. > On 23 May 2018, at 23.13, Ru

Re: Bug: Dovecot index loosing sync with FTS despite "fts_autoindex = yes"

On 28 May 2018, at 13.28, kfx wrote: > > >> Especially what is in the "fts" header vs. "next uid" header? Does the UID >> in "fts" header keep changing every time you save a new mail? I suppose it >> will. > > Diff between 2 emails: > next uid = 30104|next uid = 30105 > last_indexed_

Re: use instance-name for syslog?

> On 30 May 2018, at 19.08, SATOH Fumiyasu wrote: > > Hi! > > On Thu, 31 May 2018 00:44:58 +0900, > A. Schulze wrote: >> When running multiple instances of dovecot on the same host (or running >> multiple docker container), >> it is hard to distinguish logs from different processes: the syslo

Re: 2.3.1 Replication is throwing scary errors

Should be fixed by https://github.com/dovecot/core/commit/a952e178943a5944255cb7c053d970f8e6d49336

Re: Header DATE field not returned when placed after MIME section

On 2 Jun 2018, at 1.03, Xavier Guerin wrote: > > Hello, > > I am using Dovecot 2.2.34p0 on OpenBSD 6.3 stable. > > I am writting an application using the vmime (http://www.vmime.org) > library (x-ref issue: https://github.com/kisli/vmime/issues/199). > > I noticed through testing over my own e

Re: 2.3.1 Replication is throwing scary errors

On 7 Jun 2018, at 11.43, Michael Grimm wrote: > > Timo Sirainen: > >> Should be fixed by >> https://github.com/dovecot/core/commit/a952e178943a5944255cb7c053d970f8e6d49336 > > please ignore my ignorance but shouldn't one add this commit regarding >

v2.3.2 release candidate released

https://dovecot.org/releases/2.3/rc/dovecot-2.3.2.rc1.tar.gz https://dovecot.org/releases/2.3/rc/dovecot-2.3.2.rc1.tar.gz.sig v2.3.2 is mainly a bugfix release. It contains all the changes in v2.2.36, as well as a bunch of other fixes (mainly for v2.3-only bugs). * old-stats plugin: Don't temp

Re: doveadm: problem listing shared mailboxes using a wildcard

On 25 Jun 2018, at 16.03, Patrick Ben Koetter wrote: > > In order to do some post-login scripting foo I'd like to get a list of shared > mailboxes the user is currently subscribed to. The doveadm-mailbox man page > says "It's also possible to use wildcards in the mailbox name." > > I'd like to u

v2.3.2 released

https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz.sig v2.3.2 is mainly a bugfix release. It contains all the changes in v2.2.36, as well as a bunch of other fixes (mainly for v2.3-only bugs). Binary packages are already in https://repo.do

Re: v2.3.2 released

On 29 Jun 2018, at 15.05, Tom Sommer wrote: > > On 2018-06-29 14:51, Timo Sirainen wrote: > >> v2.3.2 is mainly a bugfix release. It contains all the changes in >> v2.2.36, as well as a bunch of other fixes (mainly for v2.3-only >> bugs). Binary packages are already

Re: v2.3.2 released

On 29 Jun 2018, at 15.28, Tom Sommer wrote: > > On 2018-06-29 15:20, Timo Sirainen wrote: >> On 29 Jun 2018, at 15.05, Tom Sommer wrote: >>> On 2018-06-29 14:51, Timo Sirainen wrote: >>>> v2.3.2 is mainly a bugfix release. It contains all the changes in >>

Re: 2.3.2 director imap-login segfaults

On 5 Jul 2018, at 15.12, Tom Sommer wrote: > > My director has started segfaulting since upgradeing to 2.3.2: > > #0 0x7fa19b3ec6ed in i_stream_get_root_io () from > /usr/lib64/dovecot/libdovecot.so.0 > No symbol table info available. > #1 0x7fa19b3ec9b5 in i_stream_set_input_pending

Re: 2.3.2 is still crashing (lmtp)

On 6 Jul 2018, at 1.53, Martynas Bendorius wrote: > > Dovecot 2.3.2 still has the same issue we reported for 2.3.X: > > Jul 05 15:10:49 lmtp(2730445): Panic: file lib-event.c: line 182 > (event_pop_global): assertion failed: (event != NULL) ... > #5 0x7f6502986e42 in event_pop_global (even

Re: Benchmarks with imaptest

On 4 Jul 2018, at 20.10, João Paulo Sacchetto Ribeiro Bastos wrote: > > Hey guys, > > Has anybody ever used imaptest to benchmark *ONLY* reads? I'm trying to run a > battery of tests in my new cluster and apparently no combination of > parameters works, because fetch instruction doesn't run.

Re: 2.3.2 is still crashing (lmtp)

> On 6 Jul 2018, at 11.42, Timo Sirainen wrote: > > On 6 Jul 2018, at 1.53, Martynas Bendorius wrote: >> >> Dovecot 2.3.2 still has the same issue we reported for 2.3.X: >> >> Jul 05 15:10:49 lmtp(2730445): Panic: file lib-event.c: line 182 >> (even

v2.3.2.1 released

https://dovecot.org/releases/2.3/dovecot-2.3.2.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.2.1.tar.gz.sig v2.3.2 still had a few unexpected bugs: - SSL/TLS servers may have crashed during client disconnection - lmtp: With lmtp_rcpt_check_quota=yes mail deliveries may have sometimes

Re: IMAP copy stopped copying flags

On 9 Jul 2018, at 16.49, Andrzej A. Filip wrote: > > Is it intended behavior? No. > It seems to be caused by upgrade to 1:2.3.2-2 on Debian/Testing. What was the old version? What's your doveconf -n? How are you testing that it's not working?

Re: v2.3.2.1 released

On 10 Jul 2018, at 10.40, Tom Sommer wrote: > > On 2018-07-09 16:48, Timo Sirainen wrote: >> https://dovecot.org/releases/2.3/dovecot-2.3.2.1.tar.gz >> https://dovecot.org/releases/2.3/dovecot-2.3.2.1.tar.gz.sig >> v2.3.2 still had a few unexpected bugs: >> - SS

Re: LMTP crashing heavily for my 2.2.36 installation

On 11 Jul 2018, at 8.41, Wolfgang Rosenauer wrote: > > Hi, > > I'm running 2.2.36 (as provided by openSUSE in their server:mail repository) > and at least at one of my systems LMTP is crashing regularly on certain > messages (apparently a lot of them). > > Sometimes (but not always a backtrac

Re: dsync panic

On 13 Jul 2018, at 21.39, Wolfgang Rosenauer mailto:wrosena...@gmail.com>> wrote: > > I think I get pretty much the same issue: > > dsync(support): Panic: file mailbox-attribute.c: line 360 > (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || > value_r->value_stream !=

Re: Auth process sometimes stop responding after upgrade

On 7 Sep 2018, at 16.50, Simone Lazzaris wrote: > > Some more information: the issue has just occurred, again on an instance > without the "service_count = 0" configuration directive on pop3-login. > > I've observed that while the issue is occurring, the director process goes > 100% CPU. I've

Re: Auth process sometimes stop responding after upgrade

On 7 Sep 2018, at 19.43, Timo Sirainen <t...@iki.fi> wrote:On 7 Sep 2018, at 16.50, Simone Lazzaris <s.lazza...@interactive.eu> wrote:Some more information: the issue has just occurred, again on an instance without the "service_count = 0" configuration directive on pop3-log

Re: Auth process sometimes stop responding after upgrade

On 8 Sep 2018, at 15.18, Simone Lazzaris wrote:Timo, unfortunately the patch doesn't compile;  I've moved the declaration of "conn" one line up to make it work. Oops, I guess I was too much in a hurry to even compile it. Here's a new patch that compiles and passes our dire

Re: Auth process sometimes stop responding after upgrade

On 11 Sep 2018, at 10.57, Simone Lazzaris wrote: > > Sep 11 03:25:55 imap-front4 dovecot: director: Panic: file > doveadm-connection.c: line 1097 (doveadm_connection_deinit): assertion > failed: (conn->to_ring_sync_abort == NULL) > Sep 11 03:25:55 imap-front4 dovecot: director: Fatal: master:

Re: Occasional crash in db-auth.c (Valgrind: Invalid read of size 4 et al.), Dovecot 2.2.27+

> On 14 Sep 2018, at 12.22, Jonas Schäfer wrote: > >> On Sonntag, 28. Januar 2018 13:59:24 CEST Jonas Wielicki wrote: >>> On Samstag, 27. Januar 2018 21:33:51 CET you wrote: >>> Hi thank you for these, can you send doveconf -n for your minimal >>> reproducer? >> > > Has this been fixed in any

Re: Auth process sometimes stop responding after upgrade

On 18 Sep 2018, at 13.29, Simone Lazzaris wrote: > > > Hi all, again; > > > > I've enabled the core dumps and let it go for some day waiting for the issue > > to reoccur. > > > > Meantime I've also upgraded the poolmon script, as Sami suggested. > > > > It seems that the upgrade has scared the is

Re: Auth process sometimes stop responding after upgrade

On 18 Sep 2018, at 15.15, Simone Lazzaris wrote: > > I've got a core dump, and here is the backtrace. Let me know if you want the > core file. It would be useful if we're able to use it. Could you use https://dovecot.org/tools/core-tar.sh to send the co

Re: Auth process sometimes stop responding after upgrade

On 19 Sep 2018, at 11.11, Simone Lazzaris <s.lazza...@interactive.eu> wrote:In data mercoledì 19 settembre 2018 09:30:47 CEST, Timo Sirainen ha scritto:> On 18 Sep 2018, at 15.15, Simone Lazzaris <s.lazza...@interactive.eu> wrote:> > I've got a core dump, and here is the

Re: Auth process sometimes stop responding after upgrade

On 19 Sep 2018, at 11.30, Timo Sirainen <t...@iki.fi> wrote:On 19 Sep 2018, at 11.11, Simone Lazzaris <s.lazza...@interactive.eu> wrote:In data mercoledì 19 settembre 2018 09:30:47 CEST, Timo Sirainen ha scritto:> On 18 Sep 2018, at 15.15, Simone Lazzaris <s.lazza...@interactive.

Re: Auth process sometimes stop responding after upgrade

On 19 Sep 2018, at 11.42, Timo Sirainen wrote: > > On 19 Sep 2018, at 11.30, Timo Sirainen mailto:t...@iki.fi>> > wrote: >> >>> >>> On 19 Sep 2018, at 11.11, Simone Lazzaris >> <mailto:s.lazza...@interactive.eu>> wrote: >>> >&

v2.3.3 release candidate released

https://dovecot.org/releases/2.3/rc/dovecot-2.3.3.rc1.tar.gz https://dovecot.org/releases/2.3/rc/dovecot-2.3.3.rc1.tar.gz.sig Binary packages are also available in https://repo.dovecot.org/ in ce-2.3.3 repository (not ce-2.3-latest). * doveconf hides more secrets now in the default output. * s

Re: Bug in conditionals to assign values to variables?

> On 28 Sep 2018, at 15.25, Angel L. Mateo wrote: > > user_attrs = ...,=relpath=%{if;%{user};eq;somevalue;valuetrue;valuefalse} > > then it reports in logs: > > Sep 28 14:23:22 myotis60 dovecot: auth: Error: var_expand_long(if;%{user}) > failed: if: requires four or five parameters, go

Re: doveadm backup abort in imapc-client.c

> On 27 Sep 2018, at 21.52, Evan Klitzke wrote: > > I am using Dovecot 2.2.36 and I am trying to use doveadm backup to migrate > email from Gmail to Dovecot. When I run doveadm backup, it goes for a while > and then eventually hits an assertion error (I've tried this a few times now > and it

Re: outlook idiocy - IMAP folders with /

On 28 Sep 2018, at 16.44, Wojciech Puchar wrote: > > user attempts to create folders with / dovecot naturally cannot create it so > it returns error but outlook of course "create" it and keep data in local > store only. data is lost when you remove local store .pst file. > > The question is -

v2.3.3 released

https://dovecot.org/releases/2.3/dovecot-2.3.3.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.3.tar.gz.sig * doveconf hides more secrets now in the default output. * ssl_dh setting is no longer enforced at startup. If it's not set and non-ECC DH key exchange happens, error is logged and

Re: 2.3.3: Panic: file ostream-zlib.c: line 37 (o_stream_zlib_close): assertion failed

On 2 Oct 2018, at 12.26, Tom Sommer wrote: > > I see this in my logs after 2.3.3: > > using zlib plugin, ofc. > > Oct 02 10:01:39 imap(u...@example.com)<50643>: Panic: file > ostream-zlib.c: line 37 (o_stream_zlib_close): assertion failed: > (zstream->ostream.finished || zstream->ostream.ostr

Re: Help for UID THREAD and SORT optimization

On 2 Oct 2018, at 12.22, Alessio Cecchi wrote: > > Hello, > > we are developing a library to show last arrived messages of all threads in a > folder with more than 300k messages. > > As per the RFC 5256, the IMAP thread command has only the option to specify > the grouping criteria (REFERENCE

Re: outlook idiocy - IMAP folders with /

On 2 Oct 2018, at 22.52, Helmut K. C. Tessarek wrote: > > On 2018-10-01 04:07, Timo Sirainen wrote: >> >> https://wiki2.dovecot.org/Plugins/Listescape maybe? > > It should be mentioned somehow that one can't just change the hierarchy > separator on the fly (

Re: Delete vs. Expunge in Public Namespace

On 3 Oct 2018, at 9.03, Chris wrote: > > On Tue, 2 Oct 2018 18:04:21 +0200 > Chris wrote: > >> Is this because the mailbox is >> part of public namespace? > > Or are they expunged because they're duplicates? Is there any check? > Based on Message ID? No.. None of this makes sense. Dovecot does

Re: Bug reports - auth is broken in Dovecot 2.3.3

On 3 Oct 2018, at 13.22, Berindeie Avram-Teodor wrote: > > I applied the patch and recompiled but nothing resolved. > What else can I do? You also need to run autogen.sh & configure again.

Re: Bug reports - auth is broken in Dovecot 2.3.3

could simply manually append to config.h: #define HAVE_CRYPT_H > > On Wed, Oct 3, 2018 at 1:53 PM Timo Sirainen <mailto:t...@iki.fi>> wrote: > On 3 Oct 2018, at 13.22, Berindeie Avram-Teodor <mailto:berindeie@gmail.com>> wrote: > > > > I applied the patc

Re: VOLATILEDIR not really used?

On 4 Oct 2018, at 14.39, Tom Sommer wrote: > > Hi > > According to the docs, setting VOLATILEDIR will improve I/O performance when > using NFS - but as far as I can see, only vsize lock-files are put here, and > little else? Right. I think also autoexpunge locking. > Is this correct, and if

Re: VOLATILEDIR not really used?

On 4 Oct 2018, at 17.13, Tom Sommer wrote: > > > On 2018-10-04 15:55, Timo Sirainen wrote: >> On 4 Oct 2018, at 14.39, Tom Sommer wrote: > >>> Is this correct, and if so are there any plans to move dotlocks etc. to >>> this directory? >> What do

Re: VOLATILEDIR not really used?

On 5 Oct 2018, at 16.42, Tom Sommer mailto:m...@tomsommer.dk>> wrote: > > On 2018-10-05 11:50, Tom Sommer wrote: >> On 2018-10-05 11:35, Timo Sirainen wrote: >>> On 4 Oct 2018, at 17.13, Tom Sommer >> <mailto:m...@tomsommer.dk>> wrote: >>>> On

Re: Panic: file istream-crlf.c: line 24 (i_stream_crlf_read_common): assertion failed: (ret != -2)

On 30 Oct 2018, at 16.25, Peter Nabbefeld wrote: > Oct 26 07:41:20 lda(peter.nabbef...@gmx.de)<24607>: > Panic: file istream-crlf.c: line 24 (i_stream_crlf_read_common): assertion > failed: (ret != -2) > > $ dovecot -n > # 2.3.3 (dcead646b): /etc/dovecot/dovecot.conf Are you using our packages

v2.3.4 released

https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz.sig Binary packages in https://repo.dovecot.org/ * The default postmaster_address is now "postmaster@". If username contains the @domain part, that's used. If not, then the server's host

Re: Problems after upgrading to 2.3.2.1

On 22 Nov 2018, at 22.28, Joel Dahl wrote: > > Hi, > > I've just upgraded dovecot from 2.2.35 to 2.3.2.1 on my mail server > and noticed something odd. My mail clients (mutt and Apple mail) both stopped > seeing new mail in my mailboxes. > > For example, ~/Maildir/mailinglist1/new has 5 new mai

Re: v2.3.4 released

On 24 Nov 2018, at 8.33, Odhiambo Washington wrote: > > > I installed 2.3.4 and just used it with the config files for 2.3.3 without > changing anything in the configuration. > I then realized that the LDA was throwing errors. > > 2018-11-24 00:02:51 1gQIaw-000AZS-Bc >

Re: Event 0x2b1a5f270bd0 leaked (parent=(nil)): auth-client-connection.c:338

On 3 Nov 2018, at 17.41, Mart Pirita wrote: > > Hi, > > > But this harmless is spamming logs, so how to disable it: > > grep auth-client-connection.c:338 maillog | wc -l >1259 Actually this specific event leak isn't a known issue. I don't really understand how it could happen. These even

Re: Event 0x2b1a5f270bd0 leaked (parent=(nil)): auth-client-connection.c:338

On 26 Nov 2018, at 13.16, Mart Pirita wrote: > > Hi, > > Auth process is not constantly being shutdown and/or restarted and Dovecot is > used for SMTP authentication (Postfix). > > Checked few servers logs, they are running v2.3.3, for example latest > (some day none, some day a lot, some day

Re: [2.3.4] Segmentation faults

See https://dovecot.org/bugreport.html#coredumps Without a backtrace it's not really possible to figure out where it's crashing. > On 28 Nov 2018, at 13.20, Joan Moreau wrote: > > Where to get that ? > > > On 2018-11-27 08:50, Aki Tuomi wrote: > >> It's still missing core dump (or bt full f

Re: Dovecot 2.3.4 crash

On 29 Nov 2018, at 15.46, azu...@pobox.sk wrote: > > Hi, > > is this a know problem? Newest Dovecot 2.3.4 package from repo.dovecot.org , > Debian Stretch (fully upgraded). > > > > Nov 29 14:25:11 server00 dovecot: lmtp(16854): Panic: file ostream-dot.c: > line 208 (o_stream_dot_sendv): asse

Re: How to unsubscribe

On 1 Dec 2018, at 12.37, Keith Edmunds wrote: > >> I am very sorry that I had to enable the delivery for people who had >> intentionally disabled delivery, but I didn't want to spend days >> figuring out the best possible way to fix the situation and in the end >> it's not a horrible bother to di

Re: Dovecot 2.3.4 crash

On 2 Dec 2018, at 22.22, Guillaume via dovecot wrote: > > I also have this kind of segfault since the update : > > Dec 2 21:12:11 xxx dovecot: auth-worker: Error: *** Error in > `dovecot/auth': double free or corruption (fasttop): 0x55573bb99f70 Is this easy to reproduce? Can you try

Re: Indexer worker small bug

On 9 Dec 2018, at 16.44, André Rodier via dovecot wrote: > > Hello, > > I think I submitted this before, but I am not sure this has been addressed > > I am using AppArmor with Dovecot, without any issue. > > However, I think there is a bug in the indexer working, from what I can see, > a miss

Re: Indexer worker small bug

On 10 Dec 2018, at 7.50, André Rodier wrote: > > On 2018-12-09 23:13, Timo Sirainen wrote: >> On 9 Dec 2018, at 16.44, André Rodier via dovecot >> wrote: >>> Hello, >>> I think I submitted this before, but I am not sure this has been addressed >>>

Re: Panic…

On 13 Dec 2018, at 7.31, SH Development wrote: > > I have started getting these in my log. What does this mean and what do I > need to do? > > Panic: file mail-index-util.c: line 37 (mail_index_uint32_to_offset): > assertion failed: (offset < 0x4000) Your dovecot.index.cache file has gr

Re: Bug in IDLE implementation for virtual mailbox

On 16 Dec 2018, at 21.26, Pali Rohár wrote: > > Hello! > > I found bug in Dovecot's IDLE implementation when virtual mailbox is in > use. IDLE does not notify about new emails when email appears in newly > created mailbox and IDLE was issued in virtual folder which matches "*" > wildcard and tha

Re: Bug in IDLE implementation for virtual mailbox

On 17 Dec 2018, at 10.44, Pali Rohár wrote: > > On Sunday 16 December 2018 21:55:23 Timo Sirainen wrote: >> On 16 Dec 2018, at 21.26, Pali Rohár wrote: >>> >>> Hello! >>> >>> I found bug in Dovecot's IDLE implementation when virtual mailbox

Re: gcc -> clang

The unit test problems aren't clang issues, they're OSX issues. So: test-net.c:79: Assert failed: strcmp(net_ip2addr(&ip), "::5") == 0 test-net.c:83: Assert failed: strcmp(net_ip2addr(&ip), "::5") == 0 This is because OSX writes the address out as "::0.0.0.5" instead of "::5". I don't remember i

Re: Solr -> Xapian ?

On 7 Jan 2019, at 16.05, Joan Moreau via dovecot wrote: > > Hi > > ANyone to answer specifically ? > > Q1 : get_last_uid -> Is this the last UID indexed (which may be not the > greatest value), or the gratest value (which may not be the latest) (the code > of existing plugins is unclear about

Re: Solr -> Xapian ?

On 11 Jan 2019, at 21.23, Joan Moreau via dovecot wrote: > > The below patch resolves the compilation error > > $ diff -p compat.h compat.h.joan > *** compat.h 2019-01-11 20:21:00.726625427 +0100 > --- compat.h.joan 2019-01-11 20:14:41.729109919 +0100 > *** struct iovec; > *** 202,2

Re: Solr -> Xapian ?

On 13 Jan 2019, at 10.45, Joan Moreau via dovecot wrote: > > Now, I can see in the logs that several times, the dovecot calls the > fts_backend_xapian_update_set_mailbox with box == NULL. WHy so ? > fts-api.h says: /* Switch to updating the specified mailbox. box may also be set to NULL to

Re: Indexing paralelism

On 13 Jan 2019, at 19.23, Joan Moreau via dovecot wrote: > > Hi > > Observing the processes of FTS, I observe the following: > > > > 1 - For one user, indexer-wroker does not start several threads for each > request. On teh contrary, it waits for the first request to finish before > startin

Re: dovecot/config processes one more time - which are safe to kill?

On 13 Dec 2018, at 11.18, Arkadiusz Miśkiewicz wrote: > > > Hello. > > The problem with dovecot/config processes never ending and spawning new > one on each reload > (https://www.dovecot.org/list/dovecot/2016-November/106058.html) is > becoming a problem here: > > # ps aux|grep dovecot/config|

Re: Doveadm error since 2.3.11.3 when run as unprivileged user

On 13. Aug 2020, at 11.00, Arjen de Korte wrote: > > I allow users to run 'doveadm' for mailbox maintenance (to expunge mail for > instance). Since the upgrade to 2.3.11.3, this no longer works and results in > the following error message: > > doveconf: Fatal: Error in configuration file /etc/

Re: Doveadm error since 2.3.11.3 when run as unprivileged user

On 13. Aug 2020, at 11.29, Timo Sirainen wrote: > > On 13. Aug 2020, at 11.00, Arjen de Korte wrote: >> >> I allow users to run 'doveadm' for mailbox maintenance (to expunge mail for >> instance). Since the upgrade to 2.3.11.3, this no longer works and

Re: 2.3.11.3 mail_cache_open_or_create_path called with null path

On 13. Aug 2020, at 14.14, Stuart Henderson wrote: > > Originally reported here - > https://marc.info/?l=openbsd-ports&m=159731598419071&w=2 > > OpenBSD's printf functions have a (mostly annoying but occasionally > useful) feature where they generate a syslog entry if printf %s format > is calle

Re: Tests failing on CentOS 6

On 15. Aug 2020, at 14.18, Peter wrote: > > Getting this when attempting to build 2.3.11.3 on CentOS 6: > > test-mail-cache.c:176: Assert failed: > strcmp(str_c(str),"123\nfoo\n456\nbar\n") >"" != "123 > foo > 456 > bar > " > test-mail-cache.c:176: Assert failed: > strcmp(str_c(str),"1

Re: zlib errors after upgrading

On 28. Aug 2020, at 12.10, Robert Nowotny wrote: > > unfortunately after re-installing 2.3.11.3, those broken-pipe errors appear > again. (on different, new files) > so for sure there is something broken with zlib. > I will go back to 2.3.10.1 now. > attached is the configuration file, though i

Re: zlib errors after upgrading

cot: imap(rprager)<237941>: > Error: zlib_save: Unknown handler: zstd > ... > > > what I do wrong here ? > > > > > Am 28.08.2020 um 13:15 schrieb Timo Sirainen: >> On 28. Aug 2020, at 12.10, Robert Nowotny > <mailto:rnowo...@rotek.at>> w

Re: about header address parsing

On 1. Sep 2020, at 6.24, TACHIBANA Masashi wrote: > > Hi, > > Is this expected or not? > > From: us...@fuga.example.com > To: us...@hoge.example.com > ↓ > a uid fetch 43055 (envelope) > * 1860 FETCH (UID 43055 ENVELOPE ("Thu, 30 Jul 2020 13:52:59 +0900" "test1" > ((NIL NIL "user1" "fuga.exam

Re: zlib errors after upgrading to 2.3.11.3

On 8. Sep 2020, at 12.35, Robert Nowotny wrote: > > > Dear Aki, > I switched to "gz" now, since "zstd" also gave some errors on writing to > files. What kind of errors? > I dont know if "xz" compression or "zstd" shreddered my MDBOX Files, but I > lost 4 days of mail. (a couple of thousand m

Re: zlib errors after upgrading to 2.3.11.3

On 8. Sep 2020, at 12.35, Robert Nowotny wrote: Dear Aki, I switched to "gz" now, since "zstd" also gave some errors on writing to files.What kind of errors?Probably this? :Panic: file ostream.c: line 287 (o_stream_sendv_int): assertio

Re: zlib errors after upgrading to 2.3.11.3

On 8. Sep 2020, at 16.28, Timo Sirainen wrote: > >>> Sep 3 08:33:25 lxc-imap dovecot: imap(mpaul)<48684><2/9E5mKuAezAqKjk>: >>> Error: Mailbox Sent: UID=2171: >>> read(zlib(/home/vmail/virtualmailboxes/mpaul/storage/m.119)) failed: >>> re

Re: zlib errors after upgrading to 2.3.11.3

On 9. Sep 2020, at 11.14, Robert Nowotny wrote: > >>> Sep 3 08:33:25 lxc-imap dovecot: imap(mpaul)<48684><2/9E5mKuAezAqKjk>: >>> Error: Mailbox Sent: UID=2171: >>> read(zlib(/home/vmail/virtualmailboxes/mpaul/storage/m.119)) failed: >>> read(/home/vmail/virtualmailboxes/mpaul/storage/m.119) f

Re: zlib errors after upgrading to 2.3.11.3

On 10. Sep 2020, at 14.07, Robert Nowotny wrote: > > > On 9. Sep 2020, at 11.14, Robert Nowotny > wrote: >> Sep 3 08:33:25 lxc-imap dovecot: imap(mpaul)<48684><2/9E5mKuAezAqKjk>: Error: Mailbox Sent: UID=2171: read(zlib(/home/vmail/virtualmailb

  1   2   3   4   5   6   7   8   9   10   >