maildrop - mail delivery agent with filtering abilities

   Copyright 1998-2005, Double Precision Inc.

   This program is distributed under the terms of the GNU General Public
   License. See COPYING for additional information.

   http://www.courier-mta.org/maildrop/

Building RPMs

   Starting with version 0.99, it is possible to build binary RPMs directly
   from the source tarball, so there's no longer a need to provide a separate
   set of source and binary RPMs. You will need RPM 3.0 or higher in order to
   build a binary RPM. Execute the following command:

    rpm -ta maildrop-3.0.3.tar.bz2

   The binary RPM will be built with a customized configuration (userdb,
   GDBM, and quota enhancements enabled). Afterwards, simply execute rpm -i
   to install it. That's it.

   With RPM 4.1 (Red Hat 8.0) use the 'rpmbuild' command instead of rpm:
   rpmbuild -ta maildrop-3.0.3.tar.bz2

   If you would like to change the RPM build options, move
   maildrop-3.0.3.tar.gz to your SOURCES directory, extract the file
   maildrop.spec, move it to your SPECS directory, customize it if necessary,
   then build from the spec file.

   maildrop includes documentation in HTML, as well as traditional man pages.
   The HTML versions may also be found at
   http://www.courier-mta.org/maildrop/maildrop.html.
    

Installation

   See INSTALL for installation information. If you are using an RPM-based
   Linux distribution, you can install build a binary RPM directly from the
   source code.

Using maildrop with sendmail

   Maildrop can be easily used as sendmail's local delivery agent, instead of
   procmail. Here is the suggested entry for sendmail.cf, courtesy of Eric J.
   Schwertfeger <ejs@bfd.com>:

  
 Mlocal,         P=/usr/local/bin/maildrop, F=lsAw5:/|@SPfhn, S=10/30, R=20/40,
                 T=DNS/RFC822/X-Unix,
                 A=maildrop -d $u

   You may also consider including the D, F, and M flags as well.

Dovecot Authentication extension for maildrop
=============================================
** Copyright 2009 Marko Njezic
** Licensed under the same terms as Courier Authlib AND/OR Courier Maildrop.

Use --enable-dovecotauth to run maildrop's configure script to enable this
extension.

In order to use it you'll need to specify additional option "-t" that will point
to the location of Dovecot's auth master socket when starting maildrop in
delivery mode. For example:

maildrop -d USER -t /var/run/dovecot/auth-master

By specifying "-t" option, maildrop will first try user lookup against Dovecot's
database. If user is not found, maildrop will fallback to local user database
(i.e. passwd), as usual. Lookups against Courier Authlib will not be done when
"-t" option is specified. If you want to perform such lookup when both
extensions are compiled, simply remove "-t" option and maildrop will behave as
usual.

One significant difference compared to Courier Authlib extension is that Dovecot
Authentication extension will never return uid/gid that's equal to zero. If such
value was returned from database, maildrop will exit with temporary failure.
This was done in order to prevent accidental mistakes. If you really want to
deliver as/to root, you'll have to start maildrop without "-t" option and let
it directly query system user database on its own.

Make sure that correct permissions are set on Dovecot's auth master socket so
that maildrop can communicate with it. Also, depending on what type of users are
being served from Dovecot's database, if user lookup returns local user
accounts, you may end up with problems when maildrop tries to write mails to the
spool directory if wrong permission are set on it, since maildrop will reset its
permissions (uid/gid) to the values returned from user database. This behavior
is the same as the behavior of lookups against Courier Authlib, since they also
reset maildrop's permissions. When you want maildrop to deliver to the local
users, it's best to let it directly query system user database on its own,
since then it can apply its own "RESET_GID" magic, which will hopefully result
in "correct" permissions that will allow maildrop to write to the spool
directory.

And last but not least, I hope that you'll find this extension useful.
Especially if you already have an existing user database in Dovecot, but would
like to use maildrop (with its powerful "xfilter" command) to deliver e-mails,
without setting up another authentication user database, like Courier Authlib.

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
  <title>maildrop - mail delivery agent with filtering abilities</title>
  <meta name="MSSmartTagsPreventParsing" content="TRUE" />
</head>

<body>
<!-- Copyright 1998 - 2005 Double Precision, Inc.  See COPYING for -->
<!-- distribution information. -->

<h1>maildrop - mail delivery agent with filtering abilities</h1>

<p>Copyright 1998-2005, Double Precision Inc.</p>

<p>This program is distributed under the terms of the GNU General Public
License. See <code>COPYING</code> for additional information.</p>

<p><a
href="http://www.courier-mta.org/maildrop/">http://www.courier-mta.org/maildrop/</a></p>

<h2>Building RPMs</h2>

<p>Starting with version 0.99, it is possible to build binary RPMs directly
from the source tarball, so there's no longer a need to provide a separate
set of source and binary RPMs. You will need RPM 3.0 or higher in order to
build a binary RPM. Execute the following command:</p>
<pre>   rpm -ta maildrop-@VERSION@.tar.bz2</pre>

<p>The binary RPM will be built with a customized configuration (userdb,
GDBM, and quota enhancements enabled). Afterwards, simply execute <code>rpm
-i</code> to install it. That's it.</p>

<p>With RPM 4.1 (Red Hat 8.0) use the 'rpmbuild' command instead of rpm:
<tt>rpmbuild -ta maildrop-@VERSION@.tar.bz2</tt></p>

<p>If you would like to change the RPM build options, move
<code>maildrop-@VERSION@.tar.gz</code> to your <code>SOURCES</code>
directory, extract the file <code>maildrop.spec</code>, move it to your
<code>SPECS</code> directory, customize it if necessary, then build from the
spec file.</p>

<p><i>maildrop</i> includes documentation in HTML, as well as traditional man
pages. The HTML versions may also be found at <code><a
href="maildrop.html">http://www.courier-mta.org/maildrop/maildrop.html</a>.</code>
<br />
�</p>

<h2>Installation</h2>
See <code><a href="INSTALL.html">INSTALL</a></code> for installation
information. If you are using an RPM-based Linux distribution, you can
install build a binary RPM directly from the source code.

<h2>Using maildrop with sendmail</h2>
Maildrop can be easily used as sendmail's local delivery agent, instead of
procmail. Here is the suggested entry for sendmail.cf, courtesy of Eric J.
Schwertfeger &lt;ejs<code>@</code>bfd.com&gt;:
<pre>�
Mlocal,�������� P=/usr/local/bin/maildrop, F=lsAw5:/|@SPfhn, S=10/30, R=20/40,
��������������� T=DNS/RFC822/X-Unix,
��������������� A=maildrop -d $u</pre>
You may also consider including the D, F, and M flags as well.</body>
</html>

Date: Sat, 31 Jan 2004 16:00:00 +1:00 (CET)
Tonni Earnshaw <postmaster@billy.demon.nl>
addition for README.postfix in maildrop package

LDAP and maildrop.

maildrop's LDAP support, combined with Courier IMAP's authldap.schema, give 3
new objectclasses over and above standard object classes, that enable LDAP-
based quotas, virtual aliases and virtual mailboxes, as well as regular
$HOME/Maildir based mail directories.

By using the standard combination of master.cf/transport as given below,
NO standard Postfix LDAP lookups are done before passing the message to the
Postfix transport, which takes care of immediate delivery. However, it's most
likely that LDAP lookups have to be done - for example on system and other
aliases - before enabling delivery to users' mailboxes.

With Postfix 2.1.0 (perhaps before that too, I'm still using
postfix-2.0.16-20031231) it is possible to circumvent the
master.cf/transport pair described below by giving maildrop as the
mailbox_command in main.cf and leaving out the master.cf/transport
examples given below. For example:

mailbox_command = /usr/local/bin/maildrop -d ${USER} -w 70 (note upper case).

In as much as maildrop 1.6.3 supports LDAP lookups, and the version of deliverquota
that I was using before (2.2.2) does not, it's thus possible to use Postfix's local
transport instead of a dedicated maildrop transport.

==============================================================================

Date: Wed, 23 Jan 2002 07:31:26 -0700 (MST)
From: Charlie Watts <cewatts@frontier.net>
Subject: addition for README.postfix in maildrop package

README.postfix recommends postfix be configured with:

        maildrop  unix  -       n       n       -       -       pipe
            flags=R user=vmail argv=/usr/local/bin/maildrop -d ${recipient}

However, since version 20010610 of postfix, you need to add the u flag as
well so that postfix downcases addresses before handing them to maildrop.

-------------------------------------------------------------------
Incompatible changes with snapshot-20010610
===========================================

The Postfix pipe delivery agent no longer automatically case-folds
the expansion of $user, $extension or $mailbox command-line macros.
Specify the 'u' flag to get the old behavior.
-------------------------------------------------------------------

It does not automatically case-fold $recipient either.

I'd recommend this instead:
        maildrop  unix  -       n       n       -       -       pipe
            flags=Ru user=vmail argv=/usr/local/bin/maildrop -d ${recipient}

--
Charlie Watts
cewatts@frontier.net
Frontier Internet, Inc.
http://www.frontier.net/


Date: Tue, 14 Mar 2000 17:02:04 -0300 (EST)
From: Bruno L. F. Cabral <bruno@openline.com.br>
Reply-To: Maildrop mailing list <maildropl@listbot.com>
To: maildropl@listbot.com
Subject: Re: [maildropl] maildrop, postfix & userdb

Maildrop mailing list - http://www.flounder.net/~mrsam/maildrop/

Hi there

I tried maildrop 0.99.1 and it is now working like a charm with
postfix & userdb, thanks Sam ! :)

vmail is my virtual user, which is a trusted maildrop (-d) user

	# id vmail
	uid=400(vmail) gid=400(vmail) groups=400(vmail)
	# install -d /home/vmail -o vmail -g vmail -m 700

on /etc/postfix/master.cf:
	maildrop  unix	-	n	n	-	-	pipe
	    flags=R user=vmail argv=/usr/local/bin/maildrop -d ${recipient}

on /etc/postfix/main.cf:
	fallback_transport = maildrop

on /etc/userdb/default:
	vmail	uid=400|gid=400|home=/home/vmail|shell=/bin/bash|systempw=*
	400=	vmail

create one /etc/userdb/domain for each domain, one line for each virtual user
(the uid & gid MUST be equal to vmail's one -- the quota is 5MB or 200 messages)
	user@domain	home=/home/vmail|mail=/home/vmail/domain/user|uid=400|gid=400|quota="5000000S,200C"

to commit the changes:
	# makeuserdb

preparing the virtual mailboxes, the install is for each new domain,
the maildirmake for each user inside the virtual domain
	# su - vmail
	$ install -d /home/vmail/domain -o vmail -g vmail -m 750
	$ maildirmake /home/vmail/domain/user
	$ exit

now, ready to fight with qmail's pop3d :)

!3runo


Date: Tue, 21 Mar 2000 12:29:48 -0300 (EST)
From: Bruno L. F. Cabral <bruno@openline.com.br>
Reply-To: Maildrop mailing list <maildropl@listbot.com>
To: maildropl@listbot.com
Subject: Re: [maildropl] maildrop, postfix & userdb

Maildrop mailing list - http://www.flounder.net/~mrsam/maildrop/

Hi there

this is an add-on to my previous post

> I tried maildrop 0.99.1 and it is now working like a charm with
> postfix & userdb, thanks Sam ! :)

to postfix handle as local our maildrop's userdb e-mails, you'll have to
(in adition of my previous instructions)

	/etc/postfix/transport:
	virtual.domain		maildrop:

if you want to do some domain redirection, use
	/etc/postfix/virtual:
	webmaster@virtual.domain	johndoe@virtual.domain

(do not use a line like
	virtual.domain		whatever
as stated on postfix' virtual(5) or unlisted users will be rejected
as 'unknown' -- a small postfix glitch, seems)

	/etc/postfix/main.cf:
	transport_maps = hash:/etc/postfix/transport
	virtual_maps = hash:/etc/postfix/virtual

as you may have noticed, no virtual domains listed on mydestination

> now, ready to fight with qmail's pop3d :)

as Sam said before, it is possible to use qmail's qpop3d to read
maildrop's userdb mailboxes. qmail's pop3d is modular, I only had
to write a shim that tests the username/password pair (received
from qmail-popup) against maildrop's userdb files and, on success,
change the current directory to the one where the user maildir++ resides.
qmail-pop3d takes care of the rest.

the line on inetd.conf becomes:

pop-3	stream	tcp	nowait	root	/usr/sbin/tcpd qmail-popup YOUR.FQHN.HERE /usr/sbin/chkpwd-userdb.pl /usr/sbin/qmail-pop3d .

if ppl think the program is interesting, I can post it. it needs
a small rewrite to get rid of debugging stuff but it is working
very well with maildrop 0.99 & DB files.

thanks Sam, for the pacience with me and for the great job on maildrop.

Cheers, !3runo


From:  Charlie Watts <cewatts@frontier.net>
To:  Sam Varshavchik <mrsam@courier-mta.com>
Date:  30 Mar 2001, 06:40:11 AM
Subject:  Suggested addition maildrop/README.postfix

You may want to add this to maildrop/README.postfix, or postfix folks
using maildrop as LDA may lose mail.

Postfix, by default, will send messages to multiple recipients at a time.

Maildrop assumes that it will be receiving messages for one recipient at a
time.

When postfix hands maildrop a message with multiple recipients, only the
first recipient receives the mail.


If maildrop is configured as a transport named "maildrop" in postfix
(which would be the normal way to do it), adding:

maildrop_destination_recipient_limit = 1

to /etc/postfix/main.cf fixes this behaviour, and causes postfix to hand
messages one recipient at a time to maildrop.




Thanks for a lovely piece of software.

--
                          "Dorothy, if you're going to Oz again, I'm
                          going with you", Em barked.
Charlie Watts
cewatts@frontier.net