On 02 Apr 2008, at 09:00, Joseph Brennan wrote: > The crucial difference is that if one writes a bad procmail recipe, > the message loops round and round until one of the MTAs considers > the hop count exceeded and bounces it to sender, but if one writes > a bad sieve rule, the message _is silently lost_. That's a much > harsher penalty. It's not really sieve that is "losing" the message, it's Cyrus LMTP duplicate suppression. This is why an internal & implicit solution is appealing, rather than requiring a "good" sieve recipe using a sieve extension which is an internet draft at the moment. :wes ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
