- dovecot - dovecot.org

[Dovecot] replication + attachment sis + zlib bug ? (HEAD version from xi.rename-it.nl)
by Pavel Stano 10 Apr '14

10 Apr '14

Hi, i have setup with mail_attachment single instance store + replication + zlib and got this bug when i try to replicate one test mailbox: On master1 in mail.log: Apr 10 13:25:22 master1 dovecot: dsync-local(zzz(a)blabla666.sk): Error: read(/nfsmnt/mailnfs1/attachments1/6b/57/6b57ad34cf6c414662233d833a7801fde4e1cdcb-92b5052558774653a728000013e2b982[base64:18 b/l]) failed: Stream is larger than expected (97824 > 97823, eof=1) Apr 10 13:25:22 master1 dovecot: dsync-local(zzz(a)blabla666.sk): Error: dsync(master2): read(attachments-connector(zlib(/nfsmnt/mailnfs1/b/l/blabla666.sk/zzz(a)blabla666.sk/mdbox/storage/m.9))) failed: read(/nfsmnt/mailnfs1/attachments1/6b/57/6b57ad34cf6c414662233d833a7801fde4e1cdcb-92b5052558774653a728000013e2b982[base64:18 b/l]) failed: Stream is larger than expected (97824 > 97823, eof=1) This is on master2 in mail.log Apr 10 13:32:21 master2 dovecot: dsync-server(zzz(a)blabla666.sk): Error: dsync(master1): read() failed: read(10.10.30.2) failed: dot-input stream ends without '.' line I tried to rm -Rf mailbox on master2 and run on master1 doveadm replicator remove zzz(a)blabla666.sk doveadm replicator replicate zzz(a)blabla666.sk but same problem happen. Thanks -- [ Ohodnotte kvalitu mailu: http://nicereply.com/websupport/Stano/ ] Pavel Stano | Troubleshooter http://WebSupport.sk *** BERTE A VYCHUTNAVAJTE ***

2 2

[Dovecot] dsync deleted my mailbox - what did I do wrong?
by Benjamin Podszun 10 Apr '14

10 Apr '14

Hi. Mostly annoying: I migrated from one machine to another, made sure the target host worked as expected, updated mx records and - after a couple of days - signed it off as good. This is just my private machine, no big deal if something goes wrong.. Everything's fine? Good, let's migrate my inbox from the old machine. There's no direct connectivity between those servers, so what I did was: (old server) sudo -u vmail dsync -u dar(a)darklajid.de backup maildir:/tmp/mail_backup/ Works fine, got my maildir. Tar'd it up, moved it to the new server. Now how do I import those mails? Ah, let's use the same command, with -R? (new server) sudo -u vmail dsync -u dar(a)darklajid.de -R backup maildir:/tmp/mail_backup Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted. Wait. What? Sure enough, the last couple of days are gone, the target mailbox is completely empty. I read the man page over and over again, but failed to see the problem. I even thought for a moment that _maybe_ dsync backup is one-way only (even if that failed as well) and tried the same command with mirror. Exactly the same output, same result, empty target mailbox. In the end I succeeded to import the mails with doveadm import, completely lost a number of days of mails. My fault, sloppy not to back the up again, but I still don't think that this should happen. Ever. My question now is: - where did I fail (ignoring the backups, please. That's .. something I know) - Can I use dsync ... for backups? I don't think that this is a good idea after yesterday night? - Should dsync EVER try to delete mailboxes? Even 'special' mailboxes? Should it warn about that, asking for a --force switch or something? Any insights would be appreciated. At this point the damage is done, but I'd like to learn how to do better. Ben

4 9

[Dovecot] integration of old mails into new dovecot Maildir
by K. C. Mohan - Personal 10 Apr '14

10 Apr '14

I just installed dovecot 2.2.9 on to a new server and want to transfer all the old mails into the email accounts I imported from the previous server into MySQL database. I am not able to view the subfolders and or old mails that I copied into their respective maildir folders. I was very much appreciate if anyone could let me know how to import old mails into the new server. All I see, is the new mails that have come into the account since I started dovecot service in the new server. --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com

2 1

[Dovecot] IMAP, POP, LMTP response time
by adarshvs 10 Apr '14

10 Apr '14

Hi, How do I retrieve the /response time/ metrics for imap, pop, lmtp and smtp. Any suggestions will be very helpful. Thank you. -- View this message in context: http://dovecot.2317879.n4.nabble.com/IMAP-POP-LMTP-response-time-tp47500.ht… Sent from the Dovecot mailing list archive at Nabble.com.

2 1

[Dovecot] Heartbleed openssl vulnerability?
by John Rowe 10 Apr '14

10 Apr '14

Do we know if dovecot is vulnerable to the heartbleed SSL problem? I'm running dovecot-2.0.9 and openssl-1.01, the latter being intrinsically vulnerable. An on-line tool says that my machine is not affected on port 993 but it would be nice to know for sure if we were vulnerable for a while. (Naturally I've blocked it anyway!). Thanks John

9 20

[Dovecot] Director NFS backups
by Murray Trainer 10 Apr '14

10 Apr '14

Hi All, What is the recommended method of taking backups of user mailboxes when using the Director setup with NFS backend mail storage? Is there any way to avoid the likely NFS locking issues by backing up the filesystem directly or do I have to do some sort of dsync method. If I have to use dsync can I dsync the mailboxes to compressed copies of the mailboxes without requiring another dovecot server to do the dsync. Thanks for you responses. Murray

1 0

Re: [Dovecot] POP3 sessions
by Joseph Tam 10 Apr '14

10 Apr '14

<doctor(a)doctor.nl2k.ab.ca> writes: > Is their a way in the config file to not lock > POP3 sessions in dovecot for only 1 user? That ought to be the default: http://wiki2.dovecot.org/POP3Server (Section Session locking) Did you set pop3_lock_session=yes somewhere? Locking is good if the client connection is stable: if you disable locking, you could end up with a scrambled mailbox as two or more users access it at the same time. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] Error: broken sync positions in index file
by Alejandro Angelico 10 Apr '14

10 Apr '14

Hi everybody, I'm runing dovecot 2.2.12 and a user mailbox got the "broken sync positions in index file" error twice in the last 20 days. this is an extract from the maillog maillog First Error -------------------- Mar 23 16:13:25 andromeda dovecot: pop3-login: Login: user=<myuser(a)mydomain.com>, method=PLAIN, rip=187.237.107.24, lip=207.7.90.83, mpid=3983, session=<5KSEbU310wC77WsY> Mar 23 16:13:27 andromeda dovecot: pop3(myuser(a)mydomain.com): Error: broken sync positions in index file /home/myuser/mail/mydomain.com/myuser/dovecot.index Mar 23 16:13:27 andromeda dovecot: pop3(myuser(a)mydomain.com): Warning: fscking index file /home/myuser/mail/mydomain.com/myuser/dovecot.index Mar 23 16:13:27 andromeda dovecot: pop3(myuser(a)mydomain.com): Error: Fixed index file /home/myuser/mail/mydomain.com/myuser/dovecot.index: log_file_tail_offset 164 -> 144 Mar 23 16:13:27 andromeda dovecot: pop3(myuser(a)mydomain.com): Panic: file mail-transaction-log.c: line 350 (mail_transaction_log_set_mailbox_sync_pos): assertion failed: (file_offset >= log->head->saved_tail_offset) Mar 23 16:13:27 andromeda dovecot: pop3(myuser(a)mydomain.com): Fatal: master: service(pop3): child 3983 killed with signal 6 (core dumps disabled) Mar 23 16:13:27 andromeda dovecot: pop3: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0xb7e59350] -> /usr/lib/dovecot/libdovecot.so.0 [0xb7e593cd] -> /usr/lib/dovecot/libdovecot.so.0 [0xb7e58c64] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_transaction_log_set_mailbox_sync_pos+0x9a) [0xb7f8c1aa] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_commit+0x9c) [0xb7f82a5c] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0xb7f00f2b] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0xb7f0034a] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0xb7f006ba] -> /usr/lib/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xc1) [0xb7f00851] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x39) [0xb7f33b79] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x3d) [0xb7f365ad] -> dovecot/pop3(client_create+0x2e2) [0x804c5e2] -> dovecot/pop3 [0x804afec] -> dovecot/pop3 [0x804b607] -> /usr/lib/dovecot/libdovecot.so.0 [0xb7e1033a] -> /usr/lib/dovecot/libdovecot.so.0 [0xb7e10622] -> /usr/li maillog Second Error -------------------- Apr 9 17:22:00 andromeda dovecot: imap-login: Login: user=<myuser(a)mydomain.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=29811, secured, session=<ZteFh6P2uAB/AAAB> Apr 9 17:22:00 andromeda dovecot: imap(myuser(a)mydomain.com): Error: Transaction log file /home/myuser/mail/mydomain.com/myuser/dovecot.index.log seq 4: log_file_tail_offset update shrank it (284 vs 420 sync_offset=268) Apr 9 17:22:00 andromeda dovecot: imap(myuser(a)mydomain.com): Error: broken sync positions in index file /home/myuser/mail/mydomain.com/myuser/dovecot.index Apr 9 17:22:00 andromeda dovecot: imap(myuser(a)mydomain.com): Warning: fscking index file /home/myuser/mail/mydomain.com/myuser/dovecot.index Apr 9 17:22:00 andromeda dovecot: imap(myuser(a)mydomain.com): Error: Fixed index file /home/myuser/mail/mydomain.com/myuser/dovecot.index: log_file_tail_offset 420 -> 284 Apr 9 17:22:00 andromeda dovecot: imap(myuser(a)mydomain.com): Panic: file mail-transaction-log.c: line 350 (mail_transaction_log_set_mailbox_sync_pos): assertion failed: (file_offset >= log->head->saved_tail_offset) Apr 9 17:22:00 andromeda dovecot: imap(myuser(a)mydomain.com): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0xb7d9ae4f] -> /usr/lib/dovecot/libdovecot.so.0 [0xb7d9aecd] -> /usr/lib/dovecot/libdovecot.so.0 [0xb7d9a744] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_transaction_log_set_mailbox_sync_pos+0x9a) [0xb7ecf60a] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_commit+0x9c) [0xb7ec5e5c] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0xb7e43f8b] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0xb7e433aa] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0xb7e4371a] -> /usr/lib/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xc1) [0xb7e438b1] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x39) [0xb7e76d19] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x3d) [0xb7e7974d] -> dovecot/imap(cmd_select_full+0x23e) [0x805721e] -> dovecot/imap(cmd_select+0x19) [0x8057bf9] -> dovecot/imap(command_exec+0x33) [0x805c9a3] -> dovecot/imap [0x805b6df] -> dove Apr 9 17:22:00 andromeda dovecot: imap(myuser(a)mydomain.com): Fatal: master: service(imap): child 29811 killed with signal 6 (core dumps disabled) Deleting dovecot.index.* files solved the problem both times, but I'm wondering if something is wrong because it's always the same mailbox. Before deleting dovecot.index I run doveadm with this oputput: root@myserver [/home/myuser/mail/.myuser@mydomain_com]# doveadm index -u myuser INBOX doveadm(myuser): Fatal: User doesn't exist root@myserver [/home/myuser/mail/.myuser@mydomain_com]# doveadm index -u myuser(a)mydomain.com INBOX doveadm(myuser(a)mydomain.com): Error: Transaction log file /home/myuser/mail/mydomain.com/myuser/dovecot.index.log seq 4: log_file_tail_offset update shrank it (284 vs 420 sync_offset=268) doveadm(myuser(a)mydomain.com): Error: broken sync positions in index file /home/myuser/mail/mydomain.com/myuser/dovecot.index doveadm(myuser(a)mydomain.com): Warning: fscking index file /home/myuser/mail/mydomain.com/myuser/dovecot.index doveadm(myuser(a)mydomain.com): Error: Fixed index file /home/myuser/mail/mydomain.com/myuser/dovecot.index: log_file_tail_offset 420 -> 284 doveadm(myuser(a)mydomain.com): Panic: file mail-transaction-log.c: line 350 (mail_transaction_log_set_mailbox_sync_pos): assertion failed: (file_offset >= log->head->saved_tail_offset) doveadm(myuser(a)mydomain.com): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0xb7d35e4f] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x43) [0xb7d35f63] -> /usr/lib/dovecot/libdovecot.so.0 [0xb7d35744] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_transaction_log_set_mailbox_sync_pos+0x9a) [0xb7e6a60a] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_commit+0x9c) [0xb7e60e5c] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0xb7ddef8b] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0xb7dde3aa] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0xb7dde71a] -> /usr/lib/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xc1) [0xb7dde8b1] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x39) [0xb7e11d19] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x3d) [0xb7e1474d] -> doveadm [0x80595db] -> doveadm [0x80558de] -> doveadm(doveadm_mail_try_run+0x293) [0x8055d03] -> doveadm(main+0x3bd) [0x805eb5d] -> /lib/libc.so.6(__libc_start_main+0xdc) [0xb7b89ebc] -> doveadm [0x8055061] Aborted Is there anything else I should try? or just wait to see if this happens again? the mailbox is not very big, around 38Mb in 84 mails. Thanks! Alex

1 0

[Dovecot] Override maildir for just a few users
by Charles Marcus 10 Apr '14

10 Apr '14

Hi all, Currently, I have mail_location = maildir:~/Maildir set and all passdb and userdb lookups are SQL based (doveconf -n pasted below). However, I want to override the users maildir location - and *only* the maildir location - for just a few users. I was thinking the easiest way would be to add a simple flat file based userdb that is checked before the SQL based one, where I can define a different maildir for these users. So, basically, dovecot checks the flat file first, and if the user isn't found, falls back to SQL. I still want all AUTH to go through SQL... It seems like this should be fairly simple, but after reading the wiki for a few days, I'm just not sure... This is on a production box, so I have to be careful (note to self - MUST set up testing box for things like this)... Is anyone else doing anything like this, and if so would you be willing to share sanitized configs? Thx, -- Best regards, Charles

3 2

[Dovecot] Sieve (randomly?) flagging messages as \\Seen \\Deleted
by Emanuele Balla (aka Skull) 09 Apr '14

09 Apr '14

Hi, I'm trying to debug (without great results, so far) a very weird behaviour in my environment. Sorry if this came out in another form before, but I've not been able to find out anything resembling what I'm experiencing, so far... OS is a debian wheezy and dovecot is the version provided by the OS: # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.4 The system uses postfix with virtual users, credentials and maildir locations stored on mysql, local delivery through LMTP and sieve+managesieve available to users (although managesieve only listens on localhost and is only usable through the webmail interface). FWIW, I've been running 10-20 systems just like this one (mostly with earlier dovecot versions and using LDA when LMTP wasn't available yet) for many years, and this is the very first time I'm so puzzled I end up searching for help here :-| Even though the system has been working for months (more or less 1 year now) without big changes, a strange behaviour appeared (or became evident enough to be noticed) in the last few days, apparently involving sieve and some sort of "default/hidden" action triggered by something. Or at least that's what I ended up supposing. The problem in short: Messages I expected to find in certain folders were simply not there, although sieve logs reported them as delivered in those same folders. By manually inspecting the maildir, I actually found the messages, but they were all flagged as \\Seen + \\Deleted and therefore not displayed by the MUA (ThunderBird in my case). I initially supposed this to be a TB issue, 'cause nothing in my sieve script ever flags messages that way, but I could not find anything on my client explaining that. Then I received a notification from one of my users saying he was experiencing exactly the same, except he's using mutt as IMAP client; that restricted the issue to server-side interactions only, but nothing useful could be found in logfiles... This is the "relevant" portion of a "dovecot -n" output: [...] plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +vacation-seconds +editheader sieve_vacation_default_period = 2d sieve_vacation_dont_check_recipient = yes sieve_vacation_max_period = 30d sieve_vacation_min_period = 2s sieve_vacation_use_original_recipient = no } [...] protocol lmtp { mail_plugins = sieve hostname = alternativename.bofhland.org } There is no sieve_(before|after) script in addition to what users create for themselves. The mailboxes are relatively low-traffic; most of the traffic is caused by a single role address translated into multiple-recipients alias going to many of the users (100-300 messages per day). Almost all the users using sieve rely on it to store traffic for that role-address in a dedicated folder, including the mutt user and myself. Not that's all that important, but means that most of the misbehaviours observed (but not all) are observed in these folders. I enabled mail_debug, but there's nothing unusual in there AFAICT: it just says: - using the following location for user's Sieve script: /blabla/.dovecot.sieve - opening script /blabla/.dovecot.sieve - script binary /blabla/.dovecot.svbin successfully loaded - not saving binary /blabla/.dovecot.svbin, because it is already stored - executing script from /blabla/.dovecot.svbin - stored mail into mailbox 'DedicatedFolder' And it does, except the message happens to be flagged as seen and deleted... In order to try restricting what may be causing the issue, I added... removeflag "\\Deleted"; removeflag "\\Seen"; ...to the rule sending messages to the dedicated folder cited above for my mailbox. The problem apparently disappeared for me as long as I kept those in place. This should mean (I suppose) that the decision of flagging messages that way is taken before the users' sieve scripts are applied (sort of "hidden sieve_before"). The problem is hard to replicate as it's apparently not deterministic: the same message is being flagged for one user but not for the other, different messages between the same people and with the same thread are sometimes flagged and sometimes not. Something is surely triggering whatever is causing this, but it's not evident enough for me to point a finger and say "ha ha!" (https://www.youtube.com/watch?v=rX7wtNOkuHo) So, a question for people knowing pigeonhole's internals: does it ever choose to mark messages as described above for any reason? If yes, I may be triggering this behavior with something I recently added/modified, and at least I'll have something to focus my investigation on. :-| Any other suggestion is obviously welcome...

3 6