Any sieve gurus? (YES, I finally made it off of procmail, and sieve is AWEsome in comparison - oh happy days :)
So two sieve failures (dodgy incoming emails got through gmail) exposed themselves in relation to sieve in the last few days as follows: 1) The first is simply a "superfluous" space char at the end of the line on the "From:" line, as follows (ignore leading spaces): From: "EFA" <memberad...@efa.org.au>⋅ Note the deceptively cheeky little space char at the end of the line - and yes, either EFA or some middle man has a dodgy MUA/ mail processing agent. QUESTION: Why is a single space at this EOL, so malformed as to cause sieve to spit the dummy with an error? 2) The dodgiest "To:" line I have literally ever seen, as follows: To: <Undisclosed-Recipient:;> Notice the colon, AND the semi colon, in this "email address". Again gmail passed it right through. I can actually accept this failure of sieve to pass the email through - such an addy is indeed rather egregious. BUT, it would be nice to have sieve actuallly OUTPUT the actual problematic email address, and to this end, does anyone know some magical incantation to add to sieve, so I can see all problematic (and only the problematic) lines of incoming emails, as "error output" by sieve to the cmd line? Manually reducing the lines being processed by sieve, running sieve each time, till I finally figured out exactly which lines of which emails is causing the problem, is quite the biatch TBH :) TIA, Zen
