[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Received header field for special processing, such as "held for moderation".
On 10/25/2011 1:11 PM, Rolf E. Sonneveld wrote:
On 10/25/11 9:15 AM, Dave CROCKER wrote:
My formulation of the generic issue is to have the Received audit trail mark
processing events other than simple smtp exchanges.
Does this mean you want to restrict it to only non-SMTP exchanges, or do you
mean it should also apply to non-simple SMTP exchanges?
simple as in simply. that is, more than merely smtp activity.
For example, sometimes a header field is added for the mailing list module's
processing. The proposal is for yet-another Received field if the MLM decides
to hold for moderation (or whatever.)
Another example is greylisting: should a sending SMTP client mark events that
Greylisting generates an SMTP reply code, whether distinctive or not. Strictly
speaking, the message does not enter a new queue. It merely stays in the
transmission queue it was already in.
But certainly there would be nothing wrong with the added Received logging,
modulo the looping count check that's already been mentioned.