February 2019 - dovecot

Maintaining table quota2
by Robert Moskowitz 14 Feb '19

14 Feb '19

Does dovecot compute that values for quota2 with each email it updates for the user? Or only an incremental change? I ask because I am looking at migrating all the user mail from the old server to the new and building a new sql database. All I see is: dovecot-dict-sql.conf.ext: connect = host=/var/lib/mysql/mysql.sock dbname=postfix user=postfix password=$Postfix_Database_Password map { pattern = priv/quota/storage table = quota2 username_field = username value_field = bytes } map { pattern = priv/quota/messages table = quota2 username_field = username value_field = messages } what is actually done with this table? thanks

3 11

problem witht working director
by Maciej Milaszewski IQ PL 13 Feb '19

13 Feb '19

Hi I have dovecot director with 2-3 ring and 4 dovecot My ring is : 10.0.100.2 9090 right never synced 8 37305225 39763861 0 723 2019-02-13 16:02:04 2019-02-13 16:02:04 10.0.100.3 9090 left never synced 8 57409664 8707830 0 737 2019-02-13 16:02:04 2019-02-13 16:02:04 10.0.100.4 9090 self never ring synced 1 - - - - - - 10.0.100.4 - This is my default server where clients connect - default direcor 2.2.36 10.0.100.3 - second direcot 2.2.36 10.0.100.2 - second director with older ver 2.2.18 Today I found the error in my default mailserver Feb 13 13:21:23 kernel: [24253349.641695] qmail-remote: page allocation failure: order:2, mode:0x204020 and problem with logging via imap and pop3 I try "doveadm director status" i get time out I try restart dovecot and get: Feb 13 13:21:03 thebe3 dovecot: master: Fatal: Dovecot is already running? Socket already exists: /var/run/dovecot/login/director before failure i found: "imap-login: Error: write(proxy-notify) failed: Resource temporarily unavailable" but my setting they seem correct https://paste.debian.net/1067596/ I moved IP (via keepalive) all to other director (secound servcer) And when I try "doveadm director status" i get time out https://paste.debian.net/1067601/ I do not understand why I had a problem with second server and restart dovecot in server2 restart solved the problem ?

1 0

smtp_address_cmp does not ignore case of localpart
by Andreas Jobs 13 Feb '19

13 Feb '19

Hi, in src/lib-smtp/smtp-address.c line 759 the localpart is compared with null_strcmp, which does not ignore the case. While this is the correct behavior (according to the RFC) it causes problems in real life. In my case the vacation notices are not sent, if someone writes to First.Last(a)ruhr-uni-bochum.de because :addresses contains (only) first.last(a)ruhr-uni-bochum.de. Regards, Andreas -- ! AJ3630-RIPE @ RUB8-RIPE Network Operation Center ! ! Dezernat 5.I Ruhr-Universitaet Bochum ! ! The amount of energy necessary to refute bullshit is ! ! an order of magnitude bigger than to produce it. -- Alberto Brandolini !

2 3

Can't sync mailbox XXX: Mailbox isn't selectable
by Tamas Hegedus 12 Feb '19

12 Feb '19

Hi, I have users with file system folders, which contain mbox files and dovecot indexes, in the ~/mail directory. If I run dsync, I have an error message and the sync can not be completed: Can't sync mailbox FOLDER_NAME: Mailbox isn't selectable I could not find any solution via google or any hint what to do in this situation. Thanks for your help and suggestion, Tamas -- Tamas Hegedus, PhD Senior Research Fellow MTA-SE Molecular Biophysics Research Group Hungarian Academy of Sciences | phone: (36) 1-459 1500/60233 Semmelweis University | fax: (36) 1-266 6656 Tuzolto utca 37-47 | mailto:tamas@hegelab.org Budapest, 1094, Hungary | http://www.hegelab.org --- This email has been checked for viruses by AVG. https://www.avg.com

2 1

doveadm import with subfolder oddity
by Mark Moseley 12 Feb '19

12 Feb '19

This has got to be something weird in my config. And the standard disclaimer of '"happy to post doveconf -n, but wanted to see if this is normal first" :) Background: Ubuntu Xenial, running 2.2.36. Mailbox type is mdbox and I've got a period separator in my inbox namespace: namespace { hidden = no inbox = yes list = yes location = mailbox Spam { auto = no autoexpunge = 1 weeks special_use = \Junk } mailbox Trash { auto = no special_use = \Trash } prefix = INBOX. separator = . subscriptions = yes type = private } If I do a import for a regular folder under INBOX, it works just fine: doveadm import -u testbox2(a)testing.local -U testbox1(a)testing.local mdbox:~/mdbox INBOX all mailbox Sent ... returns happily, message count gets incremented If I try to do the same with a subfolder (and a subfolder that most definitely exists on both source and destination side), I get an error: doveadm import -u testbox2(a)testing.local -U testbox1(a)testing.local mdbox:~/mdbox INBOX all mailbox Sub.Sub1 doveadm(testbox2(a)testing.local): Error: remote(10.1.17.98:4000): Mailbox Sub.Sub1: Mailbox sync failed: Mailbox doesn't exist: Sub.Sub1 If I use / instead of . in my query, it works: doveadm import -u testbox2(a)testing.local -U testbox1(a)testing.local mdbox:~/mdbox INBOX all mailbox Sub/Sub1 ... returns happily and message count gets incremented. Since we're using '.' as our separator, that was a bit unexpected :) Ironically, if I'm doing a IMAPc 'import', it works just fine with a query of 'all mailbox Sub.Sub1'. It's only when importing from a local src and local dest (i.e. source_location == mdbox:~/mdbox) that it fails. With source_location set to 'imapc:', it works. I imagine that's due to using straight IMAP on the source side. Likely a misconfig on my part? Expected behavior? I can see in the strace that the error is triggered when doveadm is looking at the source mailbox. It looks for mdbox/mailboxes/Sub.Sub1/dbox-Mails first, then falls back to mdbox/mailboxes/Sub/Sub1/dbox-Mails (which it finds). Then a little bit later in the strace, it again looks for mdbox/mailboxes/Sub.Sub1/dbox-Mails (which it doesn't find) but doesn't try mdbox/mailboxes/Sub/Sub1/dbox-Mails this time, and then spits out 'Mailbox Sub.Sub1: Mailbox sync failed: Mailbox doesn't exist: Sub.Sub1'. With a query of 'all mailbox Sub/Sub1', the stat() is for mdbox/mailboxes/Sub/Sub1/dbox-Mails which it finds and uses happily. Having to substitute the '.'s for '/'s in the 'mailbox' part of the query isn't an awful workaround, but it very much feels like I'm doing something wrong. This is a production setup, so everything else is otherwise working fine. But I've only just begun working with 'doveadm import', so I might be turning up some issues with my config. Thanks! Sorry I'm so verbose :)

1 1

Doveadm service as non-root user
by Mark Moseley 12 Feb '19

12 Feb '19

Running: Ubuntu xenial, dovecot 2.2.36 I've been working on moving our user base from maildir to mdbox and trying to come up with solutions for things like moving emails around. In the past, with maildir, our support guys could just mv the files around and done. For mdbox, I've been working on getting things set up to use doveadm. One weirdness I've seen is that in imports (i.e. doveadm import), mail gets copied correctly but the resulting files are left with root ownership (I don't have 'service doveadm' 'user' set, so I guess it defaults to root). It's typically new m.* files as well as the dovecot.list.index and dovecot.list.index.log files. Looking at strace, no chown is done on them, nor was there setuid. The import had no trouble finding the correct user in the db, so I know that it knows the correct UID (I can see it just fine in debug logs too). And it will happily import to existing m.* files with no permissions issues (but considering it's running as root, I wouldn't expect it to). I've seen this using 'import' via IMAPc as well as with both src and dest on the same server. I can see this behavior in both scenarios. We have a single shared UID for mail, so especially in that "src/dest on same server" case, it's not a matter of UID-mismatch. It's a director setup, so all doveadm commands are coming through the director. If I run the import directly on the backend (which obviously would be a bad idea in real life), the ownership of new m.* files seems to be correct (I can see it setuid'ing to the correct UID from userdb in strace). If I run the import on the director, I can get a new root-owned file every time it rolls over to the next m.* file. Two questions: * Is that a bug? Is this expected behavior? Seems like the expected thing would be to use the UID from userdb and either do a setuid (just like running 'doveadm import' locally did) or chown'ing any new files to the correct UID. I always always assume misconfiguration (vs bug, since it's almost never a bug) but I'm baffled on this one. * I see that it's possible to set a user for service doveadm and the wiki even suggests that it's a good idea in a single UID setup. If there are no mailboxes with any other UIDs, *will setting 'service doveadm' to the same UID possibly break anything*? I can't think of why it would, but I want to be duly diligent. Plus I'm a little leery about closing the door to ever having additional UIDs for mailboxes. Happy to provide 'doveconf -n' but wanted to check first, before spending 15 minutes gently obfuscating it :)

2 3

expunge not removing attachments?
by Ralf Hildebrandt 12 Feb '19

12 Feb '19

I have a large mail backup folder backup(a)backup.invalid; I'm cleaning up daily like this: infimum=`date -d "-4 day" +"%Y-%m-%d"` doveadm expunge -u backup(a)backup.invalid mailbox INBOX SAVEDBEFORE $infimum doveadm purge -u backup(a)backup.invalid yet I see this: # find attachments/ -type f -ctime +5 | wc -l 7522 # find attachments/ -type f | wc -l 127579 # find attachments/ -type f -mtime +5 | wc -l 14361 # find attachments/ -type f | wc -l 127793 About 5.9% of the files in attachments and below are older than 5 days. Why? Is that normal? using dovecot 2:2.3.1-1 from the official repos. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | https://www.charite.de

2 3

APPEND Error in dovecot.log
by Alessandro Battaglini 12 Feb '19

12 Feb '19

Hi dovecot --version => 2.2.22 (fe789d2) Scenario: Sometimes imap client send email correctly but there's is any message stored in sent mail folder in that scenario I have found an error in my dovecot.log : 2019-02-11 09:04:52 imap(-----@------------): Info: Disconnected in APPEND (1 msgs, 125 secs, 2818048/4426899 bytes) in=3365352 out=1522206 Question: what about this? Is there, in dovecot configuration, a parameter that insist to any kind of APPEND like value.? I have not find that. Have you any idea to solve this? Thanks

1 0

assertion failed: (srcleft <= CHARSET_MAX_PENDING_BUF_SIZE)
by Giacomo 11 Feb '19

11 Feb '19

I'm running the following: # 2.3.4 (0ecbaf23d): /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 11.2-RELEASE-p4 amd64 # FS: ZFS auth_mechanisms = plain login auth_username_format = %Ln listen = * mail_location = maildir:~/Maildir namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { driver = pam } protocols = imap lmtp service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } user = dovecot } service imap-login { inet_listener imap { port = 0 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service stats { unix_listener stats-reader { group = mode = 0600 user = } unix_listener stats-writer { group = $default_internal_group mode = 0666 user = } user = $default_internal_user } ssl_cert = </root/cert.pem ssl_key = # hidden, use -P to show it userdb { driver = passwd } dmesg shows: pid 74441 (imap), uid 1002: exited on signal 6 pid 74784 (imap), uid 1002: exited on signal 6 pid 21471 (imap), uid 1002: exited on signal 6 pid 21470 (imap), uid 1002: exited on signal 6 pid 21464 (imap), uid 1002: exited on signal 6 pid 21731 (imap), uid 1002: exited on signal 6 Sometimes the dovecot process serving an user crashes. He runs mostly airmail on macOS and samsung mail on Android. Happens only to that particular user. The log shows the following: (maillog) Dec 16 14:52:35 mail dovecot: imap-login: Login: user=<USER>, method=PLAIN, rip=79.12.201.157, lip=192.168.1.28, mpid=74779, TLS, session=<wMQI+iN9VtRPDMmd> Dec 16 14:52:39 mail dovecot: imap(USER)<74441><nLa+7SN9+fhPDMmd>: Panic: file charset-iconv.c: line 83 (charset_to_utf8_try): assertion failed: (srcleft <= CHARSET_MAX_PENDING_BUF_SIZE) Dec 16 14:52:39 mail dovecot: imap(USER)<74441><nLa+7SN9+fhPDMmd>: Fatal: master: service(imap): child 74441 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set service imap { drop_priv_before_exec=yes }) I'm here if more info is needed. Thanks for taking a look.

4 7

Bounces?
by ＠lbutlr 11 Feb '19

11 Feb '19

I just got this On 9 Feb 2019, at 00:00, dovecot-request(a)dovecot.org wrote: > Your membership in the mailing list dovecot has been disabled due to > excessive bounces The last bounce received from you was dated > 02-Feb-2019. You will not get any more messages from this list until > you re-enable your membership. You will receive 1 more reminders like > this before your membership in the list is deleted. > > To re-enable your membership, you can simply respond to this message > (leaving the Subject: line intact), or visit the confirmation page at > > https://dovecot.org/mailman/confirm/dovecot/41881d… When clicking the link I get "Bad confirmation sting" and something about maybe the link expired. I see no connection attempts from dovecot.org over the last few days other than this message. -- If at first you don't succeed, destroy all evidence that you tried.

8 18