Re: Mutt can not delete mails
Am Donnerstag, 11. November 2021, 21:53:53 CET schrieb Greg Wooledge:
No, it is not /tmp, but /var/tmp. See here from the output:
[2021-11-11 22:08:33] mutt_addr_is_user: no, all failed.
[2021-11-11 22:08:33] mutt_addr_is_user: no, all failed.
[2021-11-11 22:08:36] mutt_index_menu[807]: Got op 167
[2021-11-11 22:08:39] /var/mail/myusername wird geschrieben …
[2021-11-11 22:08:39] Sortiere Postfach …
[2021-11-11 22:08:39] ../../mbox.c:895: mutt_mktemp returns "/var/tmp/mutt-
protheus2-1000-47311-14301765248385272183".
[2021-11-11 22:08:39] Temporärdatei konnte nicht erzeugt werden!
[2021-11-11 22:08:44] Sortiere Postfach …
[2021-11-11 22:08:44] /var/mail/myusername kann nicht geschrieben werden!
[2021-11-11 22:08:44] mutt_addr_is_user: no, all failed.
[2021-11-11 22:08:44] mutt_addr_is_user: no, all failed.
[2021-11-11 22:08:44] mutt_addr_is_user: no, all failed.
Sorry, it is in German and I changed my username to "myusername".
Note, that /var is on its own partition. The rights settings are:
ls -la / | grep var
drwxr-xr-x 13 root root 4096 2. Sep 18:37 var
ls -la /var/ | grep tmp
drwxr-xr-x 26 root root 12288 12. Nov 18:53 tmp
So I do not have the right, to create files in /var/tmp. I wonder, if either
the mutt settings are wrong, or the settings of /var and /var/tmp.
Best regards
Hans
> On Thu, Nov 11, 2021 at 02:48:25PM -0600, David Wright wrote:
> > There should be some indication at this point of why it can't
> > delete your emails. The reason you see the filename
> > /home/username/.mutt-cache/scratchpad/mutt-hostname… above is
> > that I have set tmpdir="$HOME/.mutt-cache/scratchpad" in my
> > muttrc file. I use that, rather than /tmp, because it is encrypted
> > along with all of /home. But it means I have to clean it occasionally.
>
> If mutt normally writes these "temporary files" in /tmp (whaaat, how do
> you guarantee an atomic move from /tmp to /var/mail??) then the OP
> should at least check the perms and ownership of /tmp.
>
> ls -ld /tmp
>
> We've seen *so* many people with messed-up /tmp ownership lately.
Reply to: