I encountered an interesting problem that one originator was being dumped into 
the Deleted file directly by my sieve.  The sieve file was quite large and it 
was not obvious which entry was causing the issue.  I recall there was a way to 
get sieve-test to show what is going on and which lines it used, but I could 
not replicate it tonight for anything.  I ended up having to change all the 
deliver to the Deleted files to something else and test one at a time to find 
the offending entry.  It took a long time.  How do you get sieve-test to show 
the actual path it took through the file?

-- Doug

Reply via email to