On Wed, Jun 03, 2026 at 01:17:18AM +0200, Vincent Lefevre wrote:
With Mutt based on db9200c7, after writing a mail message (using the Emacs editor), I did <send-message> to send it. But I got the following message:Attachement #1 modifié. Mettre à jour le codage pour /var/tmp/mutt-qaa-1000-7767-3138321168908816236 ? ([oui]/non): which would be Attachment #1 modified. Update encoding for /var/tmp/mutt-qaa-1000-7767-3138321168908816236? ([yes]/no) in English (this corresponds to the body of the message). Ditto when I typed ^G then did <send-message> again. The problem disappeared with <edit-message> and quitting the editor. This was the first time I had such an issue. And there is nothing in the logs around the initial timestamp of this file. I'm wondering what happened.
Can you duplicate the issue?I see where the check takes place: in compose.c check_attachments(), where it compares the the mtime of each attachment with Mutt's internal record before sending. That's called in OP_COMPOSE_SEND_MESSAGE.
Somehow, the file's mtime was modified, but mutt's internal stamp was not updated. I don't think I've touched anything about that recently, but it would be helpful if you can repeat the problem.
Thank you! -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
