On Wed, Jun 03, 2026 at 09:10:12AM +0200, [email protected] wrote:
why is Mutt even reading and encoding attachments prior actual sending?

It's not encoding the attachment at that time. It scans the attachment and decides what encoding will be used later, when writing the message out.

Other thing, why is mutt looking for atime instead of mtime? 'touch' or systemwide scripts (security scans, backups, whatever) shall modify only the former one. But I suppose portability is the keyword here...

It's comparing against mtime.

--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA

Attachment: signature.asc
Description: PGP signature

Reply via email to