[BUG] mail out bug report can send bad binary
danielv at netvision.net.il
danielv at netvision.net.il
Sat May 11 15:14:54 UTC 2002
Hi, Lex.
This is generally true becuase most code (MailMessage>>addAttachment:..)
adds things as base64 encoded. The code for sending a bug is not as
careful - because it is very useful that people see your bug info
without having to decode it, I left it clear.
It was useful enough for a long time.
I think we have some encoder in the image someone contributed that is
human readable and yet can transport non-quite-ascii stuff. If someone
cares to explore a little and use it from mail a bug, that'd be nice.
Daniel
Lex Spoon <lex at cc.gatech.edu> wrote:
> Ned Konz wrote:
> > I just tried to send out a bug report, but my mail server was
> > rejecting it.
> > I found that one of the instance variables -- a String containing
> > binary junk -- contained a LF character, some NUL characters, etc.
> >
> > I suspect that Celeste should be more careful about what it sends out
> > to make sure that it's properly encoded for RFC822.
>
> It *is* very careful. It's compliant with much newer RFC's for MIME,
> not just RFC 822. That's very interesting that you are seeing problems.
>
>
> One possible problem I've run into is attaching things from files when
> using CrLfFileStream. Squeak code is often not careful to choose ascii
> versus binary mode. If you read a binary file in ascii mode, then odd
> things can happen.
>
>
>
> Lex
More information about the Squeak-dev
mailing list
|