- dovecot - dovecot.org

[Dovecot] High CPU utilization on Solaris 10
by Jon Alessandrello 17 Aug '07

17 Aug '07

Some people had this problem when giving some superoptimization flags with Sun Studio. Did you do that? -Timo No I did not use any optimization. And Dave, I took what you said and just tried both dovecot-1.0.2 dovecot-1.0.rc29 and have the same exact results :(

3 2

[Dovecot] index and control files not being created
by Luis Pablo Michelena Scaffo 16 Aug '07

16 Aug '07

Hello, I'm configurating dovecot 1.0.3 on debian etch. While trying to set public folders, y decided to have the index and control files on the users homes. those homes are mounted by nfs, with disabled access to root. In that scenario, I'm getting the errors i transcribe next: Aug 16 11:21:17 server dovecot: IMAP(user): fchown(/home/user/Maildir/shared-settings/control/.folder/dovecot-uidlis t) failed: Operation not permitted Aug 16 11:21:17 server dovecot: IMAP(user): fchown(/home/user/Maildir/shared-settings/control/.folder/dovecot-uidlis t) failed: Operation not permitted Aug 16 11:21:17 server dovecot: IMAP(user): rename(/inbox/shared/.folder/cur/mailfile, /inbox/shared/.folder/cur/mailfile :2,S) failed: Operation not permitted Aug 16 11:21:17 server dovecot: IMAP(user): fchown(/home/user/Maildir/shared-settings/control/.folder/dovecot-uidlis t) failed: Operation not permitted Aug 16 11:21:17 server dovecot: IMAP(user): rename(/inbox/shared/.folder/cur/mailfile, /inbox/shared/.folder/cur/mailfile :2,S) failed: Operation not permitted Aug 16 11:21:26 server dovecot: IMAP(user): Disconnected: Logged out Aug 16 11:21:27 server dovecot: IMAP(user): fchown(/home/user/Maildir/shared-settings/control/.folder/dovecot-uidlis t) failed: Operation not permitted Aug 16 11:21:27 server dovecot: IMAP(user): rename(/inbox/shared/.folder/cur/mailfile, /inbox/shared/.folder/cur/mailfile :2,S) failed: Operation not permitted Then I touched those files and the errors faded away. Beside that, I was testing the setup, and while trying to delete some files on the shared folder, I got another error: Aug 16 16:38:04 server dovecot: IMAP(user): rename(/inbox/shared/.folder/cur/1183976419.755_0.server:2,Sa, /inbox/shared/.folder/cur/1183976419.755_0.server:2,STa) failed: Operation not permitted Aug 16 16:38:11 server dovecot: IMAP(user): fchown(/home/user/Maildir/shared-settings/control/.folder/dovecot-uidlist) failed: Operation not permitted Aug 16 16:38:11 server dovecot: IMAP(user): rename(/inbox/shared/.folder/cur/1183976419.755_0.server:2,Sa, /inbox/shared/.folder/cur/1183976419.755_0.server:2,STa) failed: Operation not permitted Which seems odd, because I though that as a flag, the deleted flag should be marked on the index files and not directly on the shared folder (where the user hasn't any permission other than reading), ant the same goes to the "read" flag Am I wrong? Is there any workaround to make dovecot behave the way I'd liked? The config follows: login_executable: /usr/lib/dovecot/imap-login mail_extra_groups: mail mail_location: maildir:/home/%u/Maildir:INBOX=/inbox/mdir/%u mmap_disable: yes namespace: type: private separator: / location: maildir:~/Maildir:INBOX=/inbox/mdir/%u inbox: yes namespace: type: public separator: / prefix: Shared folders/ location: maildir:/inbox/shared:INDEX=/home/%u/Maildir/shared-settings/index:CONTROL=/home/%u/Maildir/shared-settings/control auth default: passdb: driver: passwd args: blocking=yes passdb: driver: shadow userdb: driver: passwd Cheers, Luis

1 0

[Dovecot] ANY password option
by Master Abi 16 Aug '07

16 Aug '07

Hi We sometimes migrate mailboxes over to one of our mail servers which has a very handy feature called 'ANY password'. This will allow access to a mailbox using the given username and disregard checking for the password. This is a useful feature for many reasons. Is there a possibility Dovecot could have such a a feature or is there a workaround already. Thanks Master

3 3

Re: [Dovecot] use of deliver from procmail advisable?
by Jerry Yeager 16 Aug '07

16 Aug '07

On Aug 15, 2007, at 5:00 AM, dovecot-request(a)dovecot.org wrote: > Message: 7 > Date: Wed, 15 Aug 2007 00:58:40 +0200 > From: martin f krafft <madduck(a)madduck.net> > Subject: Re: [Dovecot] use of deliver from procmail advisable? > To: dovecot(a)dovecot.org > Message-ID: <20070814225840.GA23721(a)piper.oerlikon.madduck.net> > Content-Type: text/plain; charset="us-ascii" > > also sprach Charles Marcus <CMarcus(a)Media-Brokers.com> > [2007.08.14.2028 +0200]: >>> Well, the whole point of sieve, I believe, is to make it >>> something that an >>> admin would want to let arbitrary users modify on their own >>> recognizance, >>> and the ability to specify arbitrary programs to run would be >>> just *asking* >>> to be hacked. >> >> Wouldn't a decent, secure alternative to procmail be sieve+amavisd- >> new? > > Except it's not really possible to make amavisd-new do per-user spam > filtering. And it's even more of a performance hog. > > -- > martin; (greetings from the heart of the sun.) > \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck > > "all language designers are arrogant. goes with the territory..." > -- larry wall > > spamtraps: madduck.bogus(a)madduck.net >

3 2

[Dovecot] Moving a mail between folders and post-processing ?
by Jerry Nicholls 16 Aug '07

16 Aug '07

Hi, Within Dovecot is there a way of spotting a change to a folder and running a post-processing script on the email that was moved ? I'm specifically after a way of seeing either an email entering or leaving a folder - preferably running a different post-process script depending on the direction. Essentially if an email enters or is moved out of a 'spam' folder I'd like to mark it as 'spam'/'ham' in the Bayesian filters respectively. Is there any such mechanism, or should I start looking at how to write a plugin to achieve this ? If it's the plugin route is there any good documentation on the plugin APIs etc ? Thanks, Jerry. -- Jerry Nicholls E: Jerry.Nicholls(a)zeninternet.co.uk Core Systems & Networks Manager W: http://www.zen.co.uk/ Zen Internet Ltd. T: 0845 058 9000 F: 0845 058 9005

3 2

Re: [Dovecot] deliver assertion failure
by Jerry Yeager 16 Aug '07

16 Aug '07

On Aug 15, 2007, at 5:00 PM, dovecot-request(a)dovecot.org wrote: > > > Message: 7 > Date: Thu, 16 Aug 2007 08:59:25 +1200 > From: Jasper Bryant-Greene <jbg(a)indy.net.nz> > Subject: [Dovecot] deliver assertion failure > To: dovecot(a)dovecot.org > Message-ID: <20070815205925.GA2808(a)port1.indy.net.nz> > Content-Type: text/plain; charset=us-ascii > > Deliver from latest 1.1 HG with sieve also from latest 1.1 HG is dying > with an assertion failure when it delivers to my mailbox. Other > mailboxes on the same system are unaffected, but I can read my mailbox > fine through IMAP. > > Dovecot and sieve were compiled with -march=nocona -pipe -ggdb > > I've commented out my entire sieve script and the problem still > occurs. > > file index-mail-headers.c: line 590 (index_mail_get_raw_headers): > assertion failed: (ret != -1) > - Last output repeated twice - > > Raw backtrace: > /usr/libexec/dovecot/deliver(i_syslog_panic_handler+0x2b) > [0x493125] > -> /usr/libexec/dovecot/deliver(i_fatal+0) [0x492b17] > -> /usr/libexec/dovecot/deliver [0x44f7cf] > -> /usr/libexec/dovecot/deliver(index_mail_get_first_header+0x30) > [0x44fb9b] > -> /usr/libexec/dovecot/deliver(mail_get_first_header+0x3a) > [0x47ca3d] > -> /usr/libexec/dovecot/deliver(deliver_get_return_address+0x21) > [0x41453b] > -> /usr/lib/dovecot/lda/lib90_cmusieve_plugin.so(cmu_sieve_run > +0x14b) [0x2b3687f194a1] > -> /usr/lib/dovecot/lda/lib90_cmusieve_plugin.so [0x2b3687f169ba] > -> /usr/libexec/dovecot/deliver(main+0x8dc) [0x415c4d] > -> /lib/libc.so.6(__libc_start_main+0xe3) [0x2b3687cf6533] > -> /usr/libexec/dovecot/deliver [0x4137a9] > > Jasper > > > ------------------------------ > > _______________________________________________ > dovecot mailing list > dovecot(a)dovecot.org > http://dovecot.org/cgi-bin/mailman/listinfo/dovecot > > End of dovecot Digest, Vol 52, Issue 56 > *************************************** I am getting the same error, the mail is still being delivered, but the system is generating an error message sent to the original sender The mail system <EMAIL ADDRESS HIDDEN>: Command died with signal 11: "/usr/local/libexec/dovecot/deliver" Reporting-MTA: dns; HIDDEN X-Postfix-Queue-ID: 7F344239D31 X-Postfix-Sender: rfc822; EMAIL ADDRESS HIDDEN Arrival-Date: Wed, 15 Aug 2007 15:53:32 -0400 (EDT) Final-Recipient: rfc822; EMAIL ADDRESS HIDDEN Action: failed Status: 5.3.0 Diagnostic-Code: x-unix; internal software error the mail logs show: to=<EMAIL ADDRESS HIDDEN>, relay=dovecot, delay=1.5, delays=0.01/0.02/0/1.5, dsn=5.3.0, status=bounced (Command died with signal 11: "/usr/local/libexec/dovecot/deliver") This did not happenr in v1.1 alpha 2, but is now appearing in 1.1 alpha 1.3 after a day or so of using the new version. Jerry Yeager

1 0

Re: [Dovecot] use of deliver from procmail advisable?
by Jerry Yeager 16 Aug '07

16 Aug '07

On Aug 15, 2007, at 5:00 PM, dovecot-request(a)dovecot.org wrote: > ------------------------------ > > Message: 3 > Date: Wed, 15 Aug 2007 18:08:58 +0200 > From: martin f krafft <madduck(a)madduck.net> > Subject: Re: [Dovecot] use of deliver from procmail advisable? > To: dovecot(a)dovecot.org > Message-ID: <20070815160858.GA22429(a)piper.oerlikon.madduck.net> > Content-Type: text/plain; charset="utf-8" > > also sprach Jerry Yeager <jerry(a)scene-naturally.dyndns.org> > [2007.08.15.1758 +0200]: >> a) Postfix milter to run ClamAv, eh something like this (for Linux >> fans) >> b) then use the regular Postfix <--> SpamAssassin <--> LDA (with >> sieve) >> setup (message routing via Postfix master.cf) so that individual >> users can >> set their own SA rules and vacation stuff. > > This is exactly how I used to have it but then the need for > a vacation autoresponse to the From: address (as opposed to > Return-Path) arose and I had to switch to procmail: > > http://dovecot.org/list/dovecot/2007-August/024766.html > > Before that, I was using spamc with --pipe-to, but always had a bad > feeling about that, since the manpage says: > > Note that there is a very slight chance mail will be lost here, > because if the fork-and-exec fails there?s no place to put the > mail message. > > and my message to SA-users on this was never answered[0]. > > 0. http://marc.info/?l=spamassassin-users&m=115185095923772&w=2 > > Now I am using procmail and at least now that failure will cause > postfix to defer a message. > > -- > martin; (greetings from the heart of the sun.) > \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck > > half a bee, philosophically, must ipso facto half not be. > but half the bee has got to be, vis-a-vis its entity. you see? > but can a bee be said to be or not to be an entire bee, > when half the bee is not a bee, due to some ancient injury? > -- monty python > > spamtraps: madduck.bogus(a)madduck.net >

1 0

[Dovecot] Errors from dovecot 1.1
by wenjie zheng 15 Aug '07

15 Aug '07

I downloaded and installed dovecot 1.1 nightly build yesterday. Here is a the errors I collected from the log file. dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=24 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension introduction for unknown id 2 dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=52 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension introduction for unknown id 2 dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=80 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension record updated without intro prefix dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=416 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension introduction for unknown id 0 dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=444 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension header update without intro prefix dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=528 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension introduction for unknown id 0 dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=556 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension header update without intro prefix dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=776 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension introduction for unknown id 2 dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=804 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension introduction for unknown id 3 dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=832 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension introduction for unknown id 2 dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=876 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension introduction for unknown id 3 dovecot: Aug 15 14:19:29 Error: IMAP(use@doamin): Sending log messages too fast, throttling.. dovecot: Aug 15 14:19:29 Error: child 8898 (imap) killed with signal 6 dovecot: Aug 15 14:19:29 Info: IMAP(use@doamin): Disconnected: Logged out bytes=36/238 dovecot: Aug 15 14:19:30 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=920 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension introduction for unknown id 2 dovecot: Aug 15 14:19:30 Error: IMAP(use@doamin): Log synchronization error at seq=7,offset=948 for /data2/mail/we/webmail.us/ji/jing/dovecot.index: Extension introduction for unknown id 2 dovecot: Aug 15 14:19:30 Error: IMAP(use@doamin): file mail-index-sync-keywords.c: line 285 (mail_index_sync_keywords): assertion failed: (rec->modify_type == MODIFY_REMOVE) dovecot: Aug 15 14:19:30 Error: IMAP(use@doamin): Raw backtrace: imap [0x80badb6] -> imap [0x80ba903] -> imap(mail_index_sync_keywords+0xee) [0x80ac3e6] -> imap(mail_index_sync_record+0x393) [0x80a0437] -> imap(mail_index_sync_map+0x208) [0x80a075c] -> imap(mail_index_map+0x89) [0x809b059] -> imap [0x8098907] -> imap [0x8098b39] -> imap(mail_index_open+0x133) [0x8098c73] -> imap(index_storage_mailbox_open+0x75) [0x8092e71] -> imap [0x806de18] -> imap [0x806dfb6] -> /usr/lib/dovecot/imap/lib10_quota_plugin.so [0x119de8] -> imap(mailbox_open+0x50) [0x80ae1ec] -> imap(_cmd_select_full+0x76) [0x805da4e] -> imap(cmd_select+0x10) [0x805dcbc] -> imap [0x805fa22] -> imap [0x805f941] -> imap [0x805fab1] -> imap(_client_input+0x56) [0x805fb6e] -> imap(io_loop_handler_run+0x100) [0x80bff0c] -> imap(io_loop_run+0x2d) [0x8066b21] -> imap(main+0x64) [0x8066518] -> /lib/tls/libc.so.6(__libc_start_main+0xda) [0x6db78a] -> imap(__fxstat64+0x71) [0x8059605] Thanks, Wenjie

2 1

[Dovecot] MANAGESIEVE patch v5 for dovecot 1.0.2
by Stephan Bosch 15 Aug '07

15 Aug '07

Hello dovecot users, I have finally updated the MANAGESIEVE patch to fix the currently known small problems with the protocol implementation. Also, I included a proxy implementation based on imap-proxy.c. This patch is designed for dovecot release 1.0.2 and it will not apply cleanly to the 1.1 versions yet. Change Log V5 ------------- - Applied patch by Uldis Pakuls to fix master_dump_settings bug - Added some compilation/installation info to the README - Moved README to source tree's root as README.managesieve - Fixed minor error handling bug in sieve_storage.c with respect to a missing root directory. - Now sieve capabilities are reported as they are specified by the implementing library and not in forced upper case. The sieve RFC now explicitly states that sieve capability identifiers are case-sensitive. This broke compatibility with SquirrelMail/Avelsieve. - Disabled ANONYMOUS login entirely until proper support is implemented. V4 claimed to do so as well, but in fact it only stopped announcing it. - Implemented managesieve-proxy. It is not so much a clean copy of imap-proxy, since the managesieve greeting is much more complex and requires parsing. Configuration is identical to imap-proxy. This seems to be a little under-documented however (http://wiki.dovecot.org/PasswordDatabase/ExtraFields) This patch still includes (yet another) instance of the CMU Sieve source, as explained in one of my previous e-mails (http://dovecot.org/list/dovecot/2006-July/015016.html) Current plans include merging src/lib-managesieve with src/lib-imap, updating the patch for dovecot-1.1 and fixing any problems you might find. The patch can be downloaded at: http://sinas.rename-it.nl/~sirius/dovecot-1.0.2-MANAGESIEVE-v5.diff.gz The README.managesieve is located in the root of the dovecot source tree after applying the patch. Have fun testing the patch. Notify me when there are problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl IRC: Freenode, #dovecot, S[r]us

5 13

[Dovecot] Dovecot deliver + sieve + postfix virtual + mysql ?
by Radek Slavicinsky 15 Aug '07

15 Aug '07

Hey there guys. I have successful postfix + mysql + sagator + clamav + spamassassin + dovecot setup (it was a really crazy month full of tweaking :]) and the only thing i miss is some per maildir specific filtering. i decided to use sieve. everything is fine except that dovecot's deliver process doesn't see the actual .dovecot.sieve file with filtering rules in the root of a maildir. description of the situation follows: from /var/log/dovecot.log: deliver(support{the_at_symbol}support.etnetera.cz): "2007-08-15 13:32:11 "Error: userdb(support{the_at_symbol}support.etnetera.cz) didn't return a home directory or sieve script location, can't find it deliver(support{the_at_symbol}support.etnetera.cz): "2007-08-15 13:32:11 "Info: msgid=<200708151330.22021.radek.slavicinsky{the_at_symbol}etnetera.cz>: saved mail to INBOX /etc/dovecot/dovecot.conf: protocols = imap imaps pop3 pop3s listen = * disable_plaintext_auth = no shutdown_clients = yes log_path = /var/log/dovecot.log log_timestamp = "%Y-%m-%d %H:%M:%S " ssl_cert_file = /etc/certs/sponka.etnetera.cz.crt ssl_key_file = /etc/certs/sponka.etnetera.cz.key ssl_ca_file = /etc/certs/CA.crt login_process_size = 64 login_processes_count = 32 login_max_processes_count = 256 login_max_connections = 512 mail_location = maildir:/srv/vmail/domains/%d/%n/ #mail_location = maildir:/ namespace private { separator = . prefix = INBOX. inbox = yes } namespace private { separator = . prefix = inbox = yes hidden = yes } mail_extra_groups = vmail verbose_proctitle = yes mbox_read_locks = fcntl mbox_write_locks = fcntl protocol imap { } protocol pop3 { pop3_uidl_format = UID%u-%v } protocol lda { hostname = sponka.etnetera.cz postmaster_address = postmaster{the_at_symbol}etnetera.cz auth_socket_path = /var/run/dovecot/auth-master mail_plugins = cmusieve } auth default { mechanisms = plain login digest-md5 cram-md5 passdb sql { args = /etc/dovecot/dovecot-sql.conf } userdb sql { args = /etc/dovecot/dovecot-sql.conf } user = dovecot-auth socket listen { client { path = /var/spool/postfix/private/auth mode = 0666 user = postfix group = postfix } master { path = /var/run/dovecot/auth-master mode = 0600 user = vmail group = vmail } } } dict { } plugin { } /etc/dovecot/dovecot-sql.conf: driver = mysql default_pass_scheme = PLAIN connect = host=127.0.0.1 dbname=postfix user=postfix password=averysecretpass password_query = SELECT password FROM mailbox WHERE username = '%u' AND active = '1' user_query = SELECT maildir, 65500 AS uid, 65500 AS gid FROM mailbox WHERE username = '%u' AND active = '1' the user_query gives: mysql> SELECT maildir, 65500 AS uid, 65500 AS gid FROM mailbox WHERE username = 'radek.slavicinsky(a)etnetera.cz' AND active = '1'; +--------------------------------+-------+-------+ | maildir | uid | gid | +--------------------------------+-------+-------+ | etnetera.cz/radek.slavicinsky/ | 65500 | 65500 | +--------------------------------+-------+-------+ 1 row in set (0.00 sec) the sieve rules file # ls /srv/vmail/domains/support.etnetera.cz/support/.dovecot.sieve -lha -rw-r--r-- 1 vmail vmail 957 Aug 15 13:30 /srv/vmail/domains/support.etnetera.cz/support/.dovecot.sieve i think there should be some specific settings for the cmusieve plugin, but i didnt find much docs about that thx for any help ;] blue4 :p

3 4