- dovecot - dovecot.org

[Dovecot] Dovecot 1.x on AIX -> Dovecot 2.x on Ubuntu
by root＠yuma.acns.colostate.edu 10 Jun '12

10 Jun '12

We are working on migrating Dovecot 1.2.17 running on AIX 5.3 (believe it or not!) to Dovecot 2.0.13 running on Ubuntu. We have hundreds of users mboxes we will be migrating. My question is regarding the index files. Should we remove those after the migration, but before we open it up to users so Dovecot can create new ones? I did a test migration of a single user, and Dovecot detects the architecture change and put out some panic errors, corrupt files and backtrace messages in syslog on Ubuntu. The messages are shown below. If every user is going to generate these types of errors, I'm thinking maybe it makes sense to remove all the .imap directories and let Dovecot create new clean ones. I realize that may slow things down for awhile while Dovecot is rebuilding new files. Thanks for any info. Jackie Hunt Acad Computing & Networking Srvcs Colorado State University Jun 6 13:43:02 newlamar dovecot: imap-login: Login: user=<cacti>, method=PLAIN, rip=129.82.100.64, lip=129.82.100.124, mpid=19593, TLS Jun 6 13:43:21 newlamar dovecot: imap-login: Login: user=<cacti>, method=PLAIN, rip=129.82.100.64, lip=129.82.100.124, mpid=19597, TLS Jun 6 13:43:21 newlamar dovecot: imap-login: Login: user=<cacti>, method=PLAIN, rip=129.82.100.64, lip=129.82.100.124, mpid=19600, TLS Jun 6 13:44:11 newlamar dovecot: imap(cacti): Disconnected: Logged out bytes=107/441 Jun 6 13:44:11 newlamar dovecot: imap(cacti): Disconnected: Logged out bytes=1676/2724868 Jun 6 13:44:11 newlamar dovecot: imap(cacti): Disconnected: Logged out bytes=129/759 Jun 6 13:51:49 newlamar dovecot: imap-login: Login: user=<cacti>, method=PLAIN, rip=129.82.100.64, lip=129.82.100.124, mpid=19657, TLS Jun 6 13:51:49 newlamar dovecot: imap(cacti): Error: Rebuilding index file /adhome/cacti/.imap/INBOX/dovecot.index: CPU architecture changed Jun 6 13:51:58 newlamar dovecot: imap-login: Login: user=<cacti>, method=PLAIN, rip=129.82.100.64, lip=129.82.100.124, mpid=19662, TLS Jun 6 13:51:58 newlamar dovecot: imap(cacti): Error: Corrupted transaction log file /adhome/cacti/.imap/Trash/dovecot.index.log seq 16777216: log file shrank (1428 < 6144) (sync_offset=6144) Jun 6 13:51:58 newlamar dovecot: imap(cacti): Panic: file buffer.c: line 295 (buffer_set_used_size): assertion failed: (used_size <= buf->alloc) Jun 6 13:51:58 newlamar dovecot: imap(cacti): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x374fa) [0x7f3ada59c4fa] -> /usr/lib/dovecot/libdovecot.so.0(+0x3753e) [0x7f3ada59c53e] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f3ada576837] -> /usr/lib/dovecot/libdovecot.so.0(+0x35319) [0x7f3ada59a319] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_transaction_log_file_open+0x21e) [0x7f3ada87acee] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_transaction_log_open+0xb8) [0x7f3ada877a68] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_open+0xe5) [0x7f3ada860e75] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_mailbox_open+0xbc) [0x7f3ada826eac] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x5f7fb) [0x7f3ada8417fb] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x28c4c) [0x7f3ada80ac4c] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_mailbox_enable+0x24) [0x7f3ada827584] -> dovecot/imap(imap_status_get+0xfd) [0x7f3adacead8d] -> doveco t/imap(cmd_status+0x182) [0x7f3adace1f92] -> dovecot/imap(+0x1105d) [0x7f3adace405d] -> dovecot/imap(+0x11135) [0x7f3adace4135] -> dovecot/imap(client_handle_input+0x125) [0x7f3adace4385] -> dovecot/imap(client_input+0x65) [0x7f3adace4c35] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x48) [0x7f3ada5a8048] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xa7) [0x7f3ada5a90c7] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7f3ada5a7fd8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f3ada5962c3] -> dovecot/imap(main+0x2f4) [0x7f3adacdc544] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f3ada1e530d] -> dovecot/imap(+0x95d5) [0x7f3adacdc5d5] Jun 6 13:51:59 newlamar dovecot: imap-login: Login: user=<cacti>, method=PLAIN, rip=129.82.100.64, lip=129.82.100.124, mpid=19664, TLS Jun 6 13:51:59 newlamar dovecot: imap(cacti): Error: Transaction log file /adhome/cacti/.imap/Trash/dovecot.index.log: marked corrupted Jun 6 13:51:59 newlamar dovecot: imap(cacti): Error: Rebuilding index file /adhome/cacti/.imap/Trash/dovecot.index: CPU architecture changed

3 2

[Dovecot] per user quota
by Andreas Meyer 09 Jun '12

09 Jun '12

Hello! I activated quota plugin { quota = maildir:User quota quota_rule = *:storage=1GB # 10% of 1GB = 100MB quota_rule2 = Trash:storage=+10%% } But when I want to do per user quota in the passwd-file ...vhosts/anup.de/anmeyer::userdb_mail=maildir:~/userdb_quota_rule=*:bytes=10G I get this in the logfile and can't login: Jun 08 22:25:52 imap(anmeyer(a)anup.de): Error: user anmeyer(a)anup.de: Initialization failed: Initializing mail storage from mail_location setting failed: Unknown setting: bytes Jun 08 22:25:52 imap(anmeyer(a)anup.de): Error: Invalid user settings. Refer to server log for more information. Same with 'storage' in the passwd-file. What's wrong? Andreas

2 2

[Dovecot] director and doveadm server
by Angel L. Mateo 09 Jun '12

09 Jun '12

Hi, I've been reading doc at http://wiki2.dovecot.org/Director to configure my servers. My question is regarding configuration of doveadm server. I have configured both, director and backend servers, as described in that doc, but I don't know how to run doveadm commands in director servers. doveadm is working, because I can run commands, but they are executed in local (director) server. For example: root@myotis40:/etc/dovecot/conf.d# doveadm director status mail server ip vhosts users 155.54.211.169 100 1 but doveadm who seems to be executed just in local: (backend server) root@myotis30:/etc/dovecot/conf.d# doveadm who username # proto (pids) (ips) angel.luis 2 imap (11931 11936) (155.54.67.5) (director server) root@myotis40:/etc/dovecot/conf.d# doveadm who username # proto (pids) (ips) And another question about this... what is the local config option? I haven't found it documented anywhere. -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información _o) y las Comunicaciones Aplicadas (ATICA) / \\ http://www.um.es/atica _(___V Tfo: 868887590 Fax: 868888337

2 1

[Dovecot] director and IPs shown at the backends
by Angel L. Mateo 09 Jun '12

09 Jun '12

Hello, I am configuring a dovecot imap/pop servers with a dovecot director in front of them. Because I am using director proxy, connections in the backends are show as coming from director IPs. Is there any way to configure director (or backends) so the backends know (and report) the original IP instead of the director IP?

3 3

[Dovecot] Corrupted mdbox on LMTP director delivery while user is logged in via IMAP
by Daniel Parthey 09 Jun '12

09 Jun '12

Hi, we get errors about corrupted indexes and we are losing flags with mdbox on NFSv4: Error: Recent flags state corrupted for mailbox Error: Corrupted dbox file Error: Corrupted transaction log file It looks like a LMTP director problem. The user has IMAP IDLE connections open and lmtp delivers to another host. This leads to nfs corruption problems. The user is logged into mail04 and has some IMAP IDLE mailbox connections open: mail04:~# ps -ef|grep someuser vmail 5217 23918 0 Jun07 ? 00:00:00 dovecot/imap [someuser(a)example.de 10.129.3.190 IDLE] vmail 8623 23918 0 Jun07 ? 00:00:00 dovecot/imap [someuser(a)example.de 10.129.3.233 IDLE] vmail 20279 23918 0 00:37 ? 00:00:00 dovecot/imap [someuser(a)example.de 10.129.3.213 IDLE] If postfix on mail01/dcmailbox01 receives an incoming mail now, the director on mail01 does NOT direct LMTP to the responsible host mail04/dcmailbox04 (10.129.3.190), but delivers it locally to mail01 (10.129.3.193), which leads to file corruption. mail01:~# doveadm -c /etc/dovecot-director/dovecot-director.conf director status someuser(a)example.de Current: not assigned Hashed: 10.129.3.193 Initial config: 10.129.3.193 mail01:~# host 10.129.3.193 193.3.129.10.in-addr.arpa domain name pointer dcmailbox01.example.net. mail01 runs the lmtp proxy and lmtp delivery, even though the user is logged in via IMAP IDLE on mail04: mail01:~# grep "^Jun 8 03:36:.*someuser@example.de" /var/log/server/dovecot.log Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27124): Debug: auth input: someuser(a)example.de home=/mail/dovecot/example.de/someuser uid=501 gid=123 quota_rule=*:bytes=5000M:messages=0 Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27124, someuser(a)example.de) Debug: Effective uid=501, gid=123, home=/mail/dovecot/example.de/someuser Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27124, someuser(a)example.de) Debug: Quota root: name=User quota backend=dict args=:proxy::quota Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27124, someuser(a)example.de) Debug: Quota rule: root=User quota mailbox=* bytes=5242880000 messages=0 Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27124, someuser(a)example.de) Debug: Quota rule: root=User quota mailbox=Trash bytes=+104857600 messages=0 Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27124, someuser(a)example.de) Debug: Quota warning: bytes=4980736000 (95%) messages=0 reverse=no command=quota-warning 95 someuser(a)example.de Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27124, someuser(a)example.de) Debug: Quota warning: bytes=4194304000 (80%) messages=0 reverse=no command=quota-warning 80 someuser(a)example.de Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27124, someuser(a)example.de) Debug: dict quota: user=someuser(a)example.de, uri=proxy::quota, noenforcing=0 Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27124, someuser(a)example.de) Debug: fs: root=/mail/dovecot/example.de/someuser/mail, index=, control=, inbox=, alt= Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27124, someuser(a)example.de) Debug: Namespace : Using permissions from /mail/dovecot/example.de/someuser/mail: mode=0700 gid=-1 Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27124, someuser(a)example.de) Debug: sieve: include: sieve_global_dir is not set; it is currently not possible to include `:global' scripts. Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27124, someuser(a)example.de) Debug: jOv8JgJX0U/0aQAA3l+BKA: sieve: using sieve path for user's script: /mail/dovecot/example.de/someuser/.dovecot.sieve Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27124, someuser(a)example.de) Debug: jOv8JgJX0U/0aQAA3l+BKA: sieve: opening script /mail/dovecot/example.de/someuser/.dovecot.sieve Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27124, someuser(a)example.de) Debug: jOv8JgJX0U/0aQAA3l+BKA: sieve: script binary /mail/dovecot/example.de/someuser/.dovecot.svbin successfully loaded Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27124, someuser(a)example.de) Debug: jOv8JgJX0U/0aQAA3l+BKA: sieve: binary save: not saving binary /mail/dovecot/example.de/someuser/.dovecot.svbin, because it is already stored Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27124, someuser(a)example.de) Debug: jOv8JgJX0U/0aQAA3l+BKA: sieve: executing script from /mail/dovecot/example.de/someuser/.dovecot.svbin Jun 8 03:36:02 10.129.3.213 dovecot: lmtp(23404): Debug: auth input: user=someuser(a)example.de proxy port=19024 host=10.129.3.193 proxy_refresh=450 Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27124, someuser(a)example.de) jOv8JgJX0U/0aQAA3l+BKA: sieve: mailbox: deliver: msgid=<201206080136.q581a1Rc024891(a)iolite.ham.srv.mcs.de> from=service(a)cityline.net: stored mail into mailbox 'INBOX' Jun 8 03:36:02 10.129.3.213 dovecot: lmtp(23406): Debug: auth input: user=someuser(a)example.de proxy port=19024 host=10.129.3.193 proxy_refresh=450 Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27125): Debug: auth input: someuser(a)example.de home=/mail/dovecot/example.de/someuser uid=501 gid=123 quota_rule=*:bytes=5000M:messages=0 Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27125, someuser(a)example.de) Debug: Effective uid=501, gid=123, home=/mail/dovecot/example.de/someuser Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27125, someuser(a)example.de) Debug: Quota root: name=User quota backend=dict args=:proxy::quota Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27125, someuser(a)example.de) Debug: Quota rule: root=User quota mailbox=* bytes=5242880000 messages=0 Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27125, someuser(a)example.de) Debug: Quota rule: root=User quota mailbox=Trash bytes=+104857600 messages=0 Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27125, someuser(a)example.de) Debug: Quota warning: bytes=4980736000 (95%) messages=0 reverse=no command=quota-warning 95 someuser(a)example.de Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27125, someuser(a)example.de) Debug: Quota warning: bytes=4194304000 (80%) messages=0 reverse=no command=quota-warning 80 someuser(a)example.de Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27125, someuser(a)example.de) Debug: dict quota: user=someuser(a)example.de, uri=proxy::quota, noenforcing=0 Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27125, someuser(a)example.de) Debug: fs: root=/mail/dovecot/example.de/someuser/mail, index=, control=, inbox=, alt= Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27125, someuser(a)example.de) Debug: Namespace : Using permissions from /mail/dovecot/example.de/someuser/mail: mode=0700 gid=-1 Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27125, someuser(a)example.de) Debug: sieve: include: sieve_global_dir is not set; it is currently not possible to include `:global' scripts. Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27125, someuser(a)example.de) Debug: gWijMAJX0U/1aQAA3l+BKA: sieve: using sieve path for user's script: /mail/dovecot/example.de/someuser/.dovecot.sieve Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27125, someuser(a)example.de) Debug: gWijMAJX0U/1aQAA3l+BKA: sieve: opening script /mail/dovecot/example.de/someuser/.dovecot.sieve Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27125, someuser(a)example.de) Debug: gWijMAJX0U/1aQAA3l+BKA: sieve: script binary /mail/dovecot/example.de/someuser/.dovecot.svbin successfully loaded Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27125, someuser(a)example.de) Debug: gWijMAJX0U/1aQAA3l+BKA: sieve: binary save: not saving binary /mail/dovecot/example.de/someuser/.dovecot.svbin, because it is already stored Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27125, someuser(a)example.de) Debug: gWijMAJX0U/1aQAA3l+BKA: sieve: executing script from /mail/dovecot/example.de/someuser/.dovecot.svbin Jun 8 03:36:02 10.129.3.233 dovecot: lmtp(27125, someuser(a)example.de) gWijMAJX0U/1aQAA3l+BKA: sieve: mailbox: deliver: msgid=<201206080136.q581a1t0024890(a)iolite.ham.srv.mcs.de> from=service(a)cityline.net: stored mail into mailbox 'INBOX' The "user logged on via IMAP on mail04" and "lmtp delivery on mail01" seems to lead to corruption of mdbox indexes: Jun 8 03:36:03 10.129.3.200 dovecot: mailbox: mail: imap(someuser(a)example.de): Error: Corrupted transaction log file /mail/dovecot/example.de/someuser/mail/mailboxes/INBOX/dbox- Mails/dovecot.index.log seq 82: Invalid transaction log size (32856 vs 32824): /mail/dovecot/example.de/someuser/mail/mailboxes/INBOX/dbox-Mails/dovecot.index.log (sync_offset=32856) Jun 8 03:36:03 10.129.3.200 dovecot: mailbox: mail: imap(someuser(a)example.de): Error: Index /mail/dovecot/example.de/someuser/mail/mailboxes/INBOX/dbox-Mails/dovecot.index: Lost log for seq=82 offset=32856 Jun 8 03:36:03 10.129.3.200 dovecot: mailbox: mail: imap(someuser(a)example.de): Warning: fscking index file /mail/dovecot/example.de/someuser/mail/mailboxes/INBOX/dbox-Mails/dovecot.index Jun 8 03:36:03 10.129.3.200 dovecot: mailbox: mail: imap(someuser(a)example.de): Error: Fixed index file /mail/dovecot/example.de/someuser/mail/mailboxes/INBOX/dbox-Mails/dovecot.index: log_file_seq 82 -> 83 Jun 8 03:36:38 10.129.3.200 dovecot: mailbox: mail: imap(someuser(a)example.de): Error: Transaction log file /mail/dovecot/example.de/someuser/mail/mailboxes/INBOX/dbox-Mails/dovecot.index.log.2: marked corrupted How to enable the LMTP director to deliver to the correct mailbox host? Configuration of mailbox and director of mail01 is attached. Regards, Daniel

1 1

[Dovecot] ntlm_auth in Dovecot
by Leonardo 09 Jun '12

09 Jun '12

Hi, I'm trying getting NTLM auth working against AD in my Dovecot 2.0.15. I'm getting the following error: Jun 08 14:18:11 auth: Info: winbind(?,10.44.3.151): user not authenticated: NT_STATUS_UNSUCCESSFUL "wbinfo -u" reports all the users of the domain and "ntlm_auth --username=%name% --domain="%domain%" gets authenticated successfully. Debugging winbind I can see the following error: [2012/06/08 14:18:11.129611, 10] winbindd/winbindd.c:651(process_request) process_request: unknown request fn number 14 [2012/06/08 14:18:11.129671, 10] winbindd/winbindd.c:738(winbind_client_response_written) winbind_client_response_written[2822:unknown request]: delivered response to client My dovecot.conf is the following: auth_mechanisms = plain ntlm login auth_username_format = %n auth_verbose = yes auth_winbind_helper_path = /usr/bin/ntlm_auth auth_use_winbind = yes auth_debug = yes disable_plaintext_auth = no info_log_path = /var/log/dovecot-info.log log_path = /var/log/dovecot.log mail_location = maildir:/var/mail/domains/%d/%n plugin { autocreate = Trash autocreate2 = Spam autocreate3 = Sent autosubscribe = Trash autosubscribe2 = Spam autosubscribe3 = Sent } protocols = imap ssl = no userdb { driver = static args = uid=100 gid=101 home=/var/mail/domains/%d/%n first_valid_uid=100 } passdb ldap { driver = ldap args = /etc/dovecot/dovecot-ldap.conf } protocol imap { mail_plugins = autocreate } Sounds like there is an issue when Dovecot runs "ntlm_auth". It doesn't appear to be a permission issue (perms are 755). Any help is appreciated. Thank you in advance. -- leonardo.

1 2

[Dovecot] [ Re: best practises for mail systems]
by Michescu Andrei 09 Jun '12

09 Jun '12

Hello, If disk space and bandwidth are affordable (and from your setup it seems that they are affordable as you have everything locally) I would split the mail storage completely and use replication in between n-master servers (n=2 for your case). The replication is not yet fully tested, but Timo is actively working on this feature. The fear of lossing the imap session does not make sense (at least to me) as the client will reconnect automatically in the background. Like this you have no SPOF and no split-brain and you get the flexibility (if needed) to geographically distribute your servers in the the future. Keep each server with its own ip, connect to them via DNS (round robin etc etc). We are currently experimenting with a setup similar to this one, but with geographically distributed servers (trans-continental) (bandwidth limited and high cost). Best regards, Andrei > We once try to use similar solution as your first. > > 3 servers for LVS -HA > > This master server redirect users for 2 or 3 dovecot backends.. > > The mail storage were maildir ontop of OCFS2 > > Our problem were that OCFS2 were too slow. We could not handle many users. > > So we took an step back and now use only user one server. > > But still thinking in go back to the first one. with LVS > > When using LVS try to sticky user to the same backend, LVs can do ths by > source ip. > > Where i work we have problens on testign storage. If you have any advices > for testing disk performance, i will be thankfull. > > I wil be glad to answer anything else. > > []'sf.rique > > > On Tue, Jun 5, 2012 at 9:59 AM, ëÏÓÔÙÒÅ× áÌÅËÓÁÎÄÒ áÌÅËÓÅÅ×ÉÞ < > a.kostyrev(a)serverc.ru> wrote: > >> I think LVS is just fine and it is not a SPOF 'cause it is actually 2 >> servers: >> active master --> and standby slave. >> LVS supports real time replication of connections from master to slave, >> so if master dies slave knows which IP was connected to which dovecot >> server. >> >> I'm more worried about right design of mailstorage.. should I use some >> cluster fs with all mail of all users >> or should I split mailstorage across servers and somehow avoid long >> downtime if one of servers goes down. >> >> >> -----Original Message----- >> From: dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org] >> On >> Behalf Of Matthias-Christian Ott >> Sent: Tuesday, June 05, 2012 11:28 PM >> To: dovecot(a)dovecot.org >> Subject: Re: [Dovecot] best practises for mail systems >> >> On 2012-06-05 05:14, ëÏÓÔÙÒÅ× áÌÅËÓÁÎÄÒ áÌÅËÓÅÅ×ÉÞ wrote: >> > On each host system we created one VM and passed through 3x2TB disks >> into it. >> > >> > >> > >> > In guests vms on top of this disks we made XFS and fired up glusterfs >> with distributed replicated volumes for our mailstorage. >> > >> > so it looks like this: >> > >> > >> > >> > vm1 replicate vm2 >> > >> > disk1 ------------> disk4 >> > >> > disk2 ------------> disk5 >> > >> > disk3 ------------> disk6 >> > >> > >> > >> > in each vm we mounted glusterfs and pointed dovecot to that dir for >> mail >> creation (as ltmp) and imap4 user access. >> > >> > also we use exim as smtp. >> > >> > >> > >> > So, with glusterfs as mailstorage we can go for LVS to load balancing >> for exim and dovecot. >> > >> > so wherenever one of host systems (hence one of mail vms) goes down, >> users don't notice that >> > >> > 'cause LVS points them to working smtp and imap4 servers >> > >> > and they get their mail 'cause of glusterfs. >> > [...] >> > Cons: >> > >> > - not quite sure if glusterfs is production ready solution 'cause I've >> experienced split-brains during setting it up >> > >> > - IO performance issue. Though we didn't yet run any io tests, but >> glusterfs uses fuse to mount on clients. And guys on #gluster told me >> writing to the glusterfs mount will not be strictly local io. >> >> I'm not familiar with LVS, but from the project description it seems >> that you need a "front server" that does the load balancing, so you >> either have to run at least two of these servers in parallel or add to >> your cons that you introduced a single point of failure. But you >> mentioned that you only have two servers, so you really can do this. >> >> I would rather ensure high availability by running the two servers as >> masters and using either IP address takeover or DNS failover (with >> dynamic DNS) and either use Dovecot's replication (I haven't tested it >> yet and I'm not sure what happens in case of IP address takeover) or a >> file system that can handle these kinds of errors (e.g. Coda). You could >> do load balancing via round-robin DNS. This only protects you against >> the failure of single machine and because IMAP sessions are not >> replicated between the servers, connections will get reset if one server >> fails, but it's cost-effective and uses software that already exists. >> >> Regards, >> Matthias-Christian >> > > > !DSPAM:4fce037e104291424646138! >

4 9

[Dovecot] 2.0.X -> 2.1 pitfalls?
by Frank Elsner 09 Jun '12

09 Jun '12

Hi all, are there any pitfalls known for the migration from 2.0.18 to 2.1? Can I simply stop dovecot, make install and start again? --Frank Elsner

10 22

[Dovecot] Maildir filename has wrong S value
by Wouter de Geus 09 Jun '12

09 Jun '12

Hello folks, This morning I tried to open an old archive mail folder using Mutt. However, while fetching headers it aborted. Checking the dovecot log gave me this: @400000004fb21996267d37d4 imap(benv): Error: Cached message size smaller than expected (9115 < 9420) @400000004fb21996267e8bac imap(benv): Error: Maildir filename has wrong S value, renamed the file from /home/vpopmail/domains/benv.junerules.com/benv/Maildir/.Old.2009/cur/1260395566.28175.black,S=9115:2,S to /home/vpopmail/domains/benv.junerules.com/benv/Maildir/.Old.2009/cur/1260395566.28175.black,S=9420:2,S @400000004fb21996267e937c imap(benv): Error: Corrupted index cache file /home/vpopmail/domains/benv.junerules.com/benv/Maildir/.Old.2009/dovecot.index.cache: Broken physical size for mail UID 294 @400000004fb21996267eaaec imap(benv): Error: read(/home/vpopmail/domains/benv.junerules.com/benv/Maildir/.Old.2009/cur/1… failed: Input/output error (uid=294) @400000004fb219962680683c imap(benv): Info: Disconnected: Internal error occurred. Refer to server log for more information. [2012-05-15 10:53:32] in=6503 out=192718 I've retried opening this folder several times, but each time Dovecot only fixes 1 file and then aborts. (the folder apparently has a lot more files with incorrect sizes). My question here is: Why does dovecot abort? Isn't the issue fixed after the rename? Also: The files are not corrupted or unreadable, reading them through the commandline works fine. I've looked through my backups and saw that at least half a year ago this mismatch in size was already present. I've been running dovecot for quite a while, so the cause of this size mismatch might very well be a issue in an older version of dovecot / my configuration. Right now I'm running dovecot 2.1.6, but I've been running the v1.2 version for quite a while before that. Is this something that can be improved in dovecot so it doesn't abort after 1 rename? (of course I could script a rename operation, but that seems like a workaround to me) Thanks for reading. Wouter. My current configuration: ========================= # 2.1.6: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32.32-g3d14ce7 x86_64 Slackware 11.0.0 base_dir = /var/run/dovecot2/ disable_plaintext_auth = no first_valid_uid = 89 info_log_path = /dev/stderr last_valid_uid = 89 log_path = /dev/stderr log_timestamp = mail_debug = yes mail_location = maildir:~/Maildir mail_max_userip_connections = 50 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 e nvironment mailbox date namespace { inbox = yes location = prefix = INBOX. separator = . type = private } passdb { driver = vpopmail } plugin { autocreate = INBOX.Spam quota = maildir sieve = ~/.sieve/dovecot.sieve sieve_dir = ~/.sieve sieve_global_dir = /etc/dovecot/sieve/ sieve_subaddress_sep = -+ } protocols = imap pop3 sieve service auth { unix_listener auth-master { group = vchkpw mode = 0660 } unix_listener auth-userdb { group = vchkpw mode = 0660 } } service imap-login { inet_listener imap { address = [::] * port = 143 } inet_listener imaps { address = [::] * port = 993 } process_limit = 256 process_min_avail = 3 service_count = 1 user = dovecot } service managesieve-login { process_limit = 256 process_min_avail = 3 service_count = 1 user = dovecot } service pop3-login { inet_listener pop3 { address = [::] * port = 110 } inet_listener pop3s { address = [::] * port = 995 } process_limit = 256 process_min_avail = 3 service_count = 1 user = dovecot } ssl_cert = </var/qmail/control/servercert.pem ssl_cipher_list = ALL:!LOW ssl_key = </var/qmail/control/servercert.pem userdb { driver = vpopmail } verbose_proctitle = yes protocol lda { hostname = mail.benv.junerules.com info_log_path = /var/log/dovecot/dovecot2-deliver.log log_path = /var/log/dovecot/dovecot2-deliver-errors.log mail_plugins = sieve postmaster_address = postmaster(a)benv.junerules.com sendmail_path = /var/qmail/bin/sendmail } protocol imap { imap_max_line_length = 64 k mail_plugins = quota imap_quota autocreate } protocol pop3 { mail_plugins = quota autocreate pop3_no_flag_updates = no pop3_uidl_format = %v-%u } =================================

5 5

[Dovecot] 2.1.7 altmove not working
by Alex Crow 09 Jun '12

09 Jun '12

Hi list, I've just set up a 2.1.7 server, and have migrated a couple of accounts across from a 2.0.15 server, keeping the old configs. I have a strange problem on the new box in that altmove just doesn't work. I have my main storage under /home/email, indexes under /home/indexes and ALT under /home/email_archive. When I run the altmove command, the following broken symlink is created in /home/email/integrafin.co.uk/acrow: lrwxrwxrwx. 1 email email 54 Jun 8 10:46 dbox-alt-root -> /home/email_archive/integrafin.co.uk/a/acrow/mailboxes But nothing is created in the archive other than the empty directory: /home/email_archive/integrafin.co.uk/a/acrow. My mail_location is: mail_location = mdbox:/home/email/%d/%n:INDEX=/home/indexes/%d/%1n/%n:ALT=/home/email_archive/%d/%1n/%n This worked perfectly on the older server. I have attached my doveconf -a output. Any help much appreciated. Regards Alex

1 2