- dovecot - dovecot.org

Looks like a bug to me: Dovecot ignores Maildir/new timestamp
by Fredrik Roubert 01 Dec '15

01 Dec '15

Hello! I run Debian jessie and have an issue with the interaction between Dovecot (2.2.13), Mutt (1.5.23) and the Android Gmail (5.8.105868218) IMAP client, when using Maildir: I use Dovecot LMTP for local delivery into Maildir and access these files both through Dovecot IMAP from the Android Gmail IMAP client and also directly through the filesystem by running Mutt locally on the mail server. When a new mail arrives, Dovecot LMTP will add a new file in Maildir/new and also update the Dovecot index cache. If I then open Mutt and just delete this new message, then Mutt will just delete this file from Maildir/new and the Dovecot index cache will be out-of-sync. (For testing, Mutt can be cut out of the equation entirely by instead just running "rm Maildir/new/*" from the command line to mimic what Mutt does when deleting a new message, but I mention the use of Mutt here to show why this is a real use-case for me.) If I after this open the Gmail app and pull down the message index to refresh from the Dovecot IMAP server, it'll get the cached version of the index, in which the new message is still present (but only the headers, no body will be loaded and the app will show no body snippet). Pulling down the message index again to force a second refresh will cause the new/deleted message to disappear again. This seems to be caused by Dovecot not looking at the Maildir/new timestamp to determine whether the index cache is up-to-date, but instead only looking at the Maildir/cur timestamp. If I instead repeat all these testing steps from the beginning, sending a new mail message, deleting it with "rm Maildir/new/*" but then also running "touch Maildir/cur" before opening the Gmail app and doing the refresh, then Dovecot does update the cache and does not send any ghost messages to the IMAP client. It does seem reasonable to me that Mutt doesn't touch Maildir/cur when just deleting new messages and I suspect that it might be a bug in Dovecot that it timestamp of Maildir/new isn't checked and the index cache updated if that timestamp is newer than the last index update done by the Dovecot LMTP service. Does this analysis seem sound? Did I miss anything? (Output of "doveconf -n" attached.) Cheers // Fredrik Roubert -- Forsterstrasse 64 | +41 78 8170377 CH-8044 Zürich | https://roubert.name/fredrik/

3 2

Sieve, shared folders, different daemons
by Frido Otten 01 Dec '15

01 Dec '15

Hi, In our dovecot setup we use 3 different config files. One for maildropping(sieve), one for dovecot/imap on standard ports with ssl config and one for dovecot/imap on standard ports+1 with a different ssl certificate. Currently the client using the standard port+1 config wants to make use of shared folders, but the thing is that the current namespace separator in all configs is '.'. This is conflicting with shared folders. Can we simply run one of the dovecot/imap daemons configured with a different separator and shared folders without having impact on sieve and the current connected users to the standard ports? Regards, Frido

2 2

How to delete "proxy" attribute in passdb lookup?
by Peer Heinlein 29 Nov '15

29 Nov '15

Hi, I have a complicated SQL backend with stored procedures to generate passdb/userdb queries. This result have the proxy-attribute set and it's very complicated to change that procedures. On one system I tried to override/delete the proxy attribute: passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf.ext override_fields = proxy=n } Looks like that doesn't work. "proxy" is always set. doveadm auth lookup username passdb: username user : username host : mailserver proxy hostip : xx.xx.xx.xx Is there any way to override/delete an existing true/false attribute like "proxy"? Peer -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

2 3

Connection between postfix and dovecot failing
by Sytse Kuijk 29 Nov '15

29 Nov '15

Hi all, Hope someone has been here and done that before. I am running a Mac mini with OSX server version 10.5, that is on El Capitan, but the problem I have started on Yosemite (the previous version) and did not change at all in the upgrade (I had hoped it would have solved itself). As you might know, OSX server uses postfix and dovecot as mailing engines, good choice. Since we suffered a short power outage a little over a week ago, the mail has failed in delivering messages to the local mailboxes. We can send mail out, check the mailboxes (they never change right now),etc. but incoming mail was first just not delivered and after a week warning are sent back to the senders, telling there is a temporary problem (hope that this message is right and I can solve the issue). What seems to go wrong is that postfix cannot connect to the local MTA. The error message that appears in several places is: recipient=ann.cools(a)surikata.be offset=769 dsn_orig_rcpt=rfc822;ann.cools(a)surikata.be status=4.4.1 action=delayed reason=delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused I find all sorts of explanations and cures, but none work up to now. I tried to find lock files that might be blocking, deleted some files ending in lck with zero size, with no result. I tried to switch off the spam/virus/junk features, no difference (some mail said that messages in the queue will not get through, but new ones would. Not so, not a single message up to now). I also get alerts in the Server application, warning that: An unassigned mail directory has been detected and is scheduled to be deleted. The unassigned mail directory located in: /Library/Server/Mail/Data/mail/702C16A8-6B2D-42D8-9362-659DD2949AFC is not associated with any user account and is scheduled to be deleted in 1 days. In the mean time no mail, and unfortunately, we need it badly. Any suggestions? Million thanks for your kind support. sytse -- ------------------------------------------ - Sytse Kuijk - ___ - R.S.R. n.v. - o|o - Gijzelaarsstraat 16 - \_____(.)_____/ - 2000 Antwerpen - - GSM: +32 468 20 00 00 - ___ - Phone: +32 3 216 4328 - o|o - E-mail: sytse(a)pobox.com <mailto:sytse@pobox.com> - \_____(.)_____/ ------------------------------------------ iThink therefore iMac

2 1

Re: Connection between postfix and dovecot failing
by Sytse Kuijk 28 Nov '15

28 Nov '15

Well, post fix tries, but cannot connect. Sounds to me like problem at the receiving side. In any case, one question would be: is amavis part of dovecot or of postfix? sytse -- ------------------------------------------ - Sytse Kuijk - ___ - R.S.R. n.v. - o|o - Gijzelaarsstraat 16 - \_____(.)_____/ - 2000 Antwerpen - - GSM: +32 468 20 00 00 - ___ - Phone: +32 3 216 4328 - o|o - E-mail: sytse(a)pobox.com - \_____(.)_____/ ------------------------------------------ iThink therefore iMac > On 28 nov. 2015, at 22:24, Edgar Pettifogging <edgar(a)pettijohn-web.com> wrote: > > This should probably move to postfix list. Doesn't look like dovecot gets a chance to deliver. > > Sent from my iPhone > >> On Nov 28, 2015, at 11:34 AM, Sytse Kuijk <sytse(a)pobox.com> wrote: >> >> Well, I tried that. I can connect a telnet session on that port and that does not refuse the connection, it sits there waiting, but I do not know the protocol so I cannot check if it does what it is supposed to. >> >> I also checked who is listening on that port, here is the dialog: >> >> sh-3.2# sudo lsof -i -n -P | grep 10024 >> perl5.18 75844 _amavisd 5u IPv4 0x866f6119e39f833d 0t0 TCP 127.0.0.1:10024 (LISTEN) >> perl5.18 75844 _amavisd 6u IPv6 0x866f6119e03f253d 0t0 TCP [::1]:10024 (LISTEN) >> >> looks sort of correct to me… >> >> sytse >> >> -- >> >> ------------------------------------------ >> - Sytse Kuijk - ___ >> - R.S.R. n.v. - o|o >> - Gijzelaarsstraat 16 - \_____(.)_____/ >> - 2000 Antwerpen - >> - GSM: +32 468 20 00 00 - ___ >> - Phone: +32 3 216 4328 - o|o >> - E-mail: sytse(a)pobox.com - \_____(.)_____/ >> ------------------------------------------ >> >> iThink therefore iMac >> >>> On 28 nov. 2015, at 18:31, Edgar Pettifogging <edgar(a)pettijohn-web.com> wrote: >>> >>> I would bet that whatever is listening at 127.0.0.1 port 10024 didn't get restarted when the power came back on. Amavis perhaps or another proxy server of some sort. >>> >>> Sent from my iPhone >>> >>>> On Nov 28, 2015, at 11:14 AM, Sytse Kuijk <sytse(a)pobox.com> wrote: >>>> >>>> Hi all, >>>> >>>> Hope someone has been here and done that before. >>>> I am running a Mac mini with OSX server version 10.5, that is on El Capitan, but the problem I have started on Yosemite (the previous version) and did not change at all in the upgrade (I had hoped it would have solved itself). >>>> >>>> As you might know, OSX server uses postfix and dovecot as mailing engines, good choice. >>>> Since we suffered a short power outage a little over a week ago, the mail has failed in delivering messages to the local mailboxes. >>>> We can send mail out, check the mailboxes (they never change right now),etc. but incoming mail was first just not delivered and after a week warning are sent back to the senders, telling there is a temporary problem (hope that this message is right and I can solve the issue). >>>> >>>> What seems to go wrong is that postfix cannot connect to the local MTA. The error message that appears in several places is: >>>> >>>> recipient=ann.cools(a)surikata.be >>>> offset=769 >>>> dsn_orig_rcpt=rfc822;ann.cools(a)surikata.be >>>> status=4.4.1 >>>> action=delayed >>>> reason=delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused >>>> >>>> I find all sorts of explanations and cures, but none work up to now. >>>> I tried to find lock files that might be blocking, deleted some files ending in lck with zero size, with no result. >>>> I tried to switch off the spam/virus/junk features, no difference (some mail said that messages in the queue will not get through, but new ones would. Not so, not a single message up to now). >>>> I also get alerts in the Server application, warning that: >>>> >>>> An unassigned mail directory has been detected and is scheduled to be deleted. >>>> >>>> The unassigned mail directory located in: >>>> /Library/Server/Mail/Data/mail/702C16A8-6B2D-42D8-9362-659DD2949AFC >>>> is not associated with any user account and is scheduled to be deleted in 1 days. >>>> >>>> In the mean time no mail, and unfortunately, we need it badly. >>>> >>>> Any suggestions? >>>> >>>> Million thanks for your kind support. >>>> >>>> sytse >>>> -- >>>> ------------------------------------------ >>>> - Sytse Kuijk - ___ >>>> - R.S.R. n.v. - o|o >>>> - Gijzelaarsstraat 16 - \_____(.)_____/ >>>> - 2000 Antwerpen - >>>> - GSM: +32 468 20 00 00 - ___ >>>> - Phone: +32 3 216 4328 - o|o >>>> - E-mail: sytse(a)pobox.com <mailto:sytse@pobox.com> - \_____(.)_____/ >>>> ------------------------------------------ >>>> >>>> iThink therefore iMac

2 1

Re: Connection between postfix and dovecot failing
by Sytse Kuijk 28 Nov '15

28 Nov '15

Well, I tried that. I can connect a telnet session on that port and that does not refuse the connection, it sits there waiting, but I do not know the protocol so I cannot check if it does what it is supposed to. I also checked who is listening on that port, here is the dialog: sh-3.2# sudo lsof -i -n -P | grep 10024 perl5.18 75844 _amavisd 5u IPv4 0x866f6119e39f833d 0t0 TCP 127.0.0.1:10024 (LISTEN) perl5.18 75844 _amavisd 6u IPv6 0x866f6119e03f253d 0t0 TCP [::1]:10024 (LISTEN) looks sort of correct to me… sytse -- ------------------------------------------ - Sytse Kuijk - ___ - R.S.R. n.v. - o|o - Gijzelaarsstraat 16 - \_____(.)_____/ - 2000 Antwerpen - - GSM: +32 468 20 00 00 - ___ - Phone: +32 3 216 4328 - o|o - E-mail: sytse(a)pobox.com - \_____(.)_____/ ------------------------------------------ iThink therefore iMac > On 28 nov. 2015, at 18:31, Edgar Pettifogging <edgar(a)pettijohn-web.com> wrote: > > I would bet that whatever is listening at 127.0.0.1 port 10024 didn't get restarted when the power came back on. Amavis perhaps or another proxy server of some sort. > > Sent from my iPhone > >> On Nov 28, 2015, at 11:14 AM, Sytse Kuijk <sytse(a)pobox.com> wrote: >> >> Hi all, >> >> Hope someone has been here and done that before. >> I am running a Mac mini with OSX server version 10.5, that is on El Capitan, but the problem I have started on Yosemite (the previous version) and did not change at all in the upgrade (I had hoped it would have solved itself). >> >> As you might know, OSX server uses postfix and dovecot as mailing engines, good choice. >> Since we suffered a short power outage a little over a week ago, the mail has failed in delivering messages to the local mailboxes. >> We can send mail out, check the mailboxes (they never change right now),etc. but incoming mail was first just not delivered and after a week warning are sent back to the senders, telling there is a temporary problem (hope that this message is right and I can solve the issue). >> >> What seems to go wrong is that postfix cannot connect to the local MTA. The error message that appears in several places is: >> >> recipient=ann.cools(a)surikata.be >> offset=769 >> dsn_orig_rcpt=rfc822;ann.cools(a)surikata.be >> status=4.4.1 >> action=delayed >> reason=delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused >> >> I find all sorts of explanations and cures, but none work up to now. >> I tried to find lock files that might be blocking, deleted some files ending in lck with zero size, with no result. >> I tried to switch off the spam/virus/junk features, no difference (some mail said that messages in the queue will not get through, but new ones would. Not so, not a single message up to now). >> I also get alerts in the Server application, warning that: >> >> An unassigned mail directory has been detected and is scheduled to be deleted. >> >> The unassigned mail directory located in: >> /Library/Server/Mail/Data/mail/702C16A8-6B2D-42D8-9362-659DD2949AFC >> is not associated with any user account and is scheduled to be deleted in 1 days. >> >> In the mean time no mail, and unfortunately, we need it badly. >> >> Any suggestions? >> >> Million thanks for your kind support. >> >> sytse >> -- >> ------------------------------------------ >> - Sytse Kuijk - ___ >> - R.S.R. n.v. - o|o >> - Gijzelaarsstraat 16 - \_____(.)_____/ >> - 2000 Antwerpen - >> - GSM: +32 468 20 00 00 - ___ >> - Phone: +32 3 216 4328 - o|o >> - E-mail: sytse(a)pobox.com <mailto:sytse@pobox.com> - \_____(.)_____/ >> ------------------------------------------ >> >> iThink therefore iMac

1 0

ldap paging
by Andre Helwig 27 Nov '15

27 Nov '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi List, in ldapsearch you are able to use paging in case of limited results on ldap server side with "-E pr=10000/noprompt" Is there any way to get the same effect for the iterate query? Thanks Andre -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJWWHvwAAoJEAoTNwRDnEhRVmMH/0+vGRx7urQ49bHbzc4asD7r XlbwS7whkDKrJpflK39PLPw5BJoptKhwLNOueotFv9Pq8EYQBkN/gX69BzxeoFk8 DZpiP/ogYQIG1lUijes4UkbttVpnviy9/mLBKjIfIkvGDu0q3zwuq5876q6t2Qxx kJkpLSizxAfnGLeD03txVPAc8wGzxhxkyEdosQ+ARriYI1Ce+dfK28z6hSAEXMA+ 4JZEvIsy6P+xepFCFYILFWeRO2YBzqHtgtjKu8KCiyBdUPG0Nii4z2YmN2AoCj7m rQ8l4CeTDw+lk0pMy26kCsmh+PK2/OXCUGjxgYJOR3mxn2HNSIfUXFVWs4ri464= =qWS+ -----END PGP SIGNATURE-----

1 0

Sieve Max Redirect
by Shakeel Shahzad 27 Nov '15

27 Nov '15

Hello, I have configured iRedMail ( 0.9.1) on Ubuntu (14.04 LTS). In my dovecot.conf file, I have set sieve_max_redirects as 500. In dovecot (2.2.9) configuration file, I see sieve_max_redirect as 100 but when I add email addresses more than 32, I see that redirect fails. Can you please help me to see this issue and fix it through? If you need anything from my side, please let me know. Regards... Shakeel

3 4

doveadm-backup verbosity?
by Andreas Fischer 27 Nov '15

27 Nov '15

Hi, according to the man page doveadm-backup, the verbosity switch "-v" should do the following: "Enables verbosity, including progress counter" However, i see no difference running the following command with or without the "-v" switch: >>doveadm -v backup -R -A remote:myhost The command itself works without problem, two mailboxes are correctly back-upped, but the output is only an empty line. Not sure if this is expected behavior. Regards # 2.2.19: /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 (357ac0a0e68b+) # OS: Linux 4.2.5-1-ARCH x86_64 dsync_remote_cmd = ssh -p 19022 -l root %{host} doveadm dsync-server -u%u first_valid_uid = 99 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate editheader passdb { args = nopassword=y driver = static } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_extensions = +editheader } protocols = service anvil { process_min_avail = 0 unix_listener anvil-auth-penalty { mode = 064 } } ssl = no userdb { args = /etc/dovecot/users default_fields = uid=nobody gid=nobody home=/backup/tmp/mail/%d/%n mail=sdbox:~/box driver = passwd-file }

1 0

fts_solr does not quote lucene's special characters
by Michael Stilkerich 27 Nov '15

27 Nov '15

Hello, I am using Dovecot 2.2.19 with the solr backend for full text search and experience the following issue. When I issue a search that includes characters that are part of lucene's query syntax (e.g. the double quote character), dovecot does not escape the special characters and issues a request with invalid syntax to the solr server. For example, I search for foo"bar, then my IMAP client (roundcube) sends the following to dovecot: A0003 UID THREAD REFS US-ASCII ALL UNDELETED BODY "foo\"bar" Dovecot in turn uses the following request URI to query SOLR: "GET /solr/select?fl=uid,score&rows=113739&sort=uid+asc&q=body:%22foo%22bar%22&fq=%2Bbox:4d86808c56d44282b35cea8700dda537+%2Buser:%22myuser%22 HTTP/1.1" 400 994 Solr responds with error 400 and the following body: type Status report message null description The request sent by the client was syntactically incorrect. This is because the " character in foo"bar is not quoted in the solr request. When I adapt the request to quote the " character solr succeeds with the expected result: "GET /solr/select?fl=uid,score&rows=113739&sort=uid+asc&q=body:%22foo%5C%22bar%22&fq=%2Bbox:4d86808c56d44282b35cea8700dda537+%2Buser:%22myuser%22 HTTP/1.1" 200 535 A fix for this would be highly appreciated. Cheers, Michael

2 1