April 2014 - dovecot - dovecot.org

[Dovecot] FTS autoindex username problem
by lee_yiu_chung＠yahoo.com 11 Apr '14

11 Apr '14

I tried to set up Solr search server according to http://wiki2.dovecot.org/Plugins/FTS/Solr, and turned on autoindexing according to http://wiki2.dovecot.org/Plugins/FTS, but I found a strange behaviour that cause server search missing some emails. Here is the login information of my mail server: login name: user1 email: user1(a)example.com Now, when I turned on autoindexing, all autoindexed email are indexed using user1(a)example.com as username key, as shown in maillog: dovecot: [ID 12345 mail.info] indexer-worker(user1(a)example.com): Indexed 1 messages in INBOX But when I triggered on-demand indexing using IMAP server search, the emails are indexed using user1 as username key instead, as shown in maillog: dovecot: [ID 12345 mail.info] indexer-worker(user1): Indexed 1799 messages in INBOX Only the emails indexed using user1 can be searched, emails indexed using user1(a)example.com cannot be found. How can I configure autoindex to index email using user1 as username key? --- (Below is a follow-up question) In my mail server config, there are a few virtual mailbox users are using the following login information instead (different auth/password backend): login name: user2(a)virtmail.example.com email: user2(a)virtmail.example.com In this case, how can I distinguish user1(a)example.com and user2(a)virtmail.example.com, so that emails for user1(a)example.com can be indexed using user1 as username key, while user2(a)virtmail.example.com can be indexed using user2(a)virtmail.example.com as username key?

1 0

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

11 Apr '14

Yes, exactly. I look at the code and find out there is functionality for that. Dovecot store attachments in base64 format without decoding if there are longer lines with more base64 blocks (4chars). So these attachments get deduplicated but are not decoded. But it don't work if last line is buggy. I think i fixed it. It looks like it works, but i test only one mailbox. Patch attached On Fri, 11 Apr 2014 09:29:53 +0200 Gilles Chauvin <gilles.chauvin(a)univ-rouen.fr> wrote: > On 10/04/2014 18:21, Pavel Stano wrote: > > Hi, > > > > yes its the same problem. > > I can confirm that it is caused by last line in base64 > > attachment which is longer than 72 chars in original message. > > > > > > Hi, > > I don't know what is the current status for this issue since Timo > never responded to my two mails. A safe way to workaround this > problem could be Dovecot skipping deduplication when it encounters a > malformed base64 attachment ? > > > > Regards, > Gilles. -- [ Ohodnotte kvalitu mailu: http://nicereply.com/websupport/Stano/ ] Pavel Stano | Troubleshooter http://WebSupport.sk *** BERTE A VYCHUTNAVAJTE ***

1 0

[Dovecot] FTS autoindex problem
by lee_yiu_chung＠yahoo.com 11 Apr '14

11 Apr '14

I tried to implement a solr search server, but I found some unexpected behaviour when I turn on autoindex according to http://wiki2.dovecot.org/Plugins/FTS. I found that all autoindexed email are using "user1(a)example.com" as username, as shown in maillog: indexer-worker(user1(a)example.com): Indexed 1 messages in INBOX However, all manually indexed email (triggered by IMAP server search) are using "user1" as username, as shown in maillog: indexer-worker(user1): Indexed 2927 messages in INBOX. I am using "user1" as login name, so all autoindexed mails don't appear in search result. How can I use "user" as the username in autoindex? BTW, I do have a few mailboxes in the format user2(a)virtualmail.example.com, which requires full email address as the login name. How can I autoindex emails that automatically distinguishes user1(a)example.com (using "user1" as username) and user2(a)virtualmail.example.com (using "user2(a)virtualmail.example.com" as username) given that the previous question is solved?

1 0

[Dovecot] FTS autoindex problem
by lee_yiu_chung＠yahoo.com 11 Apr '14

11 Apr '14

I tried to implement a solr search server, but I found some unexpected behaviour when I turn on autoindex according to http://wiki2.dovecot.org/Plugins/FTS. I found that all autoindexed email are using "user1(a)example.com" as username, as shown in maillog: indexer-worker(user1(a)example.com): Indexed 1 messages in INBOX However, all manually indexed email (triggered by IMAP server search) are using "user1" as username, as shown in maillog: indexer-worker(user1): Indexed 2927 messages in INBOX. I am using "user1" as login name, so all autoindexed mails don't appear in search result. How can I use "user" as the username in autoindex? BTW, I do have a few mailboxes in the format user2(a)virtualmail.example.com, which requires full email address as the login name. How can I autoindex emails that automatically distinguishes user1(a)example.com (using "user1" as username) and user2(a)virtualmail.example.com (using "user2(a)virtualmail.example.com" as username) given that the previous question is solved?

1 0

[Dovecot] Dovecot XAPPLEPUSHSERVICE Apple
by Volker Schwaberow 10 Apr '14

10 Apr '14

Hello list. Anybody having experience with the Apple Extensions for Dovecot at http://www.opensource.apple.com/source/dovecot/dovecot-239.8/dovecot/src/im… ? Is it possible to patch the Dovecot source with them and get them to work on a Non-Apple System? Cheers, Volker —— Volker Schwaberow Email: volker(a)schwaberow.de

3 2

[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