In message <543614e5.6060...@megan.vbhcs.org>, Noel Jones <njo...@megan.vbhcs.org> wrote:
>On 10/8/2014 8:11 PM, Ronald F. Guilmette wrote: >> That delay, in and of itself is not really a problem for me. What >> _is_ a bit of a problem is the fact that smtpd_delay_reject doesn't >> merely cause anything listed under smtpd_sender_restrictions to be >> delayed until such time as the _first_ RCPT TO is seen, but rather >> it causes each of the things listed under smtpd_sender_restrictions >> to be reevaluated, once for each RCPT TO. > >Yes, this is an implementation artifact. I don't know if it's worth >fixing since it rarely causes an issue. I completely agree, given what you said next... >Typically, policy services that only need to be run once are put in >smtpd_data_restrictions. Ahhhhhhhhhhhh! To be honest, I never even knew that there even _was_ such a restriction class until just now! Thank you very much! I believe that will solve the multiple evaluation problem for me. And I guess that executing my policy server as part of smtpd_data_restrictions will also allow me to turn back on the smtpd_delay_reject setting... which I had turned off, for the time being, in order to avoid the multiple evaluation problem.
