Lyndon Nerenberg lyn...@orthanc.ca writes:
On 2012-03-26, at 15:05 PM, Ken Hornstein wrote:
Weren't you and Paul Vixie supposed to be working on that?
Not me. I have other things I'm not working on!
This is one of the funnier lines I've read in a while :-).
--
Bill Wohler woh...@newt.com
Well, what if GNU Mailutils folks buy these changes? Then they would
have to change the header fields to mailutils-* which would be annoying.
Worse, it would then make the header fields incompatible when in fact
they would be compatible.
This header is just an implementation wart ... it's really
On 2012-03-25, at 20:40 PM, Bill Wohler wrote:
x-* is dead.
Hi Lyndon, I missed this discussion. Do you have a URL or two to
pertinent discussions?
This has been a general grumbling throughout the IETF for years now. There's
no single place it's getting discussed, but the issue crops up
Hi,
Deprecating Use of the X- Prefix in Application Protocols
http://tools.ietf.org/id/draft-ietf-appsawg-xdash-03.html
Cheers, Ralph.
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers
And this is why it's wrong to pretend they are headers. It leads to
exactly this sort of misunderstanding. I still say the syntax should
chance so there's no confusion as to what they really are - meta
commands to nmh programs.
I don't disagree with you, but I am
In message 201203160123.q2g1nay7018...@darkstar.fourwinds.com,
Jon Steinhart j...@fourwinds.com wrote:
valdis.kletni...@vt.edu writes:
--==_Exmh_1331860781_2149P
Content-Type: text/plain; charset=us-ascii
On Thu, 15 Mar 2012 18:02:48 PDT, Jon Steinhart said:
And yes, having defaults
In message 201203160200.q2g20jwt032...@hedwig.cmf.nrl.navy.mil,
Ken Hornstein k...@pobox.com wrote:
Full disclosure: I am using NMH version 1.3. Alas, version 1.4 has not
been ported to FreeBSD yet. (Is this the real root of the problem?)
When you say not ported ... do you mean, It doesn't
In message 201203160209.q2g29b1w019...@darkstar.fourwinds.com,
Jon Steinhart j...@fourwinds.com wrote:
Please excuse my ignorance here. What killed x-?
If anybody happens to know, I'd also like very much to find out who killed
Rosie Larsen.
Regards,
rfg
Sorry. I feel sure that this must be an FAQ, but how does one get this
message to go away, you know, so that I can actually send an attachment?
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers
In message 4f61a9c7.26063c0a.6da5.3...@mx.google.com, you wrote:
Ronald F. Guilmette writes:
Ummm... Well, now at least the failure message is different...
What now? attach four-leaf.jpg
What now? s
mhbuild: draft shouldn't contain MIME-Version: field
Ken Hornstein writes:
Is the attach command of whatnow making no attempt whatsoever to try
to determine the correct MIME content type specification? Is every
attachment just going to be sent as application/octet-stream?
Dude, you make it seem like using application/octet-stream is an
The only portion of the one I have here that seems at all relevant is
this:
For file names with dot suffixes, the context is scanned for a
mhshow-suffix- entry for that suffix. The content-type for
the part is taken from that context entry if a match is found.
If no
The only portion of the one I have here that seems at all relevant is
this:
For file names with dot suffixes, the context is scanned for a
mhshow-suffix- entry for that suffix. The content-type for
the part is taken from that context entry if a match is found.
If no
On Thu, 15 Mar 2012 18:02:48 PDT, Jon Steinhart said:
And yes, having defaults for common content types in the profile would
be a good thing. At the time that I wrote this stuff suffixes were not
nearly as standardized as they are today.
Wow. Maybe somebody should gather them all up into a
valdis.kletni...@vt.edu writes:
--==_Exmh_1331860781_2149P
Content-Type: text/plain; charset=us-ascii
On Thu, 15 Mar 2012 18:02:48 PDT, Jon Steinhart said:
And yes, having defaults for common content types in the profile would
be a good thing. At the time that I wrote this stuff
Lyndon Nerenberg writes:
On 2012-03-15, at 6:37 PM, Ken Hornstein wrote:
With X-MH-Attachment?
Could we please use nmh-* for this stuff? Just to make it clear this is
nmh-specific?
Are you suggesting having a header like nmh-attachment which is rfc-problematic
or just that we change
Full disclosure: I am using NMH version 1.3. Alas, version 1.4 has not
been ported to FreeBSD yet. (Is this the real root of the problem?)
When you say not ported ... do you mean, It doesn't work when I
tried to compile it?, because that's a serious problem. Or do you
mean, Not in the ports
On 2012-03-15, at 7:09 PM, Jon Steinhart wrote:
What killed x-?
The IETF has been trying to stamp out x-* headers and commands (off all forms)
for years. The momentum has finally grown to the point where it looks like it
will happen.
___
Anyway ... check out the man page for mhshow. And also mhn.defaults
has an example.
Hm, I realize now that attach does NOT CHECK mhn.defaults! Whoops.
Looks like you have to do extra work to make that happen.
Alright, so I just fixed that ... and I added a smattering of common
content types to
19 matches
Mail list logo
