Re: How to send a return receipt
> Well, the first thing that springs to my mind is some sort of
> message-hook (since that's what triggers when you view a message).
The difficulty with this approach is that you don't want to send an MDN
response any time you read the message, so you need to track whether the
message has ever been read and MDN-replied to. You can do this with
formail -D, but that involves an external Message-ID cache, separate
from the message store, wherever that might be.
I suppose that's one reason that Werner chose to implement this as a
patch instead of as a set of macros/script(s). But it might not be
compelling for everyone.
The patch certainly provides better functionality than hooks, macros,
and scripts do, given the usual constraints. Whether the better
functionality is necessary functionalty is debatable, but I'm not sure
it's worthwhile to debate it unless committers are wavering about
committing the patch. Otherwise it's clear what you should do: patch
mutt if you're comfortable patching, or settle for scripts if they're
sufficient.
--
-D. dgc@xxxxxxxxxxxx NSIT University of Chicago
"Polka music needs to prevail." John Ziobrowski, Polka America Corporation