Re: Text attachment problem

2013-03-29 Thread Janos SUTO


Hello Frank,

thanks for the bug report, please check out model/search/message.php
from the latest commit. Now it should be ok.

Janos


On 2013-03-28 23:32, Frank Ellebrecht wrote:

Hello Janos,

Am Donnerstag, den 28.03.2013, 16:46 +0100 schrieb Janos SUTO:


I've just commited a few changes to model/search/message.php to fix
this. Please try it, it should display messages/rfc822 mime parts
properly.


Thank you for your efforts. Now the body of all attached messages is
displayed in the web UI. Good work!

The only thing I noticed is that the To, From, Subject and Date header
lines from *all* messages are displayed in the message's header (see
screenshot). I don't know if this is unintentional or if it is due to
the way the parsing is done. The messages list (upper screen area) 
shows

only the data of the »main« message.

Thanks,
Frank




Re: Text attachment problem

2013-03-26 Thread Janos SUTO


Hello Frank,

On 2013-03-25 22:38, Frank Ellebrecht wrote:



I've done that and now the message looks way better. Here is the


good



interesting part, copied from the web UI:





[...]



Content-Type: application/pdf;
name==?ISO-8859-15?Q?=E4=F6=FC=DF=2Epdf?=
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename*=ISO-8859-15''%E4%F6%FC%DF%2E%
70%64%66



I think that's the expected output, isn't it?


yes, it looks ok. I think I can release 0.1.23 this week.


Janos



Re: Text attachment problem

2013-03-25 Thread Frank Ellebrecht
Hello Janos,

Am Montag, den 25.03.2013, 14:48 +0100 schrieb Janos SUTO:

 it's the same. In the middle of the night I added a few more $-signs 
 then
 required :-)
 
:-)

 Please overwrite model/search/message.php with the attached file, and 
 let's
 see whether it fixes the problem.
 

I've done that and now the message looks way better. Here is the
interesting part, copied from the web UI:



Sure. MUA (Evolution 3.6.2):

Content-Type: multipart/mixed; boundary==-/ncrUDnazGcbiebe5OCW
Mime-Version: 1.0

--=-/ncrUDnazGcbiebe5OCW
Content-Type: application/pdf; name*=ISO-8859-1''Kontenbl%E4tter%
202011.pdf
Content-Disposition: attachment; filename*=ISO-8859-1''Kontenbl%E4tter%
202011.pdf
Content-Transfer-Encoding: base64

Piler:
Content-Type: multipart/mixed; boundary==-/ncrUDnazGcbiebe5OCW
Mime-Version: 1.0

The file was sent from Evolution. But when I send a file with Umlauts
from Thunderbird, it looks like that (should read äöüß.pdf):

Content-Type: application/pdf; 
name==?ISO-8859-15?Q?=E4=F6=FC=DF=2Epdf?=
Content-Transfer-Encoding: base64
Content-Disposition: attachment; 
filename*=ISO-8859-15''%E4%F6%FC%DF%2E%
70%64%66



I think that's the expected output, isn't it?

Frank




Re: Text attachment problem

2013-03-24 Thread Janos SUTO


On 2013-03-24 22:54, Frank Ellebrecht wrote:



then try to download the
same attachment


Nope, if I open/download the attachment mail.log, it's 0 bytes.


ehh, in the 65th line it should read as:

if(!preg_match(/\s/, $s)) {

so it's not preg_replace but preg_match. Please try again.





So, should I review these, i.e. my old archived messages or your last
message (with the lines you added), or anything else?



ehh, please wait (although you can), I found a bug in the gui while
displaying a message with attachments. I'm fixing the gui parser...

Janos