- dovecot - dovecot.org

Re: [Dovecot] Problem with Dovecot LDA / Postfix
by Dominique Feyer 19 Jun '06

19 Jun '06

Thanks. The log is really useful ;-) **** deliver(info(a)lda.net4all.ch): Fatal: Running as root isn't permitted **** So it's not possible acutally to use LDA to deliver mail with different UID/GID So I need the change all the owner for my mail storage ... update the DB and restart the service ... it's bad !!! I need a lots of downtime to change the owner of 80Go data storage. So beafore that, I need to test the dovecot-sieve plugin from CVS. Next month a lot of my customer are in holiday and the need auto responders ;-) I try the dovecot-sieve plugin from the CVS and I have this error when i start make (configure as no error): libsieve.a(script.o)(.text+0xa23): In function `sieve_script_load': /usr/src/dovecot-sieve/src/libsieve/script.c:435: undefined reference to `map_refresh' libsieve.a(script.o)(.text+0xaf0): In function `sieve_script_unload': /usr/src/dovecot-sieve/src/libsieve/script.c:462: undefined reference to `map_free' libsieve.a(sieve.o)(.text+0x1e6e): In function `verify_flag': /usr/src/dovecot-sieve/src/libsieve/sieve.y:951: undefined reference to `imparse_isatom' collect2: ld returned 1 exit status make[3]: *** [sievec] Erreur 1 make[3]: Leaving directory `/usr/src/dovecot-sieve/src/libsieve' make[2]: *** [all-recursive] Erreur 1 make[2]: Leaving directory `/usr/src/dovecot-sieve/src' make[1]: *** [all-recursive] Erreur 1 make[1]: Leaving directory `/usr/src/dovecot-sieve' make: *** [all-recursive-am] Erreur 2 I have the same error last week when I try to build dovecot-lda with sieve script support from the CVS. I use Debian Sarge. I think the macro imparse_isatom is from the cyrus-imapd project. I try to install cyrus-dec and cyrus21-dev with apt-get ... but always the same error. Do you have a idea ? Le vendredi 16 juin 2006 à 10:44 -0400, My BSD a écrit : > On Fri, 16 Jun 2006 14:44:51 +0200 > Dominique Feyer <dfeyer(a)net4all.ch> wrote: > > > I have only postfix log (in syslog mail facility), no dovecot log from > > the LDA deliver binary (with mail_debug = yes), this is strange ... > > > > Jun 16 14:37:58 mail2 postfix/pickup[6014]: 5407F7FF3: uid=0 > > from=<root> Jun 16 14:37:58 mail2 postfix/cleanup[6073]: 5407F7FF3: > > message-id=<20060616123758.5407F7FF3(a)mail2.clm.net4all.ch> > > Jun 16 14:37:58 mail2 postfix/qmgr[6015]: 5407F7FF3: > > from=<root(a)localhost.localdomain>, size=326, nrcpt=1 (queue active) > > Jun 16 14:37:58 mail2 postfix/pipe[6076]: 5407F7FF3: > > to=<info(a)lda.net4all.ch>, relay=dovecot, delay=0, status=bounced > > (Command died with status 89: > > "/usr/local/dovecot-1.0-beta9/libexec/dovecot/deliver") > > > > Can i activate log for the LDA in the configuration file or deliver > > command argument in master.cf ? > > > ... > > My dovecot setup logs to a file, settings below: > > ---------------------------------------------- > mail_debug = yes > log_path = /var/log/dovecot/dovecot > info_log_path = /var/log/dovecot/dovecot.info > ---------------------------------------------- > > Make sure that the socket user has write access to the file, otherwise > it won't work (and thinking of it, also make sure that the socket user > also has access to the socket itself -- that was one of my biggest > problems before I got it to work). > > You may also want to add the following until you get it working: > > ---------------------------------------------- > auth_verbose = yes > auth_debug = yes > auth_debug_passwords = yes > ---------------------------------------------- > > Good luck! > -- Dominique Feyer Administrateur Système Ch. de la Colline 5bis CH-1007 Lausanne dfeyer(a)net4all.ch

3 4

[Dovecot] Problem with default_mail_env in beta9
by Andreas Schulze 19 Jun '06

19 Jun '06

Hallo, I am playing arround with dovecot I hat version 1.0.beta7 running fine. After installing beta9 there is a problem with default_mail_env setting. I have all users in ldap. there is an attribute "mailMessageStore" which contains a relative path to users maildir mailMessageStore: sca/ my mailer completes this relative pathinformation to /var/mail/sca/ therefor I setup default_mail_env to "maildir:/var/mail/%h" dovecot-ldap.conf includes "user_attrs = mailMessageStore=home,uidNumber=uid,gidNumber=gid" all fine in beta7 in beta9 I got this in my log: dovecot: Jun 16 14:50:22 Info: Dovecot v1.0.beta9 starting up dovecot: Jun 16 14:50:30 Info: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=127.0.0.1 rip=127.0.0.1 resp=random dovecot: Jun 16 14:50:30 Info: auth(default): ldap(sca,127.0.0.1): bind search: base=o=datev,c=de filter=(uid=sca) dovecot: Jun 16 14:50:30 Info: auth(default): client out: OK 1 user=sca dovecot: Jun 16 14:50:30 Info: auth(default): master in: REQUEST 1 30400 1 dovecot: Jun 16 14:50:30 Info: auth(default): ldap(sca,127.0.0.1): base=o=datev,c=de scope=subtree filter=(uid=sca) fields=mailMessageStore,uidNumber,gidNumber dovecot: Jun 16 14:50:30 Info: auth(default): master out: USER 1 t02985a home=sca/ uid=30014 gid=30007 dovecot: Jun 16 14:50:30 Info: pop3-login: Login: user=<sca>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1 dovecot: Jun 16 14:50:30 Error: POP3(sca): dovecot: Jun 16 14:50:30 Fatal: chdir(sca/) failed with uid 30014: Permission denied dovecot: Jun 16 14:50:30 Error: child 30407 (pop3) returned error 89 If I change user_attrs to "user_attrs = mailMessageStore=FOO,uidNumber=uid,gidNumber=gid" I got dovecot: Jun 16 14:54:36 Info: Dovecot v1.0.beta9 starting up dovecot: Jun 16 14:54:41 Info: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=127.0.0.1 rip=127.0.0.1 resp=random dovecot: Jun 16 14:54:41 Info: auth(default): ldap(sca,127.0.0.1): bind search: base=o=datev,c=de filter=(uid=sca) dovecot: Jun 16 14:54:41 Info: auth(default): client out: OK 1 user=sca dovecot: Jun 16 14:54:41 Info: auth(default): master in: REQUEST 1 30475 1 dovecot: Jun 16 14:54:41 Info: auth(default): ldap(sca,127.0.0.1): base=o=datev,c=de scope=subtree filter=(uid=sca) fields=mailmessagestore,uidNumber,gidNumber dovecot: Jun 16 14:54:41 Info: auth(default): master out: USER 1 sca uid=30014 gid=30007 dovecot: Jun 16 14:54:41 Info: pop3-login: Login: user=<sca>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1 dovecot: Jun 16 14:54:41 Info: POP3(sca): Effective uid=30014, gid=30007 dovecot: Jun 16 14:54:41 Info: POP3(sca): maildir: data=/var/mail//HOME_DIRECTORY_USED_BUT_NOT_GIVEN_BY_USERDB dovecot: Jun 16 14:54:41 Info: POP3(sca): maildir: root=/var/mail//HOME_DIRECTORY_USED_BUT_NOT_GIVEN_BY_USERDB, index=/var/mail//HOME_DIRECTORY_USED_BUT_NOT_GIVEN_BY_USERDB, control=, inbox= this inicates to me, that 1. homedirvariable is unset OK, because I assigned mailMessageStore to local FOO 2. default_mail_env is correct evaluated to maildir:/var/mail/%h Question: Why is default_mail_env not correct evalueted to maildir:/var/mail/sca/ if sca/ is set as homedir ? As mentions above, this worked fine with beta7 ... What do I wrong ??? My I provide more Informations ? -- Andreas Schulze DATEV eG, Paumgartner Strasse 6-14, D - 90429 Nürnberg Abt. Internet- und Securitydienste Telefon : +49 911 276 2648 Telefax : +49 911 276 7892 Mobil : +49 172 8122883 E-Mail : andreas.schulze_at_datev.de

2 3

[Dovecot] building dovecot lda on solaris 9
by lenny＠edpausa.com 18 Jun '06

18 Jun '06

Trying to build the latest CVS code of LDA against dovecot beta 9. Running autogen script I'm getting this message. I added the contents of /usr/local/share/aclocal/ to /usr/local/share/libtool/libltdl/aclocal.m4 #aclocaldir = /usr/local/share/aclocal/ aclocal_DATA = libmcrypt.m4 libtool.m4 ltdl.m4 but no luck. any advise ? /usr/local/share/aclocal/libmcrypt.m4:17: warning: underquoted definition of AM_PATH_LIBMCRYPT run info '(automake)Extending aclocal' or see http://sources.redhat.com/automake/automake.html#Extending-aclocal autom4te: unknown language: Autoconf-without-aclocal-m4 aclocal: autom4te failed with exit status: 1 autoheader: `lda-config.h.in' is unchanged You should add the contents of `/usr/local/share/aclocal/libtool.m4' to `aclocal.m4'. configure.in: no proper invocation of AM_INIT_AUTOMAKE was found. configure.in: You should verify that configure.in invokes AM_INIT_AUTOMAKE, configure.in: that aclocal.m4 is present in the top-level directory, configure.in: and that aclocal.m4 was recently regenerated (using aclocal). /usr/local/share/automake-1.9/am/depend2.am: am__fastdepCC does not appear in AM_CONDITIONAL /usr/local/share/automake-1.9/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL src/libsieve/Makefile.am:5: library used but `RANLIB' is undefined src/libsieve/Makefile.am:5: src/libsieve/Makefile.am:5: The usual way to define `RANLIB' is to add `AC_PROG_RANLIB' src/libsieve/Makefile.am:5: to `configure.in' and run `autoconf' again. /usr/local/share/automake-1.9/am/depend2.am: am__fastdepCC does not appear in AM_CONDITIONAL /usr/local/share/automake-1.9/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL

3 4

[Dovecot] LDA - Return-Path missing
by Timothy White 18 Jun '06

18 Jun '06

I seem to have a problem... Deliver relies on Return-Path headers? I tried sending emails from SquirrelMail, and Gmail, and both have caused the same issue (on the recieving end). (I am trying to test this part, the quota exceeded stuff). deliver(joeblogs): Return-Path missing, rejection reason: Quota exceeded I can post email headers, and stuff if needed. Does it need the Return-Path header, shouldn't it rely on the From address, if there is no Return-Path? Tim -- Linux Counter user #273956

2 1

[Dovecot] Dovecot randomly stops responding
by Miguel Saturnino 18 Jun '06

18 Jun '06

Hi! I'm running Dovecot 1.0beta7 on FreeBSD 6.0 (i386) and it randomly stops responding. To mitigate the problem I made a little ruby scripts which logs in to the POP3 server every 3 minutes and, in case of error (the errors are usually timeout or end of file errors), restarts Dovecot. Although this keeps this keeps things working, I'd like to figure out what is causing Dovecot to stop responding. Looking at the logs, nothing stands out except that there is always one or more of these messages just before Dovecot stops responding: Apr 20 19:25:00 zeus dovecot[62881]: pop3-login: Disconnected: Inactivity: rip=209.123.xxx.xxx, lip=64.21.xxx.xxx Any help debugging this would be greatly appreciated. Thanks, -- Miguel Saturnino <miguel.saturnino(a)teiadigital.pt>

2 3

[Dovecot] Maildir++ implementation issues.
by Apps Lists 18 Jun '06

18 Jun '06

Hi Timo and crew! I'm doing more testing with Dovecot and Maildrop today and have run across some strangeness. It appears as if Maildrop stores updates to the maildirquota file in a way that causes Dovecot to ignore them. In my test scenario, Dovecot just rebuilt my maildirsize file to the following: 0S 86213796 108 After delivering a few messages through Postfix -> Maildrop and have the following maildirsize file: 0S 86213796 108 5102 1 387708 1 5093 1 382406 1 3550 1 268337 1 Note the pretty formatting. These are spaces. Unfortunately, Dovecot seems to ignore these when reading the maildirsize file in maildirsize_parse(). It appears to be using sscanf to look for numeric entries: if (sscanf(*lines, "%lld %d", &bytes_diff, &count_diff) != 2) I've read and re-read the maildir++ specification at http://www.inter7.com/courierimap/README.maildirquota.html and can't understand why Maildrop implements things this way. Steve

2 1

[Dovecot] asserts and cores in beta3
by Jeff A. Earickson 18 Jun '06

18 Jun '06

My setup: Solaris 9, built with gcc 4.0.2 (I now have gcc 4.1 installed on my system, but have not rebuilt dovecot). A couple of asserts and cores in the last few days: Mar 1 09:25:13 emerald dovecot: [ID 107833 mail.error] imap(tmwillia): file mbox-sync.c: line 1471 (mbox_sync_do): assertion failed: (!sync_ctx->mbox->mbox_sync_dirty || (flags & MBOX_SYNC_UNDIRTY) == 0) Mar 1 09:58:44 emerald dovecot: [ID 107833 mail.error] imap(eewilson): file mbox-sync.c: line 1471 (mbox_sync_do): assertion failed: (!sync_ctx->mbox->mbox_sync_dirty || (flags & MBOX_SYNC_UNDIRTY) == 0) Mar 3 16:18:54 emerald dovecot: [ID 107833 mail.error] imap(tmwillia): file mbox-sync.c: line 1471 (mbox_sync_do): assertion failed: (!sync_ctx->mbox->mbox_sync_dirty || (flags & MBOX_SYNC_UNDIRTY) == 0) Backtraces from the two cores in hand are attached. I can do further poking at the cores if that would help. Jeff Earickson Colby College

2 2

[Dovecot] 1.0 beta3 not preserving X-Keyword header?
by Gregory K. Ruiz-Ade 18 Jun '06

18 Jun '06

We've been putting 1.0 Beta 3 through the paces on our test system, and one of our users pointed out to me that Thunderbird's "labels" behave strangely on the new server. In fact, there used to be a header added to the message via IMAP when Thunderbird placed a label on a message, but as of the switch from 0.99.11 to 1.0beta3, this label header is no longer placed in the message. Specifically, Thunderbird adds the "X-Keyword: $LabelN" header when you add a label to the message in tbird, where "N" is [1-9]. This works on dovecot 0.99.11 (RHEL4), but not on 1.0beta3. 1.0b3 doesn't seem to add this header at all, but rather seems to keep this information somewhere else. Perhaps in the .imap indexes? We're using mbox stores on the server. This was tested with both Thunderbird 1.0.7 (most widely deployed) and Thunderbird 1.5. Aditionally, we've found that if the .imap index directories are removed, all the Thunderbird labels on messages seem to get "confused", too. I.e., if the user uses multiple machines throughout the day, changes in one client may not be reflected in another, when the user moves to a different system. I'm still trying to get more details from the users, but have been doing preliminary testing that verifies this. One of the users complaining about this is my manager, who makes extensive use of Thunderbird's "Label" feature, so he's a bit nervous. :\ Another thing we've noticed is the potential for bad behavior if a use switches from the old dovecot to the new dovecot, which seems to be resolved if the .imap indexes are removed... Let me know what other information is needed, and I'll do my best to collect it. Gregory -- Gregory K. Ruiz-Ade Sr. Systems Administrator Computer Science and Engineering University of California, San Diego Office: EBU3b 1216 Phone: (858) 822-2625 E-mail: gkra(a)ucsd.edu

4 10

[Dovecot] RHEL 3 and quota problems...
by alan premselaar 18 Jun '06

18 Jun '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've just installed 1.0beta9 on my RHEL 3 system and am still getting the problems with the quota-fs returning "invalid argument". I think i've traced the problem down to differences in the quota versions based on the <sys/quota.h> files on RHEL 3 compared to FC3. on the system itself i'm using v2 quotas (with aquota.user and aquota.group files) however a diff of sysquota.h (copied from FC3 /usr/include/sys/quota.h) and <sys/quota.h> produces only the following: diff -u sysquota.h /usr/include/sys/quota.h - --- sysquota.h 2006-06-16 23:48:03.000000000 +0900 +++ /usr/include/sys/quota.h 2005-11-22 21:57:15.000000000 +0900 @@ -31,7 +31,7 @@ * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * - - * Version: $Id: quota.h,v 1.7.6.1 2005/07/18 02:07:37 roland Exp $ + * Version: $Id: quota.h,v 1.7 1999/10/19 03:05:21 drepper Exp $ */ #ifndef _SYS_QUOTA_H @@ -42,10 +42,10 @@ /* * Select between different incompatible quota versions. - - * Default to the version used by Linux kernel version 2.4.22 - - * or later. */ + * Default to the version used by Linux kernel version 2.4.21 + * or earlier (in RHEL version 1 is AS2.1, version 2 is RHEL3 and later). */ #ifndef _LINUX_QUOTA_VERSION - -# define _LINUX_QUOTA_VERSION 2 +# define _LINUX_QUOTA_VERSION 1 #endif /* if I edit the quota-fs.h file to load "sysquota.h" instead of <sys/quota.h> for the linux quotas, it won't compile. (i tried this instead of editing system header files directly) so I suspect the problem lies deeper than just the _LINUX_QUOTA_VERSION number being set incorrectly. incidently, the error I get compiling is this: quota-fs.c: In function `fs_quota_get_resource': quota-fs.c:214: structure has no member named `dqb_curblocks' make: *** [quota-fs.lo] Error 1 I haven't done any C programming in more than 20 years so I think I'm pushing the boundaries of my capabilities here, but I'm hoping this might just be enough information to help someone more qualified easily fix the problem and allow me to start using the FS based quota plugins to dovecot on my mail server. here are some details of my system if they're useful: # uname -a Linux <hostname_goes_here> 2.4.21-40.ELsmp #1 SMP Thu Feb 2 22:22:39 EST 2006 i686 i686 i386 GNU/Linux # more /etc/redhat-release Red Hat Enterprise Linux ES release 3 (Taroon Update 7) Thanks, Alan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEkshYE2gsBSKjZHQRAgrZAJ0cbZjSuPLV0T8C432EniCrkNw6tACgwKkz UZiSXsgXRb8w1Cc1XXXHWXs= =3CGX -----END PGP SIGNATURE-----

2 2

[Dovecot] [PATCH] Better detection for ioloop and notify
by Roy Marples 18 Jun '06

18 Jun '06

Hi List! Attached is a patch to configure.in to test that epoll, poll, inotify, kqueue and dnotify actually work. It also attempts to select the best one for you if none specified. This supercedes my previous patch in the re beta9 thread. Hopefully get this in Gentoo's beta9 ebuild soon. Thanks -- Roy Marples <uberlord(a)gentoo.org> Gentoo/Linux Developer (baselayout, networking)

3 3