It should be fixed in future sm versions, but I can't give any time estimates.
If you want quick solution - make sure that your xml file is human readable. I suspect that xml parser does not care about line feeds between xml tags and humans have problems reading long lines. > Dear Tomas > Thanks for your answer > What does it mean in generally ? I'm not skillfull in programming and > programming expression : ). > Does it mean that I cannot send content type attachment 'text' with more > than 998 characters in one line via SM? > What is result ? Could it be fixed in the future releases ( Other > clients doesn't have this problem )? > Thanks > BR > Pet > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Tomas Kuliavas > Sent: Friday, April 21, 2006 7:47 PM > To: squirrelmail-users@lists.sourceforge.net > Subject: RE: [SM-USERS] Problem with xml attachment-base64 transfer > encoding > > If content type is 'text' or 'message', SquirrelMail uses 8bit transfer > encoding. > > Behavior can be altered by changing writeBodyPart and prepareMIME_Header > functions. There functions are related. I am not sure about right > modification. Not sure if I have located right part of code. > > https://sourceforge.net/tracker/index.php?func=detail&aid=1473714&group_ > id=311&atid=100311 > > >> Thanks for your answer >> What should I change in this file ? >> If I want to turn on base64 transfer encoding do I need to make a > "hack" >> ? >> Everyone have to do this change in Deliver.class.php ? >> I saw some headers in the SM mailing lists and some users use this >> base64 tranfer encoding >> Doesn't do this SM automatically ? >> Thanks in advance >> >> Pet >> >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of >> Tomas Kuliavas >> Sent: Thursday, April 20, 2006 6:23 PM >> To: squirrelmail-users@lists.sourceforge.net >> Subject: RE: [SM-USERS] Problem with xml attachment >> >>> >>> >>> Thanks a lot for your answer Tomas, >>> How can I turn on base64 transfer encoding in SM >> >> You will have to modify class/deliver/Deliver.class.php functions. >> >>> That is to say my xml file has one row with at least 1000 characters >>> >>> -----Original Message----- >>> From: [EMAIL PROTECTED] >>> [mailto:[EMAIL PROTECTED] On Behalf Of >>> Tomas Kuliavas >>> Sent: Thursday, April 20, 2006 4:01 PM >>> To: squirrelmail-users@lists.sourceforge.net >>> Subject: RE: [SM-USERS] Problem with xml attachment >>> >>> RFC 2822 >>> 2.1.1. Line Length Limits >>> >>> If plain text attachment uses wide lines, we might have to use base64 > >>> transfer encoding in order to preserve attachment. >>> >>> >>>> Now I noticed that this is not problem xml file, but every file >>>> with >> >>>> bytes more then 990 in one row. >>>> I send simple txt file with 1000 "aaaaa" in the row and I got 1001 >>>> characters. Space was added after 990th "a" >>>> Thanks a lot for advices >>>> Pet >>>> >>>> -----Original Message----- >>>> From: Jevos, Peter >>>> Sent: Thursday, April 20, 2006 3:24 PM >>>> To: squirrelmail-users@lists.sourceforge.net >>>> Subject: RE: [SM-USERS] Problem with xml attachment >>>> >>>> >>>> Hello >>>> >>>> I completely reinstalled new linux system with new SM and tried to >>>> send this xml file through SM to the other server without SM When I >>>> received it SM again add CR LF Space after 990th byte and got "XML >>> Parsing Error: >>>> not well-formed" after I opened it. >>>> Is there some way how could I debug it and find the problem part ? >>>> Please try to send this xml file ( without any changes and format ) >>>> When I add an this xml attachment SM displays : origin.xml- >>>> text/xml(1.6 k) Do you have the same problem ? >>>> >>>> Thanks a lot for answers >>>> >>>> Pet >>>> >>>> -----Original Message----- >>>> From: [EMAIL PROTECTED] >>>> [mailto:[EMAIL PROTECTED] On Behalf Of > >>>> Tomas Kuliavas >>>> Sent: Monday, April 10, 2006 9:36 PM >>>> To: squirrelmail-users@lists.sourceforge.net >>>> Subject: RE: [SM-USERS] Problem with xml attachment >>>> >>>>> Thanks for your answer, >>>>> I tried to use evrythinnk like you said. >>>>> So I used SM 1.4.6 without any plugins but problem still remains. >>>>> I tried tou use other MUA to send xml message but result was good ( > >>>>> it >>>> >>>>> means postfix is not involved ) So I'd like to provide you >>>>> config.php >>> >>>>> ( without themes ) and user file, probably you'll find difference >>>>> against your configuration: >>>> >>>> Could you enable message_details plugin and show us xml message part >>>> headers? >>>> >>>> Maybe Content-Type and Content-Transfer-Encoding headers might help >>>> in locating code that parses xml file incorrectly. >>>> >>>> -- >>>> Tomas ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 -- squirrelmail-users mailing list Posting Guidelines: http://www.squirrelmail.org/wiki/MailingListPostingGuidelines List Address: squirrelmail-users@lists.sourceforge.net List Archives: http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.user List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
