- dovecot - dovecot.org

Re: [Dovecot] Corrupted transaction log file / record size too small
by Steven Winikoff 18 Oct '08

18 Oct '08

>This and some other bugs are now fixed by this: >http://hg.dovecot.org/dovecot-1.1/rev/262c52055f2a Thank you! Both for this and for http://hg.dovecot.org/dovecot-1.1/rev/a0693aec0245 - Steven ________________________________________________________________________ Steven Winikoff | Concordia University | "It's a control freak thing -- I Montreal, QC, Canada | wouldn't let you understand." smw(a)alcor.concordia.ca | http://alcor.concordia.ca/~smw | - Stephen H. Underwood

1 0

[Dovecot] regarding dovecot.index.cache
by Dhaval Thakar 18 Oct '08

18 Oct '08

Hi, This is regarding updating dovecot.index.cache. I have few backup ids configured. these are used only when old mail needs to be retrieved. usually these mailboxes contains more then 9,000 mails. while login to webmail, imap consumption is high, which creates performance related issues for regular mailboxes. to resolve this i have to move heavy mailbox to dedicated server. before doing that, I wanted to confirm if there any way to update dovecot.index.cache even if user is not checking his / her mails. kindly confirm, & provide direction to implement same. Following is the mailserver related details Qmail with Vpopmail 5.4.24 Dovecot-1.1.4 dovecot -n # 1.1.4: /etc/dovecot/dovecot.conf protocols: imap ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login mail_plugins: quota imap_quota trash imap_client_workarounds: delay-newmail outlook-idle namespace: type: private prefix: INBOX. inbox: yes list: yes subscriptions: yes auth default: mechanisms: plain login verbose: yes debug: yes debug_passwords: yes passdb: driver: checkpassword args: /home/vpopmail/bin/vchkpw userdb: driver: vpopmail userdb: driver: prefetch plugin: quota: maildir quota_rule: Trash:ignore thanks & regards dhaval

2 3

[Dovecot] Dovecot 1.1.4 / Maildir++ quota and move to trash
by Xavier Beaudouin 18 Oct '08

18 Oct '08

Hello, Seems there is some nasty problems with Dovecot 1.1.4... We use Maildir++ quota, and when moving mail to Trash, Dovecot just drop the connection... when the maildir is overquota. Is there any way to avoid that and just move the mail to the trash allowing user to expunge their mail easily without calling support to do rm -rf Maildir/cur ? Thanks, /Xavier

4 8

[Dovecot] Pop3 on dovecot
by Rajiv Gore 18 Oct '08

18 Oct '08

Hi When I telnet localhost 110 I get a response as +OK POP3 localhost 2006c.94 server ready I expect to get +OK Dovecot ready. Is there any other pop3 server running on port 110? If so how to assign port 110 to Dovecot? Thanks for advice -- Rajiv Gore 102 Sahakarnagar Ahmednagar 414 003 MS, India

2 1

Re: [Dovecot] Corrupted transaction log file / record size too small
by Steven Winikoff 18 Oct '08

18 Oct '08

>> 2) recompiled dovecot without optimization (ie, gcc -O0 instead of -O2) >> (as per http://www.mail-archive.com/dovecot@dovecot.org/msg12936.html) > >The problem here turned out to be a bug in Sun CC (and gcc -O2 >apparently worked after all, so maybe a problem with testing). Thanks. I'll revert to the default -O2 the next time we recompile (which will probably be version 1.1.4 sometime early next week). >> 3) reverted to using flock for file locking instead of fcntl (we'd been >> using flock with dovecot 1.0.10; 1.1.3 used fcntl by default in a >> couple of places, so I changed it back to see what would happen) > >This shouldn't really make a difference. That's good, because in hindsight I haven't noticed any difference. :-) >> - we still see the occasional assertion failure at line 1091 of >> index-mail.c; this is the one that I'd hoped to solve by >> recompiling without optimization, but at least it seems to be >> happening less frequently than before > >I had hoped v1.1.3 would have fixed this. But perhaps this is also >related to the disk quota issues. Are there any other errors that are >logged before the assert? Nothing obvious, I'm afraid. For example, this occurence is typical of the 24 which we've logged since Sept. 26 (which is as far back as we keep dovecot log data online; for the record, we upgraded from 1.0.10 to 1.1.3 on Sept. 23): Oct 8 13:56:39 alcor dovecot: pop3[15127] USER1, NNN.NNN.NNN.NNN: Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0, xfer=12/27 Oct 8 13:56:39 alcor dovecot: pop3-login: Login: [15118], USER2, NNN.NNN.NNN.NNN Oct 8 13:56:39 alcor dovecot: wrapper[15139]: pop3, USER2, NNN.NNN.NNN.NNN Oct 8 13:56:39 alcor dovecot: pop3-login: Login: [15058], USER3, NNN.NNN.NNN.NNN Oct 8 13:56:39 alcor dovecot: wrapper[15141]: pop3, USER3, NNN.NNN.NNN.NNN Oct 8 13:56:39 alcor dovecot: pop3[15141] USER3, NNN.NNN.NNN.NNN: mkdir(/home/USER3/.imap/INBOX) failed: Disk quota exceeded Oct 8 13:56:39 alcor dovecot: imap-login: Login: [15121], USER4, NNN.NNN.NNN.NNN Oct 8 13:56:39 alcor dovecot: wrapper[15143]: imap, USER4, NNN.NNN.NNN.NNN Oct 8 13:56:39 alcor dovecot: pop3[15139] USER2, NNN.NNN.NNN.NNN: Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0, xfer=12/27 Oct 8 13:56:39 alcor dovecot: imap-login: Login: [15001], USER5, NNN.NNN.NNN.NNN Oct 8 13:56:40 alcor dovecot: wrapper[15159]: imap, USER5, NNN.NNN.NNN.NNN Oct 8 13:56:40 alcor dovecot: imap-login: Login: [15158], USER6, NNN.NNN.NNN.NNN Oct 8 13:56:40 alcor dovecot: wrapper[15162]: imap, USER6, NNN.NNN.NNN.NNN Oct 8 13:56:40 alcor dovecot: imap[15159] USER5, NNN.NNN.NNN.NNN: Disconnected: Logged out bytes=305/13377 Oct 8 13:56:40 alcor dovecot: imap[15162] USER6, NNN.NNN.NNN.NNN: Disconnected: Logged out bytes=110/356 Oct 8 13:56:40 alcor dovecot: Panic: imap[15143] USER4, NNN.NNN.NNN.NNN: file index-mail.c: line 1091 (index_mail_close): assertion failed: (!mail->data.destroying_stream) Oct 8 13:56:40 alcor dovecot: imap[15143] USER4, NNN.NNN.NNN.NNN: Raw backtrace: dovecot-imap [0x4a3ddd] -> dovecot-imap [0x4a4b9d] -> dovecot-imap(i_fatal+0) [0x4a40d1] -> dovecot-imap(index_mail_close+0xfa) [0x4538d4] -> dovecot-imap [0x4538fe] -> dovecot-imap(index_mail_set_seq+0x6a) [0x453ac6] -> dovecot-imap [0x445e6e] -> dovecot-imap(mail_set_seq+0x28) [0x45f6a5] -> dovecot-imap(index_storage_search_next_nonblock+0xe9) [0x458ff0] -> dovecot-imap(mailbox_search_next_nonblock+0x33) [0x462de3] -> dovecot-imap(mailbox_search_next+0x2e) [0x462da2] -> dovecot-imap [0x415e99] -> dovecot-imap(cmd_copy+0x19c) [0x4160ac] -> dovecot-imap [0x41d0ac] -> dovecot-imap [0x41d2e9] -> dovecot-imap [0x41d41c] -> dovecot-imap [0x41d460] -> dovecot-imap(client_input+0xb4) [0x41d5ed] -> dovecot-imap(io_loop_handler_run+0x17d) [0x4aea11] -> dovecot-imap(io_loop_run+0x3b) [0x4adc6a] -> dovecot-imap(main+0x99) [0x42908b] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x2b306fee78c4] -> dovec! ot-imap [0x414939] Oct 8 13:56:40 alcor dovecot: child 15143 (imap) killed with signal 6 Oct 8 13:56:40 alcor dovecot: pop3[15141] USER3, NNN.NNN.NNN.NNN: Disconnected: Logged out top=0/0, retr=1/12816, del=1/1, size=12798, xfer=40/12944 Oct 8 13:56:40 alcor dovecot: imap-login: Login: [15003], USER7, NNN.NNN.NNN.NNN Although the usernames and IP addresses have been elided, each USERn token always represents the same specific account wherever it appears. >> - this doesn't happen often, but once in a while we see assertion >> failures at line 163 of src/pop3-login/client-authenticate.c or >> line 200 of src/imap-login/client-authenticate.c > >I think I've managed to get this also sometimes when killing dovecot- >auth or doing something else "wrong" (I don't remember exactly), but >not during normal operation. I should have noted down how to reproduce >this when I still knew how to reproduce it.. For us this appears to happen during normal operations. That's not to say I've never killed a dovecot-auth process :-), but it's not something I do often (in fact the last time I did was when I recompiled 1.1.3 as described previously, which by now was ten days ago). For what it may be worth, this particular symptom appears to happen in clusters. The most recent spate that we saw were as follows (in context, in case any of the other log messages may be relevant): Oct 10 04:48:45 alcor dovecot: pop3-login: Disconnected (no auth attempts): [9703], NNN.NNN.NNN.NNN Oct 10 04:48:45 alcor dovecot: pop3-login: Disconnected (no auth attempts): [9705], NNN.NNN.NNN.NNN Oct 10 04:48:45 alcor dovecot: pop3-login: Disconnected (no auth attempts): [9702], NNN.NNN.NNN.NNN Oct 10 04:48:46 alcor dovecot: pop3-login: Disconnected (no auth attempts): [9704], NNN.NNN.NNN.NNN Oct 10 04:48:46 alcor dovecot: pop3-login: Disconnected: Inactivity (auth failed, 1 attempts): [9500], USER10, NNN.NNN.NNN.NNN Oct 10 04:48:46 alcor dovecot: Panic: pop3-login: file client-authenticate.c: line 163 (sasl_callback): assertion failed: (!client->destroyed || reply == SASL_SERVER_REPLY_CLIENT_ERROR || reply == SASL_SERVER_REPLY_MASTER_FAILED) Oct 10 04:48:46 alcor dovecot: imap-login: Disconnected: Inactivity (auth failed, 1 attempts): [9502], USER11, NNN.NNN.NNN.NNN, TLS Oct 10 04:48:46 alcor dovecot: Panic: imap-login: file client-authenticate.c: line 200 (sasl_callback): assertion failed: (!client->destroyed || reply == SASL_SERVER_REPLY_CLIENT_ERROR || reply == SASL_SERVER_REPLY_MASTER_FAILED) Oct 10 04:48:46 alcor dovecot: imap-login: Disconnected: Inactivity (auth failed, 1 attempts): [9503], USER12, NNN.NNN.NNN.NNN, TLS Oct 10 04:48:46 alcor dovecot: Panic: imap-login: file client-authenticate.c: line 200 (sasl_callback): assertion failed: (!client->destroyed || reply == SASL_SERVER_REPLY_CLIENT_ERROR || reply == SASL_SERVER_REPLY_MASTER_FAILED) Oct 10 04:48:46 alcor dovecot: imap-login: Disconnected: Inactivity (auth failed, 1 attempts): [8777], USER9, NNN.NNN.NNN.NNN Oct 10 04:48:46 alcor dovecot: Panic: imap-login: file client-authenticate.c: line 200 (sasl_callback): assertion failed: (!client->destroyed || reply == SASL_SERVER_REPLY_CLIENT_ERROR || reply == SASL_SERVER_REPLY_MASTER_FAILED) Oct 10 04:48:47 alcor dovecot: imap[4258] USER8, 67.223.74.40: Disconnected: Logged out bytes=7407/20930 Oct 10 04:48:47 alcor dovecot: pop3-login: Disconnected: Inactivity (auth failed, 1 attempts): [9575], USER13, NNN.NNN.NNN.NNN Oct 10 04:48:47 alcor dovecot: Panic: pop3-login: file client-authenticate.c: line 163 (sasl_callback): assertion failed: (!client->destroyed || reply == SASL_SERVER_REPLY_CLIENT_ERROR || reply == SASL_SERVER_REPLY_MASTER_FAILED) Oct 10 04:48:47 alcor dovecot: pop3-login: Disconnected: Inactivity (auth failed, 1 attempts): [9576], USER14, NNN.NNN.NNN.NNN Oct 10 04:48:47 alcor dovecot: Panic: pop3-login: file client-authenticate.c: line 163 (sasl_callback): assertion failed: (!client->destroyed || reply == SASL_SERVER_REPLY_CLIENT_ERROR || reply == SASL_SERVER_REPLY_MASTER_FAILED) Oct 10 04:48:47 alcor dovecot: auth(default): Master requested auth for nonexisting client 9498 Oct 10 04:48:47 alcor dovecot: auth(default): Master requested auth for nonexisting client 9500 Oct 10 04:48:47 alcor dovecot: auth(default): Master requested auth for nonexisting client 9499 Oct 10 04:48:47 alcor dovecot: auth(default): Master requested auth for nonexisting client 9502 Oct 10 04:48:47 alcor dovecot: auth(default): Master requested auth for nonexisting client 9503 Oct 10 04:48:47 alcor dovecot: auth(default): Master requested auth for nonexisting client 9575 Oct 10 04:48:47 alcor dovecot: auth(default): Master requested auth for nonexisting client 9576 Oct 10 04:48:47 alcor dovecot: auth(default): Master requested auth for nonexisting client 9174 Oct 10 04:48:47 alcor dovecot: imap[9809] USER9, 132.205.7.20: Connection closed bytes=0/0 Oct 10 04:48:47 alcor dovecot: imap-login: Disconnected: Inactivity (auth failed, 1 attempts): [9174], USER8, NNN.NNN.NNN.NNN, TLS Oct 10 04:48:47 alcor dovecot: Panic: imap-login: file client-authenticate.c: line 200 (sasl_callback): assertion failed: (!client->destroyed || reply == SASL_SERVER_REPLY_CLIENT_ERROR || reply == SASL_SERVER_REPLY_MASTER_FAILED) Oct 10 04:48:48 alcor dovecot: imap-login: Disconnected (no auth attempts): [9896], NNN.NNN.NNN.NNN Oct 10 04:48:48 alcor dovecot: imap-login: Disconnected (no auth attempts): [9895], NNN.NNN.NNN.NNN Oct 10 04:48:48 alcor dovecot: pop3-login: Disconnected (no auth attempts): [9893], NNN.NNN.NNN.NNN >> I missed this originally, but on reflection I notice in the logs that >> every time the "record size too small" error appears, inevitably the >> user involved is over disk quota and out of grace period. For >> example, > >Yes, this is most likely what's the problem. I remember testing v1.0 >quite a lot in "out of disk space" conditions, but I haven't really >done any such testing with v1.1. I'll try that and see if I can get >these problems reproduced and fixed. Thank you! :-) Please let me know if there's anything I can do to help. - Steven ________________________________________________________________________ Steven Winikoff | Concordia University | "Hanging is too good for a man who Montreal, QC, Canada | makes puns; he should be drawn and smw(a)alcor.concordia.ca | quoted." http://alcor.concordia.ca/~smw | - Fred Allen

2 2

Re: [Dovecot] Corrupted transaction log file / record size too small
by Steven Winikoff 18 Oct '08

18 Oct '08

>> I've been working around the problem by deleting the contents of >> ~user/.imap for affected users, but I'd really prefer to fix it >> properly. :-) Any suggestions would be gratefully received. > >I think this should get fixed by itself? Although the first login fails, >the next one should succeed. Yes, that's right. I didn't realize it at first, because we were also seeing other problems (eg assertion failure at line 39 of index-sync.c) which did require the index to be deleted. I've since made the following changes: 1) commented out the assertion at line 39 of index-sync.c (as per http://www.nabble.com/dovecot-panic-after-upgrade-1.0.15-to-1.1.2-td1909850…) 2) recompiled dovecot without optimization (ie, gcc -O0 instead of -O2) (as per http://www.mail-archive.com/dovecot@dovecot.org/msg12936.html) 3) reverted to using flock for file locking instead of fcntl (we'd been using flock with dovecot 1.0.10; 1.1.3 used fcntl by default in a couple of places, so I changed it back to see what would happen) After this, we've seen fewer problems, but there are still the occasional ones: - the original corrupted transaction log error which prompted this thread - we still see the occasional assertion failure at line 1091 of index-mail.c; this is the one that I'd hoped to solve by recompiling without optimization, but at least it seems to be happening less frequently than before - this doesn't happen often, but once in a while we see assertion failures at line 163 of src/pop3-login/client-authenticate.c or line 200 of src/imap-login/client-authenticate.c >Can you reproduce this by running imaptest (on a test account)? >http://imapwiki.org/ImapTest Actually this and your other suggestions may not be necessary; I think I just realized what's been going on. I missed this originally, but on reflection I notice in the logs that every time the "record size too small" error appears, inevitably the user involved is over disk quota and out of grace period. For example, Oct 3 17:52:21 alcor dovecot: imap[14973] XXXX, NNN.NNN.NN.NNN: Corrupted transaction log file /home/XXXX/mail/.imap/sent-mail/dovecot.index.log: record size too small (type=0xcd91, offset=8180, size=0) Oct 3 17:52:21 alcor dovecot: imap[14973] XXXX, NNN.NNN.NN.NNN: fscking index file (in-memory index) Oct 3 17:52:21 alcor dovecot: imap[14973] XXXX, NNN.NNN.NN.NNN: Transaction log got desynced for index (in-memory index) Oct 3 17:52:21 alcor dovecot: imap[14973] XXXX, NNN.NNN.NN.NNN: Disconnected: IMAP session state is inconsistent, please relogin. bytes=169/1848 Oct 3 17:52:22 alcor dovecot: imap-login: Login: [14998], XXXX, NNN.NNN.NN.NNN Oct 3 17:52:22 alcor dovecot: wrapper[15023]: imap, XXXX, NNN.NNN.NN.NNN Oct 3 17:52:22 alcor dovecot: imap[15023] XXXX, NNN.NNN.NN.NNN: open(/home/XXXX/mail/.imap/CFI-Howe/.temp.alcor.15023.e786c194b1dcc08c) failed: Disk quota exceeded Having seen this, I went back to the saved log for September 30th (the one containing the excerpt I pasted into my original message in this thread) -- and interestingly, I found that the quota failure wasn't recorded there. I don't know what was different about that occurrence, but everything I've seen recently suggests that "record size too small" is due to interaction with the quota system. ...so this is where I admit that I have indeed read http://wiki.dovecot.org/Quota/FS; unfortunately, the only user-writable file system on this machine that doesn't have (or need to have!) disk quotas enabled is /var/tmp, which doesn't seem to be a suitable place for dovecot indexes. Under the circumstances, are you still interested in seeing ImapTest results and a backtrace? If so, should I do that before or after upgrading to 1.1.4? Thanks, - Steven ________________________________________________________________________ Steven Winikoff | Concordia University | "The end of the world will occur at Montreal, QC, Canada | 3:00 p.m., this Friday, with symposium smw(a)alcor.concordia.ca | to follow." http://alcor.concordia.ca/~smw | - fortune(6)

2 2

[Dovecot] Request for help with new plugin
by John Lightsey 18 Oct '08

18 Oct '08

Hi there, I was having lots of trouble with the normal expire plugin so I decided to try and come up with a plugin that handles the trash directory in the same way as Courier (when the user logs out it should clean messages from the trash that have been there for more than X days.) I used the expire and trash plugins as a guide but there are probably a number of things done wrong here and I have plenty of questions. To use this you'd need to run autoreconf for the autotools scripts, compile, make, make install, then add "autoexpire" to the imap/pop3 mail_plugins lists and "autoexpire = Trash 7" to the plugin section. 1. Is there any documentation of how the hook system and virtual mailboxes work outside of the source code? 2. I'd like the Trash cleanup to occur at logout, but the closest I could find was mailbox close. This makes the behavior a little quirky. It seems like Dovecot closes the mailbox each time it performs an operation on it, so when the client gets a list of mail in the box it does a close and the oldest items in the returned list will actually be expunged. 3. Is SAVE_DATE the correct field to be looking for here? I want the expiration to be based on the amount of time the letter has spent in the trash folder. 4. For searching through the Trash folder, SEARCH_BEFORE doesn't seem to match up with SAVE_DATE. Is there some other way to limit the search results to the dates that will fall before a certain SAVE_DATE value? J.D.

3 4

[Dovecot] Multiple "mail" field in one LDAP account
by Proskurin Kirill 18 Oct '08

18 Oct '08

Hello all! #pkg_info | grep dovecot dovecot-1.1.3_1 dovecot-managesieve-0.10.3 dovecot-sieve-1.1.5_1 Im trying to do this: Im have a LDAP account with multiple "mail" field like this(many strings cuted): dn: uid=k.proskurin,ou=Users,dc=Moscow,dc=CAS uid: k.proskurin userPassword: {CRYPT}$1$ETadxf6G$O2bNUQVSHxksUp08V/iY2. mail: sysadmin(a)domain.off mail: proskurin-kv(a)domain.off My dovecot user "mail" as login: user_filter = (&(objectClass=mailUser)(mail=%u)) pass_attrs = mail=user,userPassword=password pass_filter = (&(objectClass=mailUser)(mail=%u)) All seems work well before im add second mail field in account. In logs in see this: ---- Info: auth(default): client in: AUTH 1 PLAIN service=imap secured lip=172.16.1.19 rip=172.16.1.19 lport=143 rport=64575 resp=<hidden> Info: auth(default): ldap(proskurin-kv(a)domain.off,172.16.1.19): pass search: base=dc=CAS scope=subtree filter=(&(objectClass=mailUser)(mail=proskurin-kv(a)domain.off)) fields=mail,userPassword Info: auth(default): auth(proskurin-kv(a)domain.off,172.16.1.19): username changed proskurin-kv(a)domain.off -> sysadmin(a)domain.off Info: auth(default): auth(sysadmin(a)domain.off,172.16.1.19): username changed sysadmin(a)domain.off -> proskurin-kv(a)domain.off Info: auth(default): ldap(proskurin-kv(a)domain.off,172.16.1.19): result: userPassword(password)=<hidden> mail(user)=sysadmin@domain.off/proskurin-kv@domain.off Info: auth(default): client out: OK 1 user=proskurin-kv(a)domain.off Info: auth(default): master in: REQUEST 8 38582 1 Info: auth(default): master out: USER 8 proskurin-kv(a)domain.off uid=1002 gid=1002 home=/var/spool/dovecot/domains/domain.off/proskurin-kv Info: imap-login: Login: user=<proskurin-kv(a)domain.off>, method=PLAIN, rip=172.16.1.19, lip=172.16.1.19, secured And in my Thunderbird then im log by sysadmin(a)domain.off in see proskurin-kv(a)domain.off mail. ---- Oh - what is happening? Why it is jump from one to another? They have differnent login and same password. If it is possible to make this work well? -- Best regards, Proskurin Kirill

2 4

[Dovecot] REQ: Dovecot Authentication Problem with PAM
by Selim Kraneis 18 Oct '08

18 Oct '08

Hi , I have a problem with Authentication.I don't no, where is the problem,Can anyone help me undestand this problem. Thanks in Advance here is some files: The configuration file dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap pop3 login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login mail_privileged_group: mail mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: mechanisms: plain login debug: yes debug_passwords: yes passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /etc/postfix/private/auth mode: 432 user: postfix group: postfix master: ############################################### here is log file /var/mail/mail.log Oct 17 13:18:00 animal dovecot: Dovecot v1.0.rc15 starting up Oct 17 13:18:40 animal dovecot: auth(default): client in: AUTH^I1^IPLAIN^Iservice=IMAP^Isecured^Ilip=127.0.0.1^Irip=127.0.0.1^Iresp=AHRlc3R1c2VyQGNoZWZzLW9ubGluZS5kZQBmaW5kdXMwNQ== Oct 17 13:18:42 animal dovecot: auth(default): pam(testuser(a)blabla.de,127.0.0.1): pam_authenticate() failed: User not known to the underlying authentication module Oct 17 13:18:43 animal dovecot: auth(default): client out: FAIL^I1^Iuser=testuser(a)blabla.de Oct 17 13:20:08 animal dovecot: imap-login: Aborted login: user=<testuser(a)blabla.de>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 17 13:23:13 animal dovecot: pop3-login: Aborted login: rip=88.198.25.52, lip=192.168.3.2 Oct 17 13:34:14 animal dovecot: pop3-login: Disconnected: Inactivity: rip=88.198.25.52, lip=192.168.3.2 Oct 17 13:44:13 animal dovecot: pop3-login: Disconnected: Inactivity: rip=88.198.25.52, lip=192.168.3.2 #################################################################################### here is log file /var/log/auth.log Oct 17 13:18:40 animal dovecot-auth: (pam_unix) check pass; user unknown Oct 17 13:18:40 animal dovecot-auth: (pam_unix) authentication failure; logname= uid=0 euid=0 tty=dovecot ruser= rhost=127.0.0.1 ############################################################################ here is the configuration file for PAM /etc/pam.d/dovecot #%PAM-1.0 auth required pam_unix.so nullok account required pam_unix.so ################################ Kraneis _________________________________________________________________________ In 5 Schritten zur eigenen Homepage. Jetzt Domain sichern und gestalten! Nur 3,99 EUR/Monat! http://www.maildomain.web.de/?mc=021114

2 1

[Dovecot] deliver not picking up INDEX setting?
by Tim Bishop 18 Oct '08

18 Oct '08

I'm using the post-login script approach to give more customisation to where our users can store their mail. It detects the location and type of the mailbox at runtime and passes it through using the environment to imapd. This works great. However, I can't seem to make deliver do the same. I pass it the same MAIL and NAMESPACE settings in the environment: MAIL=maildir:/home/cur/tdb/Maildir:INDEX=/var/state/dovecot-indexes/tdb NAMESPACE_1=maildir:/home/cur/tdb/Maildir:INDEX=/var/state/dovecot-indexes/tdb NAMESPACE_1_INBOX=1 NAMESPACE_1_LIST=1 NAMESPACE_1_PREFIX=INBOX. NAMESPACE_1_SEP=. NAMESPACE_1_SUBSCRIPTIONS=1 NAMESPACE_1_TYPE=private (plus some others set by my MTA) So INDEX appears to be set correctly. deliver does correctly pick up the mailbox location and has no trouble delivering mail, but the indexes are put in the Maildir directory and not under the indexes directory. Is it possible to make deliver respect the INDEX setting? Thanks, Tim. -- Tim Bishop http://www.bishnet.net/tim/ PGP Key: 0x5AE7D984

2 1