[Dovecot] Allowing clients to test their Sieve scripts
ben at indietorrent.org
Fri Jun 14 22:36:19 EEST 2013
On 6/14/2013 3:28 PM, Thomas Harold wrote:
> On 6/14/2013 2:07 PM, Ben Morrow wrote:
>> Simply providing some way for them to read the .dovecot.sieve.log file
>> created in their home directory would be a good start. If there are any
>> problems with delivery they will be logged there. You could set up some
>> sort of web access, or even have a daily cronjob to mail the file to the
>> user if it isn't empty.
> What about having sieve add a x-rules-fired header and adding that to
> the message?
What happens when the message is never delivered for whatever reason?
That's the only problem I see with that approach.
More information about the dovecot