- dovecot - dovecot.org

[Dovecot] 1.0-test62
by Timo Sirainen 31 Jan '05

31 Jan '05

http://dovecot.org/test/ Nothing big, just random fixes. - Crashfixes in keyword code - -std=gnu99 wasn't working well in all systems, configure now checks for it - FreeBSD sendfile() calling was broken sometimes. No need to remove #define HAVE_FREEBSD_SENDFILE anymore. - FETCH BODY[] wasn't setting \Seen flag. - LDAP fixes (by Kazuo Moriwaka) - Don't crash if client disconnects while APPENDing or FETCHing - mbox: write dummy message if all mails were expunged - POP3: RETR wasn't setting \Seen flag. - Treat ::ffff:127.* addresses as secure - If maildir-shared exists in the Maildir root, copy it for each created mailbox. - inetd startup fix (by Magnus Holmgren) - passwd-file wasn't working as userdb (by Joseph Tam)

1 0

[Dovecot] How to run in debug format for SSL testing?
by Jeff A. Earickson 31 Jan '05

31 Jan '05

Help, new to dovecot... I want to get some output from my test sessions to confirm that SSL pop and imap are working. How does one get debug output from dovecot? How does one see that dovecot is using SSL in a transaction? I configured dovecot 0.99.13 with: CC=gcc CPPFLAGS=-I/opt/openssl/include LDFLAGS=-L/opt/openssl/lib \ ./configure --prefix=/opt/dovecot --with-ssl=openssl \ --with-ssldir=/opt/openssl/ssl --with-rawlog --enable-debug > configure.out on Solaris 9. BTW, if I compile with Sun's StudioOne version 8 compiler, I get a core dump of dovecot-auth into /var/run/dovecot. The gdb backtrace looks like: gdb dovecot-auth core GNU gdb 5.2.1 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "sparc-sun-solaris2.8"... (gdb complaints about lack of debug symbols from numerous libs snipped out) Core was generated by `dovecot-auth'. Program terminated with signal 10, Bus error. #0 0x0002b64c in pam_child_input () (gdb) backtrace #0 0x0002b64c in pam_child_input () #1 0x00036c68 in io_loop_handler_run () #2 0x00035e5c in io_loop_run () #3 0x00025940 in main () The code works when compiled with gcc 3.4.3. Jeff Earickson Colby College

2 3

[Dovecot] Corrupted mailboxes
by Vincent Jaussaud 31 Jan '05

31 Jan '05

Hello, We are currently facing some weird problems, and although it may not be directly related to dovecot, I hope some of you guys may have a clue on this. We used to have a POP/IMAP server running Fedora Core1, with dovecot 0.99.13 (DAG). Everything was working fine, until an hardware problem forced us to install a new server, on another machine. We installed a fresh new Fedora Core 3 box, running both sendmail 8.13.1, procmail 3.22 and dovecot 0.99.13. Now, we are seeing strange errors in our dovecot logfiles. It seems to happen randomely, but always on the same mailboxes. The following error is logged: pop3(username): Jan 27 17:26:46 Error: Error syncing mbox file /var/spool/mail/szameitatd: LF not found where expected pop3(username): Jan 27 17:26:46 Error: Error indexing mbox file /var/spool/mail/username: LF not found where expected pop3(username): Jan 27 17:26:46 Error: Couldn't open INBOX: Internal error occured. Refer to server log for more information. [2005-01-27 17:26:46] People having that problem are able to login, but cannot retrieve new mails. Clients simply says no new mails are available. We tried to remove completely the mailbox file, waiting for procmail to create a new, but after a few minutes, the problem happens again. We cannot reproduce the bug with a particular mail; it seems the problem come from nowhere. Verbosing procmail didn't helped either. The only way to fix it when this happens, is to manually edit the file, and remove the first line feed at the very beginning of the mailbox file. I saw one post in the mailing list with the same problem, and we tried the "mail_extra_groups = mail" workaround, but that didn't help either. I actually think this has nothing to do with my problem :) We have around 500 mailboxes, and only a couple of them (3-5) do have the problem. Any idea how this can happen ? Any suggestions ? Thanks ! Vincent. -- Vincent Jaussaud Kelkoo.com Security Manager email: tatooin(a)kelkoo.com GPG key: 1024D/3BFE3FC7 2002-02-07 "Those who desire to give up freedom in order to gain security will not have, nor do they deserve, either one." -- President Thomas Jefferson. 1743-1826

2 3

[Dovecot] Execute Query after Logon ...
by wiki kaha 31 Jan '05

31 Jan '05

Hello list, is there a possibility to submit a query after a login. I use this feature in tpop3d to write a popb4smtp log into mysql. I would like to replace tpop3d with dovecot for pop3 and imap. Therefor I would need something similar. Thanks for answers. Regards Karl-Heinz __________________________________ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail

4 6

[Dovecot] kqueue errors in maillog
by Chris Phillips 31 Jan '05

31 Jan '05

Hello Dovecot, Version: dovecot-1.0-test61 OS: FreeBSD 5.3-RELEASE i386 Client: Mozilla Thunderbird 1.0 (on WinXP, FreeBSD & Mac OS X) The maillog entries concerning me: - Jan 30 16:16:37 venus dovecot: imap-login: Login: user [10.6.8.3] Jan 30 16:16:37 venus dovecot: imap-login: couldn't remove filter with kqueue: Bad file descriptor Jan 30 16:16:37 venus dovecot: IMAP(user): couldn't remove filter with kqueue: No such file or directory I see these messages many times in the maillog, with the client(s) idle (no interaction from me). Please can anyone shed any light on something that I may have neglected to do on installation, or perhaps what might be happening/wrong? Regards, Chris Phillips. Scanned for viruses by MailDefender

2 1

[Dovecot] Re: Dovecot doesn't call pam_open_session, thus dodging
by Chris L. Franklin 30 Jan '05

30 Jan '05

Forgot to ask, can this patch be added into dovecot for the next update ? (just to make life a little easier for us rpm'ers) -- Chris L. Franklin -- ----- Original Message ----- From: "Chris L. Franklin" <cfranklin(a)nomadcf.com> To: <dovecot(a)dovecot.org> Sent: Sunday, January 30, 2005 1:49 PM Subject: RE: Dovecot doesn't call pam_open_session, thus dodging > This is great I've been wanting to get rid of my NFS mounts for some time and have just the user MailDirs be local to the web server. And this will help alot ! > > -- Chris L. Franklin -- > >> Message: 1 >> Date: Thu, 27 Jan 2005 16:08:28 -0700 >> From: Nicolas Lopez <nlopez(a)espri.arizona.edu> >> Subject: [Dovecot] Dovecot doesn't call pam_open_session, thus dodging >> pam_mkhomedir >> To: dovecot(a)dovecot.org >> Message-ID: <41F9746C.8080707(a)espri.arizona.edu> >> Content-Type: text/plain; charset="iso-8859-1" >> >> I hit a small snag using Dovecot-imapd smoothly in my environment >> with maildir and most of my accounts in LDAP. Since the accounts are >> created through a web interface on another server home directories on >> the mail server don't get created automatically. There's the handy pam >> module pam_mkhomedir.so to automagically create home directories, but >> unfortunatly Dovecot wasn't calling pam_open_session to run the session >> setup pam modules. I made a small patch to passdb-pam.c to call >> pam_open_session between pam_acct_mgmt and pam_get_item and now I my >> home dirs are automagically created and everyone is happy. >> >> So, I figured I'd share the little patch in case someone else finds it >> useful. My patch doesn't properly close the session which will probably >> iritate more advanced session modules that actually have something to >> clean up, oh well. >> >> Aside from manually having to create home directories Dovecot-imapd >> has been working really well for us for a number of months, I just >> finally got around to dealing with the home dir creation issue. >> >> - Nick Lopez >> nlopez(a)espri.arizona.edu >> -------------- next part -------------- >> A non-text attachment was scrubbed... >> Name: passdb-pam.c.diff >> Type: text/x-patch >> Size: 505 bytes >> Desc: not available >> Url : http://dovecot.org/pipermail/dovecot/attachments/20050127/ac7796ea/passdb-p… >

1 0

[Dovecot] RE: Dovecot doesn't call pam_open_session, thus dodging
by Chris L. Franklin 30 Jan '05

30 Jan '05

This is great I've been wanting to get rid of my NFS mounts for some time and have just the user MailDirs be local to the web server. And this will help alot ! -- Chris L. Franklin -- > Message: 1 > Date: Thu, 27 Jan 2005 16:08:28 -0700 > From: Nicolas Lopez <nlopez(a)espri.arizona.edu> > Subject: [Dovecot] Dovecot doesn't call pam_open_session, thus dodging > pam_mkhomedir > To: dovecot(a)dovecot.org > Message-ID: <41F9746C.8080707(a)espri.arizona.edu> > Content-Type: text/plain; charset="iso-8859-1" > > I hit a small snag using Dovecot-imapd smoothly in my environment > with maildir and most of my accounts in LDAP. Since the accounts are > created through a web interface on another server home directories on > the mail server don't get created automatically. There's the handy pam > module pam_mkhomedir.so to automagically create home directories, but > unfortunatly Dovecot wasn't calling pam_open_session to run the session > setup pam modules. I made a small patch to passdb-pam.c to call > pam_open_session between pam_acct_mgmt and pam_get_item and now I my > home dirs are automagically created and everyone is happy. > > So, I figured I'd share the little patch in case someone else finds it > useful. My patch doesn't properly close the session which will probably > iritate more advanced session modules that actually have something to > clean up, oh well. > > Aside from manually having to create home directories Dovecot-imapd > has been working really well for us for a number of months, I just > finally got around to dealing with the home dir creation issue. > > - Nick Lopez > nlopez(a)espri.arizona.edu > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: passdb-pam.c.diff > Type: text/x-patch > Size: 505 bytes > Desc: not available > Url : http://dovecot.org/pipermail/dovecot/attachments/20050127/ac7796ea/passdb-p…

1 0

[Dovecot] Problem with incorrect permissions with shared folders
by Dave Hatton 30 Jan '05

30 Jan '05

Hi, I'm seeing strange permissions when using an email client to create a new sub folder in a shared folder. This is dovecot-1.0test61 I have a directory /data/mail/shared owner=root group=shared permissions=2770 I have a file /data/mail/shared/dovecot-shared owner=root group-shared permissions=2660 User fred in in group shared (in /etc/group) My understanding is that now in my client I can create a folder called test and so I should have Folder /data/mail/shared/.test owner=fred group-shared permissions=2770 What I actually get is Folder /data/mail/shared/.test owner=fred group-shared permissions=2700 So dovecot doesn't appear to be honouring the permissions on dovecot-shared when creating folders. Also, when creating a folder in a shared folder should the create process automatically copy the dovecot-shared file down to the new folder to allow this to be shared as well? Thanks Daveh

2 3

[Dovecot] Problem using passwd-file authentication: does not read UID, GID
by Joseph Tam 30 Jan '05

30 Jan '05

There seems to be a problem when setting the default authentication method to passwd-file when they use the same file (which they frequently do): auth default { mechanisms = plain userdb = passwd-file /passwd passdb = passwd-file /passwd ... } The log files show dovecot: Jan 11 14:41:40 Info: Dovecot v1.0-test60 starting up dovecot: Jan 11 14:41:49 Info: auth(default): userdb(test,127.0.0.1): uid=0 gid=0 home= mail= dovecot: Jan 11 14:41:49 Error: Logins with UID 0 not permitted (user test) dovecot: Jan 11 14:41:49 Info: imap-login: Internal login failure: test [127.0.0.1] When userdb-passwd-file.c::passwd_file_init() is called, it compares the userdb passwd-file to the passdb passwd-file. If they are the same, it resets the time stamp to force a re-read of the password database during the next look-up. However, I believe it also needs to reset the userdb_pwf->userdb flag to TRUE or else it won't pick up the UID and GID and will use 0 instead: /* resync */ userdb_pwf->userdb = TRUE; /* Was FALSE in v1.0-test60 */ userdb_pwf->stamp = 0; Joseph Tam <tam(a)math.ubc.ca>

2 1

[Dovecot] STARTTLS and inetd
by Magnus Holmgren 30 Jan '05

30 Jan '05

Hi! When running dovecot from inetd (as per the instructions on http://wiki.dovecot.org/InetdInstall) imap-login and pop3-login thinks that TLS is enabled when in fact it isn't (we're connecting to port 110 and port 143, so the --ssl parameter isn't present). The reason for that is found in login-common/main.c:main(): > if (fd != -1) > (void)client_create(fd, &ip, TRUE); I added a flag which I set when ssl_proxy_new() is successfully called (see the following diff) and it seems to work fine. Is there any reason it shouldn't? What's the reason that the code is the way it is? -- Magnus Holmgren holmgren(a)lysator.liu.se P.S. Nice software! --- src/login-common/main.c 2003-11-08 16:15:42.000000000 +0100 +++ src/login-common/main.c.new 2005-01-15 17:49:53.000000000 +0100 @@ -220,7 +220,7 @@ { const char *name, *group_name; struct ip_addr ip; - int i, fd = -1, master_fd = -1; + int i, fd = -1, master_fd = -1, ssl = FALSE; is_inetd = getenv("DOVECOT_MASTER") == NULL; @@ -268,6 +268,7 @@ fd = ssl_proxy_new(fd, &ip); if (fd == -1) i_fatal("SSL initialization failed"); + ssl = TRUE; } else if (strncmp(argv[i], "--group=", 8) != 0) i_fatal("Unknown parameter: %s", argv[i]); } @@ -277,7 +278,7 @@ } if (fd != -1) - (void)client_create(fd, &ip, TRUE); + (void)client_create(fd, &ip, ssl); io_loop_run(ioloop); main_deinit();

2 1