On 9/15/2010 3:51 AM, Peter J. Holzer wrote:
I have a strong suspicion that the author meant to write
return(DENY, "Unable to queue message ($!)");
The new code is considerably better - works properly in the face of
temporary vs permanent errors from the backend server and provokes
retries if appropriate. It's how our (much hacked) smtp-forward works.
(our smtp-forward tries multiple backend servers, and does a limited
amount of optimizing which one to use.)
Parameterizing it for DECLINED vs DENY I guess would be best if someone
is expecting it to failover to another queuing plugin. It's more a
notion of whether you have multiple queuing plugins or not.
