-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
don't show some message in HTML format #2561
Comments
Comment by @alecpl on 4 Dec 2009 13:10 UTC Attach sample message source, please. |
Milestone changed by @alecpl on 4 Dec 2009 13:10 UTC later => 0.4-beta |
Status changed by @alecpl on 11 Dec 2009 19:48 UTC new => closed |
Comment by borigoto on 8 Jan 2010 14:10 UTC Hi! First, sorry, my english is very bad... I have the same error, but, not exist comments in my message.
I'm using 0.3.1 instaled from zero. In 0.2 version, this message is show ok! []'S |
Status changed by borigoto on 8 Jan 2010 14:10 UTC closed => reopened |
Comment by @alecpl on 8 Jan 2010 14:22 UTC Works for me with svn-trunk version. |
Status changed by @alecpl on 8 Jan 2010 14:22 UTC reopened => closed |
Comment by borigoto on 8 Jan 2010 15:00 UTC Hi Alec! I'm create new installation from: svn checkout https://svn.roundcube.net/trunk The sign is: RoundCube Webmail/0.3-trunk, but, the problem persists... What is a file used to show messages? I look but not sure exactly file.. []'s |
Status changed by borigoto on 8 Jan 2010 15:00 UTC closed => reopened |
Comment by @alecpl on 8 Jan 2010 20:16 UTC what PHP version/OS, what browser? check Roundcube logs. |
Comment by borigoto on 9 Jan 2010 13:07 UTC Hi Alec, I use PHP: ~# php -v And OS is: ~# cat /etc/issue 100% stable. Again, old version of RoundCube, show the message correctly. I tested version from SVN and 0.3.1 in other 2 machines, Debian SID and Debian Testing, ever installing from zero, and, same problem :( I using for tests IE8, Chrome and Firefox 3.5 from Windows, and Chrome 4.0.266.0, Iceweasel 3.5.5, Opera 10.10 from Linux.. This error not happen for all message. []'s and TFA! |
Comment by borigoto on 9 Jan 2010 13:20 UTC Alec I forgot, use the logs in syslog and saw no errors in my tests [] s |
Comment by @alecpl on 9 Jan 2010 18:03 UTC What about Roundcube /logs dir? What IMAP server? Enable imap_debug and show log. |
Comment by borigoto on 10 Jan 2010 14:48 UTC Hi Alec, See the attach! Again, sorry my english.. []'s and TFA |
Comment by @alecpl on 10 Jan 2010 18:38 UTC So, now I see the message is malformed. Contains "Content-type:" instead of "Content-Type:" and that's why your server returs it as text/plain in BODYSTRUCTURE. So, will not fix this. |
Status changed by @alecpl on 10 Jan 2010 18:38 UTC reopened => closed |
Comment by borigoto on 10 Jan 2010 21:37 UTC Mostrar romanizao I did a grep-i in the code, content-type and found several places that the system uses the same type tiny. Below, the source code itself roundcube showed me:
Sorry for insistence.. Have another idea ?? How can help more ?? []'s |
Status changed by borigoto on 10 Jan 2010 21:37 UTC closed => reopened |
Comment by borigoto on 10 Jan 2010 22:23 UTC Alec, this is the code that creates the message:
[]'s |
Comment by @alecpl on 11 Jan 2010 07:23 UTC More important is what returns your server in BODYSTRUCTIRE, if it returns text/plain for such message we can do nothing about that. Please open a new ticket if you want, because your problem is different. |
Status changed by @alecpl on 11 Jan 2010 07:23 UTC reopened => closed |
Comment by borigoto on 11 Jan 2010 08:42 UTC Hi alec. Thanks for help-me. I'm try two other versions, 0.3-stable (1 minus i user) and trunk-[from nightly.roundcube.net, and, working good.... Realy i dont understand because only 3.1 not work, but, no problem.. Again, thanks for your help! |
Reported by lmsilvero on 4 Dec 2009 12:00 UTC as Trac ticket #1486338
The same message is correctly in version 0.1-STABLE and is not in version 0.3.1.
I tried to change the header to send the messages, but do not think the problem is there, since in both versions of RC is shown as the header.
This is the header:
Return-Path: test@domain.tld
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on server.domain.tld
X-Spam-Level: ******
X-Spam-Status: No, score=6.7 required=8.0 tests=AWL,HTML_MESSAGE,
HTML_MIME_NO_HTML_TAG,MIME_HEADER_CTYPE_ONLY,MIME_ HTML_ONLY,NO_DNS_FOR_FROM,
NO_RECEIVED,NO_RELAYS,SUBJ_ALL_CAPS autolearn=no version=3.2.5
X-Original-To: user1@domain.tld
Delivered-To: user1@domain.tld
To: user1@domain.tld
Subject: TESTING
From: SENDER sender@domain.tld
Reply-To: sender@domain.tld
X-Originally_To: sender@domain.tld
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-Id: 20091202112501.7F81F1438C@domain.tld
Date: Wed, 2 Dec 2009 08:25:01 -0300 (ART)
X-Virus-Status: No
X-Virus-Checker-Version: clamassassin 1.2.4 with clamscan / ClamAV 0.93.3/10103/Wed Dec 2 00:59:01 2009
In version 0.1-STABLE can see the HTML, but in 0.3.1 version shows the body tags as follows:
TEST
Some HTML messages are not interpreted and also the following characters appear in the header --> and this:
v:* { BEHAVIOR: url(#default#VML) } o:* { BEHAVIOR: url(#default#VML) } w:* { BEHAVIOR: url(#default#VML) } .shape { BEHAVIOR: url(#default#VML) } --> UPSTI02NormalUPSTI02302007-01-03T12:37:00Z2007-01-03T12:38:00Z1215111611.810795CleanClean21falsefals efalseMicrosoftInternetExplorer4 --> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Tabla normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#400; mso-fareast-language:#400; mso-bidi-language:#400;} -->
I tried to download the latest update svn checkout https://svn.roundcube.net/trunk, but everything was the same.
I created a new installation, with a new DB, but the problem persists.
Migrated-From: http://trac.roundcube.net/ticket/1486338
The text was updated successfully, but these errors were encountered: