- dovecot - dovecot.org

[Dovecot] SSL certificate?
by Bjørn T Johansen 31 Jan '08

31 Jan '08

When I install an SSL certificate, I can't find a config option to set configure the Server Certificate Chain file... Is this not possible or can I do it another way? (When I connect, I am being told the Signature status is uncheckable...) Regards, BTJ -- ----------------------------------------------------------------------------------------------- Bjørn T Johansen btj(a)havleik.no ----------------------------------------------------------------------------------------------- Someone wrote: "I understand that if you play a Windows CD backwards you hear strange Satanic messages" To which someone replied: "It's even worse than that; play it forwards and it installs Windows" -----------------------------------------------------------------------------------------------

4 5

[Dovecot] More efficient Deleting of a whole folder (or Purging Trash)
by Daniel Watts 31 Jan '08

31 Jan '08

Hi, I've straced a few dovecot processes after hitting purge on a large Trash folder (35,000 messages). It looks like it is going through each message, one by one, and removing (unlinking) each one. Is there not a more efficient way to do this? If Dovecot knows the whole folder is being deleted (ie a Trash purge), could it do something clever with the filesystem to just remove the whole folder? Incidently, the command that initially deleted those 35k messages to Trash took about 1 hour to complete on my server and effectively locked my account out for all that time. There were also an awlful lot of these output from my strace: nanosleep({0, 131475000}, NULL) = 0 lstat("/home/virtual/xxx.com/home/admin/Maildir/.Folders.Porter/dovecot-uidlist.lock", {st_mode=S_IFREG|0600, st_size=0, ...}) = 0 Not sure if there's much one can do about speeding up deleting a lot of messages though. My webmail client has a 'delete all messages' button for each folder. If there was an efficient IMAP command for deleting a whole folder that would be useful in those circumstances. Interested to know if there is anything that can be improved. Thanks, Daniel Dovecot 1.0.9 XFS Filesystem Maildir Directories

7 12

[Dovecot] Convert MBOX
by Erin D. Hughes 31 Jan '08

31 Jan '08

To all, I am using dovecot --version 1.0.10 and trying to convert MBOXes to MailDir's with the end goal of creating one folder filled with users old MBOXes that when they log in for the first time will be converted to Mail Dir format. I tried this and it did not work and gave me this output; <snip> default_mail_env = maildir:%h/mail/ #convert_mail = mbox:%h/mail:INBOX=/usr/local/src/tmpmail/%u convert_mail = mbox:%h/mail/:INBOX=/usr/local/src/tmpmail/%u Jan 30 17:17:04 pop01.unix dovecot: [ID 107833 mail.info] pop3-login: Login: user=<x4500>, method=PLAIN, rip=192.168.30.192, lip=172.20.12.8 Jan 30 17:17:04 pop01.unix dovecot: [ID 107833 mail.info] POP3(x4500): Loading modules from directory: /usr/local/lib/dovecot/pop3 Jan 30 17:17:04 pop01.unix dovecot: [ID 107833 mail.info] POP3(x4500): Module loaded: /usr/local/lib/dovecot/pop3/lib20_convert_plugin.so Jan 30 17:17:04 pop01.unix dovecot: [ID 107833 mail.info] POP3(x4500): Effective uid=3000, gid=3000 Jan 30 17:17:04 pop01.unix dovecot: [ID 107833 mail.info] POP3(x4500): mbox: data=/export/x4500/mail/jp/n/e/jorgen/x4500/mail/:INBOX=/usr/local/src/tmpmail/x4500 Jan 30 17:17:04 pop01.unix dovecot: [ID 107833 mail.info] POP3(x4500): mbox: root=/export/x4500/mail/jp/n/e/jorgen/x4500/mail, index=/export/x4500/mail/jp/n/e/jorgen/x4500/mail, inbox=/usr/local/src/tmpmail/x4500 Jan 30 17:17:06 pop01.unix dovecot: [ID 107833 mail.info] POP3(x4500): mbox: data=/export/x4500/mail/jp/n/e/jorgen/x4500/mail/:INBOX=/usr/local/src/tmpmail/x4500 Jan 30 17:17:06 pop01.unix dovecot: [ID 107833 mail.info] POP3(x4500): mbox: root=/export/x4500/mail/jp/n/e/jorgen/x4500/mail, index=/export/x4500/mail/jp/n/e/jorgen/x4500/mail, inbox=/usr/local/src/tmpmail/x4500 Jan 30 17:17:06 pop01.unix dovecot: [ID 107833 mail.info] POP3(x4500): maildir: data=/export/x4500/mail/jp/n/e/jorgen/x4500/mail/ Jan 30 17:17:06 pop01.unix dovecot: [ID 107833 mail.info] POP3(x4500): maildir: root=/export/x4500/mail/jp/n/e/jorgen/x4500/mail, index=/export/x4500/mail/jp/n/e/jorgen/x4500/mail, control=, inbox= Jan 30 17:17:07 pop01.unix dovecot: [ID 107833 mail.error] POP3(x4500): Mailbox conversion: Couldn't copy mailbox dovecot.index.log: BUG: Unknown internal error Jan 30 17:17:07 pop01.unix dovecot: [ID 107833 mail.error] POP3(x4500): Mailbox conversion: Couldn't copy mailbox dovecot.index: BUG: Unknown internal error Jan 30 17:17:08 pop01.unix dovecot: [ID 107833 mail.error] POP3(x4500): Mailbox conversion: Couldn't copy mailbox dovecot.index.cache: BUG: Unknown internal error Jan 30 17:17:11 pop01.unix dovecot: [ID 107833 mail.info] POP3(x4500): maildir: data=/export/x4500/mail/jp/n/e/jorgen/x4500/mail/ Jan 30 17:17:11 pop01.unix dovecot: [ID 107833 mail.info] POP3(x4500): maildir: root=/export/x4500/mail/jp/n/e/jorgen/x4500/mail, index=/export/x4500/mail/jp/n/e/jorgen/x4500/mail, control=, inbox= </snip> This actually created the x4500-convert directory but did not populate it Then I tried this trying to get the mail dir created and populated. <snip> #convert_mail = mbox:%h/mail:INBOX=/usr/local/src/tmpmail/%u convert_mail = mbox:/usr/local/src/tmpmail/%u:INBOX=/var/mail/%u Jan 30 17:22:45 pop01.unix dovecot: [ID 673593 mail.info] Dovecot v1.0.10 starting up Jan 30 17:22:59 pop01.unix dovecot: [ID 107833 mail.info] pop3-login: Login: user=<x4500>, method=PLAIN, rip=192.168.30.192, lip=172.20.12.8 Jan 30 17:22:59 pop01.unix dovecot: [ID 107833 mail.info] POP3(x4500): Loading modules from directory: /usr/local/lib/dovecot/pop3 Jan 30 17:22:59 pop01.unix dovecot: [ID 107833 mail.info] POP3(x4500): Module loaded: /usr/local/lib/dovecot/pop3/lib20_convert_plugin.so Jan 30 17:22:59 pop01.unix dovecot: [ID 107833 mail.info] POP3(x4500): Effective uid=3000, gid=3000 Jan 30 17:22:59 pop01.unix dovecot: [ID 107833 mail.info] POP3(x4500): mbox: data=/usr/local/src/tmpmail/x4500:INBOX=/var/mail/x4500 Jan 30 17:22:59 pop01.unix dovecot: [ID 107833 mail.info] POP3(x4500): mbox: root=/usr/local/src/tmpmail/x4500, index=/usr/local/src/tmpmail/x4500, inbox=/var/mail/x4500 Jan 30 17:22:59 pop01.unix dovecot: [ID 107833 mail.info] POP3(x4500): mbox: data=/usr/local/src/tmpmail/x4500:INBOX=/var/mail/x4500 Jan 30 17:22:59 pop01.unix dovecot: [ID 107833 mail.info] POP3(x4500): mbox: root=/usr/local/src/tmpmail/x4500, index=/usr/local/src/tmpmail/x4500, inbox=/var/mail/x4500 Jan 30 17:22:59 pop01.unix dovecot: [ID 107833 mail.info] POP3(x4500): maildir: data=/export/x4500/mail/jp/n/e/jorgen/x4500/mail/ Jan 30 17:22:59 pop01.unix dovecot: [ID 107833 mail.info] POP3(x4500): maildir: root=/export/x4500/mail/jp/n/e/jorgen/x4500/mail, index=/export/x4500/mail/jp/n/e/jorgen/x4500/mail, control=, inbox= Jan 30 17:22:59 pop01.unix dovecot: [ID 107833 mail.error] POP3(x4500): mkdir_parents(/usr/local/src/tmpmail/x4500/.imap/INBOX) failed: Not a directory Jan 30 17:22:59 pop01.unix dovecot: [ID 107833 mail.error] POP3(x4500): open() failed with subscription file /usr/local/src/tmpmail/x4500/.subscriptions: Not a directory Jan 30 17:22:59 pop01.unix dovecot: [ID 107833 mail.error] POP3(x4500): Sending log messages too fast, throttling.. Jan 30 17:22:59 pop01.unix dovecot: [ID 961074 mail.error] child 23071 (pop3) returned error 89 </snip> I am a little confused because when I read the syntax http://wiki.dovecot.org/Plugins/Convert?highlight=%28convert%29 It looks like it should say "convert_mail= mbox:/users/home/dir/mail/:INBOX=/location/of/old/MBOX/file" I have tried a number of different combinations but am still failing to get the mail/{cur,new,tmp} created in the correct user directory with actual mail in them. Can some one please help w/this? Additionally is there a way to run mail_convert on the command line to try to sort out the arguments? I noticed the converts are .so and .a in /usr/local/lib/dovecot/ so I doubt it but it can not hurt to ask.

5 5

Re: [Dovecot] Multiple copies of a message
by Anne Wilson 31 Jan '08

31 Jan '08

On Wednesday 30 January 2008 18:14:19 you wrote: > On Wed, 30 Jan 2008, Anne Wilson wrote: > > On Tuesday 29 Jan 2008, you wrote: > >> On Tue, 29 Jan 2008, Anne Wilson wrote: > >>> I have a problem and I don't know which part of the mail chain could be > >>> causing it, although dovecot does seem to be the most logical source. > >>> > >>> I get multiple copies of messages to my Inbox. I have just deleted 24 > >>> copies of a newsletter from Computer Shopper. The worst example I have > >>> seen of this had more than 90 copies. This doesn't happen to any > >>> subfolder of Inbox, just Inbox itself. > >>> > >>> The problem started about 10-14 days ago, on the old mail server > >>> (running Mandriva 2007.1). The new server runs CentOS and exhibits the > >>> same problem. > >>> > >>> I'd be interested in any comments, as my efforts to track it down have > >>> got nowhere. > >> > >> Are you using Dovecot's 'deliver' as your LDA (local delivery agent)? > >> Otherwise I'd suspect the problem lies in whatever you're using for your > >> local deliveries, creating some kind of mail loop. Check your > >> .forward/.qmail/.procmail/whatever files. I haven't heard of/seen > >> dovecot duplicating messages unless there are actually multiple copies > >> in your mailbox. > > > > Everything looks fine, and remember that this started on a server that > > had been running correctly for a long time. > > Yes, but these aren't hard-coded things. It's usually a configuration > change of some sort that results in inadvertent loops. > Fair comment. I did look when you suggested it, but I'll go through everything again in the morning. > >> If your LDA isn't already doing so, add a 'Delivered-To' or > >> 'X-Mail-Loop' header at each stage, so you can more easily tell if this > >> is what's happening. > > > > How/where do I do that? > > With procmail, you could add something like: > > # fw means filter and wait > > :0fw > : > | formail -fbA "Delivered-To: (information here)" > > (e.g. in my case '(information here)' would be 'dovecot(a)benizi.com') > OK, thanks. I'll try that tomorrow, too. > >> And then (I assume you've done this, but it should be said) > >> look at the headers of the duplicated messages to see if they're 1) > >> actually distinct messages [external problem] 2) being delivered > >> multiple times > > > > They appear to be single messages, delivered multiple times. See my > > reply to Asheesh Laroia. > > Forthcoming? I don't see a reply on-list. > Apologies. It seems that I forgot to switch on list management in kmail. I've re-sent the message, this time to the list. It should arrive along with this. BTW, one of the pairs of messages I compared in that message now has 30 copies in my inbox - two this morning, when I wrote the message. Anne

2 2

[Dovecot] Virtual Alias Forwarding
by Eric Biondi 30 Jan '08

30 Jan '08

I'm having a problem with Dovecot and forwarding of aliases. Any help would be greatly appreciated. I'm using Postfix, Mysql, dovecot, amavis. mysql> SELECT * FROM alias; | address | goto | domain | created | modified | active | It seems from the logs that incoming mail is being delivered to the mailbox via dovecot. Mail gets to the correct mailbox (address field), however, if I change the destination mailbox (goto) in the alias table in mysql, the mail still goes to the main mailbox (address). mysql_virtual_alias_maps.cf looks to be configured correctly but I'm suspecting that dovecot is circumventing that file. I'll post maillog entry, dovecot-deliver.log entry, dovecot-mysql.conf, mysql_virtual_alias_maps.cf, and dovecot.conf below in case that helps. Thanks in advance for anything that helps me resolve this. Maillog: Jan 29 17:23:04 mail postfix/pipe[29368]: D16F657804A: to=<mtb(a)domain.net>, relay=dovecot, delay=0.03, delays=0.01/0.01/0/0.01, dsn=2.0.0, status=sent (delivered via dovecot service) dovecot-deliver.log: deliver(mtb(a)domain.net): Jan 29 17:23:04 Info: msgid=<009501c862c5$84086080$4b06a8c0@comperic>: saved mail to INBOX dovecot-mysql.conf: driver = mysql connect = host=127.0.0.1 dbname=mail user=sqluser password=sqlpasswd default_pass_scheme = MD5 # Get the mailbox user_query = SELECT '/home/vmail/%d/%n' as home, 'maildir:/home/vmail/%d/%n' as mail, 5000 AS uid, 5000 AS gid, concat('dirsize:storage=', quota) AS quota FROM mailbox WHERE username = '%u' AND active = '1' # Get the password password_query = SELECT username as user, password, '/home/vmail/%d/%n' as userdb_home, 'maildir:/home/vmail/%d/%n' as userdb_mail, 5000 as userdb_uid, 5000 as userdb_gid FROM mailbox WHERE username = '%u' AND active = '1' # If using client certificates for authentication, comment the above and uncomment the following #password_query = SELECT null AS password, '%u' AS user mysql_virtual_alias_maps.cf: user = sqluser password = sqlpasswd hosts = 127.0.0.1 dbname = mail #table = alias #select_field = goto #where_field = address #additional_conditions = and active = '1' query = SELECT goto FROM alias WHERE address='%s' AND active = '1' # dovecot -n # 1.0.7: /etc/dovecot.conf protocols: imaps pop3s ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_cert_file: /etc/pki/tls/certs/mail.domain.com.crt ssl_key_file: /etc/pki/tls/private/mail.domain.com.pem disable_plaintext_auth: yes 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 first_valid_uid: 5000 last_valid_uid: 5000 first_valid_gid: 5000 last_valid_gid: 5000 mail_location: maildir:/home/vmail/%d/%n 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/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 namespace: type: private separator: / inbox: yes auth default: mechanisms: plain login passdb: driver: pam passdb: driver: sql args: /etc/dovecot-mysql.conf userdb: driver: passwd userdb: driver: static args: uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes userdb: driver: sql args: /etc/dovecot-mysql.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: 384 user: vmail

2 3

[Dovecot] Strange signal 11 crashes
by Ralf Hildebrandt 30 Jan '08

30 Jan '08

These crashes only happen at night/during the evening, way after maximum load: Jan 27 21:19:57 postamt kernel: [1490698.849461] imap[15089]: segfault at 00000008 eip 080b779b esp bfbe20a0 error 4 Jan 27 21:20:50 postamt kernel: [1490752.022142] imap[15251]: segfault at 00000008 eip 080b779b esp bfd241e0 error 4 Jan 27 21:21:53 postamt kernel: [1490814.348208] imap[15482]: segfault at 00000008 eip 080b779b esp bfeca390 error 4 Jan 27 21:22:26 postamt kernel: [1490846.872861] imap[15710]: segfault at 00000008 eip 080b779b esp bfe262e0 error 4 Jan 27 21:22:58 postamt kernel: [1490879.492134] imap[15908]: segfault at 00000008 eip 080b779b esp bfc2e0f0 error 4 Jan 27 21:23:50 postamt kernel: [1490931.552328] imap[16074]: segfault at 00000008 eip 080b779b esp bfcef1b0 error 4 Jan 27 21:24:52 postamt kernel: [1490993.362124] imap[16523]: segfault at 00000008 eip 080b779b esp bfba8060 error 4 Jan 27 21:25:50 postamt kernel: [1491051.284134] imap[16701]: segfault at 00000008 eip 080b779b esp bf9f06b0 error 4 Jan 27 21:26:52 postamt kernel: [1491112.840002] imap[17045]: segfault at 00000008 eip 080b779b esp bfbe00a0 error 4 Jan 27 21:27:50 postamt kernel: [1491171.010657] imap[17195]: segfault at 00000008 eip 080b779b esp bf8c4580 error 4 Jan 27 21:28:23 postamt kernel: [1491203.375618] imap[17410]: segfault at 00000008 eip 080b779b esp bfbdf0a0 error 4 Jan 27 21:28:56 postamt kernel: [1491236.090416] imap[17634]: segfault at 00000008 eip 080b779b esp bfc188d0 error 4 Jan 27 21:29:52 postamt kernel: [1491292.432973] imap[17871]: segfault at 00000008 eip 080b779b esp bfc6f130 error 4 Jan 27 21:30:52 postamt kernel: [1491352.302931] imap[18136]: segfault at 00000008 eip 080b779b esp bfc83940 error 4 Jan 27 21:31:52 postamt kernel: [1491412.150117] imap[18392]: segfault at 00000008 eip 080b779b esp bfa50f10 error 4 Jan 27 21:32:52 postamt kernel: [1491472.070053] imap[18562]: segfault at 00000008 eip 080b779b esp bfe112d0 error 4 Jan 27 21:33:52 postamt kernel: [1491531.926641] imap[18821]: segfault at 00000008 eip 080b779b esp bfd189d0 error 4 Jan 27 21:34:52 postamt kernel: [1491591.760232] imap[19068]: segfault at 00000008 eip 080b779b esp bfb78030 error 4 Jan 27 21:35:52 postamt kernel: [1491651.654617] imap[19257]: segfault at 00000008 eip 080b779b esp bfebd380 error 4 Jan 27 21:36:52 postamt kernel: [1491711.489063] imap[19453]: segfault at 00000008 eip 080b779b esp bfb1bfe0 error 4 Jan 27 21:37:52 postamt kernel: [1491771.348741] imap[19679]: segfault at 00000008 eip 080b779b esp bfd91a50 error 4 Jan 27 21:38:52 postamt kernel: [1491831.200945] imap[19927]: segfault at 00000008 eip 080b779b esp bfffd4c0 error 4 Jan 27 21:39:50 postamt kernel: [1491889.366175] imap[20108]: segfault at 00000008 eip 080b779b esp bfffc4c0 error 4 Jan 27 21:40:52 postamt kernel: [1491950.954458] imap[20385]: segfault at 00000008 eip 080b779b esp bfc1b8e0 error 4 Jan 27 21:41:52 postamt kernel: [1492010.867336] imap[20590]: segfault at 00000008 eip 080b779b esp bfbc4880 error 4 Jan 27 21:42:52 postamt kernel: [1492070.656109] imap[20821]: segfault at 00000008 eip 080b779b esp bfb0efd0 error 4 Jan 27 21:43:52 postamt kernel: [1492130.371791] imap[21098]: segfault at 00000008 eip 080b779b esp bfce11a0 error 4 Jan 27 21:44:52 postamt kernel: [1492190.407380] imap[21368]: segfault at 00000008 eip 080b779b esp bfd319f0 error 4 Jan 27 21:45:52 postamt kernel: [1492250.060784] imap[21596]: segfault at 00000008 eip 080b779b esp bfaac770 error 4 Jan 27 21:46:52 postamt kernel: [1492310.001016] imap[21744]: segfault at 00000008 eip 080b779b esp bfbaf870 error 4 Jan 27 21:47:52 postamt kernel: [1492370.025871] imap[21943]: segfault at 00000008 eip 080b779b esp bfb3a7f0 error 4 Jan 27 21:48:52 postamt kernel: [1492429.710557] imap[22124]: segfault at 00000008 eip 080b779b esp bf938df0 error 4 Jan 27 21:49:52 postamt kernel: [1492489.767330] imap[22277]: segfault at 00000008 eip 080b779b esp bfeeebb0 error 4 Jan 27 21:50:52 postamt kernel: [1492549.596320] imap[22492]: segfault at 00000008 eip 080b779b esp bf980640 error 4 Jan 27 21:51:52 postamt kernel: [1492609.463280] imap[22661]: segfault at 00000008 eip 080b779b esp bfd65220 error 4 Jan 27 21:52:52 postamt kernel: [1492669.314384] imap[22835]: segfault at 00000008 eip 080b779b esp bfac1780 error 4 Jan 27 21:53:53 postamt kernel: [1492730.114634] imap[23043]: segfault at 00000008 eip 080b779b esp bfec5380 error 4 Jan 27 21:54:52 postamt kernel: [1492789.493685] imap[23251]: segfault at 00000008 eip 080b779b esp bfb72830 error 4 Jan 27 21:55:52 postamt kernel: [1492848.537290] imap[23463]: segfault at 00000008 eip 080b779b esp bfd101d0 error 4 Jan 27 21:56:52 postamt kernel: [1492908.394380] imap[23666]: segfault at 00000008 eip 080b779b esp bfd059c0 error 4 Jan 27 21:57:52 postamt kernel: [1492968.672480] imap[23905]: segfault at 00000008 eip 080b779b esp bfcef1b0 error 4 Jan 27 21:58:52 postamt kernel: [1493028.626160] imap[24075]: segfault at 00000008 eip 080b779b esp bff56410 error 4 Jan 27 21:59:52 postamt kernel: [1493088.262756] imap[24246]: segfault at 00000008 eip 080b779b esp bf863520 error 4 Jan 27 22:00:52 postamt kernel: [1493148.311438] imap[24521]: segfault at 00000008 eip 080b779b esp bf9c7680 error 4 Jan 27 22:01:52 postamt kernel: [1493208.190755] imap[24747]: segfault at 00000008 eip 080b779b esp bfcdc9a0 error 4 Jan 27 22:02:52 postamt kernel: [1493268.042169] imap[26155]: segfault at 00000008 eip 080b779b esp bf89ad60 error 4 Jan 27 22:03:52 postamt kernel: [1493327.789775] imap[26370]: segfault at 00000008 eip 080b779b esp bff8cc50 error 4 Jan 27 22:04:52 postamt kernel: [1493387.764633] imap[26684]: segfault at 00000008 eip 080b779b esp bf8eedb0 error 4 Jan 27 22:05:52 postamt kernel: [1493447.644743] imap[26977]: segfault at 00000008 eip 080b779b esp bfeecbb0 error 4 Jan 27 22:06:52 postamt kernel: [1493507.540180] imap[27125]: segfault at 00000008 eip 080b779b esp bf801cc0 error 4 Jan 27 22:07:52 postamt kernel: [1493567.369566] imap[27289]: segfault at 00000008 eip 080b779b esp bf8e85a0 error 4 Jan 27 22:08:52 postamt kernel: [1493627.231119] imap[27463]: segfault at 00000008 eip 080b779b esp bfb247e0 error 4 Jan 27 22:09:52 postamt kernel: [1493687.001615] imap[27738]: segfault at 00000008 eip 080b779b esp bf9d6e90 error 4 Jan 27 22:10:53 postamt kernel: [1493747.474619] imap[27959]: segfault at 00000008 eip 080b779b esp bfaca780 error 4 Jan 27 22:11:52 postamt kernel: [1493806.799749] imap[28128]: segfault at 00000008 eip 080b779b esp bfd44a00 error 4 Jan 27 22:12:52 postamt kernel: [1493866.861833] imap[28374]: segfault at 00000008 eip 080b779b esp bfe6eb30 error 4 Jan 27 22:13:52 postamt kernel: [1493926.548149] imap[28571]: segfault at 00000008 eip 080b779b esp bfe41300 error 4 Jan 27 22:14:52 postamt kernel: [1493986.130800] imap[28817]: segfault at 00000008 eip 080b779b esp bfa6b730 error 4 Jan 27 22:15:52 postamt kernel: [1494046.275731] imap[29091]: segfault at 00000008 eip 080b779b esp bfd1c9e0 error 4 Jan 27 22:16:52 postamt kernel: [1494105.988678] imap[29285]: segfault at 00000008 eip 080b779b esp bf857d10 error 4 Jan 27 22:17:52 postamt kernel: [1494166.024624] imap[29574]: segfault at 00000008 eip 080b779b esp bfc97150 error 4 Jan 27 22:18:52 postamt kernel: [1494225.876185] imap[29747]: segfault at 00000008 eip 080b779b esp bffd7c90 error 4 Jan 27 22:19:52 postamt kernel: [1494285.761548] imap[29926]: segfault at 00000008 eip 080b779b esp bf9c3e80 error 4 Jan 27 22:20:52 postamt kernel: [1494345.149565] imap[30237]: segfault at 00000008 eip 080b779b esp bfea5b60 error 4 Jan 27 22:21:50 postamt kernel: [1494403.787466] imap[30392]: segfault at 00000008 eip 080b779b esp bfa28ee0 error 4 Jan 27 22:22:52 postamt kernel: [1494465.489386] imap[30639]: segfault at 00000008 eip 080b779b esp bf9cbe90 error 4 Jan 27 22:23:25 postamt kernel: [1494497.752003] imap[30758]: segfault at 00000008 eip 080b779b esp bf816cd0 error 4 Jan 27 22:23:57 postamt kernel: [1494530.454853] imap[30841]: segfault at 00000008 eip 080b779b esp bfdfaac0 error 4 Jan 27 22:24:52 postamt kernel: [1494585.062982] imap[31006]: segfault at 00000008 eip 080b779b esp bfe06ac0 error 4 Jan 27 22:25:52 postamt kernel: [1494644.789199] imap[31255]: segfault at 00000008 eip 080b779b esp bf8dbda0 error 4 Jan 27 22:26:52 postamt kernel: [1494704.879185] imap[31416]: segfault at 00000008 eip 080b779b esp bf8004c0 error 4 Jan 27 22:27:52 postamt kernel: [1494764.685607] imap[31657]: segfault at 00000008 eip 080b779b esp bf862520 error 4 Jan 27 22:28:52 postamt kernel: [1494824.552415] imap[31846]: segfault at 00000008 eip 080b779b esp bfa386f0 error 4 Jan 27 22:29:52 postamt kernel: [1494884.436358] imap[32041]: segfault at 00000008 eip 080b779b esp bfb47000 error 4 Jan 27 22:30:52 postamt kernel: [1494944.287761] imap[32244]: segfault at 00000008 eip 080b779b esp bfa85f40 error 4 Jan 27 22:31:52 postamt kernel: [1495003.656530] imap[32548]: segfault at 00000008 eip 080b779b esp bf8134d0 error 4 Jan 27 22:32:52 postamt kernel: [1495064.053787] imap[330]: segfault at 00000008 eip 080b779b esp bfc89950 error 4 Jan 27 22:33:52 postamt kernel: [1495123.868411] imap[580]: segfault at 00000008 eip 080b779b esp bffe74a0 error 4 Jan 27 22:34:52 postamt kernel: [1495183.760209] imap[733]: segfault at 00000008 eip 080b779b esp bfca0160 error 4 Jan 27 22:35:53 postamt kernel: [1495244.552178] imap[996]: segfault at 00000008 eip 080b779b esp bfe1b2e0 error 4 Jan 27 22:36:52 postamt kernel: [1495303.487503] imap[1203]: segfault at 00000008 eip 080b779b esp bf996e50 error 4 Jan 27 22:37:52 postamt kernel: [1495363.343885] imap[1465]: segfault at 00000008 eip 080b779b esp bfd119d0 error 4 Jan 27 22:38:52 postamt kernel: [1495423.291009] imap[1681]: segfault at 00000008 eip 080b779b esp bfa52f10 error 4 Jan 27 22:39:52 postamt kernel: [1495483.048162] imap[1842]: segfault at 00000008 eip 080b779b esp bfc9dcc0 error 4 Jan 27 22:40:52 postamt kernel: [1495542.920011] imap[2005]: segfault at 00000008 eip 080b779b esp bfdeaab0 error 4 Jan 27 22:41:52 postamt kernel: [1495602.795677] imap[2191]: segfault at 00000008 eip 080b779b esp bfe5f320 error 4 Jan 27 22:42:52 postamt kernel: [1495662.663179] imap[2412]: segfault at 00000008 eip 080b779b esp bf8b4d70 error 4 Jan 27 22:43:52 postamt kernel: [1495722.027349] imap[2620]: segfault at 00000008 eip 080b779b esp bfd47200 error 4 Jan 27 22:44:52 postamt kernel: [1495782.234240] imap[2845]: segfault at 00000008 eip 080b779b esp bf8b0d70 error 4 Jan 27 22:45:52 postamt kernel: [1495842.253035] imap[3113]: segfault at 00000008 eip 080b779b esp bffb0c70 error 4 Jan 27 22:46:53 postamt kernel: [1495903.018329] imap[3370]: segfault at 00000008 eip 080b779b esp bfdf02b0 error 4 Jan 27 22:47:52 postamt kernel: [1495961.981124] imap[3587]: segfault at 00000008 eip 080b779b esp bfc090c0 error 4 Jan 27 22:48:52 postamt kernel: [1496021.846787] imap[3760]: segfault at 00000008 eip 080b779b esp bf80b4d0 error 4 Jan 27 22:49:52 postamt kernel: [1496081.560845] imap[3954]: segfault at 00000008 eip 080b779b esp bf8ba580 error 4 Jan 27 22:50:53 postamt kernel: [1496142.523771] imap[4125]: segfault at 00000008 eip 080b779b esp bfaf97b0 error 4 Jan 27 22:51:52 postamt kernel: [1496201.295812] imap[4313]: segfault at 00000008 eip 080b779b esp bf9345f0 error 4 Jan 27 22:52:52 postamt kernel: [1496260.799813] imap[4527]: segfault at 00000008 eip 080b779b esp bf922de0 error 4 Jan 27 22:53:52 postamt kernel: [1496320.720011] imap[4699]: segfault at 00000008 eip 080b779b esp bfa83740 error 4 Jan 27 22:54:52 postamt kernel: [1496380.573351] imap[4856]: segfault at 00000008 eip 080b779b esp bfaf3a50 error 4 Jan 27 22:55:52 postamt kernel: [1496440.439452] imap[5033]: segfault at 00000008 eip 080b779b esp bfd371f0 error 4 Jan 27 22:56:52 postamt kernel: [1496500.307642] imap[5241]: segfault at 00000008 eip 080b779b esp bfd391f0 error 4 Jan 27 22:57:52 postamt kernel: [1496560.149536] imap[5442]: segfault at 00000008 eip 080b779b esp bf981640 error 4 Jan 27 22:58:52 postamt kernel: [1496620.494374] imap[5616]: segfault at 00000008 eip 080b779b esp bfe182d0 error 4 Jan 27 22:59:52 postamt kernel: [1496680.203953] imap[5752]: segfault at 00000008 eip 080b779b esp bfe5c320 error 4 Jan 27 23:00:52 postamt kernel: [1496740.238370] imap[6015]: segfault at 00000008 eip 080b779b esp bfcc7180 error 4 Jan 27 23:01:52 postamt kernel: [1496800.103197] imap[6266]: segfault at 00000008 eip 080b779b esp bffaf470 error 4 Jan 27 23:02:52 postamt kernel: [1496859.985529] imap[7629]: segfault at 00000008 eip 080b779b esp bfe5db20 error 4 Jan 27 23:03:52 postamt kernel: [1496919.815999] imap[7845]: segfault at 00000008 eip 080b779b esp bfe4a300 error 4 Jan 27 23:04:52 postamt kernel: [1496979.640700] imap[8042]: segfault at 00000008 eip 080b779b esp bfcc8180 error 4 Jan 27 23:05:52 postamt kernel: [1497039.546839] imap[8299]: segfault at 00000008 eip 080b779b esp bfee3ba0 error 4 Jan 27 23:06:52 postamt kernel: [1497099.424993] imap[8541]: segfault at 00000008 eip 080b779b esp bfe6eb30 error 4 Jan 27 23:07:52 postamt kernel: [1497159.324847] imap[8713]: segfault at 00000008 eip 080b779b esp bfb97050 error 4 Jan 27 23:08:52 postamt kernel: [1497219.167949] imap[8887]: segfault at 00000008 eip 080b779b esp bfa7e740 error 4 Jan 27 23:09:52 postamt kernel: [1497278.561205] imap[9055]: segfault at 00000008 eip 080b779b esp bff53410 error 4 Jan 27 23:10:52 postamt kernel: [1497338.726155] imap[9326]: segfault at 00000008 eip 080b779b esp bfd85240 error 4 Jan 27 23:11:52 postamt kernel: [1497398.734613] imap[9525]: segfault at 00000008 eip 080b779b esp bfa9ff60 error 4 Jan 27 23:12:52 postamt kernel: [1497458.590435] imap[9733]: segfault at 00000008 eip 080b779b esp bf9cc690 error 4 Jan 27 23:13:54 postamt kernel: [1497519.795521] imap[9948]: segfault at 00000008 eip 080b779b esp bf8688a0 error 4 Jan 27 23:14:52 postamt kernel: [1497578.104239] imap[10104]: segfault at 00000008 eip 080b779b esp bf97fe40 error 4 Jan 27 23:15:52 postamt kernel: [1497637.980983] imap[10385]: segfault at 00000008 eip 080b779b esp bffac470 error 4 Jan 27 23:16:52 postamt kernel: [1497697.982077] imap[10612]: segfault at 00000008 eip 080b779b esp bfa6ff30 error 4 Jan 27 23:17:52 postamt kernel: [1497757.918665] imap[10869]: segfault at 00000008 eip 080b779b esp bf8054c0 error 4 Jan 27 23:18:52 postamt kernel: [1497817.727103] imap[11007]: segfault at 00000008 eip 080b779b esp bfe6d330 error 4 Jan 27 23:19:52 postamt kernel: [1497877.595778] imap[11173]: segfault at 00000008 eip 080b779b esp bf88bd50 error 4 Jan 27 23:20:52 postamt kernel: [1497937.308249] imap[11352]: segfault at 00000008 eip 080b779b esp bfb99050 error 4 Jan 27 23:21:52 postamt kernel: [1497997.328910] imap[11483]: segfault at 00000008 eip 080b779b esp bf903dc0 error 4 Jan 27 23:22:52 postamt kernel: [1498057.172791] imap[11698]: segfault at 00000008 eip 080b779b esp bfa6ff30 error 4 Jan 27 23:23:53 postamt kernel: [1498117.915910] imap[11878]: segfault at 00000008 eip 080b779b esp bfe3e300 error 4 Jan 27 23:24:52 postamt kernel: [1498176.698946] imap[12027]: segfault at 00000008 eip 080b779b esp bfd51210 error 4 Jan 27 23:25:52 postamt kernel: [1498236.751059] imap[12259]: segfault at 00000008 eip 080b779b esp bffb5ab0 error 4 Jan 27 23:26:52 postamt kernel: [1498296.659260] imap[12400]: segfault at 00000008 eip 080b779b esp bf81a4d0 error 4 Jan 27 23:27:52 postamt kernel: [1498356.554130] imap[12646]: segfault at 00000008 eip 080b779b esp bffe14a0 error 4 Jan 27 23:28:52 postamt kernel: [1498416.364134] imap[12781]: segfault at 00000008 eip 080b779b esp bfff4cb0 error 4 Jan 27 23:29:52 postamt kernel: [1498476.250874] imap[12919]: segfault at 00000008 eip 080b779b esp bff74430 error 4 Jan 27 23:30:52 postamt kernel: [1498536.066608] imap[13121]: segfault at 00000008 eip 080b779b esp bfa8cf50 error 4 Jan 27 23:31:52 postamt kernel: [1498595.882886] imap[13330]: segfault at 00000008 eip 080b779b esp bfe4bb10 error 4 Jan 27 23:32:52 postamt kernel: [1498655.847980] imap[13584]: segfault at 00000008 eip 080b779b esp bfb7f040 error 4 Jan 27 23:33:52 postamt kernel: [1498715.660556] imap[13772]: segfault at 00000008 eip 080b779b esp bfb49800 error 4 Jan 27 23:34:53 postamt kernel: [1498776.545256] imap[13951]: segfault at 00000008 eip 080b779b esp bfb91850 error 4 Jan 27 23:35:52 postamt kernel: [1498835.258066] imap[14134]: segfault at 00000008 eip 080b779b esp bfaebfb0 error 4 Jan 27 23:36:52 postamt kernel: [1498895.222671] imap[14302]: segfault at 00000008 eip 080b779b esp bfdc3280 error 4 Jan 27 23:37:52 postamt kernel: [1498954.618820] imap[14531]: segfault at 00000008 eip 080b779b esp bfcd2990 error 4 Jan 27 23:38:52 postamt kernel: [1499014.522614] imap[14664]: segfault at 00000008 eip 080b779b esp bfd249e0 error 4 Jan 27 23:39:52 postamt kernel: [1499074.837205] imap[14809]: segfault at 00000008 eip 080b779b esp bfbd5090 error 4 Jan 27 23:40:53 postamt kernel: [1499135.650847] imap[14994]: segfault at 00000008 eip 080b779b esp bfe17ad0 error 4 Jan 27 23:41:52 postamt kernel: [1499194.593713] imap[15169]: segfault at 00000008 eip 080b779b esp bfd0b1c0 error 4 Jan 27 23:42:52 postamt kernel: [1499253.963270] imap[15708]: segfault at 00000008 eip 080b779b esp bfc280e0 error 4 Jan 27 23:43:52 postamt kernel: [1499313.791662] imap[15877]: segfault at 00000008 eip 080b779b esp bfc2f0f0 error 4 Jan 27 23:44:52 postamt kernel: [1499373.647933] imap[16061]: segfault at 00000008 eip 080b779b esp bfc40900 error 4 Jan 27 23:45:52 postamt kernel: [1499433.995947] imap[16267]: segfault at 00000008 eip 080b779b esp bfda8260 error 4 Jan 27 23:46:52 postamt kernel: [1499493.713377] imap[16434]: segfault at 00000008 eip 080b779b esp bffcdc90 error 4 Jan 27 23:47:51 postamt kernel: [1499553.240307] imap[16637]: segfault at 00000008 eip 080b779b esp bfef6bb0 error 4 Jan 27 23:48:52 postamt kernel: [1499613.582920] imap[16753]: segfault at 00000008 eip 080b779b esp bff103d0 error 4 Jan 27 23:49:52 postamt kernel: [1499672.978342] imap[16905]: segfault at 00000008 eip 080b779b esp bfac1780 error 4 Jan 27 23:50:52 postamt kernel: [1499733.301011] imap[17073]: segfault at 00000008 eip 080b779b esp bfd259e0 error 4 Jan 27 23:51:52 postamt kernel: [1499793.182747] imap[17224]: segfault at 00000008 eip 080b779b esp bfd86240 error 4 Jan 27 23:52:52 postamt kernel: [1499853.043048] imap[17400]: segfault at 00000008 eip 080b779b esp bfeedbb0 error 4 Jan 27 23:53:52 postamt kernel: [1499912.906866] imap[17529]: segfault at 00000008 eip 080b779b esp bfc79130 error 4 Jan 27 23:54:52 postamt kernel: [1499972.757872] imap[17645]: segfault at 00000008 eip 080b779b esp bfe062c0 error 4 Jan 27 23:55:52 postamt kernel: [1500032.389678] imap[17917]: segfault at 00000008 eip 080b779b esp bfe20ae0 error 4 Jan 27 23:56:52 postamt kernel: [1500092.431048] imap[18205]: segfault at 00000008 eip 080b779b esp bfa3d700 error 4 Jan 27 23:57:52 postamt kernel: [1500152.322856] imap[18619]: segfault at 00000008 eip 080b779b esp bfb2c7f0 error 4 Jan 27 23:58:52 postamt kernel: [1500212.175835] imap[18833]: segfault at 00000008 eip 080b779b esp bfa01ec0 error 4 Jan 27 23:59:52 postamt kernel: [1500272.092326] imap[19007]: segfault at 00000008 eip 080b779b esp bff0abc0 error 4 Jan 28 00:00:52 postamt kernel: [1500331.907920] imap[20272]: segfault at 00000008 eip 080b779b esp bff50c10 error 4 Jan 28 00:01:52 postamt kernel: [1500391.720600] imap[20694]: segfault at 00000008 eip 080b779b esp bf827ce0 error 4 Jan 28 00:02:52 postamt kernel: [1500451.787824] imap[21892]: segfault at 00000008 eip 080b779b esp bf963e20 error 4 Jan 28 00:03:52 postamt kernel: [1500511.325729] imap[22072]: segfault at 00000008 eip 080b779b esp bfbf08b0 error 4 Jan 28 00:04:52 postamt kernel: [1500571.305433] imap[22503]: segfault at 00000008 eip 080b779b esp bfec6b80 error 4 Jan 28 00:05:52 postamt kernel: [1500631.151684] imap[22883]: segfault at 00000008 eip 080b779b esp bf9c7680 error 4 Jan 28 00:06:52 postamt kernel: [1500691.026298] imap[23089]: segfault at 00000008 eip 080b779b esp bfb0efd0 error 4 Jan 28 00:07:52 postamt kernel: [1500750.902355] imap[23358]: segfault at 00000008 eip 080b779b esp bfdde2a0 error 4 Jan 28 00:08:52 postamt kernel: [1500810.763196] imap[23513]: segfault at 00000008 eip 080b779b esp bfb7d840 error 4 Jan 28 00:09:52 postamt kernel: [1500870.615833] imap[23685]: segfault at 00000008 eip 080b779b esp bf802cc0 error 4 Jan 28 00:16:13 postamt kernel: [1501251.370985] imap[24769]: segfault at 00000008 eip 080b779b esp bff6e430 error 4 Jan 28 00:17:13 postamt kernel: [1501310.596696] imap[24946]: segfault at 00000008 eip 080b779b esp bf853510 error 4 Jan 28 00:18:13 postamt kernel: [1501370.920233] imap[25122]: segfault at 00000008 eip 080b779b esp bf967e20 error 4 Jan 28 00:19:13 postamt kernel: [1501430.766191] imap[25240]: segfault at 00000008 eip 080b779b esp bf9165d0 error 4 Jan 28 00:20:13 postamt kernel: [1501490.693524] imap[25427]: segfault at 00000008 eip 080b779b esp bfd90a50 error 4 Jan 28 00:21:13 postamt kernel: [1501550.168687] imap[25588]: segfault at 00000008 eip 080b779b esp bfad0790 error 4 Jan 28 00:22:13 postamt kernel: [1501609.977256] imap[25714]: segfault at 00000008 eip 080b779b esp bf936df0 error 4 Jan 28 00:23:13 postamt kernel: [1501670.119942] imap[25871]: segfault at 00000008 eip 080b779b esp bf942e00 error 4 Jan 28 00:24:13 postamt kernel: [1501729.991786] imap[26048]: segfault at 00000008 eip 080b779b esp bfcb9980 error 4 Jan 28 00:25:13 postamt kernel: [1501789.991210] imap[26269]: segfault at 00000008 eip 080b779b esp bfa266e0 error 4 Jan 28 00:26:13 postamt kernel: [1501849.853889] imap[26413]: segfault at 00000008 eip 080b779b esp bf9a6e60 error 4 Jan 28 00:27:13 postamt kernel: [1501909.701024] imap[26550]: segfault at 00000008 eip 080b779b esp bfac0f80 error 4 Jan 28 00:28:13 postamt kernel: [1501969.771280] imap[26762]: segfault at 00000008 eip 080b779b esp bff3ec00 error 4 Jan 28 00:29:13 postamt kernel: [1502029.435910] imap[26878]: segfault at 00000008 eip 080b779b esp bfc47100 error 4 Jan 28 00:30:13 postamt kernel: [1502089.306436] imap[27067]: segfault at 00000008 eip 080b779b esp bff2a3e0 error 4 Jan 28 00:31:13 postamt kernel: [1502149.155697] imap[27294]: segfault at 00000008 eip 080b779b esp bffbfc80 error 4 Jan 28 00:32:13 postamt kernel: [1502209.059814] imap[27463]: segfault at 00000008 eip 080b779b esp bfd309f0 error 4 Jan 28 00:33:13 postamt kernel: [1502268.888084] imap[27614]: segfault at 00000008 eip 080b779b esp bfb56810 error 4 Jan 28 00:34:13 postamt kernel: [1502328.741721] imap[27746]: segfault at 00000008 eip 080b779b esp bfba0060 error 4 Jan 28 00:35:13 postamt kernel: [1502388.156213] imap[27926]: segfault at 00000008 eip 080b779b esp bfaa0f60 error 4 Jan 28 00:36:13 postamt kernel: [1502448.062677] imap[28058]: segfault at 00000008 eip 080b779b esp bf827ce0 error 4 Jan 28 00:37:13 postamt kernel: [1502508.172595] imap[28254]: segfault at 00000008 eip 080b779b esp bff6f430 error 4 Jan 28 00:38:13 postamt kernel: [1502568.190818] imap[28390]: segfault at 00000008 eip 080b779b esp bfc64120 error 4 Jan 28 00:39:13 postamt kernel: [1502628.070471] imap[28541]: segfault at 00000008 eip 080b779b esp bfbca880 error 4 Jan 28 00:42:49 postamt kernel: [1502843.244085] imap[29043]: segfault at 00000008 eip 080b779b esp bfef83b0 error 4 Jan 28 00:43:24 postamt kernel: [1502877.724718] imap[29123]: segfault at 00000008 eip 080b779b esp bfc268e0 error 4 Jan 28 00:44:13 postamt kernel: [1502927.357346] imap[29234]: segfault at 00000008 eip 080b779b esp bfd44a00 error 4 Jan 28 00:45:13 postamt kernel: [1502987.018908] imap[29386]: segfault at 00000008 eip 080b779b esp bfd189d0 error 4 Jan 28 00:46:13 postamt kernel: [1503047.129405] imap[29535]: segfault at 00000008 eip 080b779b esp bfcdc9a0 error 4 Jan 28 00:47:13 postamt kernel: [1503106.951608] imap[29691]: segfault at 00000008 eip 080b779b esp bfdbe280 error 4 Jan 28 00:48:13 postamt kernel: [1503166.820452] imap[29820]: segfault at 00000008 eip 080b779b esp bf9d4690 error 4 Jan 28 00:49:13 postamt kernel: [1503226.508677] imap[29966]: segfault at 00000008 eip 080b779b esp bfd001c0 error 4 Jan 28 00:50:13 postamt kernel: [1503286.523513] imap[30118]: segfault at 00000008 eip 080b779b esp bf96fe30 error 4 Jan 28 00:51:13 postamt kernel: [1503346.423048] imap[30257]: segfault at 00000008 eip 080b779b esp bfad9790 error 4 Jan 28 00:52:13 postamt kernel: [1503405.755275] imap[30401]: segfault at 00000008 eip 080b779b esp bff103d0 error 4 Jan 28 00:53:13 postamt kernel: [1503466.131636] imap[30518]: segfault at 00000008 eip 080b779b esp bfe072c0 error 4 Jan 28 00:54:13 postamt kernel: [1503525.989899] imap[30660]: segfault at 00000008 eip 080b779b esp bfbdd0a0 error 4 Jan 28 00:55:13 postamt kernel: [1503585.752248] imap[30796]: segfault at 00000008 eip 080b779b esp bf964e20 error 4 Jan 28 00:56:13 postamt kernel: [1503645.222460] imap[30918]: segfault at 00000008 eip 080b779b esp bf9215e0 error 4 Jan 28 00:57:13 postamt kernel: [1503705.578693] imap[31036]: segfault at 00000008 eip 080b779b esp bf926de0 error 4 Jan 28 00:58:13 postamt kernel: [1503765.439651] imap[31140]: segfault at 00000008 eip 080b779b esp bfd6e230 error 4 Jan 28 00:59:13 postamt kernel: [1503825.315499] imap[31225]: segfault at 00000008 eip 080b779b esp bf81c4e0 error 4 Jan 28 01:00:13 postamt kernel: [1503885.246578] imap[31393]: segfault at 00000008 eip 080b779b esp bf898550 error 4 Jan 28 01:01:13 postamt kernel: [1503945.202943] imap[31556]: segfault at 00000008 eip 080b779b esp bfc178d0 error 4 Jan 28 01:02:13 postamt kernel: [1504004.816363] imap[32652]: segfault at 00000008 eip 080b779b esp bfd52210 error 4 Jan 28 01:03:13 postamt kernel: [1504064.842932] imap[624]: segfault at 00000008 eip 080b779b esp bff3ac00 error 4 Jan 28 01:04:13 postamt kernel: [1504124.319423] imap[794]: segfault at 00000008 eip 080b779b esp bfbdc0a0 error 4 Jan 28 01:05:13 postamt kernel: [1504184.493838] imap[954]: segfault at 00000008 eip 080b779b esp bfc8b950 error 4 Jan 28 01:06:13 postamt kernel: [1504244.266381] imap[1085]: segfault at 00000008 eip 080b779b esp bf80c4d0 error 4 Jan 28 01:07:13 postamt kernel: [1504304.213805] imap[1218]: segfault at 00000008 eip 080b779b esp bfc248e0 error 4 Jan 28 01:09:13 postamt kernel: [1504423.933524] imap[1517]: segfault at 00000008 eip 080b779b esp bf9df6a0 error 4 Jan 28 01:10:13 postamt kernel: [1504483.778455] imap[1678]: segfault at 00000008 eip 080b779b esp bfdd0290 error 4 Jan 28 01:11:13 postamt kernel: [1504543.914102] imap[1799]: segfault at 00000008 eip 080b779b esp bfa67f20 error 4 Jan 28 01:12:13 postamt kernel: [1504603.761115] imap[2111]: segfault at 00000008 eip 080b779b esp bf877d30 error 4 Jan 28 01:13:13 postamt kernel: [1504663.463429] imap[2214]: segfault at 00000008 eip 080b779b esp bfebcb80 error 4 Jan 28 01:14:13 postamt kernel: [1504723.291143] imap[2345]: segfault at 00000008 eip 080b779b esp bfad8f90 error 4 Jan 28 01:15:13 postamt kernel: [1504782.579991] imap[2590]: segfault at 00000008 eip 080b779b esp bfdba270 error 4 Jan 28 01:16:13 postamt kernel: [1504842.809325] imap[2719]: segfault at 00000008 eip 080b779b esp bff83c40 error 4 Jan 28 01:17:13 postamt kernel: [1504902.722683] imap[2872]: segfault at 00000008 eip 080b779b esp bfd089c0 error 4 Jan 28 01:18:13 postamt kernel: [1504962.676402] imap[2994]: segfault at 00000008 eip 080b779b esp bffb7c70 error 4 Jan 28 01:19:13 postamt kernel: [1505022.543614] imap[3130]: segfault at 00000008 eip 080b779b esp bfc328f0 error 4 Jan 28 01:20:13 postamt kernel: [1505081.936515] imap[3276]: segfault at 00000008 eip 080b779b esp bfb10f90 error 4 Jan 28 01:21:13 postamt kernel: [1505141.768812] imap[3451]: segfault at 00000008 eip 080b779b esp bff63420 error 4 Jan 28 01:23:13 postamt kernel: [1505261.818610] imap[3713]: segfault at 00000008 eip 080b779b esp bfee13a0 error 4 Jan 28 01:24:13 postamt kernel: [1505321.357798] imap[3829]: segfault at 00000008 eip 080b779b esp bf893550 error 4 Jan 28 01:25:13 postamt kernel: [1505381.550625] imap[3978]: segfault at 00000008 eip 080b779b esp bfe4d310 error 4 Jan 28 01:26:13 postamt kernel: [1505441.584355] imap[4098]: segfault at 00000008 eip 080b779b esp bff003c0 error 4 Jan 28 01:27:13 postamt kernel: [1505501.442841] imap[4268]: segfault at 00000008 eip 080b779b esp bfec0b80 error 4 Jan 28 01:28:13 postamt kernel: [1505561.257228] imap[4384]: segfault at 00000008 eip 080b779b esp bffb1c70 error 4 Jan 28 01:29:13 postamt kernel: [1505621.166565] imap[4492]: segfault at 00000008 eip 080b779b esp bfd1f9e0 error 4 Jan 28 01:30:13 postamt kernel: [1505680.877075] imap[4763]: segfault at 00000008 eip 080b779b esp bfa70f30 error 4 Jan 28 01:31:13 postamt kernel: [1505740.881620] imap[4855]: segfault at 00000008 eip 080b779b esp bfac6f80 error 4 Jan 28 01:32:13 postamt kernel: [1505800.750156] imap[4959]: segfault at 00000008 eip 080b779b esp bfa59710 error 4 Jan 28 01:33:13 postamt kernel: [1505860.605066] imap[5069]: segfault at 00000008 eip 080b779b esp bfdd5a90 error 4 Jan 28 01:34:13 postamt kernel: [1505920.474364] imap[5204]: segfault at 00000008 eip 080b779b esp bf977630 error 4 Jan 28 01:35:13 postamt kernel: [1505980.130676] imap[5333]: segfault at 00000008 eip 080b779b esp bfc62920 error 4 Jan 28 01:36:13 postamt kernel: [1506039.718655] imap[5557]: segfault at 00000008 eip 080b779b esp bf8d9590 error 4 Jan 28 01:37:13 postamt kernel: [1506100.034641] imap[5687]: segfault at 00000008 eip 080b779b esp bfe00ac0 error 4 Jan 28 01:38:13 postamt kernel: [1506159.943211] imap[5814]: segfault at 00000008 eip 080b779b esp bfb28fe0 error 4 Jan 28 01:39:13 postamt kernel: [1506219.783677] imap[5939]: segfault at 00000008 eip 080b779b esp bf865d20 error 4 Correlation with the dovecot log only shows: Jan 28 01:39:13 postamt dovecot: child 5939 (imap) killed with signal 11 Jan 28 01:38:13 postamt dovecot: child 5814 (imap) killed with signal 11 ... and so on ... $ /usr/local/sbin/dovecot --version 1.0.10 -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) plonk(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de UNIX is an operating system, OS/2 is half an operating system, Windows is a shell, and DOS is a boot partition virus." -- Peter H. Coffin

6 8

[Dovecot] sa learning from an imap spam folder
by Zbigniew Szalbot 29 Jan '08

29 Jan '08

Hello, I am sorry if I am writing to a wrong list because honestly I do not know where to write but I would like to be able to set up sa-learn via cron to learn from spam folder of a particular email account (via IMAP). Can anyone share how to do it? Is dovecot involved in it? I am using: Exim 4.69 Dovecot 1.0.10 p5-Mail-SpamAssassin-3.2.1 Thanks a lot for helping. Zbigniew Szalbot

2 1

[Dovecot] Load average on machine 400+
by Patrick 29 Jan '08

29 Jan '08

Hi all, Over the past week our mail server which NFS mounts the /home directory for mail has been experiencing major load issues. When doing a 'top', it appeared that slapd was the culprit (we use LDAP for authentication), but after upgrading the system and updating ldap, the cpu usage for LDAP has gone down, but the load average as not. I'm using Maildir. Everything from /home is NFS mounted, and the structure looks like this: /home/USERNAME/Maildir We're doing about 300 email messages a minute right now to that server, which isn't that much. I'm at a loss of words right now as I do not know where to troubleshoot from here. I've come up with the following questions: 1) I've noticed that some of our users have 500mb Maildir folders some even have 3gb+ - would this cause the CPU to have such a high load? 2) Currently on the box there is about 120 POP3 connections and 40 IMAP connections. Could this be the issue? 3) When I first set up this server, I appended INDEX=MEMORY to the end of the mail_location line. Should I remove this? I wanted to either remove it or put it on the local machine to speed things up. Here is my config: ##################### protocols = imap imaps pop3 pop3s listen = * disable_plaintext_auth = no log_path = /var/log/dovecot.log ssl_disable = no ssl_cert_file = /usr/share/ssl/xyz.com/xyz.com.crt ssl_key_file = /usr/share/ssl/xyz.com/xyz.com.key login_dir = /var/run/dovecot-login login_user = dovecot login_process_size = 64 login_process_per_connection = yes login_max_processes_count = 128 login_max_connections = 256 mail_location = maildir:/home/%u/Maildir:INDEX=MEMORY mmap_disable = yes fsync_disable = yes first_valid_uid = 200 maildir_copy_with_hardlinks = yes maildir_copy_preserve_filename = yes protocol imap { imap_client_workarounds = outlook-idle delay-newmail } protocol pop3 { pop3_no_flag_updates = no pop3_lock_session = no pop3_uidl_format = %08Xu%08Xv pop3_client_workarounds = } protocol lda { fsync_disable = no postmaster_address = postmaster(a)xyz.com hostname = mail.xyz.com } auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth_username_format = %Lu auth_verbose = yes auth_worker_max_count = 30 auth default { mechanisms = plain login passdb pam { args = blocking=yes } userdb passwd { } user = dovecot-auth socket listen { client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } dict { } plugin { } ##################### Again, this only happened within the past 1-2 weeks. How can I fix? Thanks in advance! Patrick

2 1

Re: [Dovecot] Dovecot/SeLinux issues after RHEL5.1 upgrade
by Ion Soltan 29 Jan '08

29 Jan '08

Thanks to Marius, I've got this problem fixed! I don't know how or why, but selinux directory contexts have been altered during the update for everyone else on the system except myself (what makes it odd is that my user has the same group and permissions as everyone else). So what did the trick was to apply: chcon -t user_home_dir_t to each user's home, mail, .imap and INBOX directories. Thanks again for pointing me in the right direction, Marius! Ion ----- Original Message ----- From: "Marius ROMAN" <marius.roman(a)gmail.com> To: "Ion Soltan" <webmaster(a)forlangs.net> Sent: Monday, January 28, 2008 2:05 PM Subject: Re: [Dovecot] Dovecot/SeLinux issues after RHEL5.1 upgrade > On Jan 28, 2008 9:33 PM, Ion Soltan <webmaster(a)forlangs.net> wrote: >> Marius, >> >> I do run the targeted policy. Are you suggesting a reinstall of the RPM? >> >> Thank you, >> Ion >> > > Nope. > Read http://www.dovecot.org/list/dovecot/2007-January/018989.html > maybe you have the same or related problem. > If this helps post your solution to the list. > > -- > Marius

1 0

[Dovecot] Messages not moved from Inbox by Apple Mail (Dovecot 1.0.10)
by Tom Collins 29 Jan '08

29 Jan '08

I just upgraded a server from Courier-IMAP to Dovecot, and I'm seeing some odd behavior. It's probably the result of something I did wrong in my configuration, and I'm hoping someone will let me know the easy fix for it. I have rules set up in Apple Mail to move and copy messages to different folders, some of which are IMAP folders, others on my own system. With Courier-IMAP, the messages would get moved without a problem. With dovecot, that's not happening. Here's my dovecot config. I've tried changing maildir_copy_with_hardlinks and maildir_copy_preserve_filename to "no", but that didn't seem to help. # 1.0.10: /usr/local/etc/dovecot.conf disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login verbose_proctitle: yes first_valid_uid: 89 last_valid_uid: 89 first_valid_gid: 89 last_valid_gid: 89 maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes namespace: type: private prefix: INBOX. inbox: yes auth default: mechanisms: plain login digest-md5 cram-md5 username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@% username_translation: %@ passdb: driver: vpopmail userdb: driver: vpopmail plugin: quota: maildir I haven't tried logging the IMAP session yet, but I can turn off SSL, fire up Wireshark and monitor the session if necessary. Is this a known problem? I'm able to move messages between folders manually, but when Apple Mail moves the new messages it doesn't work. -- Tom Collins - tom(a)tomlogic.com Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/ QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/

2 1

[Dovecot] Dovecot/SeLinux issues after RHEL5.1 upgrade
by Ion Soltan 28 Jan '08

28 Jan '08

Hello to everyone on the list, I have upgraded my RHEL4 to RHEL5.1 yesterday (all updates have been applied to it as well). I used to have dovecot v0.99.11 on the old system. Everything was working fine. Now I have 5.1 and its respective dovecot v1.0.rc15. Upon upgrading to RHEL5.1, dovecot no longer works correctly. The first thing I did after rewriting the config file for the updated version, was to check my own email. It works fine. However, no other user on the system can check his/hers. Here is what the log shows for everyone except myself: ============================ Jan 27 13:56:41 warp dovecot: POP3(jj): open() failed with file /home/jj/mail/.imap/INBOX/dovecot.index.log: Permission denied Jan 27 13:56:41 warp dovecot: POP3(jj): open() failed with file /home/jj/mail/.imap/INBOX/dovecot.index.log: Permission denied Jan 27 13:56:41 warp dovecot: POP3(jj): Couldn't open INBOX: Internal error occurred. Refer to server log for more information. [2008-01-27 13:56:41] ============================ There are NO complaints reported by selinux in the logs. If I setenforce 0 (disable selinux), everything is working fine for everyone. If I disable selinux monitoring on dovecot (setsebool dovecot_disable_trans 1), nothing changes, which makes me think that something else is causing the problem. I do very much want to use selinux, however, I cannot figure out what the problem is and I have been trying for many hours. Can anyone help? Thanks, Ion

2 1

[Dovecot] dovecot servers hanging with fuse/glusterfs errors
by Jordi Moles 28 Jan '08

28 Jan '08

hi. i've got a clustered mail system with glusterfs and some postfix, squirrelmail and dovecot machines sharing the same storage system through glusterfs. each server has only postfix or squirrel or dovecot installed on it. The thing is... dovecot servers hang very often and the last thing they always log is this: ************* login: Unable to handle kernel paging request at 0000000000100108 RIP: [<ffffffff88020838>] :fuse:request_end+0x45/0x109 PGD 1f729067 PUD 1faae067 PMD 0 Oops: 0002 [1] SMP CPU 0 Modules linked in: ipv6 fuse dm_snapshot dm_mirror dm_mod Pid: 678, comm: glusterfs Not tainted 2.6.18-xen #1 RIP: e030:[<ffffffff88020838>] [<ffffffff88020838>] :fuse:request_end+0x45/0x109 RSP: e02b:ffff88001f04dd68 EFLAGS: 00010246 RAX: 0000000000200200 RBX: ffff88001db9fa58 RCX: ffff88001db9fa68 RDX: 0000000000100100 RSI: ffff88001db9fa58 RDI: ffff88001f676400 RBP: ffff88001f676400 R08: 00000000204abb00 R09: ffff88001db9fb58 R10: 0000000000000008 R11: ffff88001f04dcf0 R12: 0000000000000000 R13: ffff88001db9fa90 R14: ffff88001f04ddf8 R15: 0000000000000001 FS: 00002b29187c53b0(0000) GS:ffffffff804cd000(0000) knlGS:0000000000000000 CS: e033 DS: 0000 ES: 0000 Process glusterfs (pid: 678, threadinfo ffff88001f04c000, task ffff88001fc5a860) Stack: ffff88001db9fa58 ffff88001f676400 00000000fffffffe ffffffff88021056 ffff88001f04def8 000000301f04de88 ffffffff8020dd40 ffff88001f04ddb8 ffffffff80225ca3 ffff88001de23500 ffffffff803ef023 ffff88001f04de98 Call Trace: [<ffffffff88021056>] :fuse:fuse_dev_readv+0x385/0x435 [<ffffffff8020dd40>] monotonic_clock+0x35/0x7d [<ffffffff80225ca3>] deactivate_task+0x1d/0x28 [<ffffffff803ef023>] thread_return+0x0/0x120 [<ffffffff802801d3>] do_readv_writev+0x271/0x294 [<ffffffff802274c7>] default_wake_function+0x0/0xe [<ffffffff803f0976>] __down_read+0x12/0xec [<ffffffff88021120>] :fuse:fuse_dev_read+0x1a/0x1f [<ffffffff802804bc>] vfs_read+0xcb/0x171 [<ffffffff802274c7>] default_wake_function+0x0/0xe [<ffffffff8028089b>] sys_read+0x45/0x6e [<ffffffff8020a436>] system_call+0x86/0x8b [<ffffffff8020a3b0>] system_call+0x0/0x8b Code: 48 89 42 08 48 89 10 48 c7 41 08 00 02 20 00 f6 46 30 08 48 RIP [<ffffffff88020838>] :fuse:request_end+0x45/0x109 RSP <ffff88001f04dd68> CR2: 0000000000100108 dovecot01gluster01 kernel: Oops: 0002 [1] SMP dovecot01gluster01 kernel: CR2: 0000000000100108 <3>BUG: soft lockup detected on CPU#0! Call Trace: <IRQ> [<ffffffff80257f78>] softlockup_tick+0xd8/0xea [<ffffffff8020f110>] timer_interrupt+0x3a9/0x405 [<ffffffff80258264>] handle_IRQ_event+0x4e/0x96 [<ffffffff80258350>] __do_IRQ+0xa4/0x105 [<ffffffff8020b0e8>] call_softirq+0x1c/0x28 [<ffffffff8020cecb>] do_IRQ+0x65/0x73 [<ffffffff8034a8c1>] evtchn_do_upcall+0xac/0x12d [<ffffffff8020ac1e>] do_hypervisor_callback+0x1e/0x2c <EOI> [<ffffffff802d6f56>] dummy_inode_permission+0x0/0x3 [<ffffffff8028c9b8>] do_lookup+0x63/0x173 [<ffffffff803f1232>] .text.lock.spinlock+0x0/0x8a [<ffffffff8802144c>] :fuse:request_send+0x1b/0x2a8 [<ffffffff8028f0d6>] __link_path_walk+0xdf2/0xf3c [<ffffffff80261275>] __do_page_cache_readahead+0x8a/0x28f [<ffffffff8802249f>] :fuse:fuse_dentry_revalidate+0x94/0x120 [<ffffffff80299838>] mntput_no_expire+0x19/0x8b [<ffffffff8028f2f3>] link_path_walk+0xd3/0xe5 [<ffffffff8029571e>] __d_lookup+0xb0/0xff [<ffffffff8028ca92>] do_lookup+0x13d/0x173 [<ffffffff8028e687>] __link_path_walk+0x3a3/0xf3c [<ffffffff8028f27c>] link_path_walk+0x5c/0xe5 [<ffffffff80219b90>] do_page_fault+0xee9/0x1215 [<ffffffff8027e38d>] fd_install+0x25/0x5f [<ffffffff8025daac>] filemap_nopage+0x188/0x324 [<ffffffff8028f6df>] do_path_lookup+0x270/0x2ec [<ffffffff8028e0c6>] getname+0x15b/0x1c1 [<ffffffff8028ff52>] __user_walk_fd+0x37/0x4c [<ffffffff80288883>] vfs_stat_fd+0x1b/0x4a [<ffffffff80219b90>] do_page_fault+0xee9/0x1215 [<ffffffff8027e38d>] fd_install+0x25/0x5f [<ffffffff80239287>] do_sigaction+0x7a/0x1f3 [<ffffffff80288a4e>] sys_newstat+0x19/0x31 [<ffffffff80239495>] sys_rt_sigaction+0x59/0x98 [<ffffffff8020ab73>] error_exit+0x0/0x71 [<ffffffff8020a436>] system_call+0x86/0x8b [<ffffffff8020a3b0>] system_call+0x0/0x8b ************* these are basic debian etch brand new set ups, they have nothing else than dovecot and glusterfs-client installed on them. The thing is all machines i've got have the very same version of glusterfs-client, but only the dovecot ones hang. Do you have any idea? Thank you.

3 3

[Dovecot] dbox
by Evaggelos Balaskas 28 Jan '08

28 Jan '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am trying to create a user with dbox format. i get this error: dovecot: Jan 28 13:45:34 Error: IMAP(ebal2): Mail storage creation failed with mail_location: dbox:/var/mail/folders/testuser dovecot: Jan 28 13:45:34 Error: child 5336 (imap) returned error 89 my conf has this entry: mail_location: dbox:/var/mail/folders/%u dovecot 1.0.10 any ideas? - -- Evaggelos Balaskas - http://ebalaskas.gr Unix System Engineer Informatics Engineer Technological Education -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHncCfWIK+Pe9twhoRAsqJAKCD1Ctf0Tz+2uU5LpLsrmXyNQTg9gCeO/C3 6AzUw9JG3gMwq0cPwiUDmps= =Q/0q -----END PGP SIGNATURE-----

5 7

[Dovecot] Plugin Trash
by Sebastien Andreatta 28 Jan '08

28 Jan '08

Hello, I have a problem with the trash plugin. i'm not English, but if i ave understand this http://wiki.dovecot.org/Plugins/Trash , if a mailbox is full (90% for example) and i want to delete a mail, the plugin delete a mail in mailbox specified in a file ... I have this : dovecot.conf : protocol imap { [.....] mail_plugins = quota imap_quota trash } plugin { trash = /etc/dovecot-trash.conf } And in dovecot-trash.conf : # Spam mailbox is emptied before Trash 1 Spam # Trash mailbox is emptied before Sent 2 Trash # If both Sent and "Sent Messages" mailboxes exist, the next oldest message # to be deleted is looked up from both of the mailboxes. 3 Sent 3 Sent Messages I have 3 mail in a 20Mb mailbox : 2 in Mailbox (5.1mb both) 1 in Trash (6.2Mb) When i try to delete a mail from my mailbox i have a error and i only see this in maillog : Jan 28 15:49:37 soez dovecot: child 28398 (imap) killed with signal 11 Thanks for your help !! Number :-) _________________________________________________________________ Envoyez vos voeux de façon originale grâce aux nombreuses solutions de Windows Live ! http://get.live.com

2 1

[Dovecot] Shared mailboxes
by Wouter Amsterdam 28 Jan '08

28 Jan '08

L.S. It is not clear to me why I should use namespaces or symlinks to share a single maildir mailbox with multiple users. Why not configure multiple mail clients with the same account information? TIA, Wouter

3 3

[Dovecot] Howto set mail_location for system users over LDAP?
by Patrick Ben Koetter 28 Jan '08

28 Jan '08

In parallel to /etc/passwd I do have my system users in LDAP. I want to store their messages in /srv/mail/state-of-mind/<username>. Dovecot has been configured to retrieve the extra field mail to override the mail_location setting. I can see in the log it retrieves the correct information as long as I run Dovecot deliver as Postfix service 'dovecot' as shown in section "Virtual users" <http://wiki.dovecot.org/LDA/Postfix>. However if I use deliver as specified for "System users" it ignores the LDAP settings and delivers messages to my users $HOME directory as specified in /etc/passwd. Is this correct behaviour? What do I need to do to use the Postfix $mailbox_command _and_ have Dovecot deliver honor my LDAP settings? TIA, p@rick -- state of mind Agentur für Kommunikation, Design und Softwareentwicklung Patrick Koetter Tel: 089 45227227 Echinger Strasse 3 Fax: 089 45227226 85386 Eching Web: http://www.state-of-mind.de Amtsgericht München Partnerschaftsregister PR 563

1 0

[Dovecot] Thunderbird Problem - What causes this?
by Marc Perkel 28 Jan '08

28 Jan '08

Strange problem and I'm not sure what's causing it. I'm using IMAP. A new message arives in the inbox. I see it displayed in the message list in bold. I click on the message and it looks like it's reading it by the previous message that was in the window remains and the new message is still bold (unread). However I can then click on an old message and then click on the new message again and it reads. I have also seen Thunderbird be in a somewhat unresponsive state. You can click on messages and they don't read. But Shutting down Thunderbird and restarting it make it responsive again. Has anyone seen this?

8 9

[Dovecot] proxy configuration
by bill-dovecot＠carpenter.ORG 27 Jan '08

27 Jan '08

Before I spend some time experimenting with what might be impossible, maybe someone can just tell me (either "how" or that it's impossible). I'd like to get perdition out of my environment (mainly to have one less moving part in my architecture). I'm looking at dovecot's built-in proxying. In my setup, I don't have dedicated front-end machines. A user can connect to any server, but their mail files live on one particular machine. I'd like to transparently proxy them from whatever machine they happen to hit to their home machine. Except for the "proxy_maybe" feature advertised for dovecot 1.1, I don't see a surefire way to do this. Has anyone done it, or can anyone say for sure that it can't reasonably be done until "proxy_maybe"? Tx! -- bill-dovecot(a)carpenter.ORG (WJCarpenter) PGP 0x91865119 38 95 1B 69 C9 C6 3D 25 73 46 32 04 69 D6 ED F3

4 3

[Dovecot] Thunderbird trouble with Dovecote and dbox
by Hannes Dorbath 27 Jan '08

27 Jan '08

Hi, I'm new to Dovecot -- migrating from Cyrus. Version and config: # 1.1.beta14: /etc/dovecot/dovecot.conf protocols: imaps login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login mail_location: dbox:/data/mail/%u auth default: passdb: driver: pam args: * userdb: driver: passwd Linux 2.6.22-gentoo-r10 x86_64 GNU/Linux I have chosen dbox as mailbox format as it is claimed to be the best performing -- and performance is the reason I'd like to migrate away form Cyrus. I'm aware that dbox might not be 100% mature, but I'm good at doing backups. Anyway, so far I have the following problems: - Greyed out Inbox After creating a new user and connecting to that account with Thunderbird the first time, the INBOX folder is greyed out and in italic. Restarting Thunderbird 3-4 times seems to fix the problem. Google suggests that other people have seen the same, but they never found a solution. - After creating sub folders they are not displayed, I need to manually subscribe to them after creation. - When "Trash" contains folders, Thunderbird is unable to "Empty Trash". While the folder is removed from Thunderbird's folder tree, it's there again after a restart of Thunderbird. - Deleted folders are never deleted from the file system. I'm not sure if this is intended with dbox. - Moving folders via drag & drop does not work, it just does nothing. So basically nothing besides reading existing mails seems to work reliable. My basic questions now is, are those problems related to dbox, or to Dovecot and Thunderbird in general? -- Best regards, Hannes Dorbath

2 3

[Dovecot] User-specific mail_location using passwd database
by Maxime Brugidou 26 Jan '08

26 Jan '08

current version : 1.0.rc15 Hi, I would just like to know if it's possible to have different mail locations for different UNIX users, using pam authentication and the passwd userdb. We also have some virtual users using an SQL db. The current config is : auth default: username_translation: %@ verbose: yes debug: yes passdb: driver: pam passdb: driver: passwd passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: passwd userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf Then we can only modify mail locations for virtual users on the sql userdb. But how could we change it for real users ? Thanks for help, -- Maxime Brugidou

3 4

[Dovecot] Dovecot LDA (deliver) stopped working
by falz 26 Jan '08

26 Jan '08

Hello, One day a week or so ago, a server that's Postifx w/ Local users, dovecot w/ LDA decided to stop working. The only thing that stopped is the LDA portion, the rest all works fine. I also posted to the postfix mailing list yesterday but wasn't able to debug any further. Here's the situation: if I use mailbox_command to point to deliver, postfix will always put the message in the deferred queue. However, if I run deliver from the command line, it works fine. I've recompiled Dovecot and Postfix cleanly and reinstalled a few times to ensure permissions are OK. It's not a virtual setup, so I do NOT have setuid root on the deliver binary. Postfix people suggested placing a wrapper script for mailbox_command, which I did, and have it log to a text file, so I do know that deliver is being called. However, although I have LDA debug logging on, and it DID log prior to this, when postfix supposedly calls deliver, dovecot does NOT log anything. It DOES however log if I call deliver from any account (root or not) from the command line (ls / | /path/to/deliver -d localaccountname). Any way I can debug this further? I would assume that deliver would log something even if it's called, but it appears that it does not. My postfix related details are here: http://marc.info/?l=postfix-users&m=120119147917409&w=2 I followed the postfix/lda wiki (http://wiki.dovecot.org/LDA/Postfix) when setting it up, and it worked perfectly for months. I did indeed only have to change mailbox_command and it worked (I'm also using sasl auth, but that should be unrelated). Obviously something happened on my system, but I would assume recompiling/reinstalling would reset things. Nothing in the config files for postfix or dovecot changed, from what I can see, as generally I am the only one making changes. Thanks, --falz

3 7

[Dovecot] Count breaks socket
by Marc Perkel 26 Jan '08

26 Jan '08

If I use the socket option I can't use the count option to create more authentication processes. I get this error. Thanks in advance. dovecot: Jan 25 06:57:04 Error: auth(default): Socket already exists: /var/run/dovecot/auth-client auth default { mechanisms = plain passdb passwd-file { # Master users that can log in as anyone args = /etc/dovecot.masterusers master = yes pass =yes } # Linuxconf passwd-like file with specified location passdb passwd-file { args = /etc/exim/control/vmail/shadow.%d } # Linuxconf passwd-like file with specified location userdb passwd-file { args = /etc/exim/control/vmail/passwd.%d } socket listen { master { path = /var/run/dovecot/auth-master mode = 0666 } client { path = /var/run/dovecot/auth-client mode = 0666 } } # Number of authentication processes to create # count = 10 }

3 3

[Dovecot] dovecot HEAD, assertion failed after 7193:e5af14239137 changeset
by Daniel 26 Jan '08

26 Jan '08

Hi! Using HEAD, and after the 7193:e5af14239137 changeset (Store physical message sizes also to dovecot-uidlist if needed.) I'm getting this: (gdb) bt full #0 0x0a0a80dd in kill () from /usr/lib/libc.so.41.0 No symbol table info available. #1 0x0a0e04a7 in abort () at /usr/src/lib/libc/stdlib/abort.c:65 p = (struct atexit *) 0x84992000 cleanup_called = 0 mask = 4294967263 #2 0x1c0746cd in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0x3c000100 "file %s: line %d (%s): assertion failed: (%s)", args=0xcfbee4a4 "ĐA") at failures.c:423 backtrace = 0x1c0739f1 ";\003u\vÇ\003" #3 0x1c0741cb in i_panic (format=0x3c000100 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:195 No locals. #4 0x1c029a89 in maildir_mail_get_physical_size (_mail=0x7ee27428, size_r=0xcfbee598) at maildir-mail.c:361 mbox = (struct maildir_mailbox *) 0x7ee22028 data = (struct index_mail_data *) 0x7ee2749c st = {st_dev = -809573008, st_ino = 671359322, st_mode = 3485394200, st_nlink = 134504406, st_uid = 2264813824, st_gid = 671359313, st_rdev = -809573016, st_lspare0 = -809573008, st_atimespec = {tv_sec = 671359322, tv_nsec = 3690}, st_mtimespec = {tv_sec = 0, tv_nsec = 0}, st_ctimespec = {tv_sec = 0, tv_nsec = 0}, st_size = 2883503177569592696, st_blocks = 19440464480, st_blksize = 3485394312, st_flags = 134504965, st_gen = 2264813824, st_lspare1 = 2128748960, __st_birthtimespec = {tv_sec = 671359313, tv_nsec = -809573016}, st_qspare = {20665263472, 3485394280}} path = 0x0 #5 0x1c04a120 in mail_get_physical_size (mail=0x0, size_r=0xcfbee598) at mail.c:100 No locals. #6 0x0804672b in quota_alloc (ctx=0x7d5ec5c0, mail=0x7ee27428) at quota.c:777 size = 3842 #7 0x080465cb in quota_try_alloc (ctx=0x7d5ec5c0, mail=0x7ee27428, too_large_r=0xcfbee5fb) at quota.c:725 size = 3842 ret = 0 #8 0x08049d2e in quota_check (t=0x876b3300, mail=0x7ee27428) at quota-storage.c:148 qt = (struct quota_transaction_context *) 0x7d5ec5c0 ret = 0 too_large = false #9 0x1c04c30b in mailbox_copy (t=0x0, mail=0x7ee27028, flags=0, keywords=0x0, dest_mail=0x0) at mail-storage.c:741 No locals. #10 0x1c0116e6 in fetch_and_copy (client=0x86fe3180, destbox=0x7ee22028, t=0x876b3300, search_args=0x84d55068, src_uidset_r=0x52fe, copy_count_r=0x0) at cmd-copy.c:66 ---Type <return> to continue, or q <return> to quit--- search_ctx = (struct mail_search_context *) 0x876b3700 src_trans = (struct mailbox_transaction_context *) 0x876b3500 keywords = (struct mail_keywords *) 0x0 keywords_list = (const char * const *) 0x87c890e8 mail = (struct mail *) 0x7ee27028 copy_count = 1 srcset_ctx = {str = 0x83e872f0, first_uid = 0, last_uid = 4294967295} src_uidset = (string_t *) 0x83e872f0 ret = 1 #11 0x1c011899 in cmd_copy (cmd=0x84d55028) at cmd-copy.c:136 client = (struct client *) 0x86fe3180 storage = (struct mail_storage *) 0x890a9c28 destbox = (struct mailbox *) 0x7ee22028 t = (struct mailbox_transaction_context *) 0x876b3300 search_arg = (struct mail_search_arg *) 0x84d55068 messageset = 0x876d90d0 "3691:3693,3690" mailbox = 0x876d90e0 "Trash" src_uidset = 0xc "ČÎ\a*,äžĎXäžĎ" msg = 0x0 sync_flags = 0 imap_flags = 0 copy_count = 469853808 uid_validity = 469853899 uid1 = 2213048760 uid2 = 2299171840 ret = 9 #12 0x1c015192 in cmd_uid (cmd=0x84d55028) at cmd-uid.c:26 command = (struct command *) 0x52fe cmd_name = 0x876d90c8 "COPY" #13 0x1c0160f2 in client_command_input (cmd=0x84d55028) at client.c:536 client = (struct client *) 0x86fe3180 command = (struct command *) 0x52fe #14 0x1c015fc9 in client_command_input (cmd=0x84d55028) at client.c:585 client = (struct client *) 0x86fe3180 command = (struct command *) 0x52fe ---Type <return> to continue, or q <return> to quit--- #15 0x1c01614f in client_handle_next_command (client=0x86fe3180, remove_io_r=0xcfbee7db) at client.c:601 size = 36 #16 0x1c0161f5 in client_handle_input (client=0x86fe3180) at client.c:636 _data_stack_cur_id = 3 remove_io = false handled_commands = false #17 0x1c0162b6 in client_input (client=0x86fe3180) at client.c:674 cmd = (struct client_command_context *) 0x24 bytes = 36 #18 0x1c07adb4 in io_loop_handler_run (ioloop=0x86bdf0e0) at ioloop-kqueue.c:149 ctx = (struct ioloop_handler_context *) 0x89236030 events = (struct kevent *) 0x86bdf360 tv = {tv_sec = 3, tv_usec = 424767} ts = {tv_sec = 3, tv_nsec = 424767000} io = (struct io_file *) 0x86bdf360 t_id = 2 ret = 1 i = 0 #19 0x1c07a3c9 in io_loop_run (ioloop=0x86bdf0e0) at ioloop.c:301 No locals. #20 0x1c01ccd4 in main (argc=1, argv=0xcfbee900, envp=0xcfbee908) at main.c:293 No locals. Thanks! Daniel

2 4

[Dovecot] Capturing credentials for imap sync
by Master Abi 26 Jan '08

26 Jan '08

Hi List All the imap sync apps I could find requires the username /password credentails to be known before a sync occurs. I have Dovecot using ldap acting as a nearline backup mail server to MS Exchange. Every hour imapsync syncs mail between Exchange and Dovecot. This all works fine becuase the users credentials are known, but when new users are added I would like the process to work seemless like this: The user is added to the Active Directory. The mail client is configured with 2 accounts with identical credentials, one of which is connected to Dovecot. When the new client connects to dovecot, the credentials are captured and stored so that imapsync can use it. This If there is another way this can be done with dovecot, could I please be enlighten. I have read the doco on migration but I am not quite migrating but more replicating. Thank you

3 2

[Dovecot] symbolic links to root node
by Martin Preen 25 Jan '08

25 Jan '08

Hello, I have a question about the way Dovecot limits file system access. Currently we're using Dovecot 1.0.5 (Solaris 10). In some cases users have a symbolic link like "z: -> /" in their mail directory. As a result there are log entries like Jan 25 13:30:31 imap1 dovecot: [ID 107833 mail.error] IMAP(xyz): stat(/home/xyz/.wine/dosdevices/c:/windows/profiles/xyz/.../z:/proc/28381/root/proc/28381/.../root/proc/28381/Player/#SharedObje Jan 25 13:30:31 imap1 dovecot: [ID 107833 mail.error] IMAP(xyz): x) failed: File name too long We know the reason (the links are create by Wine) but unfortunately we cannot get rid of them. Is there something I can do (these links should be ignored) ? Or is it a bug ? Greetings. Martin --------------------------------------------------------------- Martin Preen, Universität Freiburg, Institut für Informatik Georges-Koehler-Allee 52, Raum 00-006, 79110 Freiburg, Germany phone: ++49 761 203-8250 preen(a)informatik.uni-freiburg.de fax: ++49 761 203-8242 www.informatik.uni-freiburg.de

3 3