Stefan --
I've lost track of whether [the argument is that] mutt should put a
'name="*"' parameter on the Content-Type: header or [the complaint is
that] mutt expects such a parameter. It seems to me that either can be
fixed with scripts.
1) If we want mutt to provide the parameter, change $sendmail to a script
that automatically adds the name= data to the Content-Type: line and then
feeds everything on to sendmail.
2) If mutt wants to see the parameter, make a procmail rule that checks
for Content-Type: without a following name= and use formail to change it
and add the data from the Content-Disposition: header (may require a
separate script called by procmail to get the filename data and then feed
everything to formail).
In fact, it seems to me that a fairly generic perl filter could be written
which checks for a Content-Type: header, checks to see if it needs a name=
parameter, goes farther thru the message to get the info, changes the
Content-Type: header appropriately, and then spits the modified message
back out on stdout. You could then feed every outgoing message thru
that script and then sendmail via $sendmail on the way out, and then
feed every incoming message thru it with procmail on the way in.
This doesn't mean, of course, that I know anything about MIME or even
general email RFCs :-) If "everyone" out there expects a name= parameter,
maybe we could just hack mutt to spit out Content-Type: headers that way
with a leading X-Content-Type-Explanation: "for stupid mail clients like
dtmail" so that everyone knows we know why we're doing it ;-)
:-D
--
David T-G * It's easier to fight for one's principles
(play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie
(work) [EMAIL PROTECTED]
http://www.bigfoot.com/~davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
The "new millennium" starts at the beginning of 2001. There was no year 0.
Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh*
PGP signature
