Re: doveadm sync - I/O has stalled

We haven't found any specific bugs with lib-ssl-iostream so far, but we did find istream-multiplex bug that could cause hangs with doveadm-doveadm connections. Could be worth testing if it helps: https://github.com/dovecot/core/commit/bbe546bc637a6ac5c9e91fc8abefce62e4950d07 > On 30. Dec 2022,

Re: SAVEDATE is using ctime instead of btime for Maildir

On 19. Mar 2024, at 0.43, Alex via dovecot wrote: > > Dovecot supports SAVEDATE IMAP extension [1]. > This is however not implemented correctly for Maildir storage. > > Compared to "internal date", "save date" is supposed to be the same > but well-defined for APPEND and preserved when COPY

Re: Inconsistency in map index with dovecot v2.3.21

On 12. Jan 2024, at 9.37, John Alex. via dovecot wrote: > > Hi, > > since I upgraded dovecot to version 2.3.21 on a FreeBSD 13.2 system, I've > been seeing a few occurences of the following warnings daily: > > Jan 11 13:13:25 dimokritos dovecot[33170]: > lmtp(user1)<8209>: Warning: mdbox >

Re: JMAP support?

On 8. Mar 2021, at 9.11, Mark Constable wrote: > > On Fri Jan 25 2019 Aki wrote: > > There is no JMAP support in any dovecot version yet. > > Two years on so what is the status of JMAP support in Dovecot now? - We have a new JSON library, making it easier to write efficient JMAP support. -

Re: doveadm http api not responding under load

Hi, > On 22. Jan 2024, at 20.00, Achim Stahlberger > wrote: > > Hello, > > we see this problem when doveadm-server is under load. > > We enabled doveadm http api with this config: > > service doveadm { > inet_listener { >port = 5 > } > inet_listener http { >port = 50001 >

Re: Unconfigurable 500 ms debounce on IMAP IDLE notifications

On 15. Dec 2023, at 1.59, Alex wrote: > >>> I would actually like to disable this delay completely on our server setup >>> [6], >>> as for chat it is common to receive multiple >>> messages in a short period of time, >>> e.g. when sending a message to a group and receiving multiple read

Re: Unconfigurable 500 ms debounce on IMAP IDLE notifications

On 14. Dec 2023, at 16.21, Alex wrote: > > Hello all, > > I have been investigating the reason for high > end-to-end email delivery delay > (>1 second to send a message to echo bot and receive a reply back) > on a Postfix+Dovecot email server setup > used to run the tests for Delta Chat core

Re: dovecot crash with Panic: file istream-header-filter.c: line 663

On 12. Mar 2023, at 20.17, Patrick Mansfield wrote: > > Mar 12 10:32:27 goffin dovecot[8269]: imap(patman)<8452>: > Panic: file istream-header-filter.c: line 663 > (i_stream_header_filter_snapshot_free): assertion failed: > (snapshot->mstream->snapshot_pending) This is unfortunately rather

Re: How to get a server listed in the IMAP Test wiki?

On 24. Feb 2023, at 9.29, Leander Beernaert wrote: > > > Hey Timo, > > Thanks for the quick turnaround, once we have the test results I'll contact > you again. OK. > Should I also include instructions on how to run the a self contained server > with a dummy backend so you can

Re: How to get a server listed in the IMAP Test wiki?

On 23. Feb 2023, at 16.13, Leander Beernaert wrote: > > Hey, > > We recently announced Gluon (https://github.com/ProtonMail/gluon/) our IMAP > server library we are using in Proton > Bridge(https://github.com/ProtonMail/proton-bridge). We would love to have it > have it listed in the IMAP

Re: doveadm sync - I/O has stalled

On 2. Jan 2023, at 3.26, Timo Sirainen wrote: > > On 2. Jan 2023, at 3.21, Timo Sirainen wrote: >> >> >>> It may happen, but it is hard to reproduce. >> >> Are you able to try if this patch happens to fix it? : > > Actually, looking

Re: doveadm proxy list has strange entries

On 30. Dec 2022, at 23.40, Tobias Florek wrote: > > When getting the proxy list I get the following entries. > > # doveadm -f flow proxy list > username=u...@example.com proto=imap src ip=10.254.0.13 dest ip=172.23.6.194 > port=143 > username=username proto=service src ip=src-ip dest

Re: doveadm sync - I/O has stalled

On 2. Jan 2023, at 3.21, Timo Sirainen wrote: > > >> It may happen, but it is hard to reproduce. > > Are you able to try if this patch happens to fix it? : Actually, looking at it slightly more, there may be another bug in it, although I'm not sure how it affects th

Re: doveadm sync - I/O has stalled

Hi, > But when dsync connects over tcps, > it uses function implementations in lib-ssl-iostream to send and receive data. > And this simplified call stack would result in some data are read when > calling o_stream_uncork > > o_stream_uncork => o_stream_flush => o_stream_ssl_flush_buffer => >

Re: The end of Dovecot Director?

Director never worked especially well, and for most use cases it's just unnecessarily complex. I think usually it could be replaced with: * Database (sql/ldap/whatever) containing user -> backend table. * Configure Dovecot proxy to use this database as passdb. * For HA change dovemon to

Re: v2.3.19.1 released

Also, nowadays Lua would be a better way to do custom authentication and we're more careful not to break that. > On 21. Jun 2022, at 13.47, Timo Sirainen wrote: > > Oh, I think your problem is that you've implemented a separate dict-server. > And looks like we forgot to mentio

Re: v2.3.19.1 released

test ralfimapt...@egroupware.org" and one other regular > passdb lookup. > > I replaced passwords and the customer email with XX. > > I also run "doveadm user '*'" to test the iteration, which worked. > > Ralf > > > Am 20.06.22 um 13:32 schr

Re: Malformed XLIST replies

On 20. Jun 2022, at 20.23, Bogdan Szczurek wrote: > > When XLIST is used to get the list of the folders, I get, for example: > > 3 XLIST "" "*" > * XLIST (\HasNoChildren \) "." "Archive" > * XLIST (\HasNoChildren \) "." "Courses" .. > Notice, how in the XLIST example, every item has an

Re: v2.3.19.1 released

On 20. Jun 2022, at 10.03, Ralf Becker wrote: >> Fixes: Panic: file userdb-blocking.c: line 125 >> (userdb_blocking_iter_next): assertion failed: (ctx->conn != NULL) > > As the above Panic is fixed I tried again (see my attached mail to the 2.3.19 > release) and I can confirm to no longer

Re: Fatal Error after upgrade to 2:2.3.19-2+debian11

On 16. May 2022, at 14.09, Sebastian Kroczek wrote: > > Hello all, > > I updated the server tonight and with it Dovecot from 2.2.27 to > 2:2.3.19-2+debian11. However, there seems to be a problem with the ACLs, > because since then fatal errors are logged (see core dump). I suspect that >

Re: Retrieive vsz_limit programatically

Do you want to find out the service/process's own vsz_limit or another service's vsz_limit? Own vsz_limit would be easiest to get with getrlimit(RLIMIT_AS) as Aki said. If you want another service's vsz_limit that's not easily possible, because those settings just aren't sent to anything

Re: PIGEONHOLE BUG: imapsieve with virtual mailboxes

Hi, Pigeonhole shouldn't need to know anything about this being a virtual mailbox specifically. If I understand right, the problem is that imapsieve doesn't like it when the destination folder doesn't know what the IMAP UID number is for the saved/copied mail. Earlier versions assert-crash,

Re: indexer crash

On 29. Aug 2021, at 0.42, Onno Molenkamp wrote: > > Hi, > > Because I was getting segfaults in libc in calloc calls by the indexer > process of Dovecot 2.3.16, I ran indexer with valgrind to look for possible > memory corruption. It did indeed find that indexer was accessing memory that >

Re: i_stream_read_memarea: assertion failed: (!stream->blocking)

On 13. Aug 2021, at 19.10, Stuart Henderson wrote: > I get "i_stream_read_memarea: assertion failed: (!stream->blocking)" when > accessing some messages. Backtrace and doveconf -n below. Does the attached patch fix it? diff Description: Binary data

Re: dovecot 2.3.16 fail one test on s390x, alpine linux

On 10. Aug 2021, at 19.54, Michael Ströder wrote: > > Timo, > > On 8/10/21 5:55 PM, Timo Sirainen wrote: >> Well, that's annoying. I thought it would have worked. I wonder if it's >> still some issue with the #if not being right. Can you try once more >> with disa

Re: dovecot 2.3.16 fail one test on s390x, alpine linux

On 10. Aug 2021, at 14.17, Michael Ströder wrote: > > On 8/10/21 11:16 AM, Timo Sirainen wrote: >> On 10. Aug 2021, at 10.33, Michael Ströder wrote: >>> >>> On 8/10/21 10:02 AM, Milan P. Stanić wrote: >>>> I'm trying to upgrade dovecot from version 2.3

Re: dovecot 2.3.16 fail one test on s390x, alpine linux

On 10. Aug 2021, at 10.33, Michael Ströder wrote: > > On 8/10/21 10:02 AM, Milan P. Stanić wrote: >> I'm trying to upgrade dovecot from version 2.3.15 to 2.3.16 for alpine >> linux. Build and 'make check' pass on all alpine architectures except on >> s390x which is big-endian while all other are

Re: [Dovecot-news] v2.3.16 released

On 9. Aug 2021, at 11.58, Michael Ströder wrote: > > On 8/9/21 11:32 AM, Joan Moreau wrote: >> Bottom-line : 2.3.16 crashes every now and then. > > I see occasional failures in the test suite on openSUSE build system (OBS): > >

Re: [Dovecot-news] v2.3.16 released

On 9. Aug 2021, at 11.32, Joan Moreau wrote:Bottom-line : 2.3.16 crashes every now and then.Maybe is there a quick fix for production servers ?Attached a fix. fts.patch Description: Binary data

Re: [Dovecot-news] v2.3.16 released

On 9. Aug 2021, at 11.24, Timo Sirainen wrote: > > On 9. Aug 2021, at 11.03, Joan Moreau <mailto:j...@grosjo.net>> wrote: >> >> #0 0x7f2370f7fe3d in o_stream_nsendv (stream=0x0, >> iov=iov@entry=0x7ffeb9dabd70, iov_count=iov_count@entry=1) at ostream.c:

Re: [Dovecot-news] v2.3.16 released

On 9. Aug 2021, at 11.03, Joan Moreau wrote: > > #0 0x7f2370f7fe3d in o_stream_nsendv (stream=0x0, > iov=iov@entry=0x7ffeb9dabd70, iov_count=iov_count@entry=1) at ostream.c:333 > > overflow = false > #1 0x7f2370f7feca in o_stream_nsend (stream=, > data=, size=) at ostream.c:325 > iov

Re: Replication stalled by failed attemts to read attachments (mail_attachment_dir)

On 9. Aug 2021, at 10.41, Ralf Becker wrote: > > Made some progress, the attachments are not lost, the new Dovecot server (it > was a migration from 2.2.19 to 2.3.15 on a different host), searches them > under a partially different filename: > > Aug 09 08:26:19 doveadm: Error:

Re: doveadm pw

On 7. Aug 2021, at 14.07, Alexander Dalloz wrote: > > Am 07.08.2021 um 08:06 schrieb Doug Hardie: >> mail# doveadm pw >> Enter new password: >> Retype new password: >> {CRYPT}$2y$05$oSB6end9V.YumJMzON7lfeOL9N8TXK6jhYqjHOEnPd1NLZ9.QNaTy >> I thought the default was supposed to be CRAM-MD5. I

Re: [Dovecot-news] v2.3.16 released

I don't see anything wrong in git branch either: % git clone -b release-2.3.16 https://github.com/dovecot/core.git <https://github.com/dovecot/core.git> % git grep fts_user_autoindex_exclude % % git show commit 7e2e900c1a420006371e8a8cf9b4ddb36e69a986 Author: Timo Sirainen Date: Thu Au

Re: [Dovecot-news] v2.3.16 released

On 6. Aug 2021, at 15.08, Joan Moreau wrote: > > Below > > (gdb) bt full > #0 fts_user_autoindex_exclude (box=, box@entry=0x55e0bc7e0fe8) > at fts-user.c:347 > There is no such function in 2.3.16 release. That's only in the current git master. What did you install and from where?

[Dovecot-news] Pigeonhole v0.5.16 released

Hi, Pigeonhole release for Dovecot v2.3.16. https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.16.tar.gz https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.16.tar.gz.sig

Pigeonhole v0.5.16 released

Hi, Pigeonhole release for Dovecot v2.3.16. https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.16.tar.gz https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.16.tar.gz.sig

[Dovecot-news] v2.3.16 released

Hi, One interesting thing in this release is the support for configuring OAUTH2 openid-configuration element. It would be nice if IMAP clients started supporting this feature to enable OAUTH2 for all IMAP servers, not just Gmail and a few others. This would allow all kinds of new

v2.3.16 released

Hi, One interesting thing in this release is the support for configuring OAUTH2 openid-configuration element. It would be nice if IMAP clients started supporting this feature to enable OAUTH2 for all IMAP servers, not just Gmail and a few others. This would allow all kinds of new

Re: Timo - is the v2.3.15 GCC limitation really necessarily or it's just a bug?

On 29. Jul 2021, at 7.21, Mart Pirita wrote: > > Hello. > > So far I have successfully built Dovecot until v2.3.14 on Centos 4-6 (yes I > know, they are old, but as they are remote servers, distros can't upgraded), > and sometimes I have also met compilation issues, but after highlighting >

Re: Dovecot v2.3.14.1 released

On 23. Jun 2021, at 13.17, Eirik Rye wrote: > > On Mon, Jun 21, 2021 at 1:24 PM Timo Sirainen wrote: >> Binary packages in https://repo.dovecot.org/ > > The repository https://repo.dovecot.org/ce-2.3.14 does not contain the > latest binary package for version 2.3.14.1

Re: ssl_min_protocol v2.3.15

On 22. Jun 2021, at 14.55, Theo Pannen wrote: > > Hello, > > it seems that the default value for ssl_min_protocol has changed from > TLSv1 to TLSv1.2, right? > > After upgrading to v2.3.15 and with ssl_min_protocol commented out, the > server no longer offers TLSv1 and TLSv1.1. > > This is a

Re: libdict_lua linking issues

On 21. Jun 2021, at 18.57, James wrote: > > On 21/06/2021 17:39, Daniel J. Luke wrote: >> On Jun 21, 2021, at 7:20 AM, Timo Sirainen wrote: >>> Here's a new release with some security fixes and quite a lot of other >>> changes as well. >>> >>>

Re: CVE-2021-33515: SMTP Submission service STARTTLS injection

On 22. Jun 2021, at 11.11, li...@lazygranch.com wrote: > >> Vulnerability Details: >> >> On-path attacker could inject plaintext commands before STARTTLS >> negotiation that would be executed after STARTTLS finished with the >> client. Only the SMTP submission service is affected. > > Centos 7

Re: Dovecot v2.3.15 released

Hi, > On 21. Jun 2021, at 15.19, Laura Steynes wrote: > > I know I'm blonde so might be silly question, but this libsystemd dependency, > does this mean dovecot need it mandatory even if we do not use a systemd > infected OS ? Or is it only needed if we use one of those systemd infected >

[Dovecot-news] CVE-2021-33515: SMTP Submission service STARTTLS injection

Open-Xchange Security Advisory 2021-06-21 Product: Dovecot Vendor: OX Software GmbH Internal reference: DOV-4583 (Bug ID) Vulnerability type: CWE-74: Failure to Sanitize Data into a Different Plane ('Injection') Vulnerable version: 2.3.0-2.3.14 Vulnerable component: submission Report confidence:

[Dovecot-news] CVE-2021-29157: oauth2 JWT local validation path traversal

Open-Xchange Security Advisory 2021-06-21 Product: Dovecot Vendor: OX Software GmbH Internal reference: DOV-4476 (Bug ID) Vulnerability type: CWE-24: Path Traversal: '../filedir' Vulnerable version: 2.3.11-2.3.14 Vulnerable component: imap, pop3, submission, managesieve Report confidence:

[Dovecot-news] CVE-2020-28200: Sieve excessive resource usage

Open-Xchange Security Advisory 2021-06-21 Product: Dovecot Vendor: OX Software GmbH Internal reference: DOV-4159 (Bug ID) Vulnerability type: CWE-400 Vulnerable version: 1.2.0-2.3.14 Vulnerable component: lmtp, lda Report confidence: Confirmed Solution status: Fixed by Vendor Fixed version:

CVE-2021-33515: SMTP Submission service STARTTLS injection

Open-Xchange Security Advisory 2021-06-21 Product: Dovecot Vendor: OX Software GmbH Internal reference: DOV-4583 (Bug ID) Vulnerability type: CWE-74: Failure to Sanitize Data into a Different Plane ('Injection') Vulnerable version: 2.3.0-2.3.14 Vulnerable component: submission Report confidence:

CVE-2021-29157: oauth2 JWT local validation path traversal

Open-Xchange Security Advisory 2021-06-21 Product: Dovecot Vendor: OX Software GmbH Internal reference: DOV-4476 (Bug ID) Vulnerability type: CWE-24: Path Traversal: '../filedir' Vulnerable version: 2.3.11-2.3.14 Vulnerable component: imap, pop3, submission, managesieve Report confidence:

CVE-2020-28200: Sieve excessive resource usage

Open-Xchange Security Advisory 2021-06-21 Product: Dovecot Vendor: OX Software GmbH Internal reference: DOV-4159 (Bug ID) Vulnerability type: CWE-400 Vulnerable version: 1.2.0-2.3.14 Vulnerable component: lmtp, lda Report confidence: Confirmed Solution status: Fixed by Vendor Fixed version:

Dovecot v2.3.14.1 released

Hi, This is an "important fixes only" release in case you don't want to upgrade to v2.3.15. There is no matching Pigeonhole release - use the same v2.3.14 instead. https://dovecot.org/releases/2.3/dovecot-2.3.14.1.tar.gz

[Dovecot-news] Pigeonhole v0.5.15 released

Hi, Pigeonhole release for Dovecot v2.3.15. One thing we noticed a bit before release is that if you're using imap_sieve_filter plugin, the IMAP FILTER command may trigger the new excessive resource usage check since it can be processing many messages rapidly. You may want to prevent this

Pigeonhole v0.5.15 released

Hi, Pigeonhole release for Dovecot v2.3.15. One thing we noticed a bit before release is that if you're using imap_sieve_filter plugin, the IMAP FILTER command may trigger the new excessive resource usage check since it can be processing many messages rapidly. You may want to prevent this

[Dovecot-news] Dovecot v2.3.15 released

Hi, Here's a new release with some security fixes and quite a lot of other changes as well. https://dovecot.org/releases/2.3/dovecot-2.3.15.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.15.tar.gz.sig

Dovecot v2.3.15 released

Hi, Here's a new release with some security fixes and quite a lot of other changes as well. https://dovecot.org/releases/2.3/dovecot-2.3.15.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.15.tar.gz.sig

Re: Dovecot v2.3.13 reporting (very) incorrect vsize for some maildir folders

On 20. May 2021, at 14.12, Eirik Rye wrote: > > >> On 20 May 2021, at 13:44, Timo Sirainen wrote: >> >> You can also look at the folder-level vsizes to see which one is causing the >> differences (or are they all doubled?) > > In this user's case,

Re: Dovecot v2.3.13 reporting (very) incorrect vsize for some maildir folders

On 20. May 2021, at 13.08, Eirik Rye wrote: > > > >> On 20 May 2021, at 12:31, Aki Tuomi wrote: >> >> Hi! >> >> Quota will count only virtual size of mails (and not directories) and that >> will likely never match with du -bs, which counts for things more than just >> the mail contents. >

Re: Variable expansion in password field (again?!)

On 10. May 2021, at 17.33, Mathias Rabe wrote: > > pass_attrs = > mail=user,userPassword=password,=userdb_mail_crypt_private_password=%w,mailCrypt=userdb_mail_crypt_save_version .. > The users can log-in and everything works fine including the > mail-crypt-plugin until an user password

Re: Dovecot v2.3.13 reporting (very) incorrect vsize for some maildir folders

On 5. May 2021, at 15.42, Eirik Rye wrote: > > Afterwards, for a couple users, we received reports that mail delivery had > failed because they were over quota. When looking into it for a specific > user, we noticed that the vsize reported for a particular folder (with 47k > messages) was

Re: Writing an custom imap command

On 5. May 2021, at 17.28, Ryan Beethe wrote: > You probably shold look some much more simple commands as insipiration. Try looking e.g. how cmd_id is implemented instead. >>> >>> I implemented a simpler command as well, but because it was simple I >>> didn't have any questions :) >>>

Re: huge mdbox broken / Log synchronization error

On 7. May 2021, at 16.16, Florian Lohoff wrote: > > On Fri, May 07, 2021 at 09:17:26AM +0200, Florian Lohoff wrote: >> So i am pretty shure nothing else is accessing this mailbox - This morning >> i opened the screen session and i am here: > > Okay - ran doveadm force-resync and it finished

Re: mdbox / selecting folder accesses hundrets of others

On 8. May 2021, at 13.08, Florian Lohoff wrote: > > On Fri, May 07, 2021 at 06:15:55PM +0200, Florian Lohoff wrote: >> >> Dovecot: 2.3.4 >> >> Hi, >> i am debugging a problem where after a force-resync removed all cache >> files (All files are 44 byte). Trying to open a folder takes literally

Re: systemd integration not working

he later does not work and reverting to "simple" does workOn 2021-04-25 17:53, Aki Tuomi wrote: On 24/04/2021 21:56 Joan Moreau <j...@grosjo.net> wrote:chroot= does not resolve the issueI have "chroot = login" in my conf Thanks!The chroot was needed to get the core dump.C

Re: json_parse_number broken by compiler optimization

On 1. Apr 2021, at 19.14, Josef 'Jeff' Sipek wrote: > > On Wed, Mar 31, 2021 at 11:26:14 -0400, Josef 'Jeff' Sipek wrote: >> On Wed, Mar 31, 2021 at 09:07:28 +0200, Christian Ehrhardt wrote: >>> On Wed, Mar 31, 2021 at 8:46 AM Christian Ehrhardt >>> wrote: On Tue, Mar 30, 2021 at 9:21 PM

Re: feature request: prevent linking of email

On 17. Mar 2021, at 13.39, Marc wrote: > > The reason for copying an email to a different folder is that it is > important. You do not want to loose it, and you want to be able to find it > there. > It is wrong to assume that a user will notice that these emails are missing > and should look

Re: feature request: maintain folder structure with expunged email

On 17. Mar 2021, at 13.39, Marc wrote: > > Feature request: maintain folder/mailbox structure with expunging. You could use lazy_expunge with a namespace. Although it's marked as deprecated, so that might go away at some point. There have been some thoughts about the ability to remember the

Re: JMAP support?

On 8. Mar 2021, at 8.11, Mark Constable wrote: > Two years on so what is the status of JMAP support in Dovecot now? Lots of work, and nobody really seems to want it that much, so we're not actively working on it. There are also some generic optimization and code cleanup steps along the way

Re: invalid vsize-hdr

On 9. Mar 2021, at 23.26, Christopher Wensink wrote:Mar  9 13:29:07 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36Looks like the index file is a bit broken for whatever reason. You could delete it (which would lose flags if you're using dbox) or

Re: doveadm import uninterruptable?

On 16. Feb 2021, at 12.12, Ralf Hildebrandt wrote: > > I'm using > > % doveadm import -u restore@backup.invalid mdbox:/home/archive/mdbox "" > mailbox INBOX header From $PATTERN > > sometimes, I mistype the pattern and immediately try to stop the > doveadm command with CTRL-C - and this never

Re: CVE-2020-24386: IMAP hibernation allows accessing other peoples mail

On 4. Jan 2021, at 14.29, Marc Roos wrote: > > > This also applies when you have users seperated at os level? Yes, that doesn't make a difference. Only whether hibernation is enabled. > -Original Message- > Sent: 04 January 2021 13:03 > To: dovecot-n...@dovecot.org;

Re: Dovecot+Solr+Tika segmentation fault

On 4. Dec 2020, at 9.29, Manuel Josupeit-Walter wrote: > A fix was posted on this list which seems to avoid segfaults when using solr+tika. I reposted it not long ago in response to another question. Before exploring the other segfaults it would be worthwhile getting that

Re: director_username_hash = %d and doveadm director map

On 29. Nov 2020, at 16.10, Ralf Becker wrote: > > To answer my question I was able to identify the director code on Github and > the hashes are the first 4 byte of the binary md5 written as a 32 bit integer. > > With that I was able to write a script that runs doveadm director map, > queries

Re: imap dumping core in libdovecot-storage with assert "(block_count == 0 || block_idx+1 == block_count)"

On 10. Nov 2020, at 15.45, Timo Sirainen wrote: > > On 4. Nov 2020, at 13.24, Renaud Métrich <mailto:rmetr...@redhat.com>> wrote: >> I would like to report an issue which is 100% reproducible with a specific >> mail available in the reproducer attached to Re

Re: imap dumping core in libdovecot-storage with assert "(block_count == 0 || block_idx+1 == block_count)"

On 4. Nov 2020, at 13.24, Renaud Métrich wrote: > I would like to report an issue which is 100% reproducible with a specific > mail available in the reproducer attached to Red Hat's bugzilla >

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:

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)

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 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):

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

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"

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: 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

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: >

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=159731598419071=2 > > OpenBSD's printf functions have a (mostly annoying but occasionally > useful) feature where they generate a syslog entry if printf %s format > is called

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 results &

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

Re: Read-flag of mails don't update

On 10. Jun 2020, at 10.42, Marius Rasch wrote: > > Hi, > > since one or two month I have a problem with Dovecot not updating the > read-flag on mails using IMAP. I receive new mails, but when reading, they > still unread on other devices (but shown as read on the first device). > > When I

Re: mail_crypt crashing randomly during LMTP

On 31. Mar 2020, at 13.47, Timo Sirainen wrote: > > On 29. Mar 2020, at 17.07, Timo Sirainen wrote: >> >>> This is what the log says in the moment of crashing: >>> dovecot: lmtp(53852): Panic: Module context mail_crypt_user_module missing >>> *** b

Re: mail_crypt crashing randomly during LMTP

On 29. Mar 2020, at 17.07, Timo Sirainen wrote: > >> This is what the log says in the moment of crashing: >> dovecot: lmtp(53852): Panic: Module context mail_crypt_user_module missing >> *** backtrace *** (see: https://pastebin.com/YCiFtxmy) > > It shows mailbox_free(

Re: mail_crypt crashing randomly during LMTP

On 30. Mar 2020, at 14.36, Andi Krischer wrote: > >>> This is what the log says in the moment of crashing: >>> dovecot: lmtp(53852): Panic: Module context mail_crypt_user_module missing >>> *** backtrace *** (see: https://pastebin.com/YCiFtxmy) >> >> It shows mailbox_free() in the backtrace, so

Re: mail_crypt crashing randomly during LMTP

On 29. Mar 2020, at 15.15, Andi Krischer wrote: > We have a really strange bug with our dovecot setup. After weeks and month of > debugging we’re finally reached the point when we ask you for help. > > Our basic setup is quite simple: a single dovecot 2.3.10 (0da0eff44) install > on Debian 10

Re: [PATCH] lib-imap: imap-bodystructure: add test with empty header field

On 3. Mar 2020, at 20.38, Simon Ser wrote: > > This causes the body structure to be incorrect. The RFC says it's fine o > have empty header field values. The problem isn't empty header field. It's that the mail is missing Mime-Version header. If that doesn't exist, then the Content-* headers

Re: Auto Subscribe not working for LDA/Sieve created Mailbox?

It should be the same delivery code, but just in case I added also "lmtp / with sieve fileinto box" test and it passes as well. > On 25. Feb 2020, at 15.38, Larry Rosenman wrote: > > This is with lmtp if it matters. > > On Tue, Feb 25, 2020, 7:37 AM Timo Sirainen

Re: Auto Subscribe not working for LDA/Sieve created Mailbox?

On 25. Feb 2020, at 4.55, Larry Rosenman wrote: > > I have auto-subscribe turned on, but I had to doveadm mailbox subscribe to a > LDA/Sieve created mailbox today. > > Did something break? I added a bunch of tests for lda_mailbox_autocreate and lda_mailbox_autosubscribe and they seem to work

Re: [2.3.8] possible replication issue

I think there's a good chance that upgrading both will fix it. The bug already existed in old versions, it just wasn't normally triggered. Since v2.3.8 this situation is triggered on one dsync side, so the v2.3.9 fix needs to be on the other side. > On 5. Dec 2019, at 8.34, Piper Andreas via

Re: Dovecot v2.3.8 released

On 20 Oct 2019, at 11.37, Tom Sommer via dovecot wrote: > >>> This is mail_debug from one of the accounts in question: >>> Oct 18 13:39:37 imap()<7552>: Debug: Mailbox INBOX: >>> Mailbox opened because: SELECT >>> Oct 18 13:39:37 imap()<7552>: Debug: Mailbox INBOX: >>> UID 17854:

Re: Dovecot v2.3.8 released

> On 18 Oct 2019, at 13.43, Tom Sommer via dovecot wrote: > >> I am seeing a lot of errors since the upgrade, on multiple client accounts: >> Info: Connection closed: read(size=7902) failed: Connection reset by >> peer (UID FETCH running for 0.242 + waiting input/output for 108.816 >> secs, 60

Re: Coredump v2.3.8 specific msg fetch, corrupted record in index cache, Broken physical size

On 18 Oct 2019, at 15.36, Erik de Waard via dovecot wrote: > > Hi, i'm getting a coredump on a specific msg, i've attached the gdb. > > file on disk i noticed W= is missing. > 1571209735.M744550P1608.rwvirtual65,S=15886:2,S .. > mail.log > Oct 18 14:41:39 rwvirtual10 dovecot:

Re: BUG: Mailbox renaming algorithm got into a potentially infinite loop, aborting

On 25 Sep 2019, at 17.03, Alex Ha via dovecot mailto:dovecot@dovecot.org>> wrote: > > Hi all! > > I have two dovecot servers with dsync replication over tcp. > Replication works fine except for one user. > > # doveadm replicator status > username

  1   2   3   4   5   6   7   8   9   10   >