[rt-devel] Strange attachment parsing

[Dmitry Sivachenko]

On Wed, Jun 11, 2003 at 09:46:33PM +0800, Autrijus Tang wrote:
> On Wed, Jun 11, 2003 at 05:42:27PM +0400, Dmitry Sivachenko wrote:
> > Content-Disposition: inline
> > Content-Transfer-Encoding: binary
> > 
> > Wouldn't it be more sane to send it with
> > Content-Transfer-Encoding=queted-printable instead of 'binary'?
> 
> Maybe.  Maybe not.  Since RT does not preserve incoming
> attachment's transfer encoding, the best bet you have
> would be passing an extra pair of option:
> 
>     Encoding	=> '-SUGGEST'
> 
> to the $MIMEObj->attach() function.  Let me know if it
> works for you.
> 


YES!

It works exactly as I want.

It would be nice if you integrate this into next release.

Thank you very much for your help!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://pallas.eruditorum.org/pipermail/rt-devel/attachments/20030611/23040815/attachment.pgp