- dovecot - dovecot.org

[Dovecot] Quota with Dict + SQL not updating
by Michael 01 Jan '10

01 Jan '10

Hello all, I have a Dovecot server deployed with a MySQL back end. If the user logs in and there is no quota set for them in table 'quota', the system will automatically inset a line with their username and current messages/storage. However after this it fails to update the information when to reflect new messages coming to their inbox after the original insert of the information. It will only update the information when a user deletes a message. Why is it not updating this information every time their mail is checked with IMAP? Cheers, Michael

2 2

[Dovecot] Oracle SQL driver
by Alexander Bukharov 31 Dec '09

31 Dec '09

Hi all. Recently I was looking for an IMAP-server with Oracle support and unfortunatelly I couldn't find one. It was a surprise for me but there is no such functionality at all. So I've chosen an IMAP-server with most flexible and convinient architecture that was Dovecot-1.2.9 and written a driver for Oracle RDBMS support. I used Oracle Pro*C so a Pro*C preprocessor is needed to compile the driver. There is a lot of logging there that should be removed. It would be great if you consider to include this driver to mainstream so Dovecot will be the first IMAP server supporting Oracle as auth backend. All related files are attached. Cheers.

2 2

[Dovecot] A Dovecot Sieve spam filter question.
by aja-lists＠tni.org 31 Dec '09

31 Dec '09

Hi, I'd like to make a filtering threshold for users to let them deal with spamassassin spam-level starred < 8 themselves, but spam-level starred higher than 8 should be discarded how can one do that with the "anyof" option ? the following doesn't work with a test email with "gtube", which scores > 999 : # require "fileinto"; if header :matches "X-Spam-Level" "\*\*\*\*\*\*" { fileinto "discard"; } and I think it would be nice to have not so many lines in the globalsieverc file. TIA, Regards, Adrian

5 11

[Dovecot] configure optimization
by Luigi Rosa 31 Dec '09

31 Dec '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Given a server with MySQL userdb/passwd and maildir storage, excluding unused storages and authentications in configure options does save some memory and/or speed or is it worthless? I mean, is there a performance difference between this two versions of configure parameters or is just a waste of time to exclude what is not used? ./configure --with-mysql --without-ssl --sysconfdir=/etc --localstatedir=/var ./configure --with-mysql --without-ssl --with-storages=maildir - --sysconfdir=/etc --localstatedir=/var --without-passwd --without-nss - --without-passwd-file --without-shadow --without-pam --without-ssl Thank you. Ciao, luigi - -- / +--[Luigi Rosa]-- \ I told the doctor I broke my leg in two places. He told me to quit going to those places. --Henny Youngman -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAks7YWkACgkQ3kWu7Tfl6ZReewCgw97USlBGkggJre49cGp/cgsd M/sAniVsEOISC2YKKXbivTKN//JwnZhs =GEk+ -----END PGP SIGNATURE-----

2 2

[Dovecot] Pigeonhole Sieve IMAP flag question
by Julian Cowley 31 Dec '09

31 Dec '09

Hello, Here is a small script that I've been running to test a problem I've been seeing. Shouldn't this result in the mail being delivered to the inbox as a new message (ie. without the \Seen flag)? require "imap4flags"; addflag "\\Seen"; removeflag "\\Seen"; Every message gets delivered to the inbox as though it's already been read. Using Dovecot 1.2.9 and Pigeonhole Sieve 0.1.14.

3 4

[Dovecot] Hostname setting defaults
by Timo Sirainen 30 Dec '09

30 Dec '09

Any thoughts about the following? hostname setting currently defaults to system's host name, without the domain part. It's used (in v2.0): - dovecot-lda (new deliver): If -a parameter isn't specified and there's no Envelope-To: header, the destination address is generated as <username>@<hostname setting> - lda/lmtp: In generated Message-Id: headers ("dovecot-stuff@<hostname>") for rejects, vacation, etc. - lda/lmtp: in reject messages as part of MIME boundary, and also in "Reporting-UA: <hostname>; Dovecot mail delivery agent" header. - lmtp: In the protocol, e.g. "220 <hostname> Dovecot ready" or "421 4.4.2 <hostname> Disconnected for inactivity" - lmtp: In added Received: header Seems pretty clear to me that it should be host.domain.org, not just host. So I suppose I'll change that default. The other thing is postmaster_address. That's accidentally been postmaster(a)example.com in dovecot-example.conf and uncommented. So who knows how many installations have their postmaster address set to that.. I'm thinking of just commenting it out in next v1.2 release so admins needs to change that. But for v2.0 maybe there could be a good default for postmaster_address? "postmaster@<hostname setting>" I think? Because it's postmaster(a)host.domain.org instead of postmaster(a)domain.org, it might not be correct in most installations, but I'm thinking that maybe it's safer. Someone trying out Dovecot on testbox.biguni.edu probably doesn't want bounces going to postmaster(a)biguni.edu..

1 0

[Dovecot] dovecot-shared
by Frank Cusack 30 Dec '09

30 Dec '09

I'm confused about dovecot-shared. If the file exists, \SEEN flags are NOT shared? So if dovecot-shared exists, flags are actually private. The doc seems clear on this (albeit not worded very well). I only question it because intuitively you would think the opposite. If backwards compatibility is the reason for this reverse behavior, the file should have been named dovecot-private-flags. In fact that's a great name to stick a list of flags (one-per-line) that are private. -frnak

2 6

[Dovecot] Issue Authenticating to a new dovecot-postfix installation
by Anthony Nedland 30 Dec '09

30 Dec '09

I have installed dovecot-postfix and postfixadmin on an Ubuntu 9.10 machine. The userdb and passdb are both mysql. If I set up a user in postfixadmin they are able to send. I can successfully telnet into the server remotely by name on 110 and 25. I'm not looking for any authentication encryption/ssl any of that, just POP3/SMTP. When I telnet into 110 I can enter a username with user [username] then when I do pass [password] I get -ERR Authentication failed. I know the user info is correct. When I set up an account in Outlook Express I get "There was a problem logging onto your mail server. Your Password was rejected:" Also saying -ERR Authentication failed.'. (0x800ccc90,0x800ccc92) So basically the same thing. I can attach the tutorial I used in as a .doc if that would help. Anyway, here is my relevant info I think. -- -- -- Version 1.1.11 -------------------------------------------------------------- ---------------------------------------------------------------- ----------------------------------------------------------------- dovecot-sql.conf GREP driver = mysql connect = host=localhost dbname=postfix user=postfix password=password default_pass_scheme = PLAIN user_query = SELECT '/var/vmail/%d/%n' as home, 'maildir:/var/vmail/%d/%n' as mail, 150 AS uis, 8 AS gid, concat(dirsize:storage=',quota) AS quota FROM mailbox WHERE username = '%u' AND active = 1 password_query = SELECT username as user, password, '/var/vmail/%d/%n' as userdb_home,'maildir:/var/vmail/%d/%n' as userdb_mail, 150 as userdb_uid, 8 as userdb_gid FROM mailbox WHERE username = '%u' AND active = 1 -------------------------------------------------------------- ------------------------------------------------------------- ------------------------------------------------------------- root@mail:/etc/dovecot# dovecot -n # 1.1.11: /etc/dovecot/dovecot.conf Error: Error in configuration file /etc/dovecot/dovecot.conf line 1076: Unknown section type (section changed in /etc/dovecot/dovecot.conf at line 1038) Fatal: Invalid configuration in /etc/dovecot/dovecot.conf Starting line 1076---> master { # Master socket provides access to userdb information. It's typically # used to give Dovecot's local delivery agent access to userdb so it # can find mailbox locations. path = /var/run/dovecot/auth-master mode = 0660 # Default user/group is the one who started dovecot-auth (root) user = vmail group = mail } # SQL database <doc/wiki/AuthDatabase.SQL.txt> userdb sql { # Path for SQL configuration file args = /etc/dovecot/dovecot-sql.conf Line 138 --> } I don't understand the issue with these lines. They refer to dovecot.conf though. The config file is clearly dovecot-postfix.conf so I am confused as to why the other matters. I had noticed changes only when I changed dovecot.conf though. (In dovecot -n output) --

1 0

Re: [Dovecot] Retrieve Physical Message Filename
by Tony Rutherford 30 Dec '09

30 Dec '09

Thanks for the reply. I won't be changing any files, or even accessing them, i'll simply be passing the filename along to "another system". I'm not allowed to change this other system or any of its interfaces. The other system has been in place and is "off limits" as far as changes go (I'm told). To make it simple, this other system needs to be notified of any flag changes on emails. So, when we detect a flag change (in our plugin), we need to pass the message filename along to this other system. I hope this makes sense...and again...i'm not justifying the need for it, but I have to play the hand i'm dealt....Tony RutherfordSoftware EngineerBlueTie Inc.arutherford(a)bluetie.com(585) 586-2000 x1040-----Original Message-----From: "Timo Sirainen" [tss(a)iki.fi]Date: 12/29/2009 04:02 PMTo: "Tony Rutherford" CC: dovecot(a)dovecot.orgSubject: Re: [Dovecot] Retrieve Physical Message FilenameOn Tue, 2009-12-29 at 15:50 -0500, Tony Rutherford wrote: > Hi,Using Dovecot 1.2.9 with Maildir and Layout=FS.In a plugin, i'm > overriding "update_flags":void my_mail_update_flags(struct mail > *_mail, enum modify_type modify_type, enum mail_flags flags)For this > email which is having its flags updated, I need to retrieve the > physical filename of the message. I see where > using:mail_get_special(_mail, MAIL_FETCH_UIDL_FILE_NAME, &fname);...I > can retrieve part of the filename, but without the ":2" and the flags > part.Is there a method I can use to get the whole filename (without > having to reassemble it myself). I've looked around, and I'm guessing > it exists, but I don't see it offhand. The problem is that by the time you're trying to access the file, its flags may have already changed, which also means its filename could have changed. So even if you got it, your code would probably randomly fail. What exactly are you going to do with the filename? Maybe you should instead be opening the file with mail_get_stream() and doing something with the fd. This message is intended solely for the individual(s) to whom it is addressed. If you are not the intended recipient, any dissemination or copying is strictly prohibited. If you believe you received this message in error, please notify the sender and delete from your system. Thank you.

3 2

[Dovecot] Using Dovecot deliver with Postfix
by Tobias Lang 30 Dec '09

30 Dec '09

Hello, while installing Dovecot sieve, I am not able to deliver email for root. The strange thing is, that mails to ordinary users get delivered. And no, I do not use virtual mail, just ordinary unix accounts with an entry to passwd / shadow. Also before switching from Postfix deliver to Dovecot deliver, everything worked fine. Current versions for dovecot and postfix are: dovecot-1.2.8 postfix-2.6.5 Anybody an idea, where I misconfigured something? Thanks in advance Tobi dovecot.log (Dovecot daemon) ------------------------------------------------------------------------------------------------------------------------------------- Dec 25 13:15:01 deliver(root): Error: chdir(/root) failed: Permission denied Dec 25 13:15:01 deliver(root): Error: stat(/root/Maildir) failed: Permission denied Dec 25 13:15:01 deliver(root): Error: stat(/root/Maildir/tmp) failed: Permission denied (euid=65534(nobody) egid=65533(nobody) missing +x perm: /root) ------------------------------------------------------------------------------------------------------------------------------------- mail.log (Postfix daemon) ------------------------------------------------------------------------------------------------------------------------------------- Dec 25 13:15:01 h636004 postfix/pickup[9007]: ABD64208163: uid=0 from=<root> Dec 25 13:15:01 h636004 postfix/cleanup[9073]: ABD64208163: message-id=<20091225121501.ABD64208163(a)DOMAIN.net> Dec 25 13:15:01 h636004 postfix/qmgr[9006]: ABD64208163: from=<root(a)DOMAIN.net>, size=629, nrcpt=1 (queue active) Dec 25 13:15:01 h636004 postfix/local[9075]: ABD64208163: to=<tobi(a)DOMAIN.net>, orig_to=<root>, relay=local, delay=0.26, delays=0.14/0.01/0/0.12, dsn=2.0.0, status=sent (delivered to command: /usr/local/libexec/dovecot/deliver) Dec 25 13:15:01 h636004 postfix/local[9075]: ABD64208163: to=<root(a)DOMAIN.net>, orig_to=<root>, relay=local, delay=0.36, delays=0.14/0.01/0/0.21, dsn=4.3.0, status=deferred (temporary failure) ------------------------------------------------------------------------------------------------------------------------------------- Here is an excerpt from my dovecot.conf: dovecot.conf: ------------------------------------------------------------------------------------------------------------------------------------- protocol lda { postmaster_address = postmaster@DOMAIN #mail_plugins = sieve # Disabled to fix deliver issue } mail_location = maildir:%h/Maildir auth default { mechanisms = plain login passdb pam { args = * } userdb passwd { } socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } -------------------------------------------------------------------------------------------------------------------------------------

2 2

[Dovecot] 1.2.9 imap crash with backtrace
by Ralf Hildebrandt 30 Dec '09

30 Dec '09

I got about 20 (!) of these today GNU gdb (GDB) 7.0-debian Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/local/libexec/dovecot/imap...done. Reading symbols from /lib/i686/cmov/libdl.so.2...Reading symbols from /usr/lib/debug/lib/i686/cmov/libdl-2.10.2.so...done. (no debugging symbols found)...done. Loaded symbols for /lib/i686/cmov/libdl.so.2 Reading symbols from /lib/i686/cmov/librt.so.1...Reading symbols from /usr/lib/debug/lib/i686/cmov/librt-2.10.2.so...done. (no debugging symbols found)...done. Loaded symbols for /lib/i686/cmov/librt.so.1 Reading symbols from /lib/i686/cmov/libc.so.6...Reading symbols from /usr/lib/debug/lib/i686/cmov/libc-2.10.2.so...done. (no debugging symbols found)...done. Loaded symbols for /lib/i686/cmov/libc.so.6 Reading symbols from /lib/ld-linux.so.2...Reading symbols from /usr/lib/debug/lib/ld-2.10.2.so...done. (no debugging symbols found)...done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /lib/i686/cmov/libpthread.so.0...Reading symbols from /usr/lib/debug/lib/i686/cmov/libpthread-2.10.2.so...done. (no debugging symbols found)...done. Loaded symbols for /lib/i686/cmov/libpthread.so.0 Reading symbols from /usr/local/lib/dovecot/imap/lib10_quota_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib10_quota_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib11_imap_quota_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib11_imap_quota_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib11_trash_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib11_trash_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib20_autocreate_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib20_autocreate_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib20_fts_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib20_fts_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib20_mail_log_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib20_mail_log_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib20_zlib_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib20_zlib_plugin.so Reading symbols from /usr/lib/libz.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libz.so.1 Reading symbols from /lib/libbz2.so.1.0...(no debugging symbols found)...done. Loaded symbols for /lib/libbz2.so.1.0 Reading symbols from /usr/local/lib/dovecot/imap/lib21_fts_squat_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib21_fts_squat_plugin.so Reading symbols from /lib/libgcc_s.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libgcc_s.so.1 Core was generated by `imap [ctXXXX 141.42.26.107]'. Program terminated with signal 6, Aborted. #0 0xb78aa424 in __kernel_vsyscall () #0 0xb78aa424 in __kernel_vsyscall () No symbol table info available. #1 0xb77728e0 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 resultvar = <value optimized out> pid = -1215778828 selftid = 32050 #2 0xb7775e15 in *__GI_abort () at abort.c:88 act = {__sigaction_handler = {sa_handler = 0x9bb5848, sa_sigaction = 0x9bb5848}, sa_mask = {__val = {3214234984, 135196938, 3079186144, 0, 3214235104, 3214235092, 128, 0, 0, 3214235168, 3079439984, 134566866, 515, 0, 0, 0, 1, 135270254, 128, 1, 3214235092, 163272744, 69, 3214235220, 3214235064, 135198534, 163273291, 3214235092, 3214235096, 516, 163272776, 3078652995}}, sa_flags = 516, sa_restorer = 0x8106d79 <write_full+57>} sigs = {__val = {32, 0 <repeats 31 times>}} #3 0x080f15e5 in default_fatal_finish (type=<value optimized out>, status=0) at failures.c:160 backtrace = 0x9bb5618 "imap [0x80f15d1] -> imap [0x80f1642] -> imap [0x80f0fb9] -> imap [0x8063360] -> imap [0x80635b4] -> imap(cmd_list_full+0x50c) [0x806436c] -> imap(cmd_list+0x19) [0x8064669] -> imap [0x8067a2c] -> imap"... #4 0x080f1642 in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0x8109dcc "file %s: line %d (%s): assertion failed: (%s)", args=0xbf9556b4 "}\245\020\b\362") at failures.c:443 No locals. #5 0x080f0fb9 in i_panic ( format=0x8109dcc "file %s: line %d (%s): assertion failed: (%s)") at failures.c:207 No locals. #6 0x08063360 in ns_get_listed_prefix (ctx=0x9bbfec8, have_children=true) at cmd-list.c:242 glob = 0x9bb55d0 match = IMAP_MATCH_NO __PRETTY_FUNCTION__ = "ns_get_listed_prefix" #7 list_namespace_send_prefix (ctx=0x9bbfec8, have_children=true) at cmd-list.c:266 i = <value optimized out> flags = <value optimized out> name = 0x9bbf480 "INBOX." str = <value optimized out> ends_with_sep = <value optimized out> #8 0x080635b4 in list_namespace_mailboxes (cmd=0x9bbfe30) at cmd-list.c:375 info = <value optimized out> flags = 1073741828 str = 0x9bb5358 ret = 0 ns = 0xbf9557b8 name = 0x9bc52c0 "INBOX" #9 cmd_list_continue (cmd=0x9bbfe30) at cmd-list.c:762 _data_stack_cur_id = 4 ctx = 0x9bbfec8 #10 0x0806436c in cmd_list_full (cmd=0x9bbfe30, lsub=false) at cmd-list.c:933 client = 0x9bbfba0 args = 0x9bc26d0 arg = <value optimized out> ctx = 0x9bbfec8 patterns = {arr = {buffer = 0x9bbfef0, element_size = 4}, v = 0x9bbfef0, v_modifiable = 0x9bbfef0} pattern = 0x9bc2738 "inbox" #11 0x08064669 in cmd_list (cmd=0x9bbfe30) at cmd-list.c:948 No locals. #12 0x08067a2c in client_command_input (cmd=0x9bbfe30) at client.c:612 client = 0x9bbfba0 command = <value optimized out> __PRETTY_FUNCTION__ = "client_command_input" #13 0x08067ad3 in client_command_input (cmd=0x9bbfe30) at client.c:661 client = 0x9bbfba0 command = <value optimized out> __PRETTY_FUNCTION__ = "client_command_input" #14 0x08067c2d in client_handle_next_command (client=0x9bbfba0) at client.c:702 No locals. #15 client_handle_input (client=0x9bbfba0) at client.c:714 _data_stack_cur_id = 3 ret = false remove_io = <value optimized out> handled_commands = false __PRETTY_FUNCTION__ = "client_handle_input" #16 0x0806856f in client_input (client=0x9bbfba0) at client.c:753 cmd = <value optimized out> output = 0x9bbfd54 bytes = <value optimized out> __PRETTY_FUNCTION__ = "client_input" #17 0x080fa220 in io_loop_handler_run (ioloop=0x9bbd9b0) at ioloop-epoll.c:208 ctx = 0x9bbdab8 event = 0x9bbdaf8 list = 0x9bbfdd8 io = 0x9bbfdb0 tv = {tv_sec = 1799, tv_usec = 999149} t_id = 2 msecs = <value optimized out> ret = 1 i = 0 j = 0 call = <value optimized out> #18 0x080f9690 in io_loop_run (ioloop=0x9bbd9b0) at ioloop.c:335 No locals. #19 0x08070ef2 in main (argc=) at main.c:327 No locals. $1 = {prev = 0x0, next = 0x0, client = 0x9bbfba0, pool = 0x9bbfe18, tag = 0x9bbfea8 "sr6y", name = 0x9bbfeb0 "LIST", args = 0x9bbfeb8 "\"\" \"inbox\"", cmd_flags = 0, func = 0x8064650 <cmd_list>, context = 0x9bbfec8, module_contexts = {arr = { buffer = 0x9bbfe70, element_size = 4}, v = 0x9bbfe70, v_modifiable = 0x9bbfe70}, parser = 0x9bc2620, state = CLIENT_COMMAND_STATE_WAIT_INPUT, sync = 0x0, uid = 0, cancel = 0, param_error = 0, search_save_result = 0, temp_executed = 0} (gdb) quit ----- End forwarded message ----- -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

2 2

[Dovecot] Question about log entries
by Cliff Hayes 30 Dec '09

30 Dec '09

Hello, What does this information mean and how is it relevant? I cannot find documentation other than a brief description in dovecot.conf: %t - number of TOP commands %p - number of bytes sent to client as a result of TOP command %r - number of RETR commands %b - number of bytes sent to client as a result of RETR command Thanks in advance, Cliff

4 3

[Dovecot] Mail storage creation fails with virtual users
by Scott H. W. Snyder 30 Dec '09

30 Dec '09

So I have recently set up dovecot with a virtual users dovecot.passdb file, but when I attempt to telnet in, it fails because my virtual users don't have proper permissions to create mailboxes. I don't want to have to create actual users for each email account. Any idea as to what to do? The error that dovecot logs: dovecot: Dec 28 13:06:28 Error: IMAP(user1): mkdir_parents(/var/mail/ folders/user1) failed: Permission denied dovecot: Dec 28 13:06:28 Error: IMAP(user1): Mail storage creation failed with mail_location: mbox:/var/mail/folders/user1/:INBOX=/var/ mail/user1 dovecot: Dec 28 13:06:28 Error: child 27667 (imap) returned error 89 my [test] passdb file: user1:{PLAIN}pass1:2001:2001:User 1 Name:/var/mail/folders/user1:: mail_plugins=cmusieve user2:{PLAIN}pass2:2002:2002:User 2 Name:/var/mail/folders/user2:: mail_plugins=cmusieve user3:{PLAIN}pass3:2003:2003:User 3 Name:/var/mail/folders/user3:: mail_plugins=cmusieve user4:{PLAIN}pass4:2004:2004:User 4 Name:/var/mail/folders/user4:: mail_plugins=cmusieve Conf settings: -bash-3.2# /usr/local/sbin/dovecot -n # 1.0.13: /usr/local/etc/dovecot.conf base_dir: /usr/local/var/run/ log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.info.log protocols: imap listen: *:143 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run//login login_executable: /usr/local/libexec/dovecot/imap-login login_greeting: Hi buddy, have an account ? max_mail_processes: 2048 verbose_proctitle: yes first_valid_uid: 1000 last_valid_uid: 5000 mail_location: mbox:/var/mail/folders/%u/:INBOX=/var/mail/%u mail_debug: yes mbox_read_locks: dotlock fcntl auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /usr/local/etc/dovecot.passdb userdb: driver: passwd-file args: /usr/local/etc/dovecot.passdb socket: type: listen master: path: /usr/local/var/run/dovecot-auth-master mode: 432 user: dovecot group: mail

2 5

[Dovecot] Problem with dovecot and PAM
by Joss Red 30 Dec '09

30 Dec '09

Hi, I keep having errors when I try to authenticate to my imap acount, and I can't get my email like this. Here are the logs when i try to authenticate using PLAIN or CRAM-MD5 : PLAIN Dec 24 22:06:25 domain dovecot: auth(default2): client in: AUTH^I1^IPLAIN^Iservice=IMAP^Isecured^Ilip=1.2.3.4^Irip=1.2.3.4^Iresp=<hidden> Dec 24 22:06:27 domain dovecot: auth(default2): pam(email(a)domain.com,1.2.3.4): pam_authenticate() failed: User not known to the underlying authentication module Dec 24 22:06:27 domain dovecot: auth(default2): client out: FAIL^I1^Iuser=email(a)domain.com Dec 24 22:06:27 domain dovecot: imap-login: Disconnected: user=<email(a)domain.com>, method=PLAIN, rip=1.2.3.4, lip=1.2.3.4, TLS CRAM-MD5 Dec 24 22:13:17 domain dovecot: auth(default): client in: AUTH^I1^ICRAM-MD5^Iservice=IMAP^Isecured^Ilip=1.2.3.4^Irip=1.2.3.4 Dec 24 22:13:17 domain dovecot: auth(default): client out: CONT^I1^IPDAxNDgyOTE1OTk5OTE0NTEuMTI2MTY4OTE5N0BzZC0xMjE5Mj4= Dec 24 22:13:17 domain dovecot: auth(default): client in: CONT<hidden> Dec 24 22:13:17 domain dovecot: auth-worker(default): sql(email(a)domain.com,1.2.3.4): query: SELECT email as user, password FROM view_users WHERE email='email(a)domain.com'; Dec 24 22:13:17 domain dovecot: auth-worker(default): password(email(a)domain.com,1.2.3.4): Requested HMAC-MD5 scheme, but we have only PLAIN-MD5 Dec 24 22:13:18 domain dovecot: auth(default): client out: FAIL^I1^Iuser=email(a)domain.com Dec 24 22:13:18 domain dovecot: imap-login: Disconnected: user=<email(a)domain.com>, method=CRAM-MD5, rip=1.2.3.4, lip=1.2.3.4, TLS Please Help me :)

2 1

[Dovecot] Upgrade 1.0->1.2 dbox mysql
by Bradley Giesbrecht 29 Dec '09

29 Dec '09

Hi, I just upgraded to from dovecot v1.1.15 to v1.2.9 so I can use dovecot- sieve. Most everything seems to work but my webmail (roundcube) clients are not seeing their subscribed folders. Reading over the upgrade docs at http://wiki.dovecot.org/Upgrading/1.2 I'm wondering if I have the two settings below configured correctly. dovecot.conf: mail_location = dbox:/opt/local/var/mail/%d/%n/dbox dovecot_mysql.conf user_query homedir result: /opt/local/var/mail/example.com/foo bash-3.2# dovecot -n # 1.2.9: /opt/local/etc/dovecot/dovecot.conf # OS: Darwin 9.8.0 Power Macintosh hfs log_path: /opt/local/var/serveza/log/mail/dovecot.log protocols: imap imaps pop3 pop3s disable_plaintext_auth: no verbose_ssl: yes login_dir: /opt/local/var/run/dovecot/login login_executable(default): /opt/local/libexec/dovecot/imap-login login_executable(imap): /opt/local/libexec/dovecot/imap-login login_executable(pop3): /opt/local/libexec/dovecot/pop3-login login_greeting: now what? mail_location: dbox:/opt/local/var/serveza/mail/%d/%n/dbox mail_debug: yes mail_executable(default): /opt/local/etc/dovecot/bin/log_imap_login.sh mail_executable(imap): /opt/local/etc/dovecot/bin/log_imap_login.sh mail_executable(pop3): /opt/local/etc/dovecot/bin/log_pop3_login.sh mail_plugin_dir(default): /opt/local/lib/dovecot/imap mail_plugin_dir(imap): /opt/local/lib/dovecot/imap mail_plugin_dir(pop3): /opt/local/lib/dovecot/pop3 lda: log_path: /opt/local/var/serveza/log/mail/dovecot-deliver.log auth_socket_path: /opt/local/var/run/dovecot/auth-master postmaster_address: postmaster(a)pixilla.com auth default: mechanisms: plain login cram-md5 ntlm apop verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /opt/local/etc/dovecot/dovecot_mysql.conf userdb: driver: prefetch userdb: driver: sql args: /opt/local/etc/dovecot/dovecot_mysql.conf socket: type: listen client: path: /opt/local/var/spool/postfix/private/auth mode: 432 user: _postfix group: _postfix master: path: /opt/local/var/run/dovecot/auth-master mode: 384 user: _vmail Thanks for any clues, Bradley Giesbrecht

3 3

[Dovecot] Install fails when libdir and libexecdir are the same directory
by River Tarnell 29 Dec '09

29 Dec '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm using Dovecot 1.2.9. I configured it like this: % ./configure --prefix=/opt/rt --libdir=/opt/rt/lib \ --libexecdir=/opt/rt/lib [other args...] It compiled fine, but failed to install, because it tries to install a directory called <libdir>/dovecot/imap, and a file called <libexecdir>/dovecat/imap, which obviously doesn't work when libdir and libexecdir are the same directory: gmake[5]: Entering directory `/home/river/hp-pkg/mail/dovecot/work/dovecot-1.2.9/src/plugins/imap-acl' gmake[5]: Nothing to be done for `install-exec-am'. test -z "/opt/rt/lib/dovecot/imap" || /opt/rt/bin/gmkdir -p "/home/river/hp-pkg/mail/dovecot/install/opt/rt/lib/dovecot/imap" /opt/rt/bin/gmkdir: cannot create directory `/home/river/hp-pkg/mail/dovecot/install/opt/rt/lib/dovecot/imap': File exists gmake[5]: *** [install-imap_moduleLTLIBRARIES] Error 1 As a workaround I used --libexecdir=/opt/rt/lib/dovecot/libexec, but perhaps one of the conflicting files could be moved or renamed. (On System Vish platforms, e.g. Solaris and HP-UX, 'libexec' isn't used -- files that other systems put into 'libexec' go into 'lib'.) - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (HP-UX) iEYEARECAAYFAks6OpgACgkQIXd7fCuc5vJ2IACfSXNKUbHi1r0mRWIvfTgl6ATk HMEAn1uAhwdFn+yQMAnAP/RrYx07wlIv =t1pG -----END PGP SIGNATURE-----

2 1

[Dovecot] multiple attribute templates?
by Mariano Absatz 29 Dec '09

29 Dec '09

Hi, I've been using an attribute template for some time without any problems. My accounts are on an LDAP server and I have an attribute maildropPath which is the maildir path for the user relative to /home/vmail That is, user "mabsatz(a)example.org" has, in attribute maildropPath the string "example.org/mabsatz", meaning that the maildir is in /home/vmail/example.org/mabsatz This is configured like this (taken from http://wiki.dovecot.org/AuthDatabase/LDAP/Userdb) user_attrs = maildropPath=mail=maildir:/home/vmail/%$ pass_attrs = uid=user,userPassword=password,maildropPath=userdb_mail=maildir:/home/vmail/%$ and it works OK. Now I want to start using sieve and, since all accounts are virtual, I want to use a subdirectory "sieve" within the maildir to hold the scripts, so I need (I think) a userdb home to point to the same path... being a monkey I tried to imitate (or rather, extend) the previous configuration like this: user_attrs = maildropPath=mail=maildir:/home/vmail/%$,maildropPath=home=/home/vmail/%$ pass_attrs = uid=user,userPassword=password,maildropPath=userdb_mail=maildir:/home/vmail/%$,maildropPath=userdb_home=/home/vmail/%$ Alas... this didn't work... that is, apparently, the "home" attribute works OK (I got my scripts on the /home/vmail/example.org/mabsatz/sieve directory), but the "mail" attribute got lost and mail is being delivered to /home/vmail/mabsatz. Is there a way to use more than one attribute template AND that both use the same LDAP attribute? Otherwise, can someone think of a better way to do what I'm trying to do? I'm using dovecot 1.1.11 from the standard ubuntu 9.04 package (dovecot-imapd_1.1.11-0ubuntu4.1). -- Mariano Absatz - "El Baby" el.baby(a)gmail.com www.clueless.com.ar -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Real programmers use: cat > a.out http://xkcd.com/378/ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- * TagZilla 0.066 * http://tagzilla.mozdev.org

2 1

[Dovecot] Deliver EX_TEMPFAIL's without giving any information
by Denis Khromov 29 Dec '09

29 Dec '09

Hi all. I've had a hard time trying to find out why deliver isn't working after I've updated dovecot from v1.11 to v1.2.8. It just gave me EX_TEMPFAIL without any info in the logs. My deliver was setuid-root. Once I've made a simple shell wrapper script for the deliver executable which saves deliver's stdout+stderr, I've found the reason: /usr/local/libexec/dovecot/deliver must not be both world-executable and setuid-root. This allows root exploits. See http://wiki.dovecot.org/LDA#multipleuids Did a 'chmod o-x deliver' and fixed groups/owners and now everything works as it should. I think this error message should go to log files, not just to stdout/stderr. And it's worth to describe this behaviour in the Wiki. Cheers, Denis

2 1

[Dovecot] dovecot -n output of (default) is confusing me
by john.blue＠cox.net 29 Dec '09

29 Dec '09

Hello, I'm new to dovecot and I've been taking my time examining what makes dovecot work. If I have imap and pop3 listed as protocols, dovecot -n outputs: mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 I don't understand why imap is listed twice once as (default), and the other without (default). As a secondary question, why would you want a default of imap as opposed to pop3? Thanks. John

2 1

[Dovecot] Log rotation?
by Beto Moreno 29 Dec '09

29 Dec '09

Hi people. I had read dovecot logging info, they say something about using log rotation to help us rotate our log, with this setup: # dovecot SIGUSR1: Re-opens the log files. /var/log/dovecot*.log { missingok notifempty delaycompress sharedscripts postrotate /bin/kill -USR1 `cat /var/run/dovecot/master.pid 2>/dev/null` 2> /dev/null || true endscript } Well, my question is simple, Do we need to restart the service each time logrotation runs? In my case, is wrong this? var/log/dovecot*.log { weekly rotate 8 notifempty missingok copytruncate create 600 root start 0 } I have 2 dovecot logs: dovecot-info.log dovecot.log dovecot-info.log is the biggest, 5MB by week, is to much? Do I have to change our log rotation to "daily"? Centos 5.4 updated, dovecot 1.0.7-7.el5, thanks!!!

3 3

[Dovecot] Retrieve Physical Message Filename
by Tony Rutherford 29 Dec '09

29 Dec '09

Hi,Using Dovecot 1.2.9 with Maildir and Layout=FS.In a plugin, i'm overriding "update_flags":void my_mail_update_flags(struct mail *_mail, enum modify_type modify_type, enum mail_flags flags)For this email which is having its flags updated, I need to retrieve the physical filename of the message. I see where using:mail_get_special(_mail, MAIL_FETCH_UIDL_FILE_NAME, &fname);...I can retrieve part of the filename, but without the ":2" and the flags part.Is there a method I can use to get the whole filename (without having to reassemble it myself). I've looked around, and I'm guessing it exists, but I don't see it offhand.Thanks,...Tony RutherfordSoftware EngineerBlueTie Inc.arutherford(a)bluetie.com(585) 586-2000 x1040 This message is intended solely for the individual(s) to whom it is addressed. If you are not the intended recipient, any dissemination or copying is strictly prohibited. If you believe you received this message in error, please notify the sender and delete from your system. Thank you.

2 1

[Dovecot] Design: Optimizations for high-latency storage backend
by Timo Sirainen 29 Dec '09

29 Dec '09

Mainly intended for future support of key-value (etc.) databases, but this is probably useful even for regular disk I/O. By using async I/O for disk access, the OS could more intelligently do seeks on disk to read the wanted data with less latency. Problem #1: Accessing message body while searching (e.g. SEARCH BODY). The idea is that searching wouldn't block. Caller would typically use mailbox_search_next_nonblock() function, which can return "try again later" result. Whenever search sees a query that could potentially block (e.g. SEARCH BODY, or searching a header that might not be cached), it goes into a slightly different search mode: - the whole search would typically be run from beginning to end immediately, and the search result state would be stored for each message. - whenever search runs into a situation where the result can't be determined without opening message body, it issues a prefetch command for that message, marks the result for the message as "incomplete", and continues to the next message - once the search is done with all messages, it starts replying to the caller. if the next search result is incomplete at the time, the search returns "try again later". optimizations: - probably there should be prefetch limit (a queue) so that only maybe 10 requests are actually pending at a time. - probably the whole search shouldn't run immediately. maybe it should stop after having 10 requests pending. - prefetch could return only the needed parts of the message, such as "only header" or "only body" (or in future something like "message without attachments") There would be a new call, something like mailbox_search_set_nonblock_callback() that specifies a function to be called when next search result is available. The callback then would continue the search. This is similar to how IMAP SEARCH is already implemented, except currently when mailbox_search_next_nonblock() returns "try again later", Dovecot simply adds a 0 second timeout after which it's called again (that's enough for Dovecot to do some other pending work). Problem #2: Accessing index cache while searching. Cache file is typically in memory or in low-latency disk already. Anyway something similar to #1 could be implemented for it. "Make sure cache x..y bytes in cache file have been read to memory" call or something. Problem #3: Fetching message body (and uncached fields). The nice thing about lib-storage's fetching API is that the caller already specifies what fields it intends to access in mailbox_search_init(). So this code can use a similar technique than searching: - callers only use mailbox_search_next_nonblock() - which keeps returning "try again later" until the message body has been read to memory - trying to access a field that's not specified in wanted_fields in mailbox_search_init() could be (optionally) treated as a programming error and cause a crash instead of a blocking wait. Problem #4: How to drop latencies between IMAP commands? For example a (stupid) client issues commands: a FETCH 1 BODY.PEEK[] a FETCH 2 BODY.PEEK[] ..etc.. You really don't want to a delay between each command. So what Dovecot code needs to happen is to start processing the next command while waiting for previous one to finish reading the body to memory. A lot of this actually already works as intended, but there are some cases that don't, such as FETCH + SELECT (see #5). Problem #5: Opening mailbox index. So if your indexes are also stored in high-latency disk, how do you optimize getting STATUS for each mailbox? Again, a similar idea than before: Create a new mailbox_open_nonblock() function that calls a given callback function when the indexes are read to memory. During the wait it can continue processing more STATUS commands (hopefully client sends them all at once, instead of waiting for each reply before sending next STATUS). .. I think that's all of the problematic cases that could cause blocking. And the solution is always the same: Use prefetching and "try again later" status code with a callback function to be called when it's ready. Luckily there are only two functions that need the above behavior, implementing async callbacks for all functions would have made programming it horrible. The main problem will then be to optimize what and how much to prefetch. For example in the cache file case, should the cache be read to memory when mailbox is opened, or should it be delayed until something is actually wanted to be read from it? Should all of it be read, or should Dovecot attempt to be smarter to reduce memory usage and I/O bandwidth, so e.g. if the cache is wanted to be accessed to 3rd last message, maybe just read the cache file beginning from that message to EOF? Transaction log files have a similar problem. Actually all of this is similar to how Dovecot attempts to cache them to memory when using mmap_disable=yes, so it's not really a new problem.

2 2

[Dovecot] Design: Mailbox list indexes
by Timo Sirainen 29 Dec '09

29 Dec '09

I drove over 2000 miles in recent days, so I had some time to think about future Dovecot things. :) Maybe for v2.1 or v3.0, whichever I happen to release next. Here's the first thought: The main idea behind mailbox list indexes was to make getting STATUS information for mailboxes from a single index file. The code was already written for Dovecot v1.1, but it was disabled because of bugs I never got around to fixing. It also was maybe a bit overdesigned to make it fast with thousands of mailboxes. There were two indexes: Mailbox UID -> name map index, and UID -> status info index. I don't think most people have that many mailboxes. Using two index files just makes the common case slower. So the new mailbox list index could be a single index (read/written to using the same index file API as for mails). Index's header would contain an ID -> string map. So basically an array of {uint32_t id, char nul-terminated-name[]} records. Each index record would contain: - mailbox UID number (32 bit) - ID number (32 bit), pointing to a string in the header. That'll be this mailbox's name. - parent mailbox UID (e.g. if parent's name is "foo" and our name is "bar", the mailbox is "foo/bar") - mailbox global UID (128 bit) - mailbox flags (\Noselect, \Nonexistent) - STATUS information: message/unseen counts, last-non-recent-uid (for recent count), uidvalidity, uidnext, highest-modseq - storage backend specific timestamps So typically the whole index would be read into memory and the mailbox tree would be generated based on the parent UID pointers. If there are any \Noselect or \Nonexistent mailboxes, they just have their GUIDs and STATUS info zeroed out. Each time a mailbox is created or renamed, a new name ID is added to the header with the given name. I don't think it's worth it to try to reuse old IDs. Unused names (after delete/rename) will be dropped sometimes later. Whenever STATUS information changes while accessing mailbox, the STATUS info is updated in mailbox list index. Also unless mailbox_list_index_dirty_syncs=yes (or something similar), the index can't be trusted by itself. So before trusting the index, Dovecot needs to check if the index is up to date by comparing the timestamps to what exists in filesystem. For example with Maildir there would be new/ and cur/ directories' mtimes. Then there's the problem of how to notice externally added/deleted/renamed mailboxes. It'll be immediately noticed if such mailbox is tried to be opened, but what about LIST replies? One possibility would be to refresh the list once when session begins and after that just have LIST return indexed mailboxes. Another would be to keep track of directory mtimes and keep stat()ing the dirs to see if something changes. The latter is probably more trouble than worth.. Besides caching LIST and STATUS replies, there's one additional thing I thought of that the mailbox list indexes will be useful for: atomic mailbox list updates. Even if the backend doesn't support e.g. atomic RENAME (such as Maildir++), this can be made practically atomic using the list index. CREATE, RENAME and DELETE commands begin by writing and committing a record to the mailbox list index about the change. Then they'll start the actual change, and finally write to the index that the change is complete. If it crashed in the middle, the next session would finish it. If another session tries to do a conflicting change before the change is finished, it would wait for the previous one to finish. (Probably practically the index would be write-locked and all changes would wait for previous ones to finish.) And the final functionality of this mailbox list index is for the future support of key-value (etc.) databases: The mailbox list index would be the authoritative list of mailboxes. It wouldn't be stored anywhere else.

1 0

[Dovecot] checking all folders for new mail (IMAP STATUS command)
by Florian Effenberger 29 Dec '09

29 Dec '09

Hello, I use Thunderbird as IMAP client and do a lot of server-side filtering with Sieve scripts. To be notified of new mails, I want to check all folders (a lot of them...) at once for new mails, and not only the inbox. According to http://kb.mozillazine.org/Checking_for_new_messages_in_other_folders_-_Thun… it should be sufficient to enable one setting -- given that the IMAP server returns the STATUS command correctly. I still run Dovecot 1.0 (from Debian 4.0), and it seems this version doesn't support the IMAP STATUS command, as I have to explictly query each folder with the second mentioned setting. What is the recommended way of checking all folders for new mails? Is there any server-side setting I can activate? Do newer versions of Dovecot support the STATUS command in the way Thunderbird expects it? Or does Dovecot even offer an option like the mentioned IMAP_CHECK_ALL_FOLDERS=1 and IMAP_ENHANCEDIDLE=1 in Courier? Sorry for my maybe dumb question... :-) Thanks, Florian

6 13

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

29 Dec '09

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

1 0