- dovecot - dovecot.org

Re: [Dovecot] Dovecot-deliver sometimes fails when message set to discard via sieve
by Tobias Lang 29 Dec '09

29 Dec '09

Am 28.12.2009 um 21:51 schrieb Steve Wagner: > Sorry it took some time to get in to this failing situation. > > Procmail log--> > > procmail: [29952] Mon Dec 28 21:36:33 2009 > procmail: Match on "< 256000" > procmail: Locking "spamassassin.lock" > procmail: Executing "/usr/bin/spamc,-U,/var/run/spamd.sock" > procmail: [29952] Mon Dec 28 21:36:35 2009 > procmail: Unlocking "spamassassin.lock" > procmail: No match on "^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*" > procmail: No match on "^X-Spam-Status: YES" > procmail: No match on "^List-Id: .*debian-arm.lists.debian.org" > procmail: No match on "^^rom[ ]" > procmail: Executing "/opt/dovecot/libexec/dovecot/deliver" > procmail: Error while writing to "/opt/dovecot/libexec/dovecot/deliver" > procmail: Assigning "LASTFOLDER=/opt/dovecot/libexec/dovecot/deliver" > procmail: Assigning > "LASTFOLDER=/home/lanwin/Maildir/new/1262032593.29952_2.vs5923" > procmail: Notified comsat: > "lanwin@0:/home/lanwin/Maildir/new/1262032593.29952_2.vs5923" > From KeineAntwortAdresse(a)web.de Mon Dec 28 21:36:33 2009 > Subject: discoTEL > =?ISO-8859-1?Q?Tarif=3A_F=FCr_7=2C5_Cent=2FMin=2E_telefonier > Folder: /home/lanwin/Maildir/new/1262032593.29952_2.vs5923 > 41096 > procmail: Unlocking "/home/lanwin/Maildir/.lockmail" > > Dovecot Deliver Log--> > > 2009-12-28 21:36:35 deliver(lanwin): Info: sieve: > msgid=<E1NPMKF-00014k-00(a)mxnl04.web.de>: marked message to be discarded > if not explicitly delivered (discard action) Does it always fail, if you try to do a discard, just sometimes? I am using Dovecot 1.2.9 "dovecot-1.2-sieve-0.1.14" and discarding email seems to work fine. The things I can think of are: 1) Wrong privileges for deleting. What user does procmail / deliver run as? 2) Old Bug in Sieve (http://www.dovecot.org/list/dovecot/2007-July/024290.html) 3) If it fails just sometimes, what is the difference between discarded and nondiscarded mails. If this does not turn up something, I do not have an idea what is going wrong. Only bugfix I then can you provide with, is not to discard but to move those files to a folder 'SPAM' and delete them by hand. Tobi

1 0

[Dovecot] Shared mailboxes do not support subfolders
by Nick Rosier 29 Dec '09

29 Dec '09

Hi, I'm currently running Dovecot 1.2.8 with dbox mailboxes. I've configured the use of shared mailboxes. I'm able to only see the top-level mailboxes: e.g. Inbox LogWatch Trash Sent but not LogWatch/Server1 LogWatch/Server2 Is this a know limitation of a bug? Rgds, N.

2 3

[Dovecot] sieve vs deliver -m
by Frank Cusack 29 Dec '09

29 Dec '09

I'm invoking deliver through postfix with a dovecot transport in master.cf, using the -m ${extension} argument. If I have no sieve script, or a sieve script with an implicit keep, the mail gets correctly filed into the -m mailbox. However if the sieve script has an explicit discard, this gets honored if it doesn't match another sieve action. Shouldn't -m take precedence? I would say that if an extension is present any other sieve action should be ignored, perhaps just sieve_before should be run then the message filed per the extension. -frank

2 7

[Dovecot] Fwd: Dovecot-deliver sometimes fails when message set to discard via sieve
by Tobias Lang 28 Dec '09

28 Dec '09

Anfang der weitergeleiteten E-Mail: > Von: Steve Wagner <lanwin(a)lanwin.de> > Datum: 28. Dezember 2009 21:51:39 MEZ > An: Tobias Lang <tobias.lang(a)evoscout.de> > Betreff: Re: [Dovecot] Dovecot-deliver sometimes fails when message set to discard via sieve > > Sorry it took some time to get in to this failing situation. > > Procmail log--> > > procmail: [29952] Mon Dec 28 21:36:33 2009 > procmail: Match on "< 256000" > procmail: Locking "spamassassin.lock" > procmail: Executing "/usr/bin/spamc,-U,/var/run/spamd.sock" > procmail: [29952] Mon Dec 28 21:36:35 2009 > procmail: Unlocking "spamassassin.lock" > procmail: No match on "^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*" > procmail: No match on "^X-Spam-Status: YES" > procmail: No match on "^List-Id: .*debian-arm.lists.debian.org" > procmail: No match on "^^rom[ ]" > procmail: Executing "/opt/dovecot/libexec/dovecot/deliver" > procmail: Error while writing to "/opt/dovecot/libexec/dovecot/deliver" > procmail: Assigning "LASTFOLDER=/opt/dovecot/libexec/dovecot/deliver" > procmail: Assigning > "LASTFOLDER=/home/lanwin/Maildir/new/1262032593.29952_2.vs5923" > procmail: Notified comsat: > "lanwin@0:/home/lanwin/Maildir/new/1262032593.29952_2.vs5923" > From KeineAntwortAdresse(a)web.de Mon Dec 28 21:36:33 2009 > Subject: discoTEL > =?ISO-8859-1?Q?Tarif=3A_F=FCr_7=2C5_Cent=2FMin=2E_telefonier > Folder: /home/lanwin/Maildir/new/1262032593.29952_2.vs5923 > 41096 > procmail: Unlocking "/home/lanwin/Maildir/.lockmail" > > Dovecot Deliver Log--> > > 2009-12-28 21:36:35 deliver(lanwin): Info: sieve: > msgid=<E1NPMKF-00014k-00(a)mxnl04.web.de>: marked message to be discarded > if not explicitly delivered (discard action) > > Dose not look better to me. > > Steve > > Am 28.12.2009 18:06, schrieb Tobias Lang: >> >> Am 28.12.2009 um 15:09 schrieb Steve Wagner: >> >>> [snip] >>> >>> :0 w >>> | /opt/dovecot/libexec/dovecot/deliver >> >> Looks uncritical to me. Although there is no default rule at the end of >> .procmailrc, Dovecot deliver and Sieve should reroute everything not >> catched by a rule to INBOX. >> >> Did Procmails "VERBOSE=on" reveal something? >> >> Tobi >>

1 0

[Dovecot] managesieve error
by Lampa 26 Dec '09

26 Dec '09

Hello, when using sieve-php and using LOGIN auth, getting: 2009-11-21T15:13:48+0100 managesieve-login: Panic: file client.c: line 449 (client_set_auth_waiting): assertion failed: (client->to_auth_waiting == NULL) 2009-11-21T15:13:48+0100 dovecot: Error: child 8474 (login) killed with signal 6 (core dumps disabled) (latest ip=127.0.0.1) I'm using dovecot 1.2.6 from package debian testing (1:1.2.6-1) -- Lampa

2 1

[Dovecot] basic understanding of imap in dovecot
by dovecot＠paz.bz 24 Dec '09

24 Dec '09

I have always used a pop3 daemon, and switching to dovecot has been my introduction to imap. Imap is foreign to me. I am wondering if I am a little off-track here, and would like some clarification. My MTA (exim) delivers email to: /mail/user dovecot, sucks that mail from /mail/user TO /home/user/mail/<filenamesoffolders> dovecot IMAP further uses /home/user/mail/.imap/folders/{.index / .index.cache / .index.log} the mail folder which exim uses doesn't seem to get emptied by dovecot when it sucks the email into /home/user/mail/<filenamesoffolders> when using IMAP. If POP3 is used via dovecot, then it appears that the interaction is directly to the original exim folder and that it does indeed empty (or at least it has the "FOLDER INTERNAL DATA" entry). I suppose my question is, is there a way to have dovecot empty/parse the original exim mailbox so that the customer email isn't sitting in two spots, taking up double the space. This would be in the IMAP environment only, as POP3 seems to be fine. Any online references available to help a newbee understand IMAP? Thanks!

3 2

[Dovecot] 2.0.beta1/07e688afe81b imap crash
by Pascal Volk 24 Dec '09

24 Dec '09

Hi Timo, I've replaced a mdbox, as long Thunderbird was connected. The result is attached. Regards, Pascal -- The trapper recommends today: face1e55.0935803(a)localdomain.org #0 0x00007f0caa42ea18 in mail_namespace_get_vname (ns=0x0, dest=0x145d460, name=0x14bf1f9 "INBOX") at mail-namespace.c:418 No locals. #1 0x00007f0caa48eec0 in index_storage_mailbox_alloc (ibox=0x14b7890, name=0x14bf1f9 "INBOX", input=0x0, flags=265, index_prefix=0x7f0caa4e67b2 "dovecot.index") at index-storage.c:461 box = 0x14b7890 path = 0x14b7890 "x{K\001" dir_gid = 0 origin = 0x14b7828 "" dir_origin = 0x2d8 <Address 0x2d8 out of bounds> vname = 0x145d460 __PRETTY_FUNCTION__ = "index_storage_mailbox_alloc" #2 0x00007f0caa4cdd89 in mdbox_mailbox_alloc (storage=0x1462a20, list=0x0, name=0x14bf1f9 "INBOX", input=0x0, flags=265) at mdbox-storage.c:126 mbox = 0x14b7890 pool = 0x14b7828 #3 0x00007f0caa4cc84d in rebuild_restore_msg (ctx=0x14c4cf0, msg=0x151a098) at mdbox-storage-rebuild.c:545 storage = 0x1462a20 file = 0x0 hdr = 0x7fffc4a037c0 dbox_rec = {map_uid = 0, save_date = 0} mailbox = 0x14bf1f9 "INBOX" box = 0x0 mbox = 0x100000009 error = MAIL_ERROR_NONE deleted = false created = false size = 834 ret = 1 seq = 0 __PRETTY_FUNCTION__ = "rebuild_restore_msg" #4 0x00007f0caa4ccb73 in rebuild_handle_zero_refs (ctx=0x14c4cf0) at mdbox-storage-rebuild.c:632 msgs = 0x14ed000 i = 0 count = 1 #5 0x00007f0caa4ccdbe in rebuild_finish (ctx=0x14c4cf0) at mdbox-storage-rebuild.c:685 No locals. #6 0x00007f0caa4cd13e in mdbox_storage_rebuild_scan (ctx=0x14c4cf0) at mdbox-storage-rebuild.c:762 hdr = 0x14a3910 dir = 0x1475f70 d = 0x0 path = 0x145d298 dir_len = 24 uid_validity = 1261521073 ret = 0 __PRETTY_FUNCTION__ = "mdbox_storage_rebuild_scan" #7 0x00007f0caa4cd226 in mdbox_storage_rebuild (storage=0x1462a20) at mdbox-storage-rebuild.c:788 ctx = 0x14c4cf0 st = {st_dev = 2305, st_ino = 4562950, st_nlink = 2, st_mode = 16832, st_uid = 1000, st_gid = 1000, __pad0 = 0, st_rdev = 0, st_size = 4096, st_blksize = 4096, st_blocks = 8, st_atim = { tv_sec = 1261522332, tv_nsec = 0}, st_mtim = {tv_sec = 1261522325, tv_nsec = 0}, st_ctim = {tv_sec = 1261522325, tv_nsec = 0}, __unused = {0, 0, 0}} ret = 32524 #8 0x00007f0caa4cdc42 in mdbox_storage_destroy (_storage=0x1462a20) at mdbox-storage.c:93 storage = 0x1462a20 #9 0x00007f0caa43416f in mail_storage_unref (_storage=0x14a4ec0) at mail-storage.c:327 storage = 0x1462a20 __PRETTY_FUNCTION__ = "mail_storage_unref" #10 0x00007f0caa42db3a in mail_namespace_free (ns=0x14a4e70) at mail-namespace.c:50 No locals. #11 0x00007f0caa42e7df in mail_namespaces_deinit (_namespaces=0x14c0100) at mail-namespace.c:349 ns = 0x14a4e70 namespaces = 0x0 #12 0x00007f0caa436c9c in mail_user_deinit_base (user=0x14c0090) at mail-user.c:28 No locals. #13 0x00007f0ca91a22e8 in quota_user_deinit (user=0x14c0090) at quota-storage.c:463 quser = 0x14c0e10 #14 0x00007f0caa437257 in mail_user_unref (_user=0x14c8ef8) at mail-user.c:128 user = 0x14c0090 __PRETTY_FUNCTION__ = "mail_user_unref" #15 0x00000000004121e1 in client_destroy (client=0x14c8ea0, reason=0x0) at imap-client.c:197 cmd = 0x7fffc4a03ac8 __PRETTY_FUNCTION__ = "client_destroy" #16 0x0000000000413991 in client_input (client=0x14c8ea0) at imap-client.c:802 cmd = 0xc4a03b0c output = 0x0 bytes = 170 __PRETTY_FUNCTION__ = "client_input" #17 0x00007f0caa1ca9d6 in io_loop_handler_run (ioloop=0x1465f60) at ioloop-epoll.c:208 ctx = 0x1469fc0 events = 0x146a800 event = 0x146a800 list = 0x1466e80 io = 0x1467980 tv = {tv_sec = 4, tv_usec = 997221} events_count = 4 t_id = 2 msecs = 4998 ret = 1 i = 0 j = 0 call = true #18 0x00007f0caa1c9681 in io_loop_run (ioloop=0x1465f60) at ioloop.c:350 No locals. #19 0x00007f0caa1b3aef in master_service_run (service=0x1464ee0, callback=0x41f55f <client_connected>) at master-service.c:473 No locals. #20 0x000000000041f76a in main (argc=1, argv=0x146d010) at main.c:307 set_roots = {0x4234a0, 0x0} service_flags = MASTER_SERVICE_FLAG_KEEP_CONFIG_OPEN storage_service_flags = MAIL_STORAGE_SERVICE_FLAG_DISALLOW_ROOT postlogin_socket_path = 0x0

1 0

[Dovecot] Permissions errors while reading messages via IMAP
by Geoff Sweet 24 Dec '09

24 Dec '09

Greetings all, I have been trying to setup a new system using Postfix and Dovecot to manage email for a bunch of virtual domains. So far everything is great, and I am now at the point where I am trying to build a webmail interface for the system. I'm using RoundCube for now. The tutorial I have been working from is here: http://workaround.org/articles/ispmail-etch/ Which seems to be a decent enough read. At this point I can login without issue but I can't see any mail messages. When I login, dovecot throws errors like this: Dec 23 12:08:49 mail1 dovecot: auth(default): client out: OK 1 user=geoff.sweet(a)test.com Dec 23 12:08:49 mail1 dovecot: auth(default): master in: REQUEST 1 4312 1 Dec 23 12:08:49 mail1 dovecot: auth(default): master out: USER 1 geoff.sweet(a)test.com uid=5000 gid=5000 home=/home/vmail/test.com/geoff.sweet Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): Effective uid=5000, gid=5000, home=/home/vmail/test.com/geoff.sweet Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): maildir: data=/home/vmail/test.com/geoff.sweet/Maildir Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): maildir++: root=/home/vmail/test.com/geoff.sweet/Maildir, index=, control=, inbox=/home/vmail/test.com/geoff.sweet/Maildir Dec 23 12:08:49 mail1 dovecot: imap-login: Login: user=<geoff.sweet(a)test.com>, method=PLAIN, rip=192.168.20.11, lip=192.168.20.12 Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): Disconnected: Logged out bytes=39/431 Dec 23 12:08:49 mail1 dovecot: auth(default): new auth connection: pid=4315 Dec 23 12:08:49 mail1 dovecot: auth-worker(default): sql(geoff.sweet(a)test.com,192.168.20.11): query: SELECT email as user, password FROM view_mailboxes WHERE email='geoff.sweet(a)test.com'; Dec 23 12:08:49 mail1 dovecot: auth(default): client in: AUTH 1 PLAIN service=imap lip=192.168.20.12 rip=192.168.20.11 lport=143 rport=43878 resp=AGdlb2ZmLnN3ZWV0QHdob290aXMuY29tAGJvYjEyMzQ1 Dec 23 12:08:49 mail1 dovecot: auth(default): client out: OK 1 user=geoff.sweet(a)test.com Dec 23 12:08:49 mail1 dovecot: auth(default): master in: REQUEST 2 4311 1 Dec 23 12:08:49 mail1 dovecot: auth(default): master out: USER 2 geoff.sweet(a)test.com uid=5000 gid=5000 home=/home/vmail/test.com/geoff.sweet Dec 23 12:08:49 mail1 dovecot: imap-login: Login: user=<geoff.sweet(a)test.com>, method=PLAIN, rip=192.168.20.11, lip=192.168.20.12 Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): Effective uid=5000, gid=5000, home=/home/vmail/test.com/geoff.sweet Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): maildir: data=/home/vmail/test.com/geoff.sweet/Maildir Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): maildir++: root=/home/vmail/test.com/geoff.sweet/Maildir, index=, control=, inbox=/home/vmail/test.com/geoff.sweet/Maildir Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): Namespace : Using permissions from /home/vmail/test.com/geoff.sweet/Maildir: mode=0700 gid=-1 Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): open(/home/vmail/test.com/geoff.sweet/Maildir/dovecot.index.log) failed: Permission denied (euid=5000(vmail) egid=5000(vmail) missing +r perm: /home/vmail/test.com/geoff.sweet/Maildir/dovecot.index.log) Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): open(/home/vmail/test.com/geoff.sweet/Maildir/dovecot-uidlist) failed: Permission denied Dec 23 12:08:49 mail1 last message repeated 2 times There is some permission issue that allows dovecot to deliver email to the /home/vmail location (I dislike this location and want to change it) via the dovecot LDA process, but then not be able to read it when accessed via IMAP. I'm very confused lol. Dovecot version 1.2.9 dovecot -n: # 1.2.9: /etc/dovecot.conf # OS: Linux 2.6.18-164.6.1.el5 i686 CentOS release 5.4 (Final) ext3 login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting: Dovecot ready. mail_location: maildir:/home/vmail/%d/%n/Maildir mail_debug: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 lda: log_path: /home/vmail/dovecot-deliver.log auth_socket_path: /var/run/dovecot/auth-master postmaster_address: postmaster(a)test.com mail_plugins: global_script_path: /home/vmail/globalsieverc auth default: mechanisms: plain login debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: static args: uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail

2 4

[Dovecot] virtual plugin: Broken mailbox list
by e-frog 23 Dec '09

23 Dec '09

Hello Timo, I'm testing the latest hg version from the 1.2 series and get the following in dovecot's error log as soon as I try to access the virtual mailbox Dec 11 18:23:07 ubuntu-test dovecot: IMAP(xxxxx): virtual index /etc/dovecot/virtual/unseen: Broken mailbox list $ cat dovecot-virtual * unseen $ dovecot -n # 1.2.8: /etc/dovecot/dovecot.conf # OS: Linux 2.6.31-16-generic-pae i686 Ubuntu 9.10 protocols: imap imaps managesieve disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login verbose_proctitle: yes mail_location: maildir:~/.maildir mail_debug: yes mail_drop_priv_before_exec: yes mail_executable(default): /usr/lib/dovecot/rawlog /usr/lib/dovecot/wrapper.sh mail_executable(imap): /usr/lib/dovecot/rawlog /usr/lib/dovecot/wrapper.sh mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): expire fts fts_squat virtual quota imap_quota mail_log acl mail_plugins(imap): expire fts fts_squat virtual quota imap_quota mail_log acl mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve mail_log_max_lines_per_sec: 0 namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: private separator: / prefix: virtual/ location: virtual:/etc/dovecot/virtual:INDEX=~/.maildir/control:CONTROL=~/.maildir/control list: children lda: postmaster_address: postmaster@ubuntu hostname: ubuntu mail_plugins: sieve virtual expire quota acl mail_plugin_dir: /usr/lib/dovecot/modules/lda deliver_log_format: msgid=%m: from=%f: %$ log_path: /var/log/deliver.log info_log_path: /var/log/deliver.log sendmail_path: /usr/lib/sendmail rejection_subject: Rejected: %s rejection_reason: Your message to <%t> was automatically rejected:%n%r auth_socket_path: /var/run/dovecot/auth-master auth default: passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 438 plugin: quota: dict:user::proxy::dictionary expire: Trash 1 "INBOX/log check" 1 expire_dict: proxy::dictionary mail_log_events: delete undelete expunge copy mailbox_delete mailbox_rename flag_change mail_log_fields: uid box msgid size flags sieve: ~/.dovecot.sieve sieve_dir: ~/sieve deliver_log_format: msgid=%m: from=%f: %$ fts: squat fts_squat: partial=4 full=10 dict: dictionary: mysql:/etc/dovecot/dovecot-dict-sql.conf

2 2

[Dovecot] imap-login crashes after upgrade to Dovecot 1.2.8 Linux 64-bit
by Chris Wakelin 23 Dec '09

23 Dec '09

Hi all, We moved our Dovecot installation first of all to have all folders and inboxes on NetApps via NFS (with indexes local) then from a physical Solaris 8 4-way UltraSparc server running Dovecot 1.2.5 (32-bit) to a virtualised Ubuntu 8.04 64-bit server with a single virtual processor (in VMWare ESX 3.5) running Dovecot 1.2.8 (64-bit). Since the change, many of our users have experienced random disconnections when proxied in imap-login (either using the internal SSL proxy, or to an external IMAP server) and the error logs contain things like: > Dec 18 00:27:58 imap-login: Info: Disconnected: Connection queue full (auth failed, 1 attempts): user=<user0>, method=PLAIN, rip=<ip0>, lip=134.225.32.156, TLS > Dec 18 00:27:58 imap-login: Panic: file ioloop.c: line 39 (io_add): assertion failed: (fd >= 0) > Dec 18 00:27:58 IMAP 9486 <user1> <ip1> : Info: Connection closed bytes=224/1753 > Dec 18 00:27:58 IMAP 10116 <user2> <ip2> : Info: Connection closed bytes=82/707 ... > Dec 18 00:27:58 IMAP 10296 <user3> <ip3> : Info: Disconnected in IDLE bytes=44/435 > Dec 18 00:27:58 IMAP 10298 <user3> <ip3> : Info: Disconnected in IDLE bytes=263/1662 > Dec 18 00:27:58 dovecot: Error: child 5124 (login) killed with signal 6 (core dumped) (latest ip=<ip0>) > Dec 18 00:27:58 imap-login: Info: Aborted login (no auth attempts): rip=<ip0>, lip=134.225.32.156, TLS: Disconnected and a backtrace gives: > (gdb) bt > #0 0x00007ff1030ad095 in raise () from /lib/libc.so.6 > #1 0x00007ff1030aeaf0 in abort () from /lib/libc.so.6 > #2 0x00000000004112d5 in default_fatal_finish (type=<value optimized out>, status=0) at failures.c:160 > #3 0x0000000000411333 in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=<value optimized out>, args=<value optimized out>) at failures.c:443 > #4 0x0000000000410996 in i_panic (format=0x6 <Address 0x6 out of bounds>) at failures.c:207 > #5 0x000000000041420e in io_add (fd=-1, condition=IO_READ, callback=0x404db0 <client_input>, context=0x6af000) at ioloop.c:39 > #6 0x00000000004059db in client_auth_failed (client=0x6af000, nodelay=true) at client-authenticate.c:103 > #7 0x0000000000405e07 in client_handle_args (client=0x6af000, args=<value optimized out>, success=true, nodelay_r=0x7fff571009af) > at client-authenticate.c:198 > #8 0x0000000000406214 in sasl_callback (_client=0x6af000, reply=SASL_SERVER_REPLY_SUCCESS, data=0x0, args=0x6361d0) at client-authenticate.c:277 > #9 0x000000000040eb13 in auth_client_input_ok (conn=0x75b6c8, args=<value optimized out>) at auth-server-request.c:196 > #10 0x000000000040dbf3 in auth_client_input (conn=0x75b6c8) at auth-server-connection.c:136 > #11 0x0000000000414aa8 in io_loop_handler_run (ioloop=<value optimized out>) at ioloop-epoll.c:208 > #12 0x0000000000413b9d in io_loop_run (ioloop=0x6552b0) at ioloop.c:335 > #13 0x0000000000408e81 in main (argc=2, argv=0x7fff57100c58, envp=0x7fff57100c70) at main.c:494 Up until this afternoon we had "login_process_per_connection = yes", and login_max_connections at the default (256). This evening I tried with "login_process_per_connection = no" with no problems, except more CPU load and needing to increase login_max_processes_count (and strictly speaking the max fds set with ulimit -n would need to be increased, though I didn't do that as it would have involved killing and restarting the master process - come back Solaris plimit!) Just after midnight, I switched back to "login_process_per_connection = no" and set "login_max_connections = 32" and managed to get core dumps enabled, hence the above! Apart from this problem, the virtual machine has been doing extremely well, so it's not CPU or I/O load related. I'm not sure whether the problem is caused by the switch from Dovecot 1.2.5 to 1.2.8, Solaris to Linux, physical to virtual, or 32-bit to 64-bit! Perhaps we changed too much at once, but it did mean we kept the service going while power was turned off in our main machine room last weekend ... Best Wishes, Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

2 6