> From: http://www.cs.utk.edu/~moore (Keith Moore) > Date: Mon Jan 4, 10:58pm > > > However, there are plenty of user agents that will deal better with the > > name= parameter on the Content-Type header than with the filename= > > parameter of the Content-Disposition header. > > Except for applicaiton/octet-stream, those user agents are broken. > > > Adding Content-Disposition to metasend isn't all that hard though; I > > did it by adding a -N filename option, and arranging things such that > > if that option was given, a disposition of "attachment" was used, otherwise > > it was treated as "inline". Just look for all the instances of code > > supporting the existing Content-Description header, and add additional > > variables and code modelled on that. > > I've done much the same thing to my version of metamail, which > (along with other portability fixes) I plan to release in a few days. > > Keith Hi. Did you release this code (metamail)? Also, you might consider my patch that's in http://dummy.us.eu.org/robert/software/procmail/mime.shtml It makes the -x flag work better.