January 2013 - dovecot

[Dovecot] problems with sieve
by Carsten Laun-De Lellis 10 Jan '13

10 Jan '13

Hi all I am running a simple mail server on ubuntu 12.04LTS with postfix 2.9.3 and dovecot 2.1.10. Since this morning sieve doesn't work anymore. I changed the sieve script forth and back but sieve is not working. I also replaced the sieve file with the backup, but no success. But I can't any error messages in the log files indicating any problem with sieve. The only thing I found is: Jan 10 00:03:26 vmd187 dovecot: lda(carsten.delellis(a)delellis.net): sieve: msgid=<12155505.mmailer335539222(a)fritz.box>: stored mail into mailbox 'Fritz!Box' -- with working sieve Jan 10 13:52:29 vmd187 dovecot: lda(carsten.delellis(a)delellis.net): msgid=<1898328495.2554803.1357821905269.JavaMail.app(a)ela4-app2316.prod>: saved mail to INBOX -- with sieve not working As you can see that after dovecot: lda(carsten.delellis(a)delellis.net): the sieve tag is missing. I have also attached my settings from 90-sieve.conf from dovecot configuration. ## ## Settings for the Sieve interpreter ## # Do not forget to enable the Sieve plugin in 15-lda.conf and 20-lmtp.conf # by adding it to the respective mail_plugins= settings. plugin { # The path to the user's main active script. # sieve = ~/.dovecot.sieve sieve = /vmail/%d/%n/dovecot.sieve # A path to a global sieve script file, which gets executed ONLY # if user's private Sieve script doesn't exist. Be sure to # pre-compile this script manually using the sievec command line # tool. sieve_global_path = /var/lib/dovecot/sieve/default.sieve # Directory for :personal include scripts for the include extension. # sieve_dir = ~/sieve sieve_dir = /vmail/%d/%n # Directory for :global include scripts for the include extension. sieve_global_dir = /var/lib/dovecot/sieve # Which Sieve language extensions are available to users. By default, # all supported extensions are available, except for deprecated # extensions or those that are still under development. Some system # administrators may want to disable certain Sieve extensions or # enable those that are not available by default. This setting can # use '+' and '-' to specify differences relative to the default. # For example `sieve_extensions = +imapflags' will enable the # deprecated imapflags extension in addition to all extensions # enabled by default. #sieve_extensions = +notify +imapflags # The separator that is expected between the :user and :detail # address parts introduced by the subaddress extension. This may # also be a sequence of characters (e.g. '--'). The current # implementation looks for the separator from the left of the # localpart and uses the first one encountered. The :user part is # left of the separator and the :detail part is right. This setting # is also used by Dovecot's LMTP service. recipient_delimiter = + # The maximum size of a Sieve script. The compiler will refuse to # compile any script larger than this limit. #sieve_max_script_size = 1M # The maximum number of actions that can be performed during a single # script execution. #sieve_max_actions = 32 # The maximum number of redirect actions that can be performed during # a single script execution. #sieve_max_redirects = 4 # The maximum number of personal Sieve scripts a single user can have. # (Currently only relevant for ManageSieve) #sieve_quota_max_scripts = 0 # The maximum amount of disk storage a single user's scripts may occupy. # (Currently only relevant for ManageSieve) #sieve_quota_max_storage = 0 } And also you can see that sieve is listening on port 4190 and managesieve on 2000 > lsof -i :4190 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME dovecot 2503 root 15u IPv4 14101 0t0 TCP *:sieve (LISTEN) dovecot 2503 root 16u IPv6 14102 0t0 TCP *:sieve (LISTEN) lsof -i :2000 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME dovecot 2503 root 17u IPv4 14103 0t0 TCP *:cisco-sccp (LISTEN) dovecot 2503 root 18u IPv6 14104 0t0 TCP *:cisco-sccp (LISTEN) I would appreciate any hints. Regards, Carsten Laun-De Lellis Hauptstrasse 13 D-67705 Trippstadt Phone: +49 6306 992140 Fax: +49 6306 992142 Mobile: +49 151 27530865 email: carsten.delellis(a)delellis.net http://www.linkedin.com/in/carstenlaundelellis

2 1

[Dovecot] Confused about "Authentication Mechanism" and "Password Schemes"
by Thomas Pries 10 Jan '13

10 Jan '13

Hi, I am currently setting up a Mailserver and decided to use Dovecot as IMAP/POP3-Server. I read the wiki an thought about how to transmit and store the passwords (I want to use a MySQL-database). I want to use encrypted transmission and encrypted storage. The wiki says: "If you want to use only one non-plaintext mechanism, you can store the passwords using the mechanism's own password scheme. " Ok, one secure mechanism is acceptable in my scenario and the wiki gives a list of supported authentication mechanisms and a list of supported password schemes. But I am missing the relation between the two lists, which mechanism expects which storage scheme? Did I overlooked any easy answer (other then "read the RFCs"). Best Regards Thomas

2 1

[Dovecot] v2.2.beta1 released
by Timo Sirainen 10 Jan '13

10 Jan '13

http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta1.tar.gz http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta1.tar.gz.sig Lots of fixes since 2.2.alpha1, especially related to dsync. Also dsync now supports syncing private message flags when INDEXPVT is used. Here's again the list of all the major changes in v2.2: * When creating home directories, the permissions are copied from the parent directory if it has setgid-bit set. For full details, see http://wiki2.dovecot.org/SharedMailboxes/Permissions * "doveadm auth" command was renamed to "doveadm auth test" * IMAP: ID command now advertises server name as Dovecot by default. It was already trivial to guess this from command replies. * dovecot.index.cache files can be safely accessed only by v2.1.11+. Older versions may think they're corrupted and delete them. + Implemented IMAP MOVE and BINARY extensions + Implemented IMAP CATENATE, URLAUTH and URLAUTH=BINARY extensions (by Stephan Bosch). + Implemented IMAP NOTIFY extension. Requires mailbox_list_index=yes to be enabled. + Redesigned and rewritten dsync. The new design makes the syncing faster, more reliable and more featureful. The new dsync protocol isn't backwards compatible with old dsync versions (but is designed to be forwards compatible with future versions). + All mailbox formats now support per-user message flags for shared mailboxes by using a private index. It can be enabled by adding :INDEXPVT=<path> to mail location. This should be used instead of :INDEX also for Maildir/mbox to improve performance. + Improved mailbox list indexes. They should be usable now, although still disabled by default. + Added LAYOUT=index. The mailbox directories are created using their GUIDs in the filesystem, while the actual GUID <-> name mapping exists only in the index. + LMTP proxy: Implemented XCLIENT extension for passing remote IP address through proxy.

2 4

[Dovecot] Mark Crispin - RIP
by Robert Moskowitz 09 Jan '13

09 Jan '13

'Father' of the IMAP protocol. Died Dec 28. http://en.wikipedia.org/wiki/Mark_Crispin Had a TOPS-20 in his basement that did a great job of keeping the house warm in the cool months (I remember one BAR bof where he extoled the benefits of this form of home heating).

3 2

[Dovecot] Squat FTS plugin not kicking in
by Frerich Raabe 09 Jan '13

09 Jan '13

Hi, I'm running Dovecot 2.1.12 on FreeBSD. I configured Dovecot to use the Squat plugin to provide faster full-text searches. The output of 'dovecot -n' is attached to this mail. However, I just noticed that this plugin doesn't seem to kick in. A raw telnet session seems to confirm this: [..] . SEARCH BODY abcdefg * OK Searched 57% of the mailbox, ETA 0:06 * SEARCH 3425 6254 14710 . OK Search completed (17.262 secs). . SEARCH BODY abcdefg * OK Searched 63% of the mailbox, ETA 0:05 * SEARCH 3425 6254 14710 . OK Search completed (18.651 secs). [..] A SEARCH BODY command doesn't create the dovecot.index.search or dovecot.index.search.uids files mentioned on http://wiki2.dovecot.org/Plugins/FTS/Squat . Also, two subsequent SEARCH BODY invocations don't seem to be any different as far as search time goes. I checked the logs but couldn't see anything which is related, except: Jan 8 21:36:10 imap2 dovecot: indexer-worker(frerich): Indexed 0 messages in INBOX Does anybody have some idea how to get more logging out of index-worker, or whether there's a flaw in my configuration? -- Frerich Raabe - raabe(a)froglogic.com www.froglogic.com - Multi-Platform GUI Testing

1 1

Re: [Dovecot] Migrating mailboxes - SOLVED
by Odhiambo Washington 09 Jan '13

09 Jan '13

On Wed, Jan 9, 2013 at 5:36 PM, Eduardo M KALINOWSKI < eduardo(a)kalinowski.com.br> wrote: > On Qua, 09 Jan 2013, Odhiambo Washington wrote: > >> See the output below >> >> [root@mail home]# cd johndoe/ >> [root@mail johndoe]# du -h mail/ >> 32K mail/.imap/Sent >> 40K mail/.imap/Trash >> 32K mail/.imap/Drafts >> 176K mail/.imap/INBOX >> 284K mail/.imap >> 88M mail/ >> > > Clearly most of the data (probably the emails) is not under the .imap > subdir, which is exactly what you didn't show us. It's probably mbox files. > > Sure! Looking further, I have found the mboxes and I am now able to migrate! Thanks for being my "third eye". That version of Dovecot had shocked my senses senseless!! -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ I can't hear you -- I'm using the scrambler.

1 0

[Dovecot] Migrating mailboxes
by Odhiambo Washington 09 Jan '13

09 Jan '13

Hello everyone and Happy 2013! I have a situation -- the first ever I have come across -- which I don't understand. A friend was/is running Postfix and Dovecot - with default configs - nothing was ever changed :-) [root@mail home]# dovecot --version 0.99.11 Anyway, he had a problem with a user mailbox which I wasn't able to diagnose and fix easily. maillog showed: Jan 9 16:11:29 mail imap-login: Login: userx [::ffff:127.0.0.1] Jan 9 16:11:29 mail imap(userx): file lib.c: line 37 (nearest_power): assertion failed: (num <= ((size_t)1 << (BITS_IN_SIZE_T-1))) Jan 9 16:11:29 mail dovecot: child 25217 (imap) killed with signal 6 Jan 9 16:12:03 mail imap-login: Login: userx [::ffff:127.0.0.1] Jan 9 16:12:03 mail imap(userx): file lib.c: line 37 (nearest_power): assertion failed: (num <= ((size_t)1 << (BITS_IN_SIZE_T-1))) Jan 9 16:12:03 mail dovecot: child 25229 (imap) killed with signal 6 Jan 9 16:13:15 mail pop3-login: Login: userx [::ffff:192.168.0.55] Jan 9 16:13:15 mail pop3(userx): file lib.c: line 37 (nearest_power): assertion failed: (num <= ((size_t)1 << (BITS_IN_SIZE_T-1))) My aim is not to fix the above. I have reconfigured both Postfix and Dovecot to use Maildir now and things are fine (not securitywise, but I don't care about that) for now. However, I'd like to migrate old mail for some users, but I don't know how to go about this, given the mailbox format, which I don't understand: Here is what a typical one looks like: [root@mail home]# ls -al johndoe/mail/.imap/ total 24 drwx------ 6 johndoe users 4096 May 27 2010 . drwx------ 3 johndoe users 4096 May 27 2010 .. drwx------ 2 johndoe users 4096 May 27 2010 Drafts drwx------ 2 johndoe users 4096 Jan 9 15:46 INBOX drwx------ 2 johndoe users 4096 May 27 2010 Sent drwx------ 2 johndoe users 4096 May 27 2010 Trash [root@mail home]# ls -al johndoe/mail/.imap/INBOX/ total 180 drwx------ 2 johndoe users 4096 Jan 9 15:46 . drwx------ 6 johndoe users 4096 May 27 2010 .. -rw------- 1 johndoe users 5 Dec 18 2007 .customflags -rw------- 1 johndoe users 10272 Jan 9 15:46 .imap.index -rw------- 1 johndoe users 132774 Jan 9 11:27 .imap.index.data -rw------- 1 johndoe users 5136 Sep 26 2011 .imap.index.log -rw------- 1 johndoe users 9404 Jan 8 18:44 .imap.index.tree [root@mail home]# ls -al johndoe/mail/.imap/Sent/ total 36 drwx------ 2 johndoe users 4096 May 27 2010 . drwx------ 6 johndoe users 4096 May 27 2010 .. -rw------- 1 johndoe users 5 May 27 2010 .customflags -rw------- 1 johndoe users 1608 May 27 2010 .imap.index -rw------- 1 johndoe users 10264 May 27 2010 .imap.index.data -rw------- 1 johndoe users 2576 May 27 2010 .imap.index.log -rw------- 1 johndoe users 1556 May 27 2010 .imap.index.tree [root@mail home]# ls -al johndoe/mail/.imap/Drafts/ total 36 drwx------ 2 johndoe users 4096 May 27 2010 . drwx------ 6 johndoe users 4096 May 27 2010 .. -rw------- 1 johndoe users 5 May 27 2010 .customflags -rw------- 1 johndoe users 1608 May 27 2010 .imap.index -rw------- 1 johndoe users 10264 May 27 2010 .imap.index.data -rw------- 1 johndoe users 2576 May 27 2010 .imap.index.log -rw------- 1 johndoe users 1556 May 27 2010 .imap.index.tree [root@mail home]# ls -al johndoe/mail/.imap/Trash/ total 44 drwx------ 2 johndoe users 4096 May 27 2010 . drwx------ 6 johndoe users 4096 May 27 2010 .. -rw------- 1 johndoe users 5 May 27 2010 .customflags -rw------- 1 johndoe users 1608 May 27 2010 .imap.index -rw------- 1 johndoe users 17950 May 27 2010 .imap.index.data -rw------- 1 johndoe users 2576 May 27 2010 .imap.index.log -rw------- 1 johndoe users 1556 May 27 2010 .imap.index.tree How can I migrate these mails into /home/johndoe/Maildir/ ?? They don't seem like mbox to me so mb2md.pl doesn't seem to apply here.. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ I can't hear you -- I'm using the scrambler.

5 9

[Dovecot] Dsync didn't updates automatically
by Breno Moreira 08 Jan '13

08 Jan '13

Hi, I'm trying to use the Dsync cluster feature in a simple setup, without director, but I'm having some troubles. First of all, I want to know if this functionality syncs the mailbox when the user receive a mail or only when the dovecot starts? Reading the Dovecot mailing list and the design description for a dsync-replicated Dovecot cluster, I understood that it should sync every time a new mail arrives, but it isn't happening in my system. So, can I do this update automatically? If yes, why is it not working properly? Maybe is my configuration files or maybe I'm confusing the capability of this feature. I'm using Dovecot 2.1.7 included in the Debian Wheezy, with virtual users in a MySQL database, Moreover, I have the following configuration: mail_plugins = $mail_plugins notify replication service aggregator { # give enough permissions for mail processes fifo_listener replication-notify-fifo { user = vmail #mode = 0666 } unix_listener replication-notify { user = vmail #mode = 0666 } } service replicator { # start replication at startup process_min_avail = 1 } plugin { # host1 replicates to host2 #mail_replica = remote:vmail at 10.127.0.2 # host2 replicates to host1 mail_replica = remote:vmail@10.127.0.5 } dsync_remote_cmd = ssh -l vmail %{host} doveadm dsync-server -u%u -l%{lock_timeout} -n%{namespace} service doveadm { # if you're using a single virtual user, set this to # start ssh as vmail (not root) user = vmail } service config { unix_listener config { user = vmail } } The vmail user has rsa id's in both servers, so it can do ssh connections without asking for password. I appreciate your help. Best Regards, -- --------------------------------------------------------------------- Breno Moreira "I have no idols. I admire work, dedication and competence." Ayrton Senna

2 6

[Dovecot] dovecot-antispam-plugin compile error
by Bradley Giesbrecht 08 Jan '13

08 Jan '13

$ hg --cwd ./work/dovecot-antispam-plugin-50 glog -l3 --style compact @ 50[tip] 0319240072d8 2012-12-20 03:56 +0200 Eugene Paskevich <eugene(a)raptor.kiev.ua> | Made use of new DOVECOT_ABI_VERSION macro. ... $ configure; make Compiling signature-log.c (plugin)... signature-log.c:122: error: too many arguments to function ‘dict_init’ ... Reverting src/signature-log.c from r49 to r30 allows make to succeed again. Regards, Bradley Giesbrecht (pixilla)

1 0

[Dovecot] Question about supporting EAI in Devecot
by Abdulrahman I. ALGhadir 08 Jan '13

08 Jan '13

Dear all, I would like to ask the staff of Devecot if they are planning (working) or supporting EAI (http://tools.ietf.org/wg/eai/) in the future versions? If there is a working progress on it can anybody guide me to it? Thank you, AbdulRahman, ----------------------------------------------------------------------------------- Disclaimer: This message and its attachment, if any, are confidential and may contain legally privileged information. If you are not the intended recipient, please contact the sender immediately and delete this message and its attachment, if any, from your system. You should not copy this message or disclose its contents to any other person or use it for any purpose. Statements and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of the Communications and Information Technology Commission (CITC). CITC accepts no liability for damage caused by this email.

2 3