[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bad rfc2047 encoding
From: |
Dave Love |
Subject: |
Re: bad rfc2047 encoding |
Date: |
30 Aug 2002 19:08:05 +0100 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 |
Simon Josefsson <jas@extundo.com> writes:
> Yes. It would be nice to have it do the right thing, but it seem to
> require at least a fairly working rfc 2822 parser/decoder. Lots of
> work, I think.
I don't think it should be so much work, at least for the fields
relevant here. I guess I'll have to do it if it means the difference
between mail getting delivered or not, but I've got other things to
do...
The thing is that there are already three or four different parsing
packages, including rfc822, ietf-drums (which should presumably be
rfc2822), mail-extr, mail-utils, and presumably things like supercite,
but none of them actually have an interface for tokenizing addresses
and it's not clear how correct they all are. Someone should sort this
out...
- bad rfc2047 encoding, Dave Love, 2002/08/15
- Message not available
- Re: bad rfc2047 encoding, Dave Love, 2002/08/20
- Re: bad rfc2047 encoding, Simon Josefsson, 2002/08/20
- Re: bad rfc2047 encoding, Dave Love, 2002/08/21
- Re: bad rfc2047 encoding, Simon Josefsson, 2002/08/21
- Re: bad rfc2047 encoding, Reiner Steib, 2002/08/21
- Re: bad rfc2047 encoding, Dave Love, 2002/08/22
- Re: bad rfc2047 encoding, Simon Josefsson, 2002/08/22
- Re: bad rfc2047 encoding,
Dave Love <=
- Message not available
- Re: bad rfc2047 encoding, Simon Josefsson, 2002/08/21
- Re: bad rfc2047 encoding, Dave Love, 2002/08/22
- Message not available
- Re: bad rfc2047 encoding, Bjørn Mork, 2002/08/22
- Re: bad rfc2047 encoding, Dave Love, 2002/08/30
- Message not available
- Re: bad rfc2047 encoding, Simon Josefsson, 2002/08/22