of which I thought it should match on mails which contain a file attachment like "test.zip":
Content-Type: application/zip; name="test.zip";
But the test doesn't match. What could have went wrong? Is "full" the wrong test method?
Based on this test from the ruleset of 2.54, "full" would appear to be the correct keyword:
full __SMIME_SIGNED_BODY /\nContent-Type: application\/x-pkcs7-signature;/
Although many other rules use "header Content-Type =~" type rules for mime boundary checks.. Perhaps the header ones only work on the first mime Content-Type declaration.
It might be worth trying the header version of the rule, see if that works.
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
