[quote user="Vincent Fatica"]
But I did discover that the queue's QDF file is not locked at daemon call-time and can simply be edited by the daemon. Now I have a working daemon in place getting rid of the "Sender: Maiser" header.
[/quote]
You MUST NOT DO THIS! This is so much of a problem that if I find that a Daemon is doing it, I will be forced to add code to Mercury to detect and suppress loading of that daemon. Mercury DOES provide a daemon-level method of modifying the raw data files of a job, but it's not shown in the current version of the daemon toolkit. Even so, that is the only approved way of modifying the actual data fork of a job, and you must not attempt to do it "behind Mercury's back" in this way.
The real problem here is the mail program that's trying to reply to Maiser. The RFC822/2822 definition of the Sender: field is quite unambiguous - it must be used whenever the entity sending the message is not the same entity as the one shown in the "From" field - the most usual example is a secretary sending a message on behalf of her boss. It makes no sense for the reply to go to the secretary - the mail program should be sending the reply to the actual author.
I'll consider adding an option to suppress or restructure the "Sender" field in an upcoming version of Mercury, but initially, I'd be trying to find out why the mail client is doing such a bizarre thing.
Cheers!
-- David --