On Montag, 18. Dezember 2006 06:02 Aaron Stone wrote: > > Why not throw the address as received from the MTA into dbmail, and > > the "rewriting" is done there? It makes sense to do it there: > > So DBMail does the rewrite before delivery.
Yes, but the MTA doesn't have to care about anymore, which makes setup easier. > > And yes, I do of course recipient validation at MTA level. That's a > > similar query: > > [snip query] > > So the MTA does the rewrite before handing off to DBMail. And it needs extra work. > > Sorry that I stepped on toes here, I just like simple interfaces. > > Doesn't look like a simple interface to me at all! Why? Right now I have to extra 1) configure postfix to rewrite recipients with recipient_canonical_maps = pgsql:/etc/postfix/recipient_canonical.sql 2) put the correct and big and complicated sql query there Ah, I think I just found what you mean: The big sql query for whether a given e-mail address *exists* would still be there. That could be solved via a view or stored procedure. Then the queries from the MTA could be made much simpler, but I wonder if that would be a performance penalty? > Btw, don't worry about toes. Arguing useful ideas is great. It only > gets ugly when people start calling names to those who disagree. > Thankfully, we've never had that problem here. Good. I like discussing ideas, but sometimes people feel pissed, which I never mean, honey (does that count as a name? :-)) > Perhaps a solution is to have a 'dbmail-checkaddr' that returns 0 or > 1 depending on whether or not the given address can be delivered at > all? Bad news is that this would have horrible scalability issues > unless it were a daemon. Why scalability? I'm not so fit in databases, but what is the difference if the MTA makes the queries or they are done by dbmail? > At that point, I wonder if some MTA's might > support using a VRFY query against the LMTP daemon before beginning > the delivery process, thus removing the need for a separate daemon or > database interface. I think this is not useful: If you configure postfix to verfiy recipients, it starts storing them in it's own verify.db. I'm not sure this scales too good (it's a berkeley db), when I hear some people having 3M customers (probably with extra aliases). mfg zmi -- // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0676/846914666 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi3.asc | gpg --import" // Fingerprint: 44A3 C1EC B71E C71A B4C2 9AA6 C818 847C 55CB A4EE // Keyserver: www.keyserver.net Key-ID: 0x55CBA4EE
pgpWuUYprtai8.pgp
Description: PGP signature
_______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
