From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: mime problem
Date: 20 Apr 2000 02:40:52 +0200 [thread overview]
Message-ID: <m3hfcxbo4r.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <vafvh1wp3yi.fsf@lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Try typing `A D' (or C-d?) on the message and have a look at the
> central part. Maybe if nndoc grokked that, too, it would be really
> useful?
nndoc could try to grok non-MIME mail bounces, but it would be
guesswork. Some of those bounces are really difficult to figure out.
It would be nice if there was a function (kinda along the lines mm-uu)
that goes through the bounced message, tries to guess at what's the
bounced message, and then return a list of MIME handles for Gnus to
process. That would be helpful...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2000-04-20 0:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-05 18:45 lconrad
2000-04-05 19:14 ` Kai Großjohann
2000-04-05 19:30 ` Alan Shutko
2000-04-05 22:40 ` Kai Großjohann
2000-04-05 22:39 ` Kai Großjohann
2000-04-06 14:31 ` Laura Conrad
2000-04-20 0:40 ` Lars Magne Ingebrigtsen [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=m3hfcxbo4r.fsf@quimbies.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).