seems to me an ideal candidate for MailAttributes - if i am not mistaken with my understanding of that thread.
each mail will have attributes and one of them could be a "do not send before xx:xx:xx" in the main processor loop (the queue, stack, pipeline, etc.) attribute examination would be part of the process. > Serge Knystautas wrote: > > Brian Behlendorf mentioned on the infrastructure list > > this rather important point... > > > > "You also have to make sure to only respond to a given > > address no more than once per day to avoid loops, that > > kind of thing." > > Not sure how we could best incorporate this notion into > > james, but seems very sensical. > > Sorry, the context was sending bounces error messages. > > -- > Serge Knystautas > President > Lokitech >> software . strategy . design >> > http://www.lokitech.com p. 301.656.5501 > e. [EMAIL PROTECTED] > > > ---------------------------------------------------------- > ----------- To unsubscribe, e-mail: > [EMAIL PROTECTED] For additional > commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
