Hi,
I've been looking into Qpsmtpd recently and am contemplating whether
to start using
it on production servers in the near future. In an effort to get to
know the intricacies
and inner workings of the Qpsmtpd plugin system, I wrote a small
plugin that looks up
the RCPT TO address in any number of Postfix BerkeleyDB address maps
(like relay_recipient_maps
and virtual_alias_maps). This can be used for early rejection of mail
to unkown users.
(See below for an excerpt from the perldoc).
Strangely enough, I couldn't find any existing plugin that does this?
Perhaps I just wasn't
looking hard enough...
I haven't actually used this on any production servers yet. However,
I've done some tests
and no problems came up. Ergo, the status of the plugin is: works for
me and will most likely
work for others as well. Of course, use at your own risk and YMMV :-)
You can find the plugin at http://leander.koornneef.net/qpsmtpd/
Anyway, I really like the idea of Qpsmtpd and will certainly be doing
some further testing.
Keep up the good work!
regards,
Leander Koornneef
-----
NAME
check_postfix_address_maps - Lookup recipient in Postfix
address maps
DESCRIPTION
Checks for the existence of the given "RCPT TO" address in
the Postfix address maps (like relay_recipient_maps or
virtual_alias_maps). This allows for early rejection
of mails for unknown (local) recipients. Postfix commonly
stores these in BerkeleyDB files. Multiple DB files can be used for
the lookup (see CONFIGURATION). Catch-all
addresses (@domain.com) are also supported (although you
should not use those of course...)
Currently, only DB files stored in BerkeleyDB HASH format are
supported.
CONFIGURATION
Put the following in config/plugins:
check_postfix_address_maps <path> [<path>] [...]
You must give at least one path to a DB file in config/
plugins. Qpsmtpd will fail to start if no path is given. The plugin
does no autodetection of db paths, as it
has no way of knowing which database file(s) to use.
Multiple files are supported. Each recipient is checked against all
the databases.
LIMITATIONS
Currently, only DB files stored in BerkeleyDB HASH format are
supported (which is the most commonly used format, I believe).
DEPENDENCIES
Requires the BerkeleyDB Perl module: http://search.cpan.org/
~pmqs/BerkeleyDB/ (libberkeleydb-perl on Debian)
