Text-wrapping should really be accomplished using a MailMessage object,
not by messing with the raw message text.  A
MailMessage>>withTextWrapped message would seem like a good way to do it.


-Lex




Ned Konz <ned at bike-nomad.com> wrote:
> MailMessage>>asSendableText  wraps MIME attachment headers, thereby damaging them. It changes:
> 
> -==CelesteAttachment61739==
> Content-Type: application/octet-stream; name="InvertChangeListSelections-nk.cs.gz"
> Content-Disposition: attachment;
> 
> into:
> 
> -==CelesteAttachment61739==
> Content-Type: application/octet-stream;
> name="InvertChangeListSelections-nk.cs.gz"
> Content-Disposition: attachment;
> 
> If you have wordwrap on, it broke the Content-Type: line into two at the space before name=.
> 
> This breaks mail readers.
> 
> I notice that there are vestiges of code to look for attachments, but they're commented out.
> This is probably because they wouldn't work right; they'd look for the line that started with
> -== and assume that it started an attachment. Not all do (in this message, I have 3 such lines
> in the body).
> 
> What probably should happen is that the separator should be looked for. But the separator
> doesn't seem to be set when I get a message from the MailDB. This information is in the
> boundary= attribute of the Content-Type: field in the body.
> 
> -- 
> Ned Konz
> currently: Stanwood, WA
> email:     ned at bike-nomad.com
> homepage:  http://bike-nomad.com