[Nmh-workers] x-unix-mode MIME parameter?
So I think people know I've been working on the attach stuff, as part of the always running mhbuild so we don't send out invalid messages all of the time problem. As part of this, I've noticed that when you run attach with -attachformat 0, you get a x-unix-mode MIME parameter. My question is: why? Obvious no standard defines this MIME parameter. We don't do anything with this parameter upon receipt. I don't actually know which MUAs process such a parameter. It looks like maybe an old version of Apple Mail might have SENT such a parameter, but I don't know if would ever do anything with it. I guess what I'm really wondering is ... should we even provide any support for an attachformat other than 1? The big difference between 1 and 2 is the modification-date MIME parameter (which is actually standardized in RFC 2183). --Ken ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] x-unix-mode MIME parameter?
What ho, Ken! Obvious no standard defines this [x-unix-mode] MIME parameter. We don't do anything with this parameter upon receipt. I don't actually know which MUAs process such a parameter. It looks like maybe an old version of Apple Mail might have SENT such a parameter, but I don't know if would ever do anything with it. Do you know about Debian Code Search? http://codesearch.debian.net/search?q=x-unix-mode. Various packages mention it, the top hit for me is a comment, We use the x-unix-mode convention from dtmail 1.2.1 SunOS 5.6. I didn't find any web page defining it but did see that dtmail is now available with the source-release of CDE. http://sourceforge.net/p/cdesktopenv/code/ci/master/tree/ Don't know if that has clues. It isn't in Debian Code Search AFAICS. Cheers, Ralph. ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] x-unix-mode MIME parameter?
Ken wrote: So I think people know I've been working on the attach stuff, as part of the always running mhbuild so we don't send out invalid messages all of the time problem. As part of this, I've noticed that when you run attach with -attachformat 0, you get a x-unix-mode MIME parameter. My question is: why? Jon did it that way originally, I don't know why. I needed a different format, with a Content-Disposition. When I created that, I dropped the x-unix-mode. Fine with me if we want to drop -attachformat support. David ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] x-unix-mode MIME parameter?
On Mon, Jan 13, 2014 at 9:17 PM, Jon Steinhart wrote: I've noticed that when you run attach with -attachformat 0, you get a x-unix-mode MIME parameter. My question is: why? Jon did it that way originally, I don't know why. I needed a different format, with a Content-Disposition. When I created that, I dropped the x-unix-mode. ... I'm embarassed to say that I don't remember why I did that. I think that it was because I looked at attachment headerss in emails that I received, maybe even some created by mhbuild, and they had it. Looks like an AppleMail thing, at least based on some simple searching on the Net. IMO, it is useless, and a security problem if MUAs honor the parameter when saving an attachment. --ewh ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] x-unix-mode MIME parameter?
I'm embarassed to say that I don't remember why I did that. I think that it was because I looked at attachment headerss in emails that I received, maybe even some created by mhbuild, and they had it. I didn't do the -attachformat stuff, someone else did and I have never used it so wouldn't notice if it went away. Okay, that sounds plausible about the origins ... I used the Debian Code Search (thanks, Ralph! Didn't know about it!) and it seems like most of the uses of it appear in regression tests for OTHER MUAs. It doesn't sound like anyone objects if we drop support for sending this via attach (users are of course free to construct their own headers via mhbuild directives and include whatever MIME parameters they want). And I've got to agree with Earl ... sure seems like a big potential security problem to me. --Ken ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
