I solved this issue...
By using a TEXTENCODE resource , the $filename is already decoded before
calling the MAILhead_get_disposition, therefore, a "if (/filename="([^"]+)"/i)"
in the MAILhead_get_disposition sets wrong "$1" if filename contains x22
(sorry,not x25. '"' is 0x22 !).
I've used a res
On February 6, 2003 at 10:29, Tomohiko Sugihara wrote:
> My explanation was not enough...
> I tried 2003-02-05 snapshot build and I found the same issue.
> Normally it's good . If attachment file name contains x??24 (ex. x2524),
> file name is converted to unexpected string. Is it caused by Perl
I'm terribly sorry , I sent a wrong report.
From: Earl Hood <[EMAIL PROTECTED]>
Subject: Re: invalid link label for a message attachment if file name is MIME encoded.
Date: Wed, 05 Feb 2003 13:04:59 -0600
> > 2) In the Head of Message ( to
> >"@" is convert
On February 5, 2003 at 17:08, Tomohiko Sugihara wrote:
> Thank you for your reply and BUGFIX #2474 .
>
> > On February 4, 2003 at 12:07, =?ISO-2022-JP?B?GyRCP3k4NhsoQg==?= wrote:
> Ah,Sorry.
>
> I've tested snapshot(2003-02-04) + TEXTENCODE , snapshot + latest
Try 2003-02-05 snapshot build. 20
Thank you for your reply and BUGFIX #2474 .
> On February 4, 2003 at 12:07, =?ISO-2022-JP?B?GyRCP3k4NhsoQg==?= wrote:
Ah,Sorry.
I've tested snapshot(2003-02-04) + TEXTENCODE , snapshot + latest
library from CVS marked *BUGFIX #2474 + TEXTENCODE .
But now I have two problems.
1) If attachment file
On February 4, 2003 at 12:07, =?ISO-2022-JP?B?GyRCP3k4NhsoQg==?= wrote:
> Hi,list!
>
> If attachment file name is MIME encoded with multibyte language,
> a link label to an attachment file is incorrect.
> I think this is caused by to avoid any potential XSS.
Not exactly. The readmail::MAILhead_
Hi,list!
If attachment file name is MIME encoded with multibyte language,
a link label to an attachment file is incorrect.
I think this is caused by to avoid any potential XSS.
This is a sample original mail
--
:
Content-Type: application/octet-stream; name="
