- dovecot - dovecot.org

[Dovecot] Dovecot doesn't call pam_open_session, thus dodging pam_mkhomedir
by Nicolas Lopez 03 Feb '05

03 Feb '05

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

3 3

[Dovecot] Dovecot doesn't call pam_open_session, thus dodging pam_mkhomedir (fwd)
by Pasi Sjoholm 02 Feb '05

02 Feb '05

On Tue, 1 Feb 2005, it was written: > Nicolas Lopez wrote: > > 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. This patch closes the session.. but you will see many "opened session\n closed session"-lines on your log files. =) --cut-- --- src/auth/passdb-pam.c-org 2004-10-07 08:38:28.000000000 +0300 +++ src/auth/passdb-pam.c 2004-10-07 08:38:59.000000000 +0300 @@ -193,6 +193,18 @@ return status; } + if ((status = pam_open_session(pamh, 0)) != PAM_SUCCESS) { + *error = t_strdup_printf("pam_open_session(%s) failed: %s", + user, pam_strerror(pamh, status)); + return status; + } + + if ((status = pam_close_session(pamh, 0)) != PAM_SUCCESS) { + *error = t_strdup_printf("pam_close_session(%s) failed: %s", + user, pam_strerror(pamh, status)); + return status; + } + status = pam_get_item(pamh, PAM_USER, (linux_const void **)&item); if (status != PAM_SUCCESS) { *error = t_strdup_printf("pam_get_item(%s) failed: %s", --cut-- > I am running dovecot-0.99.13 on FC2 with pam_mkhomedir, and it has been > working fine. Not sure why you are having a problem. If I could just > figure out how to get Exim to do the same, I'd be happy :-) I think that Fedora has probably patched that version of dovecot which they are providing. -- Pasi Sjöholm

1 0

[Dovecot] test61 ./configure fails on OpenBSD 3.6
by Jamie Herre 02 Feb '05

02 Feb '05

Test version 61 ./configure is failing on my OpenBSD 3.6-stable system. The following corrects the problem. Would it be possible to test for gnu99 option before using it in subsequent tests? --- configure.in.orig Fri Jan 14 14:04:10 2005 +++ configure.in Fri Jan 14 16:44:22 2005 @@ -236,7 +236,7 @@ # say specifically that we want C99 features. # we can make use of GNU features as well, so don't use -std=c99. - CFLAGS="$CFLAGS -std=gnu99" + CFLAGS="$CFLAGS -std=gnu9x" fi dnl **

2 2

[Dovecot] dovecot-stable branch
by Timo Sirainen 01 Feb '05

01 Feb '05

To confuse Dovecot versioning even more, I've added "dovecot-stable" module into CVS. This is a version of Dovecot before the recent keyword changes but with several bugfixes backported to it. It's thought to be mostly stable. I intend to keep it updated with important bugfixes and with other simple bugfixes. Although I'm not sure if I'll make a large code base upgrade once keyword changes are stable. This is mostly meant for people who _really_ want to use 1.0-test codebase in production right now. Perhaps it's already more stable than 0.99.x, but upgrading should probably be made easier for v1.0. The dovecot-stable module itself is just a hack that will go away at some point. Once the main codebase is stable enough for v1.0 beta release, I'll make a stable branch instead in the main dovecot module (and probably with different RCS than CVS).

6 10

[Dovecot] vpopmail oddities
by Allen Parker 01 Feb '05

01 Feb '05

vpopmail + qmail + dovecot + thunderbird = huge headache ;-) alright, when attempting to connect via imaps to my .maildir based vpopmail install, $user@$domain is having some problems. /var/vpopmail/domains/$domain/$user is the location of the user folders with vpopmail and yet dovecot isn't exactly passing on the domain :-\ i'm not sure if this is a pebkac issue or if it's the root of something far more evil, but this is really bothering me after about 4 days. i've got dovecot set to auth against vpopmail and i'm running a dovecot authd. i know that i've given very little information, is there any way that someone can ping me back requesting the particular information they need to properly diagnose this? -- ________________________________________ To avoid being added to my spam filter: 1. Utilize list replies unless otherwise requested. 2. If you DO send me a personal email, use english. 3. HTML isn't cute. It belongs on the web, not in my inbox.

2 1

[Dovecot] mbox vs maildir
by poohba＠blkpoohba.dyndns.org 01 Feb '05

01 Feb '05

I am a little confused and maybe if I figure this out I will be able to get this to work. I am now able to get my pop3 working but not imap. My inbox is in /var/spool/mail/%u and my mail directory is /home/%u/mail and then all the 'folders' are there which are actually files. Is that maildir or mbox? Which do I have to use for dovecot? Or can I use whichever I choose. I would like to keep the setup I have and use IMAP but i am finding this very difficult. I find some places that say I have to convert what I have and other places that say I don't. Can someone please break it down for me.

3 6

[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

[Dovecot] Dovecot shared folder woes
by Dave Hatton 30 Jan '05

30 Jan '05

Hi I'm new to Dovecot so please be gentle with me. I did a search through the list archives but couldn't quite work out my problem. I have Dovecot installed and running and I can connect to it from my email clients (Outlook and Evolution) ... so looking good so far. I would like to setup three types (groups?) of mail store 1. A per user - e.g. Fred, Harry, Betty. (For my purposes they all have Unix Accounts on the mail server) 2. A public store which can contain folders that may be read and written to by any user who is authenticated 3. A per group store (e.g. accounts, sales, marketing) that may be read and written to by any user who is authenticated and is in the specified group Firstly, should this be possible with Dovecot? I have tried the following dovecot.conf parameters which I thought should do the trick ... --------------------- cut ------------------------- ### this should give each user a mail store default_mail_env = maildir:/var/mail/%lu/%u/Maildir ### Create Public mail store namespace public { separator = / prefix = Public/ location = /var/mail/public inbox = no hidden = no } ### Create mail store for accounts namespace shared { separator = / prefix = Accounts/ location = /var/mail/accounts inbox = no hidden = no } ### Create mail store for sales namespace shared { separator = / prefix = Sales/ location = /var/mail/sales inbox = no hidden = no } --------------------- cut ------------------------- I then: 1. created the directories /var/mail/{public,accounts,sales} 2. chgrp each one to a group (public,accounts,sales respectively) 3. chmod 770 each one 4. created a dovecot-shared in each one - chgrp and chmod appropriately And then restarted the server Now my problem When I try to connect from a client it fails and the tcp/ip connection dies When I look in /var/log/mail I see and error 89 (which I understand is a generic error) and IMAP(fred): Failed to create storage for 'Public/' with data: /var/mail/public What and I doing wrong? TIA Daveh

3 6

[Dovecot] mutt's new mail error
by Frédéric Gobry 30 Jan '05

30 Jan '05

Hi, I use dovecot 0.99.13-3 (debian testing) in conjunction with mutt (1.5.6-20040907+2, also debian), and mutt keeps reporting new mails in my subscribed folders, even when none is available. I've seen a report from december 2003 which seems to correspond http://dovecot.org/pipermail/dovecot/2003-December/002741.html In this thread, it seems that if I don't use INDEX=MEMORY, I should not suffer from the problem. My config uses default_mail_env = maildir:~/Mail:INDEX=/var/indexes/%d/%n Do you have a hint regarding this problem ? Would a traffic dump be useful ? Thanks in advance, Frédéric -- Frédéric Gobry Infoscience DIT-KIS / EPFL Tel: +41216932288 http://people.epfl.ch/frederic.gobry

2 1

[Dovecot] Help with Outlook2003 hanging on receiving email with attachments
by John Suter 30 Jan '05

30 Jan '05

I have one user running Outlook 2003 that hangs up when receiving emails with attachments. He is connecting using POP3. It's almost as if something is timing out and closing the connection. The client is on a 1500/256 DSL connection and the server is on a 768/768 fractional T-1. I have other users that connect with Outlook/POP3 without any problems. I have done a fresh install of Windows/Outlook to make sure it's not a client machine problem. Any help or ideas are greatly appreciated.

2 1

[Dovecot] maildir and /var/spool/mail/$USER
by Rob Campbell 29 Jan '05

29 Jan '05

I was told to use dovecot because it was easier than cyrus. I just upgraded from fc1 to fc3. I am not sure what fc1 used but I think it was cyrus and it worked perfect out of the box no configurations to do. The new cyrus-imapd is not so simple so I got dovecot. I see examples saying to use mbox=~/mail:INBOX=/var/spool/mail/%u but when I try that I cannot map mail folders that reside under ~/mail. I have tried default_mail_env = maildir:~/mail:INBOX=/var/spool/mail/%u default_mail_env = mbox:~/mail:INBOX=/var/spool/mail/%u which is the setup i have now. I get this error when trying to connect via evolution error while scanning folders in "IMAP server localhost" imap command failed. invalid mask. when I use default_mail_env = maildir:~/mail:INBOX=/var/spool/mail/%u the error i get is: This store does not support subscriptions or they are not enabled. I have an Inbox Junk and Trash folder under that account. When I set up outlook as pop3 it says it connects fine but it doesn't download any mail. When I try to subscribe to folders via Outlook it says that it cannot connect.

3 4

[Dovecot] mbox slowness in dovecot-1.0-test61
by Todd Burroughs 28 Jan '05

28 Jan '05

Hi, We're trying out Dovecot to see if it's a good replacement for UW-imapd. It seems to be very slow in opening an mbox file, even after it's been indexed. (I mean way slower than UW) Here's some info on the system: Dovecot-1.0-test61 SuSE 8.1, Linux kernel 2.4 Using NFS to access mail. I've tried turning off mmap, using dotlocking, using fcntl locking (lockd, etc. are running), mbox_dirty_syncs and mbox_very_dirty_syncs. Also tried putting the cache files on local disk. Compile options where basically default. I'm accessing it with pine, using several filters which tend to do SEARCH commands. Has anyone come across this? Maybe I'm missing something obvious??? Thanks, Todd Burroughs - Hostopia todd(a)hostopia.com

2 2

[Dovecot] Moving to Dovecot
by Matt Saunders 27 Jan '05

27 Jan '05

Hi there, I'm currently running IMAP with Courier and POP3 with Solid-POP3d. I'd like to migrate IMAP and POP3 to both use Dovecot. All this works fine in testing, except for the fact that I have two types of users for legacy reasons. One type of user has a Maildir-style inbox at ~/Maildir/ The other type has a mbox-style inbox at ~/Mailbox Is it possible to make Dovecot look for both? As far as I can see I'd need default_mail_env to accept multiple names, something like this: default_mail_env = maildir:~/Maildir/ mbox:~/Mailbox ...but it doesn't, so I'm stuck. :-( By default, Dovecot would work for me if I moved all my users' ~/Mailbox files to ~/mail/inbox but I really don't want to have to do that if at all possible as that'll break other custom stuff. Does anyone have any ideas? [ Apologies if this is a FAQ - I've had a good Google around and a look at the mail archives but can't find the info. ] TIA, Matt. -- Matt Saunders http://www.yoyo.org/matts/contacts/ "This is getting very silly. Too silly." - Professor Yaffle

3 2

[Dovecot] dovecot Maildir issue
by Tadghe Danu 26 Jan '05

26 Jan '05

I'm working on switching a domain from a Cyrus+postfix+procmail to Dovecot+postfix+procmail (using Maildir). It works great, except one small problem. I cannot figure out what the permissions for my Maildir directories should be. Can anyone point me to a doc or just a few pointers on what the permissions of the Maildirs should be? The only way I seem to be able to make this config work is to make the Maildirs world read+write. I can't exactly roll out a config like that :). I have postfix+procmail delivering to per user Maildirs under /var/mail. The permissions on /var/mail (pulled from the Wiki) are mail:/var/mail# ls -l /var/ |grep mail drwxrwxrwt 7 root mail 4096 Jan 25 22:37 mail The user Maildirs are set as: mail:/var/mail# ls -l /var/mail/ |grep tadghe drwxr-xrwt 2 tadghe tadghe 4096 Jan 25 22:36 tadghe When I try and access a mail box I get this in the logs an 25 22:35:34 mail imap(tadghe): opendir(/var/mail/tadghe/tmp) failed: Permission denied Jan 25 22:35:34 mail imap(tadghe): opendir() failed with file /var/mail/tadghe/new: Permission denied Jan 25 22:35:34 mail imap(tadghe): opendir() failed with file /var/mail/tadghe/new: Permission denied Jan 25 22:35:34 mail imap(tadghe): opendir(/var/mail/tadghe/tmp) failed: Permission denied Tadghe

2 1

RE: [Dovecot] disable_plaintext_auth, inetd, localhost, IPv6, and mapped addresses
by Villalovos, John L 26 Jan '05

26 Jan '05

dovecot-bounces(a)dovecot.org wrote: > Dovecot 0.99.13. > > I've noticed that the condition > > client->secured = ssl || > (IPADDR_IS_V4(ip) && strncmp(addr, "127.", 4) == 0) || > (IPADDR_IS_V6(ip) && strcmp(addr, "::1") == 0); > > (in (imap-login|pop3-login)/client.c) isn't enough, at least not when > running from inetd. The thing is that you will come across >>> ffff:127.0.0.1, which is secure, but not covered by the above. > > I thought I saw someting on this earlier, but in that case I > cant't find > it now. Yes I mentioned something about it in a message titled, "RE: [Dovecot] Plaintext Authentication from Localhost" On 19-Jan-2005. Seems to be a bug. At least it didn't work quite right for me. John

1 0

[Dovecot] imap://anonymous@dovecot.org/dovecot gets only 4 messages
by Sergey Ivanov 26 Jan '05

26 Jan '05

I have just trying to connect as user anonymous to the imap server at dovecot.org. And got only 4 messages in dovecot folder, one of them unread. Is it some problem at this server I have encountered? WBR, Sergey

1 1