Tristan Ball wrote:
>
> Yes, definately. Infact, a configurable list of mailboxes to create
> would be the ideal, as currently my user creation scripts also create
> an INBOX.trash.
That shouldn't be too hard to add on. It's a pretty good idea, too.
There needs to be another configuration option for that, though.
``autocreatefolders''?
> Ooh, ooh, even better, auto creation of user.* mailboxes on delivery,
> providing that user exists... that way I don't have to worry about
> user mailboxes at all!
I specifically did not do that so as to not waste space on the server.
I figure that if someone isn't going to check their mail, they shouldn't
be able to receive any.
Also, I'm not sure that the deliver process has either the permissions
or the right hooks in order to be able to create maildrops, nor do I
know if it has the ability to check to see if the user exists or not,
nor would I want it to create maildrops willy-nilly when email is
attempted to be delivered. IMHO, that possibility would create more
administrative problems than it would solve.
Since I'm on the subject, it looks like it should be possible to perform
the same task for POP users by injecting a similar patch into pop3d.
I'll post the patch a little later tonight or tomorrow after I've had a
little bit of a chance to test it against 2.0.11. Might as well add
your suggestion first :-)
-Bitt
