Temporary files are not cleaned up from where they're created.
It seems that it is safe to remove a file after mutt has openned it,
because it hangs on to the same file descriptor, and thus the file is
not yet removed from disk.
A cleanup routine, that would look at /tmp/$uid/TemporaryItems/
MailtoMutt-* and remove files older than ... might be a good idea,
because it is not really a problem if there are a few files lying
around.
I don't know how often these are cleaned up by the OS. I assume
no more frequently than every login, probably only every restart
from the RC file.
On machines with lots of uptime, and heavy MailtoMutt usage, this
could be a /slight/ (i don't think very practical) problem. The
cleanup solution solves this scenario.
An interesting solution, nice way to learn new stuff is to present a
model dialog bitching to the user if more than N files exist, and
asking whether to zap or keep them.