- dovecot - dovecot.org

[Dovecot] v1.1.alpha4 released / about dbox
by Timo Sirainen 22 Sep '07

22 Sep '07

http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha4.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha4.tar.gz.sig Lots of fixes since alpha3. Also includes the dbox rewrite. Currently dbox works properly only in one-message-per-file mode. I'm not actually even sure how good idea it would be to use it with multiple-messages-per-file mode. But I guess it won't hurt to finish its implementation and see. :) As you can see I haven't been replying much to the mailing list lately. My school started again, which meant that I had to start sleeping again at night instead of at day :) Doing that always takes a few weeks of feeling too tired to get much of anything done. Hopefully that goes away soon. A bit more about dbox: Originally I had thought that it'd be good to have multiple messages per file. The bad thing about that is that it works badly without fcntl locks, which don't work all that great with NFS. So I changed my plans a bit so that dbox also supports one-message-per-file behavior where it doesn't need locking much. (Multiple-messages-per-file is still supported by the format, but currently the code is not fully working.) dbox files begin with a header, then they have the message data and at the end of file there's a metadata block. Metadata contains things like message flags, keywords, received date and so on. When a flag/keyword is updated, the change is normally done only to index files. This is why dovecot.index and dovecot.index.log files are important with dbox format, they contain flag changes that haven't been written anywhere else. But since there's still a chance that index files could break (although v1.1 tries harder than v1.0 to fix problems), it would be nice if the flags/keywords were written to metadata block once in a while. So if the index files are lost, flag changes wouldn't be completely lost. Metadata updates of course use disk I/O so they shouldn't be done too often. I was thinking that the metadata could be updated: - if IMAP connection has been idling for 4 hours (not changing flags) - when closing mailbox and there are changes older than 4h - immediately if there are changes older than 24h (whenever mailbox is being synced, e.g. SELECT/NOOP/STATUS) Or something like that. Those rules can of course be changed, but I'm not sure if I should bother making them configurable from dovecot.conf. There are already too many settings.

4 6

[Dovecot] Unexpected input from auth master: CUID
by Branislav Baca 22 Sep '07

22 Sep '07

Hello, I'm using postfix(2.4.5) and dovecot(1.0.5), and till now I have been using postfix deliver agent. Now I have tried to reconfigure postfix to use the dovecot LDA, but I'm getting some strange error: Sep 9 18:07:57 hostname deliver(username(a)domain.tld): BUG: Unexpected input from auth master: CUID^I5 For IMAP and POP3 my configuration works fine. I have tried it also with dovecot versions 1.0.4 and 1.0.1, but the behaviour is the same. What can be the reason of this? What should I look for to get more details what can causing this? I have this line in postfix master file: dovecot unix - n n - - pipe flags=DRhu user=mails:mails argv=/opt/dovecot-1.0.5-1/libexec/dovecot/deliver -f ${sender} -d ${recipient} In main.cf: dovecot_destination_recipient_limit = 1 virtual_transport = dovecot Relevant parts of dovecot.conf: auth default { passdb sql { args = /path/to/dovecot-sql.conf } userdb sql { args = /path/to/dovecot-sql.conf } socket listen { client { path = /var/run/dovecot/auth-master mode = 0600 user = mails group = mails } } } protocol lda { postmaster_address = postmaster(a)domain.tld auth_socket_path = /var/run/dovecot/auth-master } And relevant parts of dovecot-sql.conf: driver = mysql password_query = SELECT address as user, passwd as password FROM mail_users WHERE address='%u' user_query = SELECT CONCAT('/home/',maildir) as home, 999 as uid, 999 as gid FROM mail_users WHERE address='%u' Thanks, BB

2 2

[Dovecot] Dovecot "authentication failed" interaction with Postfix
by Julian Cowley 22 Sep '07

22 Sep '07

Hi, I'm not sure if I should be posting this question here or on the Postfix mailing list, but I'll start here. When using Dovecot SASL with Postfix, is there a way to return a login-failed reason in the SMTP AUTH dialog using "nologin", similar to the way it can be done with Dovecot IMAP and POP? Details: I have a Dovecot authentication-only daemon working with a Postfix server doing SMTP AUTH. The Dovecot configuration uses a MySQL driver to get the password information, and one of the fields in the database is "access". In my SQL query, I return a row only if "access" is non-zero. This all works -- I can shut down an account from accessing mail while retaining the user's original password. password_query = SELECT username AS user, password FROM mailbox WHERE username = '%u' AND access != 0 Now, in my Dovecot IMAP and POP server configuration, I'm using "access" in a similar way, except that instead of not returning a row when "access" is zero, I return the "nologin" extra field (along with a "reason" field). The MySQL query for this is slightly tricky, but it works: password_query = SELECT username AS user, password, NULLIF(access != 0, 1) AS nologin, 'Access not allowed for this account' AS reason FROM mailbox WHERE username = '%u' While this second query works correctly with IMAP and POP authentication, it does not work with Postfix SMTP AUTH. Assuming the password is correct, the user is authenticated even when "access" is zero. It seems that either Postfix and/or dovecot-auth (I'm not sure which) is ignoring the "nologin" field in this case. In addition, when using the first SQL query, nothing is returned as a reason following Postfix's message. For example: AUTH PLAIN (correct password) 535 5.7.0 Error: authentication failed: <-- no reason returned here I'd like to return a reason here in the (optimistic :) hope that this will be shown to the user by the email client when an account is shut off. Here's an example of it working correctly with IMAP with an account that is shut off: 001 LOGIN user (correct password) 001 NO Access not allowed for this account

2 1

[Dovecot] Wrong size calculating with maildirquota
by Umut Arus 22 Sep '07

22 Sep '07

Hello, I'm using dovecot-1.0.5 with postfix. There is a problem which dovecot folder's size calculating wrong. It doesn't calculates whole folders' sum. Only maildirsize file keeps the first requested folder's size (in this example, Inbox). The example shows Inbox's size, another folder's size didn't add although connecting with IMAP. As the effect, I can not manage users' quota. Is there any hint with using namespace. Include quota size infos in control file, [root@xxxx Maildir]# cat /var/no-quotas/control/oneusername/maildirsize 512000000S 4941014 190 1849 1 40788 1 Also, namespace descriptions in dovecot.conf, namespace private { separator = / prefix = inbox = yes location = maildir:~/Maildir:INDEX=/var/no-quotas/index/%u:CONTROL=/var/no-quotas/control/%u } namespace private { separator = / prefix = mail/ #hidden = yes location = maildir:~/Maildir/.mail:INDEX=/var/no-quotas/index/%u:CONTROL=/var/no-quotas/control/%u } thanks in advance.

2 1

[Dovecot] Deliver parameter problem
by Umut Arus 22 Sep '07

22 Sep '07

Hello, I'm using dovecot-1.0.5 with postfix. I have to use deliver from procmail because I have some filters. There is no document about how to using deliver parameters (-d) other than http://wiki.dovecot.org/LDA . If I set -d parameters manually as a username everything is ok. I can not set users' mail quota (don't lookup) with mysql db if I haven't set -d parameter as receipt username in procmail. How can I describe user (-d) parameter's variable in procmail? Procmail configuration, :0 | /usr/local/dovecot/libexec/dovecot/deliver -f $blabla -d $blabla2 Output of the configuration, # 1.0.5: /usr/local/dovecot/etc/dovecot.conf protocols: imap imaps pop3 pop3s listen: 10.1.1.168 ssl_cert_file: /usr/local/dovecot/etc/dovecot.cert.pem ssl_key_file: /usr/local/dovecot/etc/dovecot.key.pem disable_plaintext_auth: no login_dir: /usr/local/dovecot/var/run/dovecot/login login_executable(default): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(imap): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3-login mail_location: maildir:%h/Maildir:INDEX=/var/no-quotas/index/%u:CONTROL=/var/no-quotas/control/%u mail_debug: yes mail_full_filesystem_access: yes mail_executable(default): /usr/local/dovecot/libexec/dovecot/imap mail_executable(imap): /usr/local/dovecot/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): mail_plugin_dir(default): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot/lib/dovecot/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xv%08Xu namespace: type: private separator: / location: maildir:~/Maildir:INDEX=/var/no-quotas/index/%u:CONTROL=/var/no-quotas/control/%u inbox: yes namespace: type: private separator: / prefix: mail/ location: maildir:~/Maildir/.mail:INDEX=/var/no-quotas/index/%u:CONTROL=/var/no-quotas/control/%u auth default: verbose: yes debug: yes passdb: driver: pam userdb: driver: sql args: /usr/local/dovecot/etc/dovecot-sql.conf userdb: driver: prefetch socket: type: listen master: path: /var/run/dovecot/auth-master mode: 438 plugin: quota: maildir:storage=500000:ignore=trash regards,

2 1

[Dovecot] Assertion failure in mail-index-view-sync.c
by Doug Council 22 Sep '07

22 Sep '07

I have been getting these assertion failures every couple days, killing the IMAP process. After it happens, I can login immediately and everything is fine until it happens again. Here is the log entry: Sep 10 10:03:41 mailbox-4 dovecot: nh: IMAP(username): file mail-index-view-sync.c: line 666 (mail_index_view_sync_end): assertion failed: (view->log_file_offset >= view->map->hdr.log_file_int_offset) Sep 10 10:03:41 mailbox-4 dovecot: child 38458 (imap) killed with signal 6 It started after I disabled indexing for deliver and IMAP: mail_location = maildir:~/Maildir:INDEX=MEMORY I removed the dovecot.index* files from all of the maildir directories (including the root/INBOX), but that didn't help. I have upgraded to 1.0.5, but that didn't help either. Any ideas as to what might be causing this? Thanks, -Doug

3 2

[Dovecot] "unknown user" with: Dovecot Pop3 - SASL pam Postfix - Authtentification
by noracentral＠gmx.net 22 Sep '07

22 Sep '07

Hallo I build my Installation after HowTo with Archlinux packages: http://wiki.dovecot.org/HowTo/SimpleVirtualInstall I can send e-mail, but pop3 failed: "unknown user" For good popularity needed one or more 100% complete howto step-by-step reusable for full folk. (not many-many with small pieces solutions by problems...) thanks nora Auth.log: Sep 17 14:35:49 dns su: pam_unix(su:session): session opened for user vmail by (uid=0) Sep 17 15:24:06 dns su: pam_unix(su:session): session closed for user vmail Dovecot.log: dovecot: Sep 19 08:32:40 Info: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=212.254.241.22 rip=77.56.100.9 resp= dovecot: Sep 19 08:32:40 Info: auth(default): client out: CONT 1 dovecot: Sep 19 08:32:40 Info: auth(default): client in: CONT 1 AG1vZGVybmxvdmVAdmVyYmVuLmNoADEyMzQ1Njc4OTA= dovecot: Sep 19 08:32:40 Info: auth(default): cache(modernlove(a)verben.ch,77.56.100.9): hit dovecot: Sep 19 08:32:40 Info: auth(default): client out: OK 1 user=modernlove(a)verben.ch dovecot: Sep 19 08:32:40 Info: auth(default): master in: REQUEST 709 24114 1 dovecot: Sep 19 08:32:40 Info: auth(default): passwd(modernlove(a)verben.ch,77.56.100.9): lookup !!! unknown user dovecot: Sep 19 08:32:40 Info: auth(default): passwd(modernlove(a)verben.ch,77.56.100.9): unknown user dovecot: Sep 19 08:32:40 Info: auth(default): master out: USER 709 modernlove(a)verben.ch uid=1000 gid=101 home=/home/vmail/modernlove(a)verben.ch dovecot: Sep 19 08:32:40 Info: pop3-login: Login: user=<modernlove(a)verben.ch>, method=PLAIN, rip=77.56.100.9, lip=212.254.241.22 dovecot: Sep 19 08:32:40 Info: POP3(modernlove(a)verben.ch): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0

2 1

[Dovecot] Error: auth(default): passwd-file ... is missing userdb info
by noracentral＠gmx.net 22 Sep '07

22 Sep '07

Hallo Have "pop3 plain login Error" and need some changes somewhere... ?where? Please see log down nora --- dovecot.log --- 20 14:17:23 Error: auth(default): passwd-file /etc/dovecot/passwd: User modernlove(a)verben.ch is missing userdb info dovecot: Sep 20 14:19:16 Error: Logins with UID 0 not permitted (user modernlove(a)verben.ch)

2 1

[Dovecot] v1.1 alpha6: Log synchronization error ... Append with UID 0
by Asuka Sato 22 Sep '07

22 Sep '07

Hi. I am testing E-mail delivery by using dovecot 1.1 alpha6. But, The following message(syslog) is output while receiving mail. And, I'm try to looked for this reason in that source code. Hum... I think why the deliver is not using a 'MAILBOX_TRANSACTION_FLAG_ASSIGN_UIDS' flag. # deliver/deliver.c:142::deliver_save() function - calling mailbox_transactio n_begin() The imap's COPY/APPEND commands is using this flag. Thanks. -- Asuka Sato ========================================================= [syslog] ------------------------- Sep 18 14:04:41 host212 deliver(asuka.sato(a)example.jp): \ Log synchronization error at seq=2,offset=208 \ for /var/mss/example.jp/p001/mail/dovecot.index: \ Append with UID 0, but next_uid = 2 [logview] ------------------------- # logview /var/mss/example.jp/p001/mail/dovecot.index.log version = 1.0 hdr size = 24 index id = 1190185480 file seq = 2 ..... record: offset=128, type=append (ext), size=16 - 1 (flags=20), ..... record: offset=208, type=append (ext), size=16 - 0 (flags=20), ..... [system] ------------------------- * dovecot 1.1 alpha6 * Postfix 2.4.3 (LDA dovecot's deliver)

2 1

[Dovecot] Broken header
by Jon 22 Sep '07

22 Sep '07

Hi, I just upgraded to version 1.0.5 hoping to get rid of a problem that made Thunderbird download all mails from time to time. I now see this error (below). Does anyone know what it means? Error: IMAP(user): /mail2/home/user/.Maildir/.Folders.Persons.Foldername/dovecot-uidlist: Broken header (uidvalidity = 0, next_uid=10) Error: IMAP(user): /mail2/home/user/.Maildir/.Folders.2005/dovecot-uidlist: Broken header (uidvalidity = 0, next_uid=1186) Mails are stored in userhomedirs that are located on a NFS export. See below output from dovecote -n [root@mail dovecot-1.0.5]# /usr/local/sbin/dovecot -n # 1.0.5: /usr/local/etc/dovecot.conf log_path: /var/log/dovecot.log login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_processes_count: 2 mail_location: maildir:%h/.Maildir mmap_disable: yes auth default: passdb: driver: pam userdb: driver: passwd Best Regards - Jon

2 1