mirror of
https://github.com/d99kris/nmail.git
synced 2026-04-26 09:46:01 +03:00
[GH-ISSUE #173] "Move message failed" when trying to delete #126
Labels
No labels
bug
enhancement
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nmail#126
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @graysky2 on GitHub (Dec 15, 2024).
Original GitHub issue: https://github.com/d99kris/nmail/issues/173
Originally assigned to: @d99kris on GitHub.
Description: When I hit "D" to delete a message, I get "Move message failed". I set
trash=Trashwhich corresponds to the name on the server. I also tried settingcopy_to_trash=1but get the same. Is there something else I need to configure?How to reproduce it: Attempt to delete a message as described above.
Environment:
Screenshot of web interface to mail provider:

@d99kris commented on GitHub (Dec 15, 2024):
Hi @graysky2 - if you press left arrow (or <) to view the folder list, is the trash folder listed with the same name there?
(You can press right or > or enter to go back to inbox after checking)
If the name is matching, please help share your log file from
~/.config/nmail/log.txtThanks!
@graysky2 commented on GitHub (Dec 15, 2024):
Yes, the name is present and is the same as I defined in the config file:

Here is the basic log without verbose options:
I started with:
nmail -eto generate this log. Let me know if I need to use-ee:EDIT: I just build the latest commit and am seeing the same error.
@d99kris commented on GitHub (Dec 17, 2024):
Thank you 👍 Do you happen to know what software the email server is running? I see you're using port 143 which is not super common (unencrypted typically) unless you're on a LAN/VPN, so I am wondering if it's some old outdated server version perhaps. And you did try
copy_to_trash=1already - do you know if the log.txt looked same during that test (gettingMAILIMAP_ERROR_PROTOCOL)?If the email service you're using is something provided free to "anyone", please let me know, then I can sign up and troubleshoot.
Otherwise, yes a log using
-eecould help (it will dump most IMAP communication, including handshaking about supported functionalities). It can contain some private information, so please review before sharing, or just send it to my personal email address d99kris at gmail dot com, and I will delete the information after reviewing the relevant parts.@graysky2 commented on GitHub (Dec 17, 2024):
copy_to_trash=1set using the latest commit behaves as expected. No error and mails go to the trash.I will close this, thanks for your help and for developing nmail. I love it.
@graysky2 commented on GitHub (Dec 17, 2024):
@d99kris - as a side question, is there an option I can set to have nmail not ask me if I am sure I want to delete the message, ie just delete it?
@d99kris commented on GitHub (Dec 18, 2024):
Thanks, that's good to hear 👍
Yes. While nmail is not running, edit
~/.config/nmail/ui.confand setdelete_without_confirm=1, then start nmail again.