Sieve script not working
Andrea Venturoli
ml at netfence.it
Fri Mar 1 09:29:46 EST 2019
On 3/1/19 3:18 PM, Willem Offermans wrote:
> Dear Andrea and Cyrus friends,
>
> That is exactly the point: it was not ``stupid`` in any way.
> It was ignorance, which we can only avoid by improving the
> documentation.
I blame myself for this; I'll be glad if the documentation was improved,
obviously.
> By the way, the debug/logging question is still not answered.
> Debugging/logging might also enlighten the user/administrator.
That's right.
Better logs would be a very big improvement: what I was looking for was
an option to write sieve activity (like "executing script ...", "message
moved to folder ...", etc...).
That would have confirmed the script was NOT even executed (and avoided
several attempts at modifying it).
bye & Thanks
av.
More information about the Info-cyrus
mailing list