Hi, In my previous question [1] Viktor Dukhovni suggested
> you could use a policy service to impose rate limits per SASL login, or sender address as a means of preventing active queue congestion. This took me down a bit of a rabbit hole looking at SMTP Access Policy delegation and tcp_tables. However I have not managed to find much (ANY???!!!) information on what the server responses should look like. Although I don't yet know exactly what they look like, I have only seen mention of accepting or rejecting emails at submission using SMTP Access Policy delegation. I really want to be able to generate, on a per message basis, the behaviours that I currently have statically defined in a transport map. These are: (condition1) customtransport: (condition2) smtp:[othernode] Is this possible with either mechanism? What would the specific responses be? There is also a secondary issue: I'm trying to do load balancing here, but the load balancing would be non-deterministic. I don't want the messages to bounce around between nodes. While I could handle that based on the helo_from= in SMTP Access Policy delegation, I don't believe this information is available in tcp_tables. Assuming that the custom transport is possible via tcp_table but NOT SMTP Access Policy delegation, how can I ensure that a message only gets bumped to a peer once? TIA Colin [1] https://www.mail-archive.com/postfix-users@postfix.org/msg101676.html -- -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCM d s+:+ a+ C+++(---)$ UL+++ P+(--) L+++ E--- W+++ N++ w-- PS++(+++()) t+ 5+ X R- tv-- b++ DI++ D e+++ h---- ------END GEEK CODE BLOCK------
_______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org