From: Vladimir Volovich <vvv@vvv.vsu.ru>
Subject: Re: dealing with "mime" messages without c-t header
Date: 27 Oct 1998 12:03:11 +0300 [thread overview]
Message-ID: <m3iuh6cr74.fsf@vvv.vsu.ru> (raw)
In-Reply-To: Jason L Tibbitts III's message of "26 Oct 1998 20:56:56 -0600"
"JLT" == Jason L Tibbitts writes:
VV> often in mailing lists served by majordomo, and in other
VV> situations (gatewaying between fidonet and internet, etc) one can
VV> see messages which do not contain content-type header (which was
VV> lost after processing/gatewaying), but which were multipart/*
VV> before translation.
JLT> Majordomo? Pardon? Majordomo doesn't do anything with
JLT> Content-Type: headers. It certainly doesn't strip them unless
JLT> you go out of your way to configure it to do so.
Well, i meant majordomo-generated digests. When majordomo generates a
letter digest, it strips most of headers (except To, Subject, From,
Date), so MIME messages in digests become broken.
Best regards, -- Vladimir.
prev parent reply other threads:[~1998-10-27 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-25 7:43 Vladimir Volovich
1998-10-25 22:22 ` Lars Magne Ingebrigtsen
1998-10-27 2:56 ` Jason L Tibbitts III
1998-10-27 9:03 ` Vladimir Volovich [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3iuh6cr74.fsf@vvv.vsu.ru \
--to=vvv@vvv.vsu.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).