-
-
Notifications
You must be signed in to change notification settings - Fork 290
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
🐛: Email cannot be deleted after moving it #1201
Comments
Log with Debug turned up to 5 on a MacOS system using mail, attempting to delete a message, and it immediately being rejected. |
I'm unsure if I'm affected by #1201 or #1199, but this sounds 1% more like my issue. I have 1 single user (me) on stalwart, with 1 single e-mail address (mine) and I only have 2 E-Mails in my Inbox, but I see 4 E-Mails on my iPhone's Inbox. Here are trace logs from stalwart this morning. I tried it two times and the relevant lines seem to be:
Here is the complete log:
|
@xenadmin Looking at your logs it looks like an Apple bug: Here your client is selecting "Inbox" and Stalwart is indicating that there are only 2 messages. * OK [CLOSED] Closed previous mailbox\r\n* 2 EXISTS\r\n* FLAGS (\\Answered \\Flagged \\Deleted \\Seen \\Draft)\r\n* 0 RECENT\r\n* OK [PERMANENTFLAGS (\\Deleted \\Seen \\Answered \\Flagged \\Draft \\*)] All allowed\r\n* OK [UIDVALIDITY 3930792974] UIDs valid\r\n* OK [UIDNEXT 117] Next predicted UID\r\n* OK [HIGHESTMODSEQ 224762049875775520] Highest Modseq\r\n* OK [MAILBOXID (ieaaaaaa)] Unique Mailbox ID\r\nL38 OK [READ-WRITE] SELECT completed\r\n Here your client is searching for all messages in the folder and Stalwart indicates there are only two messages with UIDs 83 and 116: L46 UID SEARCH RETURN (ALL) UID 1:120\r\n
* ESEARCH (TAG "L46") UID ALL 83,116\r\nL46 OK UID SEARCH completed\r\n Then your client is trying to move message with UID 113 which is not included in the results: L57 UID MOVE 113 "Deleted Items"\r\n
L57 NO No messages were found.\r\n Can you check the logs prior to the ones you provided above? It might provide some hints on where is Apple Mail obtaining this UID 113 from. Edit: Perhaps the message has been already moved but your client failed to parse the response. |
@mtomasek780 Similar to what I wrote above, please check in the logs previous occurrences of the UID 2142 as it no longer exists in that folder. |
Happy to work to review and post those logs this weekend, @mdecimus . My only follow-up question is in my case, I have the same issue using Thunderbird on Fedora and Apple's mail apps, so does that change your opinion on my log at all? |
@mtomasek780 Yes, according to the logs posted the error message returned by Stalwart is correct because that UID does not appear in the results. We need to find out at which point the mail client got "confused" to believe that message is there. |
There seem to be two issues:
|
I can't turn up logging right now, But I wanted to add that I can reproduce situation #1 described by @NathanHbt :
I delete some messages, hit cmd-z to undo it, and then delete them again, and they reappear after a second in the mailbox. |
If you can reproduce this on a blank account and provide the raw IMAP logs from start to finish it will certainly help. I use Apple Mail on Mac and iOS and could not reproduce it unfortunately. |
I have ran into this issue several times in the last few weeks also. After un-junking messages, they remain 'stuck' in the inbox and can't be archived or deleted. This affects my iOS device and Apple Mail on MacOS. I am unable to reproduce the issue right now of course, but I've definitely seen it as recently as two days ago. |
My issue with finding the details in the logs is that I have hundreds of users, and only a few are reporting the issue, and typically not until late in the process, and I'm not in a position to tell them "okay, do it right now" or to sequester them to a different stalwart instance. If you have any suggestions on how to pare down voluminous logs to find the ones that might most directly apply, I'm open to trying to filter out through hundreds of thousands of lines of logging data.... |
If anyone in this thread can help by posting here the raw IMAP logs it will certainly help. I can't reproduce this issue on Mac or iOS. The logs provided before do not help because they show that your client is using a UID that no longer exists, so I need to see what happened before that point. Perhaps you could create a fresh Stalwart setup on a temporary container, reproduce the issue with logging on and then send them over. |
I will try to do that by the end of the week, on a secondary instance. |
I hope this helps. I had the issue happen on an account and was able to grab the logs right away. There are thousands of users on this cluster of servers, but I found the smtp delivery of the message in question, and then pulled all the following entries based on the IP address of the user reading the message. They deleted the message, and it reappeared right away. Mac OS Sequoia 15.1.1 |
What happened?
A similar issue to bug #1199 , when I moved a group of messages from junk to the inbox, I am unable to delete the messages. I have tried the following steps:
How can we reproduce the problem?
I used macOS 15.1.1 and Apple Mail, I simply dragged the messages out of Junk and into the Inbox. There was no error displayed, but when I tried to delete the messages, I received errors.
Version
v0.11.x
What database are you using?
RocksDB
What blob storage are you using?
None
Where is your directory located?
Internal
What operating system are you using?
Docker
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: