however when testing this, I kept getting my test exe file through the matcher...
hmm from what I saw, the matcher did not work..
so I started to trace down the problem by setting all the logsto debug and trying to find ut why the exe file got through.
after searching, banning I finally found the problem (and felt so stupid)
the matcher DOES work,but not just under certain envioments...
It CAN let files through even though it really should have matched...
the problem is not with normal files, but with files that use some sort of national characters (for me that are the norwegian characters ������)
I used 2 different ways of sending the message, first I used mozilla (from linux) to send a file called �yenblikksfoto1.exe (it was a png that i had renamed) here is what came through as name in the mime encapsulation.
Content-Type: application/octet-stream; name="=?ISO-8859-1?Q?=F8yeblikksfoto1=2Eexe?=" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="=?ISO-8859-1?Q?=F8yeblikksfoto1=2Eexe?="
and since the matcher matches for *.exe this file gets through, since there is NO *.exe in that filename (mozzilla parsed this filename correctly)
I then had a friend send me an "exe" file through hotmail (I don't have that myself) the file was called "n�nting.exe" and here is what came to me in the mime-encapsulating...
Content-Type: application/octet-stream;
name="=?iso-8859-1?B?buVudGluZy5leGU= ?="
Content-Disposition: attachment; filename="=?iso-8859-1?B?buVudGluZy5leGU= ?="
Content-Transfer-Encoding: base64
This file also got through to me, but this time not even mozilla could parse that filename...
well i just wanted to let you know :-) perheps this is already fixed an later versions of james... I tried to use jira to find it, but I did not find anything related to this when searching for "attachment"
/Christian Andersson
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
