Charles Boling a écrit : >> with SQL, there is no need to use pcre. just do that in the SQL query to >> avoid having to keep an external file up to date... > > ...except that the "+" (and everything between it and the "@") is *not* > actually part of the email address.
of course the "+" is part of the email address. you may want to reread my post. > To use your address as an example: > > When Postfix receives an envelope for: > [email protected] > It automatically strips the "+nobulk" and what it actually looks up in > the database is: > [email protected] > you want to read the docs about recipient_delimiter. PS. mail to [email protected] and [email protected] will get to the same mailbox. both '-' and '+' are supported here, for now. but '-' is "encouraged" because '+' is not well accepted, as you noticed. so at some time, '+' support may be removed. > > I assume that the "+" magic is hard-coded in Postfix, so if I [knew what > I was doing, and] were to dig out the source code, it would be pretty > simple to change it to use "_" instead of "+". If I were to upgrade > this "hack" to something more respectable, I would: > 1. Create a configurable parameter, rather than hard-coding it that's recipient_delimiter... > 2. Allow multiple characters (so I could still use "+" as well) > postfix doesn't support multiple chars in recipient_delimiter. to understand why, try to read the docs about what lookups postfix does when it sees [email protected] it will check: [email protected] [email protected] example.com (or @example.com ... depending on context) That's 3 queries. now, if you want two delimiters, say '+' and '-' then how many queries would [email protected] result in? [email protected] [email protected] [email protected] ... as you can see, each additional delimiter adds one query...
