From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: dealing with "mime" messages without c-t header
Date: 25 Oct 1998 23:22:59 +0100 [thread overview]
Message-ID: <m3btn0qo1o.fsf@sparky.gnus.org> (raw)
In-Reply-To: Vladimir Volovich's message of "25 Oct 1998 10:43:10 +0300"
Vladimir Volovich <vvv@vvv.vsu.ru> writes:
> 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.
If someone were to write such a command, I'd apply the patches. (The
command would have to guess what the separators were, and then insert
MIME headers into the header, and then just call gnus-display-mime.)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1998-10-25 22:22 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 [this message]
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=m3btn0qo1o.fsf@sparky.gnus.org \
--to=larsi@gnus.org \
/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).