It's built into recent versions of Postfix, just with a configure option. Basically you just have a text file that has db connection info in it, and then a query to send, and the @ symbol is replaced with the deliver to address from the email header.
So, it's pretty freeform. Mysql has pretty extensive string manipulation functions so I don't see a problem on Postfix's end at all. -Micah On Tuesday 19 October 2004 03:18 pm, Aaron Stone wrote: > The issue is that you have Postfix pre-checking the addresses against the > database, and only if they exist does Postfix pass the message to DBMail > for delivery? > > If that's the case, perhaps we can extend Postfix with the same address > and domain logic? I wonder if Wietse would choke on adding this... (is the > MySQL lookup part of stock Postfix as it is, or is it a patch anyways?) > > Aaron > > Blake Mitchell <[EMAIL PROTECTED]> said: > > Yeah, it would likely necessitate an alias lookup daemon. I have seen a > > couple requests for such a thing on the list already, so that may be the > > direction things end up anyway. Of course that adds just that much more > > complexity to the whole thing, which has to be weighed against the > > benefits. > > > > Micah wrote: > >>The only downside of this I see is that I use the alias table as a lookup > >>table for postfix to accept/deny addresses at the smtp stage, which is > >> much more efficient, I have a feeling that it would barf on a regexp > >> address. > >> > >>Actually, now that I think about it, would it handle a [EMAIL PROTECTED] > >>style > >>address? I'll dig around and see about this. > >> > >>I don't know anything about sendmail, that would be a valid question > >> there if anyone uses similar function for that MTA. > >> > >>-Micah > > > > _______________________________________________ > > Dbmail-dev mailing list > > Dbmail-dev@dbmail.org > > http://twister.fastxs.net/mailman/listinfo/dbmail-dev