On Sun, Nov 16, 2008 at 1:11 AM, mouss <[EMAIL PROTECTED]> wrote: > in theory, you could use wildcard virtual_alias_maps: > @alternatename.example @primary.example > > unfortunately, this makes all addresses [EMAIL PROTECTED] valid during > the smtp transaction, and this will cause a bounce if the address cannot be > delivered (if [EMAIL PROTECTED] does not exist). Thus backscatter.
Yeah, I probably wouldn't want to do that.. > so the choices I can see are: > > - use a script to create the virtual aliases > > - if your users are stored in sql, you could use sql statements to generate > the aliases (only when the "primary" address really exists) > > - write a policy service to do recipient validation. Then you can use > wildcard virtual aliases. I'm undecided on the back-end as of yet; I'd like to use LDAP for authentication, possibly against AD (as was discussed here earlier). But some other data such as alias maps would seem to be more straightforward to store in SQL. Someplace I've seen a warning against mixing LDAP and SQL — may have been in the "Book of Postfix", but since MySQL and OpenLDAP are on the server anyway, I don't see why I couldn't use them both. I'll look into a policy service option, too. I'll probably end up using SQL for the alias maps with some kind of simple front-end (quickly put together with CodeCharge) to maintain them. Perhaps "Virtual Canonical Domains" is something Wietse could address in a future version of Postfix. I think lack of such option is the first thing I've come across that qmail has on Postfix. Ville
