- dovecot - dovecot.org

[Dovecot] Multiple SSL certs
by Daniel L. Miller 10 Mar '08

10 Mar '08

Does 1.1 support multiple certs? -- Daniel

4 4

[Dovecot] Maildirsize automatically (re)build
by Jan van den Berg 10 Mar '08

10 Mar '08

Hi, Im testing with 1.1RC1. I read here: http://wiki.dovecot.org/Quota/Maildir "If you configure quota limits in Dovecot (e.g. quota=maildir:storage=102400(kilobytes)), Dovecot makes sure that this header is kept up to date. If the file does not exist, it's simply rebuilt." This is my query: password_query = SELECT username as user, username as userdb_user, passwd as password, 1001 as userdb_uid, 1001 as userdb_gid, concat('maildir:storage=', quota, 'M:ignore=Spam\ e\-mail') AS userdb_quotarule, 'Trash:storage=20M' as userdb_quota_rule2 FROM mailboxen WHERE username = '%n' Also in the main config I use: mail_plugins: quota imap_quota plugin: quota: maildir So I use maildir:storage in my config. However when I delete the maildirsize (for testing purposes) it doesn't get automatically recreated? According to the Wiki it should right? Cheers, Jan

3 8

[Dovecot] Sorting by Sender Name
by Daniel Watts 10 Mar '08

10 Mar '08

Dear Timo, Posted this originally to the squirrelmail list but they said that sorting is done server side so concluded I needed to talk to you: ============= I feel there is an error in the logic of the sort by From column. If you sort by this column, the messages are re-ordered in alphabetical order using the *email address* as the sorted word. However most people these days have their clients configured to include a sender's name. For example: Daniel Smith <daniel(a)hotmail.com>. In the message list the name 'Daniel Smith' is then shown, not the email. When sorting by From it should use the name as the sorted element and NOT the email address. If my email was zippydan(a)yahoo.com, my emails, showing as 'Daniel Watts' would come right near the bottom of the list rather than with the other 'D's near the top. I know my email clients (Thunderbird and Outlook) both act like this - using the name if available and if not THEN using (and displaying) the email address. This seems to make the most sense to me. Thanks as always for your attention. Daniel

2 2

[Dovecot] invoking LDA in .forward
by Jeremie Bouttier 10 Mar '08

10 Mar '08

Hi, We're running a Debian server with system users where the mail is by default delivered by postfix and procmail, before being served by Dovecot (mail_location = mbox:~/Mail:INBOX=/var/mail/%u) or read by local MUAs, depending on users' preferences. For people using mostly remote MUAs, it might be interesting to use Dovecot's LDA. I read on http://wiki.dovecot.org/LDA that this is possible using .forward files, however this fails on our system with : file_lock_dotlock() failed with mbox file /var/mail/user: Permission denied (/var/mail is 2775 for root:mail as recently discussed). Is there a possible fix ? I also read that deliver is not designed to be run setuid root, I guess this also applies to being run setgid mail... Regards, Jeremie

2 3

Re: [Dovecot] Wrong message information reported shortly after delivery
by Ron Avriel 10 Mar '08

10 Mar '08

> Thanks, in my previous tests I didn't use quota plugin with deliver > which was needed to notice this. The problem is: > > 1. deliver adds "message appended" to index file > 2. quota plugin runs for a while > 3. deliver updates filename<->uid mapping in dovecot-uidlist > Thanks for the quick answer. Why does it take four seconds (!) from the time dovecot first reports an invalid message information until the correct information is reported? The time is measured for the delivery of a 1KB message to an empty mailbox on a completely idle system. 2008-03-09 17:00:41.449833 Sent 1011 bytes to test1(a)imap4test.com 2008-03-09 17:00:41.472034 No messages in INBOX. Waiting... 2008-03-09 17:00:42.480654 No messages in INBOX. Waiting... 2008-03-09 17:00:43.487617 **** ERROR: Got invalid RFC822.SIZE 0: 1 (FLAGS (\Recent) INTERNALDATE "01-Jan-1970 00:00:00 +0000" RFC822.SIZE 0 UID 63) 2008-03-09 17:00:44.494382 **** ERROR: Got invalid RFC822.SIZE 0: 1 (FLAGS (\Recent) INTERNALDATE "01-Jan-1970 00:00:00 +0000" RFC822.SIZE 0 UID 63) 2008-03-09 17:00:45.501444 **** ERROR: Got invalid RFC822.SIZE 0: 1 (FLAGS (\Recent) INTERNALDATE "01-Jan-1970 00:00:00 +0000" RFC822.SIZE 0 UID 63) 2008-03-09 17:00:46.550623 **** ERROR: Got invalid RFC822.SIZE 0: 1 (FLAGS (\Recent) INTERNALDATE "01-Jan-1970 00:00:00 +0000" RFC822.SIZE 0 UID 63) 2008-03-09 17:00:47.593704 Got valid RFC822.SIZE 1509: 1 (FLAGS (\Recent) INTERNALDATE "09-Mar-2008 17:00:41 +0200" RFC822.SIZE 1509 UID 63) Thanks again, Ron ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs

1 0

[Dovecot] Quota problems with IMAP and POP?
by Nicolas Letellier 10 Mar '08

10 Mar '08

Hello, I would like to know if it could be appears problem using POP and IMAP in a mailbox? Is it adviced to use one of the two protocols? My users use IMAP to see their emails (in the webmail) and POP3 to download their emails (in outlook/thunderbird). Is it best to use the same protocol? POP and IMAP have the same quota engine? Thanks. -Nicolas

2 2

[Dovecot] 1.1 master auth not expanding static userdb variables
by Andrew Roberts 10 Mar '08

10 Mar '08

Can dovecot-1.1 deliver work with static userdb? I'm currently running dovecot-1.0.12 and postfix-2.4.6, with virtual users' maildirs all owned by vmail and mail_location = maildir:/var/mail/%Lu. The following definition of the dovecot transport in postfix/master.conf works fine with dovecot-1.0: dovecot unix - n n - 1 pipe flags=DRh user=vmail:vmail argv=/usr/libexec/dovecot/deliver \ -d ${user}@${nexthop} -n -m ${extension} Note that I'm not using postfix pipe's "u" flag, since that lowercases everything to the left of "@", including the extension, and we need the extension to be case sensitive. Dovecot is configured with static userdb and args = user=%Lu uid=206 gid=206 home=/var/mailhomes/%Lu, which takes care of making sure the username is lowercase. All of this has been working fine for some time with dovecot-1.0. After upgrading to 1.1_rc2, however, deliver creates a maildir named "%Lu" and delivers all mail for all users to it. Everything else works just fine as before: users can log in, postfix can auth smtp via dovecot sasl, etc. I've tried invoking deliver with -k, adding "mail=maildir:/var/mail/%Lu" to the end of the userdb args, and checked file permissions on the auth sockets, maildirs, and virtual homes. Rolling back to 1.0.12 is the only way I can get deliver to behave as expected. What changed between 1.0 and 1.1 in the way deliver does userdb lookups or how dovecot auth serves to it that could cause this? Does anyone here here have a similar config working with 1.1? Has anyone else observed similar behavior? Thanks, Andrew

3 6

[Dovecot] Update from 1.0.10 -> 1.1rc1 file message-parser.c: line 766 (message_parser_parse_next_block): assertion failed
by Ralf Hildebrandt 10 Mar '08

10 Mar '08

Feb 23 20:40:36 postamt dovecot: IMAP(username): file message-parser.c: line 766 (message_parser_parse_next_block): assertion failed: (ctx->input->eof || ctx->input->closed || ctx->input->stream_errno != 0) Feb 23 20:40:36 postamt dovecot: IMAP(username): Raw backtrace: /usr/local/libexec/dovecot/imap [0x8009236d] -> /usr/local/libexec/dovecot/imap [0x80091ed8] -> /usr/local/libexec/dovecot/imap(message_parser_parse_next_block+0xad) [0x8008ae0d] -> /usr/local/libexec/dovecot/imap(index_mail_cache_parse_continue+0x32) [0x80053ab2] -> /usr/local/libexec/dovecot/imap(index_mail_cache_parse_deinit+0x35) [0x80055295] -> /usr/local/libexec/dovecot/imap(maildir_save_finish+0xdb) [0x80034f9b] -> /usr/local/libexec/dovecot/imap(mailbox_save_cancel+0x1b) [0x8005f6ab] -> /usr/local/libexec/dovecot/imap [0x80015d08] -> /usr/local/libexec/dovecot/imap [0x80015ecd] -> /usr/local/libexec/dovecot/imap(client_command_cancel+0x2a) [0x8001b7ca] -> /usr/local/libexec/dovecot/imap(client_destroy+0x6c) [0x8001c0ac] -> /usr/local/libexec/dovecot/imap [0x8001c893] -> /usr/local/libexec/dovecot/imap(io_loop_handle_timeouts+0xeb) [0x80099ddb] -> /usr/local/libexec/dovecot/imap(io_loop_handler_run+0x93) [0x8009aa03] -> /usr/local/libexec/dove Feb 23 20:40:36 postamt dovecot: IMAP(username): /usr/local/libexec/dovecot/imap(main+0x4ae) [0x80024d6e] -> /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7db7450] -> /usr/local/libexec/dovecot/imap [0x80015be1] Feb 23 20:40:36 postamt dovecot: child 15224 (imap) killed with signal 6 -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) snickebo(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de vista policy violation: Microsoft optical mouse detected penguin patterns on mousepad. Partition scan in progress to remove offending incompatible products. Reactivate MS software.

3 3

[Dovecot] 1.1r1: auth-worker(default): BUG: PASSV had missing parameters, sig11
by Adam McDougall 10 Mar '08

10 Mar '08

I don't know how this happened. I'm not sure if there is a coredump somewhere because I don't know what user, and I have nothing for 'root' or 'dovecot'. Any advice, or should I make all my coredumps go to a central writable directory so I have better chance of catching it if it happens again? Is it maybe from someone connecting to postfix and causing a SMTP-AUTH to timeout? Although that is unlikely because users should not know how to reach this server's SMTP ports. I cut most of the surrounding log entries below because they seemed unrelated normal activity, but two of the lines below I left because of the timestamp. socket: type: listen client: path: /var/spool/postfix/private/auth mode: 384 user: postfix group: postfix Mar 8 17:02:17 boomhauer dovecot: auth-worker(default): BUG: PASSV had missing parameters Mar 8 17:03:47 boomhauer dovecot: auth-worker(default): BUG: PASSV had missing parameters Mar 8 17:05:17 boomhauer dovecot: imap-login: Disconnected: Inactivity: method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Mar 8 17:05:17 boomhauer dovecot: child 72819 (login) killed with signal 11 Mar 8 17:06:47 boomhauer dovecot: imap-login: Disconnected: Inactivity: method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Mar 8 17:06:47 boomhauer dovecot: child 72857 (login) killed with signal 11

2 5

[Dovecot] (no subject)
by Brent Clark 10 Mar '08

10 Mar '08

Hi Im trying something new with my test dovecot. I set my mail_location to to a new location mail_location = maildir:/var/maildir/%u/Maildir But with this new setup i too am authenticating against Mysql. This worked fine till i decided to move the mail. So now i have moved the mail, deleted the account from /etc/passwd,, but now in my mail client, i cant view my test mail. Here is my DB set up : +-----------------------------+--------+ | home | user | +-----------------------------+--------+ | /var/maildir/bclark/Maildir | bclark | +-----------------------------+--------+ dovecot-sql set up password_query = SELECT username as user, password, home , uid as userdb_uid, gid as userdb_gid FROM user WHERE username = '%u' and domain = '%d' I have removed Mar 8 15:42:56 eccostorage dovecot: auth(default): client out: CONT^I1^I Mar 8 15:42:56 eccostorage dovecot: auth(default): client in: CONT^I1^IAGJjbGFyawBxYXo= Mar 8 15:42:56 eccostorage dovecot: auth-worker(default): sql(bclark, 192.168.111.31): query: SELECT username as user, password, home , uid as userdb_uid, gid as userdb_gid FROM user WHERE username = 'bclark' and domain = 'eccotours.biz' Mar 8 15:42:56 eccostorage dovecot: auth(default): client out: OK^I1^Iuser=bclark^Ihome=/var/maildir/bclark/Maildir Mar 8 15:42:56 eccostorage dovecot: auth(default): master in: REQUEST^I15^I24965^I1 Mar 8 15:42:56 eccostorage dovecot: auth(default): passwd(bclark, 192.168.111.31): lookup Mar 8 15:42:56 eccostorage dovecot: auth(default): passwd(bclark, 192.168.111.31): unknown user Mar 8 15:42:56 eccostorage dovecot: auth(default): userdb(bclark, 192.168.111.31): user not found from userdb Mar 8 15:42:56 eccostorage dovecot: auth(default): master out: NOTFOUND^I15 Mar 8 15:42:56 eccostorage dovecot: imap-login: Internal login failure: user=<bclark>, method=PLAIN, rip=192.168.111.31, lip=192.168.111.11

2 1