Anne, Depending on how you implement delivery in Postfix, this can be very easy. I use relay_recipient_maps (since I relay everything via LMTP). I have a SQL query that is actually a stored proceedure (aka function) in the dbmail database.
The function checks the username and aliases table to see if it's valid (and I also add a check that makes sure the customer has paid this month). I've also recently added a way to check for over quota using the same idea so I can immediately reject the message rather than queue it, attempt LMTP delivery, and then have to bounce it. This has made a huge difference in my deferred queue. -- David A. Niblett | email: [EMAIL PROTECTED] Network Administrator | Phone: (352) 334-3400 Gainesville Regional Utilities | Web: http://www.gru.net/ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anne Sent: Monday, October 09, 2006 10:54 AM To: [email protected] Subject: [Dbmail] Postfix check dbmail before content-checking Hi, We're running Postfix 2.2 + Amavisd-new 2.4.0 + dbmail 2.1.7 (Mysql backend) Currently all mail is checked by Amavis regardless of whether the recipient exists. All junkmail found is directed to a separate mailbox. This is not ideal, especially with dictionary attacks. I'd like Postfix to connect to dbmail and have it check whether the recipient exists. This should happen after 'virtual' is processed. If the user doesn't exist then Postfix should send a bounce. Content-checking should be skipped. Can this be done? Alternatively, is it possible for Amavis to check for a known user? thanks, Anne _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
