May 2006 - dovecot - dovecot.org

[Dovecot] statfs() error message
by John Wong 05 May '06

05 May '06

i use openbsd/i386, dovecot-1.0b7 i see the error message in maillog dovecot: statfs(mail/username) failed: No such file or directory i guess the statfs() can not find the directory, because i run dovecot-imap in chroot userdb static { args = uid=34567 gid=34567 home=/var/./mail } i am sure, i have this directory "/var/mail/username", and i add "nfs_check = no" to dovecot.conf, the error message will gone

1 0

[Dovecot] .imap locaction
by Obantec Support 05 May '06

05 May '06

Hi is it possible to have the .imap directory and sub-directory located under the same directory as mbox users. i.e /var/spool/mail/%u is where mbox files are i would like to use /var/spool/maildir/%u/.imap reason being i do not want my users /home/username used for anything otherthan their website. how big do the files under .imap get? Mark

2 1

[Dovecot] sigsev with postfix + dovecot SASL
by Udo Rader 05 May '06

05 May '06

hi, I am just playing a bit with the dovecot SASL plugin for postfix and so far my tests have been very successfull, can't wait to get the cyrus-sasl beast replaced. However, I found a potential problem when doing some "illegal" stuff on the postfix side: -------CUT------- cerberus:/var/log# telnet smtptest 25 Trying 192.168.99.99... Connected to smtptest.bestsolution.at. Escape character is '^]'. 220 smtptest.bestsolution.at ESMTP Postfix (bestsolution.at GmbH) EHLO localhost 250-smtptest.bestsolution.at 250-PIPELINING 250-SIZE 51200000 250-ETRN 250-AUTH PLAIN DIGEST-MD5 CRAM-MD5 250-AUTH=PLAIN DIGEST-MD5 CRAM-MD5 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN AUTH somestring 535 5.7.0 Error: authentication failed: Connection lost to authentication server -------CUT------- dovecot logs this: -------CUT------- dovecot: Apr 27 10:27:36 Error: auth(default): BUG: Authentication client 4315 requested unsupported authentication mechanism somestring dovecot: Apr 27 10:27:36 Error: child 445 (auth) killed with signal 11 -------CUT------- I am very aware that "AUTH somestring" is not valid in the given context, but dovecot should not sigsev IMO. dovecot is 1.0-beta7. regards Udo Rader b e s t s o l u t i o n . a t EDV Systemhaus GmbH ------------------------------------------------------------------------ udo rader technischer leiter/CTO mobile +43 660 5263642 ------------------------------------------------------------------------ eduard-bodem-gasse 8/3 A-6020 innsbruck fax +43 512 935833 http://www.bestsolution.at phone +43 512 935834

2 1

[Dovecot] auth-request.c: assertion failed: (*name != '\0')
by Tom Sommer 05 May '06

05 May '06

I upgraded to beta7 from alpha4, and got this error during the auth process: dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=0.0.0.0 rip=0.0.0.0 resp=<hidden> dovecot: auth-worker(default): sql(webmaster(a)example.com,0.0.0.0): query: SELECT username as user, NULL as password FROM users WHERE username = 'webmaster(a)example.com' AND password = PASSWORD('mypassword') dovecot: auth(default): file auth-request.c: line 723 (auth_request_set_field): assertion failed: (*name != '\0') dovecot: child 8552 (auth) killed with signal 6 My SQL conf: password_query = SELECT username as user, NULL as password FROM users WHERE username = '%u' AND password = PASSWORD('%w') as advised in a previous discussion in this list Regards -- Tom Sommer

3 4

[Dovecot] maildir format
by DINH Viêt Hoà 05 May '06

05 May '06

Hello Timo and other dovecot-dev or users, It looks like Dovecot accepts (with APPEND command) messages that begins with 'From[SPACE]' line, which are not valid from RFC 2822 point of view. Additionnally, Dovecot will store them as they are APPENDed, I mean with the starting 'From[SPACE]' line, which generates a bad Maildir format. http://www.qmail.org/man/man5/maildir.html states the following : << Each file in new is a newly delivered mail message. The modification time of the file is the delivery date of the message. The message is delivered without an extra UUCP- style From_ line, without any >From quoting, and without an extra blank line at the end. The message is normally in RFC 822 format, starting with a Return-Path line and a Delivered-To line, but it could contain arbitrary binary data. It might not even end with a newline. >> -- DINH Viêt Hoà

2 3

[Dovecot] Solution: NFS & Dovecot!
by Apps Lists 05 May '06

05 May '06

Hi folks! It looks like Timo nailed down the NFS issues we've been seeing here in last night's CVS build. Anyone running Dovecot in a high-usage environment should check this out. Here are some relevant ChangeLog updates that seem to address the problem: 2006-05-02 11:11 Timo Sirainen <timo.sirainen(a)movial.fi> * src/lib-storage/index/maildir/: maildir-save.c, maildir-storage.h, maildir-sync.c, maildir-uidlist.c, maildir-uidlist.h: Adding mail to index while saving it had a race condition. Fixing it required a bit larger changes. Switched uidlist/index locking order so that uidlist is now locked first. 2006-05-02 11:04 Timo Sirainen <timo.sirainen(a)movial.fi> * src/lib-index/: mail-index-private.h, mail-index-sync-update.c, mail-index.c: mmap_disable: When syncing in-memory index from transaction log, we didn't skip external transactions which were already been in our in-memory mapping, causing "Append with UID n, but next_uid = m" errors. The build is available here: http://dovecot.org/nightly/dovecot-20060503.tar.gz Thus far, I've seen no complaints of corrupted indexes or core dumps. This is absolutely fantastic. As always... hats off to Timo. Great work! Steve

3 2

[Dovecot] "fchown() failed with file" and Operation not permitted with indexes
by Gavin Henry 05 May '06

05 May '06

Dear all, Getting lots of these errors in our maillog with the INDEX changed: dovecot: IMAP(ghenry): fchown() failed with file /home/ghenry/Maildir/index/.INBOX/dovecot.index.tmp: Operation not permitted For .log and .cache as well. We have: location = maildir:/home/%u/Maildir:CONTROL=%h/Maildir/control:INDEX=%h/Maildir/index I looked in safe-mkdir.c and saw: fchown() failed for (line 42) to change the owner first, so don't know why we are getting this error? Thanks, Gavin. -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 742001 E ghenry(a)suretecsystems.com Open Source. Open Solutions(tm). http://www.suretecsystems.com/

3 5

[Dovecot] dovecot LDA and pop3 session lock question
by Ken A 05 May '06

05 May '06

If pop3_lock_session = yes, how does Dovecot LDA handle the situation when the pop3 mbox is locked? Does it requeue mail for later delivery immediately (EX_TEMPFAIL), or wait until mbox_lock_timeout? Thanks, Ken A. Pacific.Net

2 2

[Dovecot] Problems with Dovecot 1.0 beta7 rpm form atrpm for RHEL4
by Oliver Schulze L. 05 May '06

05 May '06

Hi, I just want to install dovecot 1.0 beta7 from atrpm and noted that it depends on a non official dependency. If you have RHEL4 (Centos) 4.3 fully updated and you try to install: http://dl.atrpms.net/all/dovecot-1.0-0_10.99.beta7.el4.at.i386.rpm You get this error: # rpm -ivh dovecot-1.0-0_10.99.beta7.el4.at.i386.rpm error: Failed dependencies: openssl >= 0.9.7f-4 is needed by dovecot-1.0-0_10.99.beta7.el4.at.i386 The lates official openssl version for RHEL 4.3 is: # rpm -q openssl openssl-0.9.7a-43.8 I think I can solve this problem by compiling the src.rpm, but I get this error: # rpmbuild --rebuild --target=i686 --clean dovecot-1.0-0_10.99.beta7.el4.at.src.rpm Installing /opt/shares/tmp/dovecot-1.0-0_10.99.beta7.el4.at.src.rpm Building target platforms: i686 Building for target i686 error: line 4: Tag takes single token only: Release: 0_%atrelease 10.99.beta7 How can I compile the .src.rpm from atrpm? It seems that there is an error in the spec file: This line: Release: 0_%atrelease 10.99.beta7 should it looks like this: Release: 0_%{atrelease}10.99.beta7 Many thanks Oliver -- Oliver Schulze L. <oliver(a)samera.com.py>

3 13

[Dovecot] support for no modules, patch
by Jens Laas 05 May '06

05 May '06

--- src/lib/module-dir.c~ 2006-02-26 13:14:12.000000000 +0100 +++ src/lib/module-dir.c 2006-05-05 11:09:11.000000000 +0200 @@ -255,8 +255,8 @@ } #else - struct module *module_dir_load(const char *dir __attr_unused__, + const char *module_names __attr_unused__, bool require_init_funcs __attr_unused__) { i_error("Dynamically loadable module support not built in"); ----------------------------------------------------------------------- 'Old C programmers don't die ... they're just cast into void*' ----------------------------------------------------------------------- Jens Låås Email: jens.laas(a)data.slu.se Department of Computer Services, SLU Phone: +46 18 67 35 15 Vindbrovägen 1 P.O. Box 7079 S-750 07 Uppsala SWEDEN -----------------------------------------------------------------------

1 0