On 2003-12-19 21:29:50 +0100, Peter J. Holzer wrote: > This is why I think that we need a standard way to access per-recipient > configurations. Then we can have a number of modules which get the > configuration from a file, a database, or whatever, and other modules > can access the configuration without having to bother how it is > retrieved.
To generalize this a bit:
There may not only be per-recipient configurations, but also
configurations dependent on the sender's email address and on the
client's identity (IP address, host name, name given in HELO, ...).
See for example Gavin Carr's whitelist_soft plugin, which provides a
uniform way to specify such configurations, but only for a specific
purpose (whitelisting).
By adding further transaction notes "sender_options" and "host_options"
we can cover that, too. Unlike "recipient_options", these notes are
valid until the end of the transaction.
hp
--
_ | Peter J. Holzer | In this vale
|_|_) | Sysadmin WSR | Of toil and sin
| | | [EMAIL PROTECTED] | Your head grows bald
__/ | http://www.hjp.at/ | But not your chin. -- Burma Shave
pgp00000.pgp
Description: PGP signature
