You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The server in quesion does support the "index" extension. The script above was not freshly created in SnappyMail but fetched from the server. I created it before using Sieve Editor and stored in to the server using the ManageSieve protocol.
Does the editor used in SnappyMail perform some kind of client side checking? All checking should be done by the server using the CHECKSCRIPT command of ManageSieve. I assume this is some kind of bug in the editor.
Thanks, I'm aware of that. The header in question is a "Received" generated by my own email provider for every incoming mail I want to catch with that filter. The :index makes sure, I don't accidentially catch a "Received" header of any previous mail server along the chain.
Describe the bug
SnappyMail's Sieve editor cannot handle an :index directive in rules.
To Reproduce
I've created the following valid Sieve script as example:
When trying to edit this script in SnappyMail, I get an "this.index is undefined" message
Screenshots
Please complete the following information:
The text was updated successfully, but these errors were encountered: