- dovecot - dovecot.org

imap-login segfaults when using post-login
by Nico Rittner 26 Nov '14

26 Nov '14

hello, i get these lines in syslog when using post-login within imap-login: imap-login: Fatal: master: service(imap-login): child 574 killed with signal 11 (core dumps disabled) imap[5523]: segfault at 14 ip b7556276 sp bfc1c940 error 4 in libdovecot.so.0.0.0[b7529000+d4000] these are the relevant sections i added: service imap-login { executable = imap post-login } service post-login { executable = script-login /path/to/exec } i also used /bin/true as /path/to/exec to exclude the used exec itself as the reason. same result. version is 2.2.13 on gentoo-linux. i wonder if this error is gentoo-specific (cflags/etc...) or a bug in dovecot. this behaviour can be reproduced on two other of my gentoo-machines. same configuration worked in previous versions, don't know the exact version number. thanks a lot for your suggestions. i'll also cc to the gentoo-people. nico

2 1

Sieve counterpart of IMAP SPECIAL-USE
by Peter Mogensen 26 Nov '14

26 Nov '14

Hi, It would be useful to allow Sieve scripts to "fileinto" based on SPECIAL-USE flags. But all I've been able to find about it is this: http://www.ietf.org/mail-archive/web/sieve/current/msg05171.html Has there been any progress since? /Peter

1 0

slow incremental indexing of maildirs with squat
by vitalif＠yourcmc.ru 26 Nov '14

26 Nov '14

Hi! I'm using Dovecot 2.1.7 on Debian Wheezy 32-bit (package version is 1:2.1.7-7+deb7u1) with maildirs. My problem is that the incremental indexing of maildirs with squat takes a very long time... I don't know if it reindexes anything, but it seems it iterates though all messages on each search query and reads them. It works fast only on successive queries within several minutes, probably because of the messages being in cache. What do you think, is it a bug? -- With best regards, Vitaliy Filippov

2 1

Shared mailboxes using SQL
by Daniel Miller 26 Nov '14

26 Nov '14

I recently tried to change from the simple file to a SQL dictionary for ACL. While the Wiki instructions seemed fairly clear I was having errors. After some further digging, and a little thinking - I read the errors and tried to infer what was happening. I have some IMAP groups configured for sharing. And I guessed the example dictionary didn't allow for them. Looking at my existing shared-mailboxes.db flat file I saw something that gave me a clue. So I added the following: map { pattern = shared/shared-boxes/group/$to/$from table = user_shares value_field = dummy fields { from_user = $from to_user = $to } } And things started working again! A suggestion that perhaps this be added to the wiki - possibly with a bit more information on the "map" sections. Also - would there be any benefit to setting up a separate SQL table for groups? -- Daniel

1 0

v2.2.14 released
by Timo Sirainen 25 Nov '14

25 Nov '14

http://dovecot.org/releases/2.2/dovecot-2.2.14.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.14.tar.gz.sig Looks like it took a bit longer to make this release after RC1 than I thought. I'm now in San Jose area for a few months and still jumping between apartments and trying to adjust to the new timezone. Some of the more important fixes since RC1: - Fixed several race conditions with dovecot.index.cache handling that may have caused unnecessary "cache is corrupted" errors. - auth: If auth client listed userdb and disconnected before finishing, the auth worker process got stuck (and eventually all workers could get used up and requests would start failing). Some of the larger changes since v2.2.13: * lmtp: Delivered-To: header no longer contains <> around the email address. Other MDAs don't have it either. * "Out of disk space" errors are now treated as temporary errors (not the same as "Out of disk quota"). * replication plugin: Use replication only for users who have a non-empty mail_replica setting. + lmtp proxy: Log a line about each mail delivery. + Added login_source_ips setting. This can be used to set the source IP address round-robin from a pool of IPs (in case you run out of TCP ports). + Rawlog settings can use tcp:<host>:<port> as the path. + virtual plugin: Don't keep more than virtual_max_open_mailboxes (default 64) number of backend mailboxes open. + SSL/TLS compression can be disabled with ssl_options=no_compression + acl: Global ACL file now supports "quotes" around patterns. + Added last-login plugin to set user's last-login timestamp on login. + LDAP auth: Allow passdb credentials lookup also with auth_bind=yes - IMAP: MODSEQ was sent in FETCH reply even if CONDSTORE/QRESYNC wasn't enabled. This broke at least old Outlooks. - passdb static treated missing password field the same as an empty password field. - mdbox: Fixed potential infinite looping when scanning a broken mdbox file. - imap-login, pop3-login: Fixed potential crashes when client disconnected unexpectedly. - imap proxy: The connection was hanging in some usage patterns. This mainly affected older Outlooks. - lmtp proxy: The proxy sometimes delivered empty mails in error situations or potentially delivered truncated mails. - fts-lucene: If whitespace_chars was set, we may have ended up indexing some garbage words, growing the index size unnecessarily. - -c and -i parameters for dovecot/doveadm commands were ignored if the config socket was readable. - quota: Quota recalculation didn't include INBOX in some setups. - Mail headers were sometimes added to dovecot.index.cache in wrong order. The main problem this caused was with dsync+imapc incremental syncing when the second sync thought the local mailbox had changed. - doveadm backup didn't notice if emails were missing from the middle of the destination mailbox. Now it deletes and resyncs the mailbox.

7 8

Message is missing GUID
by Ralf Hildebrandt 25 Nov '14

25 Nov '14

# doveadm force-resync -u username inbox doveadm(username): Warning: fscking index file /srv/vmail/04/05/14331/mdbox/storage/dovecot.map.index doveadm(username): Warning: mdbox /srv/vmail/04/05/14331/mdbox/storage: rebuilding indexes doveadm(username): Error: Corrupted dbox file /srv/vmail/04/05/14331/mdbox/storage/m.122 (around offset=10056504): Message is missing GUID doveadm(username): Error: mdbox rebuild: Failed to fix file /srv/vmail/04/05/14331/mdbox/storage/m.122 Can I fix this somehow? % doveadm fetch -u username body ALL > /dev/null % doveadm fetch -u ulli.achter(a)posteo.de GUID ALL > /dev/null Don't throw errors! -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein

1 0

Re: failed login message
by 24x7server＠24x7server.net 25 Nov '14

25 Nov '14

thanks for your reply i intentionaly put the wrong password and checked the dovecot log and the message i got was # tail -f /var/log/dovecot.log | grep "xxx(a)yyy.com" Nov 25 08:47:46 imap-login: Info: Aborted login (auth failed, 1 attempts in 2 secs): user=<xxx(a)yyy.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, session=<xObTWqYIwgB/AAAB> but in the squirrelmail login page instead of the message "unknown user or password incorrect" i get the message ERROR: Connection dropped by IMAP server. Query: LOGOUT in my old server where it is working correctly dovecot logs shows the error Nov 25 14:46:12 imap-login: Info: Aborted login (auth failed, 1 attempts): user=<"xxx(a)yyy.com">, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured and squirrelmail gives the error : "unknown user or password incorrect" which is correct. is there any other place i need to check or some other config file (either squirrelmail or dovecot) that i need to modify could you kindly guide me rajesh ----- Original Message ----- From: Robert Schetterer [mailto:rs@sys4.de] To: dovecot(a)dovecot.org Sent: Sun, 23 Nov 2014 17:21:29 +0100 Subject: Re: failed login message Am 23.11.2014 um 17:14 schrieb Rajesh M.: > hi > > i am using dovecot for pop3 and imap along with qmail toaster > > i had recently changed over from a 32 bit system to a 64 bit system. > > i use squirrelmail. > > the issue i face is that when the user inserts an invalid password then the message he gets is connection dropped by imap server (instead of invalid userid or password) > > such a message confuses the user. > > my earlier 32 bit version used to give the correct message > > i am posting this issue here because i am not sure if this is squirrelmail issue or a dovecot issue. > > can somebody please let me know the reason for this ? > > rajesh > yes , you may ask some magic bubble, or post your configs and related logs Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein

2 1

Possible to adjust username used to determine the proxy destination?
by Andy Dills 25 Nov '14

25 Nov '14

I'm in a fairly standard cluster environment: shared storage, bunch of servers each acting as both proxies and backends. We do /bin/checkpassword authentication, allowing a great deal of flexibility...protection against brute force, billing mechanisms, but relevant to this issue, I have it set up to allow users to login with either their username (if they are in one of our default domains) or their email address. I'm realizing now that as a consequence of this, "joe" and "joe(a)xecu.net" are unique as far as dovecot is concerned. Users who login with just their username (and not the full email address) can get assigned to a different backend server than when they login with the full email address (which would also include LMTP deliveries). This has been happening for years, a few broken indexes here and there that seem to resolve themselves, so it hasn't been impacting the service, but I'd like to correct it properly. Is there a way to manipulate this? For example, if I moved the authentication to the proxy layer (it's currently proxy=y nopassword=y), and set $ENV{USER} to the full email address, will director use that for selection instead of the user-supplied username? I'm open to suggestions on how best to accomplish this. Thanks, Andy --- Andy Dills Xecunet, Inc. www.xecu.net 301-682-9972 ---

3 2

doveadm backup for all users to file system
by Jeff Larsen 24 Nov '14

24 Nov '14

The wiki says that doveadm backup supports the -A option for all users, but when I specify a file-system destination (like /tmp, or an NFS mounted folder), it just rewrites each user backup to the same location overwriting the previous user's content. You end up with just the content for the last user processed. I tried the typical %u substitution but that just created folder named '%u' and had the same overwrite problem. My userdb is LDAP which works just fine for other doveadm commands. The verbose/debug output from doveadm backup shows that it is processing every user. Example: doveadm -vD backup -A sdbox:/tmp/backup My understanding is that "doveadm backup" is just a front-end for dsync. The dsync manpage on the other hand says "dsync can currently sync only one user at a time. If you want to dsync all users, you'll need to get a list of all users and execute dsync separately..." It appears that "doveadm backup -A" is doing the iteration for me, but it's not generating individual destination paths for each user. So, is this is a documentation problem for "doveadm backup"? Or am I missing something here? Is there some secret sauce for "doveadm backup -A" that I'm not finding? If all else fails, I know I can write a script to iterate over the available users and run the backup repeatedly, but I would like to keep this as simple as possible. Thanks, Jeff

1 0

Replication warnings
by Jan Behrend 24 Nov '14

24 Nov '14

Hi list, I get these warnings quite frequently. Warning: Failed to do incremental sync for mailbox INBOX, retry with a full sync Is this something to worry about? Otherwise the replication works perfectly. Cheers Jan -- MAX-PLANCK-INSTITUT fuer Radioastronomie Jan Behrend - Rechenzentrum ---------------------------------------- Auf dem Huegel 69, D-53121 Bonn Tel: +49 (228) 525 359, Fax: +49 (228) 525 229 jbehrend(a)mpifr-bonn.mpg.de http://www.mpifr-bonn.mpg.de

2 1