2 messages in net.sourceforge.lists.courier-maildrop[maildropl] Question about installing...
FromSent OnAttachments
Russel WinderJan 21, 2004 7:52 pm 
Sam VarshavchikJan 22, 2004 3:56 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[maildropl] Question about installing maildropActions...
From:Russel Winder (rus@russel.org.uk)
Date:Jan 21, 2004 7:52:48 pm
List:net.sourceforge.lists.courier-maildrop

Apologies if this turns out to be a pathetic newbie question but...

I am running postfix (postfix-1.1.12-1, standard RH9) with maildirs and so use maildrop as the final delivery agent. For the moment I am using rpmbuild with the tarball from http://prdownloads.sourceforge.net/courier/maildrop-1.6.3.tar.bz2

Everything works effectively out of the box. The issue is that the default delivery destination is the mailbox in /var/spool/mail rather than the maildir in ~/Maildirs. Dan Alderman who runs a not dissimilar set up chose to manually edit the files and recompile to change the default behaviour whereas I am choosing to use a final `to "Maildirs"' in my .mailfilter and use maildrop as distributed.

The question I have is whether we have missed something in the configuration process of maildrop that would allow is to more easily state that we want maildirs rather than mailbox as the default delivery. I had a quick peek at the configuration system and it seems to check for Courier and QMail for maildirs behaviour and then otherwise assume mailboxes and sendmail. Whilst postfix emulated sendmail by default the postfix + maildrop + maildirs is, I believe, a common way of configuring things and so could usefully be detected.

Is it actually necessary to do the configuration at compile time or could it be done at runtime as is the case with postfix and courier-imap?