Re: The end of Dovecot Director?

On 2022-11-01 16:58, Mark Moseley wrote: This *feels" to me like a parent company looking to remove features from the open source version in order to add feature differentiation to the paid version. I've loved the Dovecot project for over a decade and a half. And incidentally I have a very

Re: The end of Dovecot Director?

To be clear, you are removing the Director... --- Tom On 2022-10-21 13:28, Aki Tuomi wrote: To be clear, we are not removing proxying features from Dovecot either. Just the director ring feature. Aki On 21/10/2022 14:14 EEST Amol Kulkarni wrote: Nginx has an mail proxy for pop, imap,

Re: Monitoring of director back end nodes

On 2021-07-31 19:28, darkc0de wrote: So dovemon for Dovecot pro, but nothing for community? https://github.com/brandond/poolmon --- Tom

Re: Where is dovemon

On 2021-01-13 12:30, li...@mlserv.org wrote: I found this link in the documentation: https://doc.dovecot.org/configuration_manual/dovemon/ But where can I find the program "dovemon"? I searched all over whithout luck. In the source code, Google, nothing. It seems as only the web site

systemctl unit should depend on remote-fs

The shipped systemctl unit file should have "remote-fs.target" added in "After="? -- Tom

shutdown_clients ignored on Director upgrade/restart

When yum updates a Dovecot Director, it restarts all processes - however a few imap-login and pop3-login processes hang because they are still proxying connections. It's like the now orphaned processes are stalled, and needs a kill -9 to die. This is a problem because those stalled

Re: Flush userdb cache entry

On 2020-02-19 10:14, Tom Sommer wrote: I have a problem when users change quota in SQL, the change is not reflected in Dovecot immediately so quota_warning is still triggered on some occasions. I think it's because the quota is stored in userdb, and there is no way to flush userdb cache

Flush userdb cache entry

Hi all I have a problem when users change quota in SQL, the change is not reflected in Dovecot immediately so quota_warning is still triggered on some occasions. I think it's because the quota is stored in userdb, and there is no way to flush userdb cache? Is there a way to flush userdb

Sieve prevents tigger of quota-warning

Hi All I have a few reports from Sieve users, that they are not receiving quota warnings. It appears that when a mailbox is reaching quota, and sieve is responsible for moving mail the mail due to a rule, the quota-warning directive is not triggered? It works fine if Sieve is not part of

Re: v2.3.9 released

On 2019-12-04 11:34, Aki Tuomi via dovecot wrote: + Add lmtp_add_received_header setting. It can be used to prevent LMTP   from adding "Received:" headers. Thank you for this :) -- Tom

Re: About "received" header when using Dovecot proxy

On 2019-12-02 13:42, Riku via dovecot wrote: Hello. My name is Riku. Currently, I use Dovecot as a proxy for another SMTP server. However, this seems to cause the IP address of the "received" header to be that of the proxy server. Is it possible to change this so that the IP address of the

Re: Dovecot v2.3.8 released

On 2019-10-20 11:30, Timo Sirainen via dovecot wrote: On 18 Oct 2019, at 13.43, Tom Sommer via dovecot wrote: Quite a lot of mail downloads for a single session. I wonder if the user really had that many new mails or if they were being redownloaded for some reason? Oct 18 13:40:56 imap

Re: Dovecot v2.3.8 released

On 2019-10-20 11:30, Timo Sirainen via dovecot wrote: 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

Re: Dovecot v2.3.8 released

On 2019-10-18 14:55, Aki Tuomi via dovecot wrote: On 18/10/2019 14:25 Tom Sommer via dovecot wrote: On 2019-10-08 13:18, Aki Tuomi via dovecot wrote: > https://dovecot.org/releases/2.3/dovecot-2.3.8.tar.gz > https://dovecot.org/releases/2.3/dovecot-2.3.8.tar.gz.sig > Binary

Re: Dovecot v2.3.8 released

On 2019-10-18 13:25, 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 B in + 24780576

Re: Dovecot v2.3.8 released

On 2019-10-08 13:18, Aki Tuomi via dovecot wrote: https://dovecot.org/releases/2.3/dovecot-2.3.8.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.8.tar.gz.sig Binary packages in https://repo.dovecot.org/ - imap: SETMETADATA with literal value would delete the metadata value instead of

Re: fts-elastic plugin

On 2019-09-19 10:24, Filip Hanes via dovecot wrote: Hi all, I have recently worked on fts plugin for ElasticSearch. https://github.com/filiphanes/fts-elastic It is forked from fts-elasticsearch as you can see in PR https://github.com/atkinsj/fts-elasticsearch/pull/21 In my opinion

Re: Force dovecot-uidlist reset

Nevermind, the indexes were not deleted correctly - the method described below works :) --- Tom On 2019-09-09 09:45, Tom Sommer via dovecot wrote: Is there a way to force Dovecot to rebuild dovecot-uidlist from zero? It seems deleting all indexes and dovecot-* files followed by "do

Force dovecot-uidlist reset

Is there a way to force Dovecot to rebuild dovecot-uidlist from zero? It seems deleting all indexes and dovecot-* files followed by "doveadm force-resync" is not enough? It just gets the same UIDs? Perhaps from Maildir filenames? But I would like to reset the uid of all mails. Thanks -- Tom

Re: Feature wishlist: Allow to hide client IP/host in submission service

On 2019-08-28 14:07, Timo Sirainen via dovecot wrote: On 25 Aug 2019, at 21.51, Sebastian Krause via dovecot wrote: Hi, In many mail setups a required feature (for privacy reasons) is to hide the host and IP of clients (in the "Received" header) that use the authenticated submission over

Re: Feature wishlist: Allow to hide client IP/host in submission service

On 2019-08-25 20:51, Sebastian Krause via dovecot wrote: Hi, In many mail setups a required feature (for privacy reasons) is to hide the host and IP of clients (in the "Received" header) that use the authenticated submission over port 587. In Postfix that's possible

Re: Dovecot v2.3.7.1 & Pigeonhole v0.5.7.1 released

On 2019-07-23 14:01, Timo Sirainen via dovecot wrote: https://dovecot.org/releases/2.3/dovecot-2.3.7.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.7.1.tar.gz.sig https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.7.1.tar.gz

Re: Dovecot release v2.3.7

On 2019-07-16 09:46, Timo Sirainen via dovecot wrote: > On 13 Jul 2019, at 14.44, Tom Sommer via dovecot wrote: > >> LMTP is broken on director: >> >> Jul 13 13:42:41 lmtp(34824): Panic: file smtp-params.c: line 685 >> (smtp_params_mail_add_body_to_ev

Re: Dovecot release v2.3.7

On 2019-07-13 13:44, Tom Sommer via dovecot wrote: LMTP is broken on director: Jul 13 13:42:41 lmtp(34824): Panic: file smtp-params.c: line 685 (smtp_params_mail_add_body_to_event): assertion failed: ((caps & SMTP_CAPABILITY_8BITMIME) != 0) Jul 13 13:42:41 lmtp(34824): Error: Raw backt

Re: Dovecot release v2.3.7

Can you please put dovecot-2.3.6-2.x86_64 back in the repo so we can downgrade? --- Tom On 2019-07-12 14:29, Aki Tuomi via dovecot wrote: Hi! We are pleased to release Dovecot release v2.3.7. Tarball is available at https://dovecot.org/releases/2.3/dovecot-2.3.7.tar.gz

Re: Dovecot release v2.3.7

LMTP is broken on director: Jul 13 13:42:41 lmtp(34824): Panic: file smtp-params.c: line 685 (smtp_params_mail_add_body_to_event): assertion failed: ((caps & SMTP_CAPABILITY_8BITMIME) != 0) Jul 13 13:42:41 lmtp(34824): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xdf06a)

Re: Orphaned processes after doveadm log reopen

On 2019-07-09 07:37, Aki Tuomi wrote: On 8.7.2019 14.54, Tom Sommer via dovecot wrote: On 2019-07-08 13:36, Tom Sommer via dovecot wrote: I rotate logs every night on my Director, running "doveadm log reopen" It happens on "/etc/init.d/dovecot restart", not "do

Re: Orphaned processes after doveadm log reopen

On 2019-07-08 13:36, Tom Sommer via dovecot wrote: I rotate logs every night on my Director, running "doveadm log reopen" It happens on "/etc/init.d/dovecot restart", not "doveadm log reopen" - sorry So it happens when you run killproc on dovecot --- Tom

Re: Orphaned processes after doveadm log reopen

On 2019-07-08 13:36, Tom Sommer via dovecot wrote: I rotate logs every night on my Director, running "doveadm log reopen" I've noticed a problem with processes not closing correctly, they can be open for days and cause corrupt index files because they are connected to different ba

Orphaned processes after doveadm log reopen

I rotate logs every night on my Director, running "doveadm log reopen" I've noticed a problem with processes not closing correctly, they can be open for days and cause corrupt index files because they are connected to different backends (so it writes to the wrong server when the process

Re: Frequent Out of Memory for service(config)

On 2019-05-13 21:56, Root Kev via dovecot wrote: Hello Group, We have dovecot deployed as solely a Pop3 service that is used by our applications to pass mail from one application to another internally. We have roughly 4 applications that connect to the Pop3 service every 2 seconds, to

Re: [Dovecot] Dovecot LDA/LMTP vs postfix virtual delivery agent and the x-original-to header

On 2019-04-19 15:26, Aki Tuomi via dovecot wrote: Unfortunately we have quite long list of things to do, so sometimes even trivial things can take a long time. Not to hijack the thread, but perhaps you could elaborate on what has changed within Dovecot? Timo seems to be put in the

Re: quota-service with Director - A workaround

On 2019-03-21 10:28, Sami Ketola via dovecot wrote: On 20 Mar 2019, at 18.17, Tom Sommer via dovecot wrote: On 2019-03-20 16:40, Sami Ketola via dovecot wrote: On 20 Mar 2019, at 17.13, Tom Sommer via dovecot wrote: I realize quota-service on Director is not supported, which is a shame

Re: quota-service with Director - A workaround

On 2019-03-20 16:40, Sami Ketola via dovecot wrote: On 20 Mar 2019, at 17.13, Tom Sommer via dovecot wrote: I realize quota-service on Director is not supported, which is a shame. As a workaround I'm thinking of setting up quota-service on one of my backend nodes, and have all my

quota-service with Director - A workaround

I realize quota-service on Director is not supported, which is a shame. As a workaround I'm thinking of setting up quota-service on one of my backend nodes, and have all my Postfix services ask this one node for the quota status. This sort of defeats the purpose of the Director (having

Re: [ext] Dovecot Wiki: Please disable edit on double click

On 2019-03-20 12:02, Aki Tuomi via dovecot wrote: On 20.3.2019 12.59, Ralf Hildebrandt via dovecot wrote: * Michael Goth via dovecot : could you maybe disable the 'edit on doubleclick' feature on wiki2.dovecot.org? Everytime I try to select a word by double clicking on it, I end up in

Director 2.3.5: openssl_iostream_handle_error

Thanks for 2.3.5 - it fixed a lot of stuff :) I see this Panic in my Director logs now, randomly and rarely: Mar 07 11:01:29 pop3-login: Panic: file iostream-openssl.c: line 586 (openssl_iostream_handle_error): assertion failed: (errno != 0) Mar 07 11:01:29 auth: Warning: auth client 13625

Re: Request: option to hide user IP/HELO content from mail sent via submissiond

On 2018-10-19 18:55, Lee Maguire wrote: For reasons of user privacy and security I usually configure submission servers to not include accurate IP address and HELO information of authenticated users. (Usually replacing it with a private-use domain / IPv6 address.)

Re: Calendar function ?

On 2018-10-22 19:58, Dave Stevens wrote: On Mon, 22 Oct 2018 19:48:17 +0200 Tom Sommer wrote: On 2018-10-22 12:56, María Arrea wrote: > We use sabredav for caldav+cardav and roundcube+agendav for nice > web ui :) Is Sabre still maintained? http://sabre.io/ says 2018 is most

Re: Calendar function ?

On 2018-10-22 12:56, María Arrea wrote: We use sabredav for caldav+cardav and roundcube+agendav for nice web ui :) Is Sabre still maintained?

Re: VOLATILEDIR not really used?

On 2018-10-05 21:56, Timo Sirainen wrote: Looks like it works. But could you: 1) Add it to github as merge request Done, for the first part of the code. 2) MAILBOX_LIST_PATH_TYPE_VOLATILEDIR might be useful, but it's kind of a separate change of its own. To simplify, in Maildir code you

Re: VOLATILEDIR not really used?

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

Re: VOLATILEDIR not really used?

On 2018-10-05 11:35, Timo Sirainen wrote: 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 dotlocks? I guess mbox

Re: VOLATILEDIR not really used?

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 dotlocks? I guess mbox and Maildir have some locks that could be moved there, but a better performance

VOLATILEDIR not really used?

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? Is this correct, and if so are there any plans to move dotlocks etc. to this directory? Thanks. -- Tom

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

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.ostream.stream_errno != 0 ||

Re: Adding namespace alias_for causes index resync?

On 2018-09-12 16:54, Tom Sommer wrote: I just added a new namespace-alias with alias_for. Apparently this causes all mailbox indexes to be resynced? Is this intentional and/or is there some way to avoid this? My NFS storage pretty much kills itself when hundreds of thousands of users needs

Adding namespace alias_for causes index resync?

I just added a new namespace-alias with alias_for. Apparently this causes all mailbox indexes to be resynced? Is this intentional and/or is there some way to avoid this? My NFS storage pretty much kills its elf when hundreds of thausands of users needs to resync indexes :) Thanks -- Tom

Disconnects on Director

Hi I am seeing a lot of clients time out on my Director. I'm wondering if this is "normal" or there is some opportunity to tweak something? Log line: imap-login: Info: proxy(u...@example.com): disconnecting 1.2.3.4 (Disconnected by client: read(size=433) failed: Connection timed out(37s

Re: Is the Doveadm HTTP API considered stable for production use?

On 2018-08-22 11:55, James Beck wrote: Hi, I'm running 2.2.34 in production (installed from Debian stretch backports) and want to rework some scripts. Can the HTTP API be considered stable in 2.2.34 please? I use it in 2.3 and it works just fine :) I might have used it in 2.2 as well, I'm

allow_nets based on RBL

This was brought up in 2014, and left without conclusion, so I thought it would be time to bump it :) I would love a way to do allow_nets based on an RBL check, could this be added to the feature-list? https://wiki2.dovecot.org/PasswordDatabase/ExtraFields/AllowNets Thanks -- Tom

imap-login: Error: BUG: Authentication server sent unknown id

I randomly get these errors on my Director Aug 17 10:52:37 imap-login: Error: BUG: Authentication server sent unknown id 98448 Aug 17 10:52:37 imap-login: Warning: Auth connection closed with 2 pending requests (max 2 secs, pid=27036, Received broken input: FAIL 98448 user=u...@example.com)

lmtp 2.3.2.1 segfault with backtrace

lmtp on Director crash with 2.3.2.1 # gdb /usr/libexec/dovecot/lmtp /var/core/60174 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are

Re: Set X-Original-To based an ORCPT?

On 2018-08-07 13:07, Marco Giunta wrote: Hi, to get a 'Delivered-to' header based on ORCPT, I wrote a patch (attached) to force Dovecot lmtp to advertise DSN after a LHLO command. In this way, Postfix add an ORCPT to the RCTP command

Re: Set X-Original-To based an ORCPT?

On 2015-09-02 22:01, Peer Heinlein wrote: Since http://dovecot.org/pipermail/dovecot-cvs/2014-November/025241.html Dovecot's LMTP does support ORCPT. Is it possible to set X-Original-To-Header based on that ORCPT? Any news or response on this? I too am in need of this header being passed

Re: [Dovecot] quota-status not working in distributed environment

On 2013-06-16 21:46, Timo Sirainen wrote: On 14.6.2013, at 9.15, Benoit Panizzon wrote: Is there a way to get quota-status to also use the proxy feature to request the quota information from the correct machine? Looks like this is a missing feature. I first thought quota-status would go

Re: v2.3.2.1 released

On 2018-07-10 13:17, Timo Sirainen wrote: 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: - SSL

Re: v2.3.2.1 released

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: - SSL/TLS servers may have crashed during client disconnection - lmtp: With

Re: 2.3.2 director imap-login segfaults

On 2018-07-06 10:30, Timo Sirainen wrote: 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

Re: 2.3.2 director imap-login segfaults

ailable. --- Tom On 2018-07-05 15:43, Aki Tuomi wrote: > Can you install debuginfo and try again? > > --- > Aki Tuomi > Dovecot oy > > Original message > From: Tom Sommer > Date: 05/07/2018 14:12 (GMT+01:00) > To: Dovecot > Subject: 2.3.2 director imap-

2.3.2 director imap-login segfaults

My director has started segfaulting since upgradeing to 2.3.2: # gdb /usr/libexec/dovecot/imap-login ./core.9757 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

Re: v2.3.2 released

On 2018-06-29 16:00, Timo Sirainen wrote: 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 v2.2.36

Re: v2.3.2 released

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 v2.2.36, as well as a bunch of other fixes (mainly for v2.3-only bugs). Binary packages

Re: v2.3.2 released

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 in https://repo.dovecot.org/ A simple "yum update" will result in a ton of these

More and better logging

In general I feel there is a lack of debug and "when things go wrong"-logging in Dovecot (information that should perhaps be provided with a verbose toggle). I was debugging problems with sasl user logins and a generic "SASL CRAM-MD5 authentication failed: Connection lost to authentication

2.3.1: Core dump on quota reach

Just upgraded from 2.2.34 to 2.3.1: Jun 12 16:06:38 lmtp(exam...@example.name)<46176><8JrHEW7TH1tgtAAAd9aEAw>: Info: msgid=: save failed to INBOX: The email account that you tried to reach is over quota (Mailbox is full). Jun 12 16:06:38

Auth cache prevents login when non-password fields change

The auth cache contains all fields returned by "password_query" (in itself a little odd), including the fields "nologin" and "reason". If a user is cached with "nologin=Y" and the database-source is changed so nologin condition is no longer true, then the cache prevents login for as long as

Re: Package repository now available

for this. Awesome! When do you push the packages? Sometimes you do re-releases of the source tarballs if minor bugs are found, so I'm wondering if it would make sense to wait 1 week to release rpms? So you don't yum-autoupdate all installations with possibly faulty releases? Thanks again. -- Tom Sommer

Re: NOTIFY broken in 2.2.31?

On 2017-06-30 17:09, Timo Sirainen wrote: On 29 Jun 2017, at 13.27, Bojan Smojver wrote: Hi, I just updated my Dovecot to the new build in Fedora 26, which is based on 2.2.31. After I did that, Evolution (3.24.3) is no longer receiving notifications about new mail in

Re: v2.2.30.1 released

On 2017-06-05 15:10, Tom Sommer wrote: On 2017-05-31 15:24, Timo Sirainen wrote: https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz.sig Due to some release process changes I didn't notice that one important bugfix wasn't included

Re: v2.2.30.1 released

On 2017-05-31 15:24, Timo Sirainen wrote: https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz.sig Due to some release process changes I didn't notice that one important bugfix wasn't included in the v2.2.30 release branch before I

Re: v2.2.30.1 released

On 2017-05-31 15:24, Timo Sirainen wrote: https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz.sig Due to some release process changes I didn't notice that one important bugfix wasn't included in the v2.2.30 release branch before I

Re: lmtp segfault after upgrade

On 2017-05-19 08:41, Timo Sirainen wrote: On 2 May 2017, at 11.19, Timo Sirainen <t...@iki.fi> wrote: On 2 May 2017, at 10.41, Tom Sommer <m...@tomsommer.dk> wrote: (gdb) bt full #0 i_stream_seek (stream=0x21, v_offset=0) at istream.c:298 _stream = #1 0x

Re: lmtp segfault after upgrade

--- Tom On 2017-05-18 10:05, Teemu Huovila wrote: On 18.05.2017 10:55, Tom Sommer wrote: On 2017-05-18 09:36, Teemu Huovila wrote: Hello Tom On 02.05.2017 11:19, Timo Sirainen wrote: On 2 May 2017, at 10.41, Tom Sommer <m...@tomsommer.dk> wrote: (gdb) bt full #0 i_stream_seek (

Re: lmtp segfault after upgrade

On 2017-05-18 09:36, Teemu Huovila wrote: Hello Tom On 02.05.2017 11:19, Timo Sirainen wrote: On 2 May 2017, at 10.41, Tom Sommer <m...@tomsommer.dk> wrote: (gdb) bt full #0 i_stream_seek (stream=0x21, v_offset=0) at istream.c:298 _stream = #1 0x7fe983

Re: lmtp segfault after upgrade

On 2017-05-18 09:36, Teemu Huovila wrote: Hello Tom On 02.05.2017 11:19, Timo Sirainen wrote: On 2 May 2017, at 10.41, Tom Sommer <m...@tomsommer.dk> wrote: (gdb) bt full #0 i_stream_seek (stream=0x21, v_offset=0) at istream.c:298 _stream = #1 0x7fe983

Re: lmtp segfault after upgrade

On 2017-05-02 09:35, Aki Tuomi wrote: On 2017-05-02 10:20, Tom Sommer wrote: On 2017-05-01 19:26, Aki Tuomi wrote: On May 1, 2017 at 8:21 PM Tom Sommer <m...@tomsommer.dk> wrote: I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg and /var/log/messages are g

Re: lmtp segfault after upgrade

On 2017-05-01 19:26, Aki Tuomi wrote: On May 1, 2017 at 8:21 PM Tom Sommer <m...@tomsommer.dk> wrote: I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg and /var/log/messages are getting flooded by these errors: lmtp[45758]: segfault at 21 ip 7fb412d3a

Re: lmtp segfault after upgrade

On 2017-05-01 19:34, Aki Tuomi wrote: On May 1, 2017 at 8:26 PM Aki Tuomi <aki.tu...@dovecot.fi> wrote: > On May 1, 2017 at 8:21 PM Tom Sommer <m...@tomsommer.dk> wrote: > > > I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg > and /var/log/m

lmtp segfault after upgrade

I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg and /var/log/messages are getting flooded by these errors: lmtp[45758]: segfault at 21 ip 7fb412d3ad11 sp 7ffe83ad2df0 error 4 in libdovecot.so.0.0.0[7fb412c95000+11c000] lmtp[46304]: segfault at 91 ip

dsync with namespaces

I have a major dsync headache which I am hoping someone can help me with. I have to migrate mails from a 'namespace/inbox/prefix=INBOX.' server to a 'namespace/inbox/prefix=' server. So I'm trying # dsync -o 'namespace/inbox/prefix=' sync -1 -f -u x...@xx.com tcp:1.2.3.4 It works fine for

Custom cache_key for passdb-sql

The cache_key for the SQL-passdb should be created automatically, but for some reason the service (%s) is not part of the key, and I need it to be I've tried to set a manual cache_key, but that fails: Mar 15 11:54:02 auth: Fatal: sql /etc/dovecot/dovecot-sql.conf cache_key=%s%u%{real_ip}:

Re: v2.2.28 released

On 2017-02-24 14:34, Timo Sirainen wrote: http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig Are there any plans to do a bugfix-release, that includes the few issues seen in the mailing-list, or do you consider 2.2.28 safe to

Re: quota-warning: possible to have size also?

On 2017-03-05 19:13, dovecot@avv.solutions wrote: I have a questions though: when running the warning script, the example foundis it possible to pass the *quota size *as argument also? This would be useful with per-user quota. e.g. /some/script xx% username *xxxbytes* (order is not relevant

Re: Director+NFS Experiences

On 2017-02-27 10:40, Sami Ketola wrote: On 24 Feb 2017, at 21.28, Mark Moseley wrote: Attached. No claims are made on the quality of my code :) With recent dovecots you probably should not use set_host_weight( server, '0’ ) to mark backend down but instead should use

Re: Changes to userdb not picked up

I know, but I'm changing the quota in dict:sql so running commands on the mailserver itself it something I would like to avoid. --- Tom On 2017-02-06 14:29, Urban Loesch wrote: You can flush the cache with: "doveadm auth cache flush $USER" Regards Urban Am 06.02.2017 um 13:59 s

Changes to userdb not picked up

I have my quota limits stored in userdb and auth_cache enabled (default settings). When I change the quota limit the old limit is still cached for the user for another hour. Is there any way to prevent this from happening? Thanks -- Tom

Auth cache does not take %real_rip into account

I run a Director setup with a webmail in front, the webmail is in login_trusted_networks and sends IMAP-ID x-original-ip to log the client IP. If I enable auth_debug on the director, I see that the cache key contains the client IP, and not the %real_rip. This is causing problems because in

Re: Quota count does not work with lock_method=dotlock

On 2017-01-24 10:25, Aki Tuomi wrote: On 24.01.2017 11:13, Tom Sommer wrote: On 2017-01-18 15:27, mkli...@gmx.de wrote: dovecot crashes when I switch the quota tracking from dict to count. I have the same problem, but I use 'dict:file' as quota backend - Maybe the error is due

Re: Quota count does not work with lock_method=dotlock

On 2017-01-18 15:27, mkli...@gmx.de wrote: dovecot crashes when I switch the quota tracking from dict to count. I have the same problem, but I use 'dict:file' as quota backend - Maybe the error is due to quota_vsizes and not 'count'. // Tom Sommer

Re: Poolmon: Problem with index-locking

On 2017-01-10 22:34, Timo Sirainen wrote: On 10 Jan 2017, at 20.38, Tom Sommer <m...@tomsommer.dk> wrote: I have Poolmon (https://github.com/brandond/poolmon) set up. When it does all the checks concurrently, obviously there are locking issues on each mailserver it tests: &q

Poolmon: Problem with index-locking

I have Poolmon (https://github.com/brandond/poolmon) set up. When it does all the checks concurrently, obviously there are locking issues on each mailserver it tests: "Warning: Locking transaction log file /indexes/dovecot.list.index.log took 60 seconds (syncing)" It's just an empty

Index-cache sizes

I had a customer with an INBOX cache of 400MB+ (5.5GB maildir) which gave me "Error: mmap_anon(474165248) failed: Cannot allocate memory" errors, then I deleted the cache files and ran 'doveadm index -u x...@example.com "*"', now the INBOX cache is 7MB What is up with that? Is the cache now

Re: Errors with count:User quota and NFS

On 2016-11-01 09:47, Tom Sommer wrote: On 2016-10-31 22:04, Timo Sirainen wrote: Oct 31 10:52:37 imap(x...@.xx): Warning: Locking transaction log file /mnt/nfs/xxx.xx/xxx/indexes/dovecot.list.index.log took 31 seconds (syncing) Oct 31 10:52:37 imap(x...@xxx.xx): Warning: Locking

2.2.26.0: Error: redis: Unexpected input (state=0): -ERR max number of clients reached

I use redis as quota backend (currently). After upgrading to 2.2.26.0 I see a ton of "Error: redis: Unexpected input (state=0): -ERR max number of clients reached" errors. It looks like either more Redis connections are being made, or Redis connections don't time out/are reused correctly

Re: Errors with count:User quota and NFS

On 2016-10-31 22:04, Timo Sirainen wrote: Oct 31 10:52:37 imap(x...@.xx): Warning: Locking transaction log file /mnt/nfs/xxx.xx/xxx/indexes/dovecot.list.index.log took 31 seconds (syncing) Oct 31 10:52:37 imap(x...@xxx.xx): Warning: Locking transaction log file

Re: Errors with count:User quota and NFS

On 2016-10-31 11:01, Tom Sommer wrote: I upgraded to 2.2.26.0 and enabled count as quota backend, expecting the recent fixes to allow me to use the backend, however I get the following errors: It just occured to me, that the reason for the locking/errors may be, that it is big mailboxes being

Errors with count:User quota and NFS

I upgraded to 2.2.26.0 and enabled count as quota backend, expecting the recent fixes to allow me to use the backend, however I get the following errors: Oct 31 10:52:13 imap(x...@.xx): Error: Transaction log file /mnt/nfs/.xx/xxx/indexes/dovecot.list.index.log: marked corrupted Oct

Re: Change dovecot hostname

Removing the headers entirely was discussed: http://dovecot.markmail.org/search/?q=received#query:received+page:1+mid:t4utsjcionjcfwce+state:results Don't know if it was forgotten for 2.3, but hope not :) --- Tom On 2016-08-22 15:14, Scott W. Sander wrote: Here are some example headers from

Header's corrupted flag is set

I have a ton of these errors in my logs: Aug 11 14:16:04 imap(x...@x.): Error: Corrupted index file./dovecot.list.index: Header's corrupted flag is set Does Dovecot not automatically fix these? Or what is the correct action to take? -- Tom

  1   2   >