I just committed support for Content-Disposition headers in mhbuild directives. I elected for the point solution, using optional {}, instead of a more general solution. It just seems more appropriate to me. And there are no issues with backward compatibility. David _______________________________________________ Nmh-workers mailing list Nmh-workers@nongnu.org http://lists.nongnu.org/mailman/listinfo/nmh-workers
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Re: [Nmh-workers] A script for threading, Peter Galbraith |
---|---|
Next by Date: | [Nmh-workers] Somebody out there have a virus or something? Also release stuff., Jon Steinhart |
Previous by Thread: | Re: [Nmh-workers] mhbuild Content-Disposition header, David Levine |
Next by Thread: | Re: [Nmh-workers] suppress Content-ID's with new mhbuild option?, Joel Reicher |
Indexes: | [Date] [Thread] [Top] [All Lists] |