On Mar 10, 2011, at 19:41, Chris Lewis wrote: > I think we'd be better served by coming up with, for example, a "qpsmtpd way" > of doing this sort of thing. > > For example: for basic RCPT TO functionality, have a basic RCPT time plugin > that can handle aliasing, allowable domain relays, lists of valid addresses, > tagged addresses etc. Base the plugin around being able to read a "qpsmtpd > format" file specifying all that stuff. [...]
Aha, you are right! In the 'STATUS' file there's actually a TODO item for doing this. " - Add user configuration plugin infrastructure - Add plugin API for checking if a local email address is valid" The idea here was to allow one or more plugins to lookup user information (in LDAP, aliases.db, users.cdb, PAM, ...) and then a standard API for accessing the information. A "not found" user should by default just have the recipient be rejected. Of course I added this to the TODO in 2004 or something like that ... - ask
