-
-
Notifications
You must be signed in to change notification settings - Fork 265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug]: cannot clear IMAP flags that were set by a Sieve script #1059
Comments
Does it work if you remove flags that were set by Thunderbird? |
Yes, all other emails can be flagged and unflagged just well For comparison, logs from an email that was not affected by the Sieve script:
|
Noticed a fun fact: after marking the problem email as unread and back as read, the
|
To clarify — flagging the problem email as
|
For the sake of science, I did the opposite — added the require "imap4flags";
setflag ["Junk"]; And I can clear this flag without any problems (as well as
|
What happened?
I was playing with Sieve scripts and once I noticed I can no longer mark some (but not all) emails as unread.
How can we reproduce the problem?
I can reproduce the problem by doing the following steps:
Create and activate a Sieve script that uses
setflag
, I made this one (using the ManageSieve protocol):Receive an email that will automatically be marked as read by the Sieve script
Deactivate / remove the Sieve script to make sure it can no longer affect any emails
Try to mark the email as unread (i.e. remove the
\Seen
flag, I use Thunderbird if this is important)Refresh the mailbox and notice the email is marked as read again for no reason
Version
v0.11.x
What database are you using?
RocksDB
What blob storage are you using?
RocksDB
Where is your directory located?
Internal
What operating system are you using?
Linux
Relevant log output
When I mark the email as unread, these lines appear in the log:
So Stalwart understands that the
\Seen
flag should be removed but doesn't remove it for some reasonCode of Conduct
The text was updated successfully, but these errors were encountered: