Aaron Stone wrote: > I like the idea of adding a dbmail.conf option to turn the messages off in > the case of a bum email, and only alert if the script itself is broken > (which can happen, if, say, you wrote a web sieve client that inserts > directly into the dbmail_sievescripts table, bypassing the checks in > ManageSieve and dbmail-sievecmd).
That would be my course of action. Being able to turn those messages of, period, is a requirement for me, even for broken sievescripts. But then I use timsieve to insert them which guarantees syntax checks. In general, broken sievescripts should simply be ignored, unless notification is enabled (user option?). Loud failure is nice for debugging but should not be default behaviour. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
