Hi Ken,
> - If it was run on a message with a CTE or Mime-Version header, it would
> error out.
...
> Why that specific behavior? No idea! But it was very deliberate.
I agree the earliest git commit checks both, but the RFC says C-T-E is
optional. I think the only mandatory MIME header is th
Hi Duane,
> Apparently, it depends on whether you define "MIME Message" as
> "Conforms to RFC 2045... or "Contains Readable Mime Data"...
If it does not conform to the RFCs then it doesn't contain readable
MIME. It contains data that could be interpreted as MIME if assumptions
are made, and that
>> - If it was run on a message with a CTE or Mime-Version header, it would
>> error out.
>...
>> Why that specific behavior? No idea! But it was very deliberate.
>
>I agree the earliest git commit checks both, but the RFC says C-T-E is
>optional. I think the only mandatory MIME header is the
Hi Ken,
> > I agree the earliest git commit checks both, but the RFC says C-T-E
> > is optional. I think the only mandatory MIME header is the version
> > so can't we ditch the other test? Otherwise it just leads to calls
> > to extend the list.
...
> I find it odd that it bails out on a Mime-Ve
>Is this just in the email headers, not the part headers?
Stepping back a bit ...
As I see it, the job of mhbuild is to take a "draft message" and turn
it into a valid MIME message; it's job is NOT to verify an existing MIME
message. When invoked in send with the -auto flag, it needs to decide
i
On Fri, 10 May 2019 12:58:22 -0400, Ken Hornstein said:
> >And many MIME-extension-fields may be present.
> >https://www.rfc-editor.org/rfc/rfc2045.html#section-9 suggests that's a
> >header matching /^content-/i, including `Content-: foo', I presume,
> >unless some RFC says a header can't end in
Hi Valdis,
> My under-caffeinated mind is whispering about a myth regarding ancient
> software
> on SunOS that stuck in things like 'Content-Type: uuencode' when using its
> pre-MIME scheme for sending non-text data.
https://www.mhonarc.org/archive/html/ietf-822/1994-12/msg00167.html
makes that
>> My under-caffeinated mind is whispering about a myth regarding ancient
>> software on SunOS that stuck in things like 'Content-Type: uuencode'
>> when using its pre-MIME scheme for sending non-text data.
Unclean!
>https://www.mhonarc.org/archive/html/ietf-822/1994-12/msg00167.html
>makes that
