What we are talking about - "Attachment Blocking Level 4 not working" ???
In a default setup, assp will detect attachments only in the first
'MaxBytes - setting' - bytes of the raw email. If you want to make sure
that all attachments are detected, use the ASSP_AFC.pm plugin.
---------------
>Like the Jibberish messed up headers?
How ever - these are characters of human languages - no Klingon nor Asgard
:)
Perl is designed to process text in any human language. From the technical
point of view you can process byte by byte, but this will be hard to do.
You can block east asian and other languages by there characterset - for
example :
(?:BIG5|CHINESEBIG|GB2312|KS_C_5601|KOI8-R|EUC-KR|ISO-2022-JP|ISO-2022-KR|ISO-2022-CN|CP1251).
How ever, this will not work, if the UTF-8 enconding is used - like in
your case.
For UTF-8 encoded mails I would do any of the following:
- report the mails as spam to assp - enable the Bayesian- and HMM-check
I use this way with large success.
OR
- set 'AllowInternalsInRegex' to on
- use the assp- internal regular expression variable $SymLangRE in a
bomb definition : (?:$SymLangRE)
This requires the latest version of V2. Notice that this will block ALL
non single unicode character definition - means also symbols, smilies
...... and so on.
OR
If you want to block specific languages, first you need to know which
language. Than you need to know in which unicode table the language
symbols are defined.
Than you can use for example
(?:\p{InHangulJamo}|\p{InBengali})
in a bomb definition of your choice. This will block/score on any
character of the selected unicode tables/languages.
some important links:
http://www.unicode.org/Public/UNIDATA/Blocks.txt
http://www.mathematik.uni-ulm.de/help/perl5/doc/perlunicode.html
http://unicode.org/charts/
http://perldoc.perl.org/perlunicode.html#Unicode-Encodings
http://perldoc.perl.org/perlunicode.html
http://perldoc.perl.org/perluniprops.html
http://perldoc.perl.org/perlretut.html
These are the multibyte unicodes blocks of unicode 6.1 - available with
Perl 5.16 ( Perl 5.18 supports unicode 6.2 )
These unicode blocks are in assp's '$SymLangRE'.
InArrows
InBengali
InBlockElements
InBopomofo
InBopomofoExtended
InBoxDrawing
InBraillePatterns
InBuhid
InByzantineMusicalSymbols
InCJKCompatibility
InCJKCompatibilityForms
InCJKCompatibilityIdeographs
InCJKCompatibilityIdeographsSupplement
InCJKRadicalsSupplement
InCJKSymbolsAndPunctuation
InCJKUnifiedIdeographs
InCJKUnifiedIdeographsExtensionA
InCJKUnifiedIdeographsExtensionB
InCherokee
InCombiningDiacriticalMarks
InCombiningDiacriticalMarksforSymbols
InCombiningHalfMarks
InControlPictures
InCurrencySymbols
InDeseret
InDevanagari
InDingbats
InEgyptianHieroglyphs
InEnclosedCJKLettersAndMonths
InEthiopic
InGeneralPunctuation
InGeometricShapes
InGujarati
InGurmukhi
InHalfwidthAndFullwidthForms
InHangulCompatibilityJamo
InHangulJamo
InHangulSyllables
InHanunoo
InHighPrivateUseSurrogates
InHighSurrogates
InHiragana
InIPAExtensions
InIdeographicDescriptionCharacters
InKanbun
InKangxiRadicals
InKannada
InKatakana
InKatakanaPhoneticExtensions
InKhmer
InLao
InLowSurrogates
InMalayalam
InMiscellaneousMathematicalSymbolsA
InMiscellaneousMathematicalSymbolsB
InMiscellaneousSymbols
InMiscellaneousTechnical
InMongolian
InMusicalSymbols
InMyanmar
InNumberForms
InOgham
InOriya
InPrivateUseArea
InRunic
InSinhala
InSmallFormVariants
InSpacingModifierLetters
InSpecials
InSuperscriptsAndSubscripts
InSupplementalArrowsA
InSupplementalArrowsB
InSupplementalMathematicalOperators
InSupplementaryPrivateUseAreaA
InSupplementaryPrivateUseAreaB
InSyriac
InTagalog
InTagbanwa
InTags
InTamil
InTelugu
InThaana
InThai
InTibetan
InUnifiedCanadianAboriginalSyllabics
InVariationSelectors
InYiRadicals
InYiSyllables
Thomas
Von: blood618 <[email protected]>
An: [email protected],
Datum: 12.07.2013 10:57
Betreff: Re: [Assp-user] Attachment Blocking Level 4 not working
Hmm Interesting..
That is the complete headers of the files.
right click e-mails -> Properties. -> grab them all and posted it here.
I found this on the other e-mails though
> Content-Type: multipart/mixed;
> boundary="----=_NextPart_000_0F21_01CC82A8.13394940"
>
Other than that there is none
It is there maybe a possibility that we can block them from the headers if
they have randoms like this? Like the Jibberish messed up headers?
Thanks!
--
View this message in context:
http://anti-spam-smtp-proxy-server.996265.n3.nabble.com/Attachment-Blocking-Level-4-not-working-tp37133p37139.html
Sent from the assp-user mailing list archive at Nabble.com.
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user
DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally
privileged and protected in law and are intended solely for the use of the
individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no
known virus in this email!
*******************************************************
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user