Re: Balsa/Pine bug



Gleef wrote:
> 
> 
> When Balsa sends out email, it includes a header line:
>   Content-Transfer-Encoding: x-unknown
> 
> When Pine receives this email, if this line is present Pine thinks that
> the text/plain message is in some foreign encoding, and forces you to go
> down two levels in the attachment viewer just to read the email.  If I
> remove that line manually from the mail file, the message displays
> normally.  If the line will just be filled in with "x-unknown", does Balsa
> really need to send it?

Yuck, that is a bug imported from mutt.  Balsa shouldn't set this
header at all if it doesn't know what it's talking about.

Pine is dumb about what it is doing, not recovering in an RFC-spec
manner.  BTW, tell the Pine guys they should not default to
base64-encoding text/plain attachments...  :)


> On a related note, Balsa labels its email as:
>   Content-Type: text/plain

Nine out of ten RFCs agree, this is ok.

	Jeff





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]