On Sun Jan 27, 2008 at 08:28:42 +0100, Hanno Hecker wrote:
> This is for the user "root" or is "/path/to/root" the base directory?
/path/to/root is the base directory as specified in the plugins
configuration file.
> As long as the current behaviour of queue/maildir is kept (i.e. all
> mails go into the dir which is named by the first argument) I'll apply
> the changes.
They don't. That's the whole point! They go *beneath* the directory
specified by the first argument, if that is sufficient?
Previously if you specified /home/archive as the argument you'd
end up with:
/home/archive/new/
/home/archive/cur/
/home/archive/tmp/
Now if you specify the same argument those three directories wouldn't
be created. Instead one sub-directory would be created for the domain
of each delivered mail. So, for example, if you handled mails for
example.com, example.net, and example.org you'd end up with a tree
looking like this:
/home/archive/example.com/new
/home/archive/example.com/cur
/home/archive/example.com/tmp
/home/archive/example.net/new
/home/archive/example.net/cur
/home/archive/example.net/tmp
/home/archive/example.org/new
..
> If not, it would be better to drop this (and some others plugins? :))
> into a new subdirectory of contrib/. I can act as proxy to get them
> into svn.
Either would be fine with me, although I guess the changes are
small enough that I'd be happy with either acceptance or dropping.
(ie. no need to pollute contrib with a minor change like this unless
you strongly think it would be of interest. I'm unsure.)
Anyway a context diff against svn trunk, and the full file is
online here:
http://www.steve.org.uk/Software/tmp/qpsmtpd/
I might have some more changes to come, but no genuinely new
plugins. Most of my work has been updating the existing ones
to pull configuration information out of a MySQL database and
changing the way rejections happen.
(Right now no plugin except for queue/exim ever returns
DENY/DENYSOFT. Instead I record a note in the transaction and continue
the transaction right to queuing. I have two queue plugins one
to archive if the mail should be rejected, and one to deliver if
it shouldn't be. This way regardless of which plugin denys the
connection I archive or deliver it. Providing a chance to let
a user un-archive a mail that was rejected in error.)
Steve
--
# The Debian Security Audit Project.
http://www.debian.org/security/audit
