mirror of
https://github.com/HaschekSolutions/opentrashmail.git
synced 2026-04-25 14:45:59 +03:00
[GH-ISSUE #37] Deleting emails from web interface fails #24
Labels
No labels
bug
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/opentrashmail#24
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 @t10ss on GitHub (Jan 20, 2022).
Original GitHub issue: https://github.com/HaschekSolutions/opentrashmail/issues/37
I suspect it is due to nginx running under nginx user but files being created under root.
What's the fix for that?
@jackblk commented on GitHub (Feb 7, 2022):
I'm checking out the project, I use
docker run -it -p 25:25 -p 80:80 hascheksolutions/opentrashmailto run the server and I also cannot delete the email. My test email does not have attachment.Nice project by the way :).
@jfg commented on GitHub (Mar 23, 2022):
Hello, i have the same issue.
Impossible to delete mail from the client interface.
I use the app from the docker hub.
Thanks
@rlyttle commented on GitHub (May 14, 2022):
This still seems to be happening on master. The delete API request returns 200, but the web interface displays a popup showing
Error deleting email: Could not delete email. Permission problem?API request:
http://2049ad.com:8082/api.php?a=del&email=<EMAIL>@<DOMAIN>&mid=1652515203418&_=1652515026379Response Status code:
200Following deleting and clicking OK on the error alert, if I refresh the web page the email has been deleted (but the delete doesn't show in the UI unless I refresh).
[EDIT] Also, great project, thank you!
@geek-at commented on GitHub (May 15, 2022):
Oh man I forgot to return the actual return code of the deletion so even if the file was deleted successfully it would says permission problem. So that should be fixed now @rlyttle
@rlyttle commented on GitHub (May 15, 2022):
Many thanks @geek-at !