Skip to content
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

IMAP: Delete (move to trash) no longer issues EXPUNGE command #7721

Closed
2 tasks done
PRBUK opened this issue Mar 15, 2024 · 3 comments · Fixed by #7722
Closed
2 tasks done

IMAP: Delete (move to trash) no longer issues EXPUNGE command #7721

PRBUK opened this issue Mar 15, 2024 · 3 comments · Fixed by #7722
Assignees
Labels
type: bug Something is causing incorrect behavior or errors

Comments

@PRBUK
Copy link

PRBUK commented Mar 15, 2024

Checklist

  • I have used the search function to see if someone else has already submitted the same bug report.
  • I will describe the problem with as much detail as possible.

App version

6.712

Where did you get the app from?

Other

Android version

12 and 14 - Manufacturer Shipped (Samsung)

Device model

Samsung Galaxy Tab S4/9 and phone S10+

Steps to reproduce

Delete a message (say from Inbox) using K9 Client

Expected behavior

The message is moved (ie: deleted from Inbox) and placed in Deleted Items (Trash)

Actual behavior

In version 6.711 deletion works as expected.
In version 6.712 a copy is placed in Deleted Items and the original email only marked for deletion in Inbox, when viewed on Webmail. It no longer displays in K9, however the email still counts towards the number of emails held in the K9 Inbox. (Probably the move is performed but the delete from Inbox partially fails - marked for delete rather than deleted).

The Server is running legacy software from a company that is no longer trading, so the change in 6.712 'Added support for the IMAP MOVE extension' may be the root cause. I am unable to update the software if this new IMAP extension was added after the last server software release.

Accepting that a move to a new platform is ultimately inevitable, but is a longer term requirement, is it possible to detect the failure of the new command (or test whether the server supports the command) and fall back/revert to the previous method if not - which has been working perfectly for a long time!?

A debug log of a successful deletion under 6.711 and a subsequent failed deletion after upgrading to 6.712 is attached (APKs retrieved from GitHub Assets)

The issue was discovered when the latest version (6.800) was pushed from the Google Play Store. The ticket relates to a posting of a similar title in the support forum

Logs

V6.711 08-40 k9mail-logs.txt
V6.712 08-50 k9mail-logs.txt

@PRBUK PRBUK added type: bug Something is causing incorrect behavior or errors unconfirmed Newly reported issues awaiting triage or confirmation labels Mar 15, 2024
@cketti
Copy link
Member

cketti commented Mar 15, 2024

No longer issuing an EXPUNGE command when moving a message ("delete" is moving a message to the trash folder) was an intentional change. See #7366.

However, I can now see that this was a mistake. When a trash folder is used and the expunge policy is set to "immediately" there's never a situation where a regular EXPUNGE command is issued (in folders other than the trash folder).

Side note: You should look into updating your server software. Not supporting the MOVE or UIDPLUS extensions makes for a subpar user experience.

@cketti cketti changed the title Delete No Longer Purging from the Server IMAP: Delete (move to trash) no longer issues EXPUNGE command Mar 15, 2024
@cketti cketti removed the unconfirmed Newly reported issues awaiting triage or confirmation label Mar 15, 2024
@cketti cketti self-assigned this Mar 15, 2024
@PRBUK
Copy link
Author

PRBUK commented Mar 15, 2024

Your Side Note: acknowledged in my original 'Actual Behaviour' comments - but as the supplier is no longer trading, there is no upgrade path. The platform provides more than email and still meets our needs. I need to find another solution and work out a migration plan!

Do I take it from your comments that a future release will be able to once again co-exist with my platform? If so, Thank You!!

@cketti
Copy link
Member

cketti commented Apr 17, 2024

This should be fixed in K-9 Mail 6.802.

@cketti cketti closed this as completed Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something is causing incorrect behavior or errors
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants