Author Topic: Attachments not handled correctly at all ...  (Read 7861 times)

Offline marin

  • Jr. Member
  • **
  • Posts: 17
Attachments not handled correctly at all ...
« on: August 15, 2006, 09:28:04 AM »
Hi there,

I was very excited about roundcube and we're testing it here but what striked me today is that attachments are not being handled like they should.
I mean that I send myself a test message with attached picture, par example, and when I open the message I see the clip, the filename, but when I click the attached file's filename it doesn't open - there's screenshot attached (screenshot1.gif).

Also when I download the picture its somewhat corrupted because I can't open it...
I've got squirrelmail there too and everything works like a charm there, the exactly same message etc.

Is there anyone experiencing the same problem out there ?

Also, another issue I have is that when I try to create folder with cyrrilic name it gets "hashed", I've seen some encoding problems but I couldn't figure this one out ? Screenshot attached too, screenshot2.gif

And the search doesn't work with cyrillic letters too, if someone can give me a hint on that, I believe it wouldn't be too hard for me to fix it.

And finally, that's not a bug, I just need some info on wheter it is possible to link this googie spell thingy to local aspell with the language file I need installed (my language is not in the supported list ) ?

Offline VenCo

  • Newbie
  • *
  • Posts: 1
Re: Attachments not handled correctly at all ...
« Reply #1 on: August 16, 2006, 04:25:57 PM »
I have a similar problem...

At first i was unable to download any attachments, after i commented out this line:

header(sprintf('Content-Length: %d', strlen($cont)));
(line 100 of program/steps/mail/get.inc)

i was able to download a attachment, but all files are corrupted.

Offline marin

  • Jr. Member
  • **
  • Posts: 17
Re: Attachments not handled correctly at all ...
« Reply #2 on: August 31, 2006, 01:32:13 PM »
I'm just wondering is someone besides us two having issues with attachments ?
I was that close to starting using this webmail I'm inlove with it but... when it doesn't work, it doesn't work... :(

Offline kali

  • Jr. Member
  • **
  • Posts: 57
Re: Attachments not handled correctly at all ...
« Reply #3 on: August 31, 2006, 02:54:29 PM »
Tested just as you did. Sent jpg files, attachments uploaded fine, and were displayed inline when received and viewed - no problems. Might it be the encoding you're using?

Just additional info for you guys.

Offline Delta-9

  • Jr. Member
  • **
  • Posts: 35
Re: Attachments not handled correctly at all ...
« Reply #4 on: September 01, 2006, 02:35:06 PM »
I've been having wierd results with attachments. As long as the JPEGs are not "too big" they open fine inline. If the attachments get over about 1mb or so, then the message stops loading on me and I get nothing. Maybe its a size limitation / constraint of some sort.

I have zero luck SENDING attachments from roundcube.  While this is an annoyance, I quickly switch to my squirrelmail installation if I really need to use an attachment that doesn't work in roundcube.

I have a feeling the attachhment issue might have something to do with the database and how roundcube uses the database to do some caching.

Offline infoeon

  • Newbie
  • *
  • Posts: 3
Re: Attachments not handled correctly at all ...
« Reply #5 on: September 07, 2006, 09:18:39 AM »
I have a different issue with attachments but it might turn out to be related somehow. When I receive an email from a Juno.com account (yeah, I know), RoundCube shows the paperclip icon denoting an attachment but when I open the email there are no attachments listed. It doesn't matter the attachment type or size. the attachments are viewable when using Squirrel or Thunderbird and I can see the encoded attachment when I select "show source" in RoundCube. I believe there is something wrong with the code that parses MIME boundaries. There is a MIME boundary with MIME type definitions followed by another MIME boundary that defines the attachment type. I think RoundCube possibly chokes when there is no content-type but I haven't had a chance to look at the code in depth. Here is some sample data:

From - Wed Aug 30 19:32:00 2006
X-Account-Key: account4
X-UIDL: 2743
X-Mozilla-Status: 1001
X-Mozilla-Status2: 10000000
Return-Path:
Received: from m9.nyc.untd.com ([127.0.0.1])
   by server.XXXX.com
   with XXXX ; Wed, 30 Aug 2006 19:29:56 -0500
Received: from 64.136.22.72 ([64.136.22.72] helo=m9.nyc.untd.com) by
   spam.XXXX.com; 30 Aug 2006 19:29:54 -0500
Received: from m9.nyc.untd.com (localhost [127.0.0.1])
   by m9.nyc.untd.com with SMTP id XXXX
   for (sender );
   Wed, 30 Aug 2006 17:31:07 -0700 (PDT)
X-UNTD-OriginStamp: XXXX==
Received: (from XXXX@juno.com)
 by m9.nyc.untd.com (jqueuemail) id XXXXXXXX; Wed, 30 Aug 2006 17:30:22 PDT
To: XXXX@XXXX.com
Cc: XXXX@XXXX.com
Date: Wed, 30 Aug 2006 19:04:27 -0500
Subject: Fw: Treadmill dance
Message-ID: <20060830.190428.3516.4.XXXX@juno.com>
X-Mailer: Juno 5.0.33
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary=--__JNP_000_2426.1280.6e14
From: XXXX
X-ContentStamp: 1:1:493504430
X-UNTD-Peer-Info: 127.0.0.1|localhost|m9.nyc.untd.com|XXXX@juno.com
X-Assp-Received-SPF: pass (spam.XXXX.com: domain of XXXX@juno.com
   designates 64.136.22.72 as permitted sender) client-ip=64.136.22.72;
   envelope-from= XXXX@juno.com; helo=m9.nyc.untd.com;

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

----__JNP_000_2426.1280.6e14
Content-Type: multipart/alternative; boundary=--__JNP_000_4817.464d.5164

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

----__JNP_000_4817.464d.5164
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


 This is a fun workout!
----__JNP_000_4817.464d.5164
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: quoted-printable






 

style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"> FONT>face=3DArial color=3Dblue size=3D2>style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"> This is a =
fun=20
workout!
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"> FONT>


style=3D"FONT-SIZE: 12pt"> 


 


----__JNP_000_4817.464d.5164--

----__JNP_000_2426.1280.6e14
Content-Type: video/x-ms-wmv; name="some file.wmv"
Content-Transfer-Encoding: base64



----__JNP_000_2426.1280.6e14--

Offline zman818

  • Newbie
  • *
  • Posts: 2
Re: Attachments not handled correctly at all ...
« Reply #6 on: September 08, 2006, 02:11:01 PM »
Running Beta2 here. Small images appear inline and download fine. Similarly small zip files are corrupted during the retrieval process, and cannot be opened once downloaded.

I have Beta1 deployed alongside Beta2, and in Beta1 I'm able to open the same exact message, download the same exact zip and open it without issue locally.

A diff of the two downloaded files shows clear corruption in the version from Beta2. Clearly Beta2 is mangling attachments.

Offline marin

  • Jr. Member
  • **
  • Posts: 17
Re: Attachments not handled correctly at all ...
« Reply #7 on: September 18, 2006, 04:18:33 AM »
So would it be possible someone to do a diff on the part of the code handling the attachments too ?
If you have an idea where is this at all, and release a patch for beta2?
I really hope we get this resolved soon as I've already shown Roundcube here and a bunch of people is asking "why its not ready yet, what are you doing all day" :D
I think this issue should be very high in the developers priorities as really makes roundcube unusable :'(

Offline powereds

  • Newbie
  • *
  • Posts: 2
Re: Attachments not handled correctly at all ...
« Reply #8 on: September 30, 2006, 12:13:26 AM »
same here. can't send attachment beyond 500kb. jpeg attachments aren't corrupted as well as the others types.
i hope that a patch will be released soon to fix this bug.

thanks :D

Offline powereds

  • Newbie
  • *
  • Posts: 2
Re: Attachments not handled correctly at all ...
« Reply #9 on: September 30, 2006, 12:48:08 AM »
i got this rcmail error(./logs/errors):

[30-Sep-2006 10:09:57] PHP Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 1379834 bytes) in /var/www/html/mail/program/lib/Mail/mimePart.php on line 236

i increased the php memory limit to 16M from 8M (/etc/php.ini). i can send 1Mb attachment.

when i increased to 32M@php memory limit, i got this error:

[30-Sep-2006 10:29:16] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 7921339 bytes) in /var/www/html/mail/program/lib/Net/SMTP.php on line 745

hoping a bug fix or work around on this :D

Offline desertadmin

  • Jr. Member
  • **
  • Posts: 36
Re: Attachments not handled correctly at all ...
« Reply #10 on: October 04, 2006, 02:31:28 PM »
Anything new on this yet?

-Sincerely
DesertAdmin

Offline Arabian

  • Jr. Member
  • **
  • Posts: 10
Re: Attachments not handled correctly at all ...
« Reply #11 on: October 04, 2006, 07:09:02 PM »
I wish this get fixed ASAP.

Thank you,

Arabian

Offline tommie

  • Newbie
  • *
  • Posts: 4
Re: Attachments not handled correctly at all ...
« Reply #12 on: November 05, 2006, 06:58:05 AM »
I had the same problem and was able to find the cause. The problem was that I was able to download attachments, however they were corrupted. After a while I found the cause of this: localisation. If you set your language in the Personalisation prefferences to English US, it worked for me. After I replaced the nl_BE by a copy of en_US and I put it back to flemish the issue was solved. for some reason there was a bug in my localisation file...

maybe you can give it a try?

Offline marin

  • Jr. Member
  • **
  • Posts: 17
Re: Attachments not handled correctly at all ...
« Reply #13 on: November 06, 2006, 04:24:45 AM »
Hi All,
The reason was exactly the same here, we fixed it last week too.

Not that we don't have thousand of other issues now :D

Offline desertadmin

  • Jr. Member
  • **
  • Posts: 36
Re: Attachments not handled correctly at all ...
« Reply #14 on: November 07, 2006, 11:12:37 AM »
How did you fix it?

-Sincerely,
DesertAdmin