Gnus development mailing list
 help / color / mirror / Atom feed
From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: mail-extr.el brokenness
Date: Tue, 02 Jul 2002 14:35:27 -0400	[thread overview]
Message-ID: <87u1nix9jk.fsf@alum.wpi.edu> (raw)
In-Reply-To: <m2bs9qzb31.fsf@tnuctip.rychter.com>

Jan Rychter <jan@rychter.com> writes:

> Are there plans to work on mail-extr, rewrite it, maybe replace it
> with something else?

I went through this a few weeks ago wrt bbdb not working with Kai's
newly encoded latin-9 name.

> Any useful advice?

Well, the conclusion we came to was that mail-extr should *not* have
to deal with 8 bit characters, since 8 bit characters are not allowed
in message headers.

What should be done is:

1) extract the header contents with mail-extr functions from the raw
   message
2) decode any encoded header contents
3) use (for bbdb, etc...)

Does this make sense?  Are you having these problems when dealing with
bbdb, or something else?

ttyl,

-- 
Josh Huber



       reply	other threads:[~2002-07-02 18:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m2bs9qzb31.fsf@tnuctip.rychter.com>
2002-07-02 18:35 ` Josh Huber [this message]
     [not found]   ` <m2vg7xx4h6.fsf@tnuctip.rychter.com>
2002-07-02 20:46     ` Josh Huber
2002-07-02 18:52 ` Simon Josefsson

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=87u1nix9jk.fsf@alum.wpi.edu \
    --to=huber@alum.wpi.edu \
    /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).