- dovecot - dovecot.org

[Dovecot] Subscribe to root of Maildir namespace?
by Adam Tilghman 06 Oct '07

06 Oct '07

Our users currently make use of a single namespace, mbox format: namespace private { separator = / prefix = hidden = no inbox = yes location = mbox:~/:INBOX=/var/spool/mail/%u:INDEX=/var/spool/poptemp/dovecot/%u } I'd like to give them access to additional Maildir-format storage area, so to the above I've added: namespace private { separator = / prefix = archive/ hidden = no location = maildir:/newmail/%-3.3i/%u/:INDEX=/var/spool/poptemp/dovecot/%u.a-thumper-mail } I can set up subfolders of archive/, and they work as expected. I can also designate the "root" of archive/ as INBOX and that works properly. But "SUBSCRIBE archive" fails. Is it possible to subscribe to the "root" of this new Maildir heirarchy as if it were just another folder? If not, would this be a useful feature to add? Thanks, -- Adam Tilghman | Systems Support / Academic Computing | +1 858 822 0711 agt(a)ucsd.edu | University of California, San Diego | fax +1 858 534 7018

2 1

[Dovecot] problematic ACL with shared folders and maildir
by Dominik L. Borkowski 05 Oct '07

05 Oct '07

Hello, Recently we have been asked to deploy some shared imap folders within our instance of dovecot. However, we ran into a problem with how ACLs are implemented, and consequences regarding maildir++ mailboxes. Long story short: * IMAP clients sees the hierarchy as a tree: sample/1, where 1 is a child of sample * on the filesystem, sample/1 is represented as .sample and .sample.1, both on the same level This presents a problem: dovecot-acl file meant for sample mailbox does not apply to mailbox 1. In fact, a user with permissions to create mailboxes under sample, will not be able to access those mailboxes, once created. Wonder if anybody has been in a similar predicament, and found a solution. Any hints would be greatly appreciated. PS) I'm also documenting this process, maybe others will find it useful: https://collaboration.vbi.vt.edu/display/~dom/dovecot+-+shared+imap+folders -- Dominik L. Borkowski - Senior Systems Administrator Virginia Bioinformatics Institute - www.vbi.vt.edu

1 0

Re: [Dovecot] How to upgrade a running Dovecot?
by Jerry Yeager 05 Oct '07

05 Oct '07

On Oct 5, 2007, at 12:41 PM, dovecot-request(a)dovecot.org wrote: > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 5 Oct 2007 10:25:49 +0100 > From: Mike Brudenell <pmb1(a)york.ac.uk> > Subject: Re: [Dovecot] How to upgrade a running Dovecot? > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Message-ID: <B9A4EC9A-82C0-4250-BC98-606695775041(a)york.ac.uk> > Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed > > Hi, Jerry/et al - > Hello Mike, (stuff chomped out) > >>> Scenario 2: Altered SSL Certificates >>> ===================================== >>> I need to replace our current certificates and have prepared new >>> files containing the replacement certificate and private key. Am I >>> right in thinking that I can simply modify dovecot.conf to point at >>> the new files and send a HUP signal to dovecot? Specifically, will >>> new connections use the revised certificates, and existing >>> connections continue to work OK without interruption? >> >> Ehh not really, the auth child processes can be killed and new ones >> started. See your next scenario question. > > ...So here you're saying that although the "dovecot" master process > re-reads the configuration file, it doing so has no effect on the > existing authenticator child processes? And is it these processes > that are dealing with the SSL connection? ... I'd have thought it was > either the "imap-login" or "imap" processes? > Just to be clear about this for myself, (instead of relying on the 'ol saying 'that is how it used to work' -- because I am switching over to 1.1 from 1.0.n your question takes on new relevance for me as well) I tested this and yes it works as before, the new files seem to be used for the new connections (all of the dovecot auth processes are killed on the HUP signal -- dovecot itself just rereads the conf file and new auth listeners are started -- assuming that you use Dovecot for the auth mechanism to Postfix) and existing connections seem to handle things okay. I did find something new (or I have not noticed it before) If you kill (not just restart) the Dovecot process itself and restart it with existing connections (someone was connected to IMAPS when you killed Dovecot) Dovecot will not restart, complaining that port 993 is taken already. This happens regardless of the shutdown_clients = yes/no setting. This may be particular to the new version 1.1, I do not know. > Jerry

1 0

[Dovecot] Thunderbird and imap alerts
by Marco De Benedetto 05 Oct '07

05 Oct '07

Is Thunderbird supposed to show alerts sent via post-login scripts as in the wiki example? dovecot-imapd 1.0.5-1 (Debian) Thunderbird (Icedove) 2.0.0.4 (Debian) # dovecot -n|grep 'mail_executable(imap)' mail_executable(imap): /usr/local/sbin/dovecot-alert.sh # cat /usr/local/sbin/dovecot-alert.sh #!/bin/sh echo "* OK [ALERT] Hello World." exec /usr/lib/dovecot/imap Logging in with Thunderbird I get this alert: "Mail server imap.example.org is not an IMAP4 server". -- Thank you, Marco De Benedetto

1 0

Re: [Dovecot] How to upgrade a running Dovecot?
by Jerry Yeager 05 Oct '07

05 Oct '07

> Have you considered sending out a message to each user to the effect that on some day, darned-early a.m. the system will be offline for 30 minutes for maintenance (no incoming email will be lost, etc., etc.). > Message: 3 > Date: Thu, 4 Oct 2007 13:57:03 +0100 > From: Mike Brudenell <pmb1(a)york.ac.uk> > Subject: [Dovecot] How to upgrade a running Dovecot? > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Message-ID: <06B4C604-41E3-4061-96B2-C7C719E21D49(a)york.ac.uk> > Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed > > Greetings - > > Could someone confirm how to perform various upgrades on a live > system running Dovecot please? > > > Scenario 1: Change to dovecot.conf > =================================== > If I make a change to dovecot.conf am I right in thinking I can > simply send a HUP signal to the main dovecot process to get it to re- > read the configuration file and act on its revised content? > Yes, this is correct. > > Scenario 2: Altered SSL Certificates > ===================================== > I need to replace our current certificates and have prepared new > files containing the replacement certificate and private key. Am I > right in thinking that I can simply modify dovecot.conf to point at > the new files and send a HUP signal to dovecot? Specifically, will > new connections use the revised certificates, and existing > connections continue to work OK without interruption? > > Ehh not really, the auth child processes can be killed and new ones started. See your next scenario question. > Scenario 3: Software Upgrade > ============================= > I build a particular version of Dovecot into the tree /usr/local/ > dovecot-A.B.C and then have a symlink called "dovecot" pointing at > the this directory. To upgrade I can then build the new version > into /usr/local/dovecot-X.Y.Z and test. > > To actually switch over the live service to the new X.Y.Z version do > I need to: > > a) Totally shut down the old A.B.C version of Dovecot, thereby > breaking all > open connections for users? or > > b) Assuming I am using "shutdown_clients = no" can I just kill the > master > "dovecot" process and then start up the new version? > See the preface, do the update when you typically have few folks using the system -- which gives you fewer complaints from users should things break on their end. > Ideally I want existing connections to remain running, but new > connections to start up using the new X.Y.Z version of Dovecot. > > The comment for "shutdown_clients" implies this, but also says: > > "This however means that after master process has died, the > client > processes can't write to log files anymore." > > So if I understand this correctly then with "shutdown_clients = no" > in force then the sequence and behaviour is this? ... > > 1. Old version A.B.C of Dovecot running, clients can log > through the > master "dovecot" process to the logfiles. > > 2. Kill the old master "dovecot" process, start new X.Y.Z > version up. > > 3. New connections get served by version X.Y.Z. > Old connections DON'T get killed and can continue, BUT can > no longer > write anything to the logfiles? > > > With many thanks, > Mike B-) > > -- > The Computing Service, University of York, Heslington, York Yo10 > 5DD, UK > Tel:+44-1904-433811 FAX:+44-1904-433740 > > * Unsolicited commercial e-mail is NOT welcome at this e-mail > address. * > > > > >

4 3

[Dovecot] Compiling drac.c on a 64 bit system
by Robin Atwood 05 Oct '07

05 Oct '07

I have just installed dovecot and want to set up the drac interface. However, when I compile drac.c I get the following link errors; anybody know what the right compile options are for a 64 bit system? I have a Gentoo Linux system using the amd64 architecture. gcc -Wall -W -shared -fPIC -DHAVE_CONFIG_H -I$dovecot -I$dovecot/src/lib drac.c -o drac.so -ldrac /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../lib64/libdrac.a(dracauth.o): relocation R_X86_64_32S against `a local symbol' can not be used when making a shared object; recompile with -fPIC /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../lib64/libdrac.a: could not read symbols: Bad value collect2: ld returned 1 exit status TIA -Robin. -- ---------------------------------------------------------------------- Robin Atwood. "Ship me somewheres east of Suez, where the best is like the worst, Where there ain't no Ten Commandments an' a man can raise a thirst" from "Mandalay" by Rudyard Kipling ----------------------------------------------------------------------

2 2

[Dovecot] Deliver prints passwort to the syslog
by Dominik Schulz 05 Oct '07

05 Oct '07

Hi, I've got the problem that dovecot's deliver prints the authentification information to the syslog. Like this: Sep 18 12:11:22 mail deliver(user(a)domain.tld): auth input: user=user(a)domain.tld Sep 18 12:11:22 mail deliver(user(a)domain.tld): auth input: password=XXXX Sep 18 12:11:22 mail deliver(user(a)domain.tld): auth input: home=/home/mail/domain.tld/user Sep 18 12:11:22 mail deliver(user(a)domain.tld): auth input: uid=8 Sep 18 12:11:22 mail deliver(user(a)domain.tld): auth input: gid=8 I guess that it's only a configuration option but right now I can't figure out which one I need to change to turn this off. Any help would be appreciated. Thanks in advance. Best Regards Dominik

3 3

[Dovecot] UIDL and IMAP
by Kenneth Porter 04 Oct '07

04 Oct '07

I finally got my aging FC2 box retired and moved all email to my new CentOS 5 box. My site is all-IMAP, no POP3. I have one user who downloads all email to Thunderbird on his laptop so that he can work offline while away from a network connection (eg. on an airplane). I forgot to change the pop3_uidl_format setting as described here: <http://wiki.dovecot.org/Upgrading/1.0> So he was seeing repeated downloads of all his mail (about 300 MBytes) every time he connected. (I'm not sure why it didn't happen only the first time.) I changed the setting and haven't heard back whether if fixed things for him. Does this setting in fact get used by IMAP? It's in the POP3 section, so I'm wondering if it takes effect when one is using IMAP from the client. CentOS 5 is currently shipping with: dovecot-1.0-1.2.rc15.el5 I may look for a newer release. CentOS, based on RHEL, is intended to be a conservative distro, so I'll probably need to look at RPMForge (an addon repository of more exotic and bleeding edge software) to see if it offers a newer release.

2 1

[Dovecot] Dovceot user pop3 last connect info?
by Tim Tyler 04 Oct '07

04 Oct '07

Dovecot experts, I am a newbie to Dovecot. I am in the process of replacing qpopper with dovecot to support pop 3 clients. I have installed the latest version of Dovecot on Fedora Core 6. Everything seems to be working fine using ldap, etc. However, with qpopper, I used to have .pop.username files which would give me a time stamp of the last time a user established a pop3 connection. I know that Dovecot has logs of connection in the /var/log/maillog files, but these files rotate out over a relatively short period of time. Is there a method by which one can keep track of the last time a pop3 connection was established for each user when using Dovecot? Tim Tyler Network Engineer - Beloit College tyler(a)beloit.edu

2 1

[Dovecot] Namespace "hidden" option not working?
by Ed W 04 Oct '07

04 Oct '07

I either misunderstand the namespace hidden option, or else perhaps it's not working correctly in 1.0.5? dovecot.conf # default namespace namespace private { separator = / prefix = inbox = yes hidden = yes } # for backwards compatibility: namespace private { separator = . prefix = INBOX. inbox = yes } Then login and test s6jh LIST "" "*" SND: <<< len(939) Comp_len(118) Time:0.137985 * LIST (\HasNoChildren) "/" "Diary" * LIST (\HasNoChildren) "/" "Spam" * LIST (\HasNoChildren) "/" "Sent" * LIST (\HasNoChildren) "/" "Archive" * LIST (\HasNoChildren) "/" "Sent Items" * LIST (\HasNoChildren) "/" "Subdir" * LIST (\HasNoChildren) "/" "Junk E-mail" * LIST (\HasNoChildren) "/" "Trash" * LIST (\HasNoChildren) "/" "Drafts" * LIST (\HasNoChildren) "/" "Deleted Items" * LIST (\HasNoChildren) "/" "INBOX" * LIST (\HasNoChildren) "." "INBOX.Diary" * LIST (\HasNoChildren) "." "INBOX.Spam" * LIST (\HasNoChildren) "." "INBOX.Sent" * LIST (\HasNoChildren) "." "INBOX.Archive" * LIST (\HasNoChildren) "." "INBOX.Sent Items" * LIST (\HasNoChildren) "." "INBOX.Subdir" * LIST (\HasNoChildren) "." "INBOX.Junk E-mail" * LIST (\HasNoChildren) "." "INBOX.Trash" * LIST (\HasNoChildren) "." "INBOX.Drafts" * LIST (\HasNoChildren) "." "INBOX.Deleted Items" * LIST (\HasChildren) "." "INBOX" The idea was to support an old client using Courier like access whilst still letting new clients access using the normal process Ed W

3 6