Gnus development mailing list
 help / color / mirror / Atom feed
From: Vladimir Volovich <vvv@vvv.vsu.ru>
Subject: dealing with "mime" messages without c-t header
Date: 25 Oct 1998 10:43:10 +0300	[thread overview]
Message-ID: <m3af2lccj5.fsf@vvv.vsu.ru> (raw)

Hi,

often in mailing lists served by majordomo, and in other situations
(gatewaying between fidonet and internet, etc) one can see messages
which do not contain content-type header (which was lost after
processing/gatewaying), but which were multipart/* before translation.

would it be possible to view these messages in gnus as if they were
normal multipart messages? maybe, adding some command which will try
to treat the message as such a broken mime message will be possible?

as far as i understand, such a comand should look for the first line
in the message body starting with regexp "^--[^ ]*$" and treat the
"[^ ]*$" part as a boundary. Perhaps, gnus should default to
multipart/mixed C-T for such messages.

	Best regards, -- Vladimir.


             reply	other threads:[~1998-10-25  7:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-25  7:43 Vladimir Volovich [this message]
1998-10-25 22:22 ` Lars Magne Ingebrigtsen
1998-10-27  2:56 ` Jason L Tibbitts III
1998-10-27  9:03   ` Vladimir Volovich

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=m3af2lccj5.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).