> >>> v2 overcomes this and tracks the recipients for each smtpd instance. To > >>> track quotas precisely v2 can be used in smtpd_recipient_restrictions > >>> and smtpd_end_of_data_restrictions. v2 knows about the various > >>> restrictions. > >> False. You will not be able to use Recipient throttling at > >> the smtpd_end_of_data_restrictions. This has nothing to do > >> with Policyd but an is Postfix limitation. > > > > I suggest you review the v2 code before making an assumption like that, > > furthermore you did not read what I said. > > > > V2 tracks all the recipients for the message. Therefore in end_of_data > > state, this information is available. > > The information is not available in end_of_data.
"V2 tracks all the recipients for the message.". This is done in the recipient_restrictions and referenced using the Postfix instance. Look at table session_tracking , there is a column RecipientData which stores matched policies and the recipients for the current smtp transaction (instance). The unique instance variable is available in end_of_data, which then does a query against the DB to get the list of recipients. So it is available to policyd v2 in end_of_data (I made no mention of Postfix providing a recipient list in end_of_data).
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Register now and save $200. Hurry, offer ends at 11:59 p.m., Monday, April 7! Use priority code J8TLD2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________ policyd-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/policyd-users
