 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
6 messages in net.sourceforge.lists.courier-maildrop[maildropl] automatic creation of mai...| From | Sent On | Attachments |
|---|---|---|
| Tom Metro | Aug 29, 2004 4:11 pm | |
| Sam Varshavchik | Aug 29, 2004 5:05 pm | |
| Tom Metro | Aug 29, 2004 6:14 pm | |
| Ron Johnson | Aug 29, 2004 6:55 pm | |
| Tony Earnshaw | Aug 30, 2004 1:24 am | |
| Tom Metro | Aug 30, 2004 8:41 pm |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | [maildropl] automatic creation of maildir directories | Actions... |
|---|---|---|
| From: | Tom Metro (tmet...@vl.com) | |
| Date: | Aug 29, 2004 4:11:39 pm | |
| List: | net.sourceforge.lists.courier-maildrop | |
I recently installed maildrop-1.5.3 (built from source w/Debian patches) to act as a replacement for Postfix's 'virtual' LDA, and I noticed it didn't automatically create maildirs upon initial mail deliver, as Postfix's virtual does.
This seems like a fairly significant behavior that isn't mentioned in the maildrop man page.
I checked the changelog in 1.7.0 and didn't see anything relevant. (By the way, it's not so clear from the changelog what the major changes were that justified the jump in release numbers from 1.5.x to 1.6.x and to 1.7.x. What's listed seems mostly like maintenance items. Are the release numbers changing in order to track Courier MTA releases?)
Spending a few hours searching through the mailing list archives turns up stuff like:
In http://sourceforge.net/mailarchive/message.php?msg_id=9113891 Ty <ty@la...> writes:
Basically I'm trying to do what many others have tried...have maildirs created by maildrop without patching or manually addidng the dirs.
In http://sourceforge.net/mailarchive/message.php?msg_id=7494233 Andreas Stollar <andreas@sp...> writes:
How can I specify maildrop to create Maildir (and homedirectory if needed) when it doesn"t exist ?
In /etc/maildroprc
`until test -d $HOME/Maildir; do /usr/local/bin/maildirmake $HOME/Maildir; done`
In http://sourceforge.net/mailarchive/message.php?msg_id=7411663 Saulo Calixto Bonfim <cuenco@sa...> writes:
I know it is a old known issue and already had been discuted here, but actually I see no way for solving my problem... [...] My mail server have Postfix 2.0.18...It was working smoothly without maildrop when I needed creating new users via mysql. The Postfix virtual delivery agent was creating maildirs perfectly. When I switched out the transport table for "maildrop:"...Maildirs wasn't being created when new users were add in mysql db.
I've googled for few days and discovered that maildrop actually is unable to create maildir for virtual users. Some people said to patch courier imap's source so it would be capable to create nonexisting maildirs with the very first login from the user. Other people said to use maildroprc file to make the job.
In http://www.marlow.dk/site.php/tech/postfix Martin List-Petersen <martin at list-petersen dot dk> writes:
Maildrop will NOT create maildirs, if they don't exist. It will just report a temporary failure (means, mail don't get lost, but can't be delivered). If you look in the global include above, you will notice, that i've found ways to get around that.
In http://sourceforge.net/mailarchive/message.php?msg_id=7110450 Hector Tapia <htapia@cs...> writes:
I'm currently running Postfix and Courier-IMAP. With this configuration, new user maildirs are automatically created when the first email arrives. It is my understanding that this behaviour stops when Maildrop is included into the mix. I read somewhere on a how-to that a patch to Maildrop exists that allows for the automatic creation of maildirs, but have not been able to locate this patch.
Most threads suggest using a maildroprc hack, but these messages from Chris Masters <rotis23@ya...>:
http://sourceforge.net/mailarchive/message.php?msg_id=6292015 http://sourceforge.net/mailarchive/message.php?msg_id=6542867
dating back about a year ago (2003-10-15) show a patch for maildrop that fixes this problem. Fixing it directly in the maildrop code is clearly the more efficient (minimal extra I/O - create dirs if open() fails) and clean way to solve this. (The same patch also addresses what sounds like an arguably more significant issue - returning a temporary failure exit code when the database is unavailable.)
What seems missing from the discussion is why this functionality hasn't made it into the core source. Are there arguments against adding this?
As there could be security implications, it seems the best way to enable such functionality would be with a command line switch, rather than having it always enabled. (I believe the above referenced patch enables the functionality whenever maildrop is compiled with support for a virtual user database (the code was in a "#if USEMYSQL" conditional block), though this might mean it is also enabled for local users if the same binary is used for both, which might not be desirable.)
There probably should be some discussion over whether home directories are automatically created in addition to maildir directories, and if so, should it be enabled via a separate switch.
Are the developers/maintainers of the stand alone maildrop monitoring this list? (There seem to be a lot of unanswered questions on the list, though that may be due to the SourceForge.net archive UI not showing complete threads. Is there another archive site for the list?)
-Tom