[imp] address book -> compose window

Rong-En Fan rafan at csie.org
Tue Sep 7 20:53:58 PDT 2004

On Tue, Sep 07, 2004 at 02:44:02PM -0400, Chuck Hagenbuch wrote:
> Quoting Rong-En Fan <rafan at csie.org>:
> > As you see, we call RFC822::parseAddressList()
> > before we do MIME:encode(), then in parseAddressList()
> > it calls _splitAddresses() which calls _splitCheck().
> > In _splitCheck() enforces RFC822's address format check.
> It looks to me like this could be fixed by using a multibyte-aware
> substr() call
> in _splitCheck in the check for trailing \ characters - that sound
> right to you?

It sounds nice, but besides \ there are also [ ] < > in big5

> > In my opinion, I think those addresses should be encoded
> > before using RFC822's parser.
> Okay. So we need a way to split up the list of addresses that doesn't involve
> calling RFC822 but still handles RFC822 groups, etc.
> The more I think about this, the more it seems like we ought to store
> the actual
> addresses vs. what we display to the user seperately, and pre-encode
> individual
> addresses so that we don't have to worry about all this.
> Thoughts?
> -chuck

When I went home last night, I thought about doing this way.
If users selects addresses from addres books, it is ok.
But if they enter it manually, we can not do this pre hand.
Have any idea to solve is?


More information about the imp mailing list