ah, sorry, that was in 17244.
On Fri, Sep 1, 2017 at 7:52 PM, K Post <nntp.p...@gmail.com> wrote:
> Also, I think you missed that HTMLParser is now a configuration parameter.
>
> On Fri, Sep 1, 2017 at 7:37 PM, K Post <nntp.p...@gmail.com> wrote:
>
>> You sure do work fast! Questions and commends on the UserAttach
>> functionality:
>>
>> 1) You had previously mentioned inheritance, but I don't see reference to
>> that here. That's fine, but say you've got something like
>>
>> *@Domain.com=>block=>~~commonRule
>> specificu...@domain.com=>block=>doc
>>
>> I know you said that ASSP will combine rules, but I didn't know if that
>> was only when multiple rules were on a single line or if it's also when a
>> user matches multiple lines. So does ASSP and these rules together so
>> specificu...@domain.com would have all of the ~~commonRule blocks and
>> also .doc being blocked?
>>
>>
>> 2) In your example, you have:
>> ~~commonRule=>block=>~executables|~scripts|xls,block-in=>:M
>> SOM,block-out=>:CSC
>> and executables is defined as
>> ~executables => cmd|com|cpl|exe|exe\-bin|lnk|pif
>>
>> That block-in rule of :MSOM removes office macros from exe-bin (which is
>> sadly very useful for select users in our org). What I don't understand is
>> how the block rule is combines with the block-in rule.
>>
>> If the user gets an office macro file, that would match the block rule
>> for exe-bin. But there's also a rule in that same line for :MSOM. ASSP is
>> smart enough to let this through?
>>
>>
>>
>> 3) I'm so excited that you implemented the -- (double minus) feature to
>> remove extensions from the definitions. This is going to be great!
>>
>> THANK YOU
>> Ken
>>
>>
>>
>>
>>
>>
>> On Thu, Aug 31, 2017 at 9:48 AM, Thomas Eckardt <
>> thomas.ecka...@thockar.com> wrote:
>>
>>> Hi all,
>>>
>>> fixed in assp 2.5.6 build 17243:
>>>
>>> - if two email addresses were defined in the from: header tag - like:
>>> from: du...@localdomain.com <sen...@senderdomain.org>
>>> the first address was used by assp instead of the right second. This
>>> made spam detection difficult and caused the DKIM check to fail.
>>>
>>>
>>> added:
>>>
>>> - 'UserAttach' got an enhancement - it is now possible to define and use
>>> regular expression templates as well as rule templates
>>> - the GUI is changed
>>> .....
>>> block=> rules cause specific file types to be blocked (but does not
>>> block the others).
>>> good=> rules block all file types except for those specified in the
>>> rule.
>>> ....
>>>
>>> It is possible to define templates (see the preceding single tilde ~ )
>>> for extension regular expression and to use them in any entry at any place
>>> (except other extension regular expression templates) - like:
>>>
>>> ~executables => cmd|com|cpl|exe|exe\-bin|lnk|pif
>>> ~scripts => js|pl|ps1?|sh|vb[es]?|wms|ws[cfh]
>>> us...@domain.tld => block => ~executables|~scripts|mht|ms[cipt] ,
>>> block-in =>:MSOM , block-out => :CERTPDF
>>> [allDomains] => block => ~executables|:CSC
>>>
>>> Extension regular expression template names have to start with a
>>> single tilde. Allowed name characters are A-Z, a-z, 0-9 and underscrore.
>>>
>>> It is also possible to define rule templates and to use them in
>>> combination with any other rule definitions or rule templates.
>>> Rule templates starts with two tilde (~~template). Allowed name
>>> characters are A-Z, a-z, 0-9 and underscrore. For example:
>>>
>>> ~~commonRule=>block=>~executables|~scripts|xls,block-in=>:MS
>>> OM,block-out=>:CSC
>>> ~~devRule=>~~commonRule=>block-out=>:WIN|:ELF
>>> ~~allowALL=>good=>*
>>> *@domain.com=>~~commonRule
>>> [IT]=>~~devRule
>>> u...@domain.com=>~~commonRule,~~anySecondRule,~~anyOtherRule
>>> =>block=>~anyExt,block-in=>~otherExt|xls|--doc
>>>
>>> Notice the leading -- in front of the --doc regular expression in the
>>> last example. The -- removes all occurences of this regular expression from
>>> the resulting entry,
>>> here from block-in.
>>> ASSP will resolve all extension regular expression templates and all
>>> rule tempates and will combine them all in to one resulting user attachment
>>> rule.
>>> ASSP will throw a warning, if a rule template is define multipe times
>>> - like: *@domain.com=~~commonRule,~~devRule - here ~~devRule already
>>> contains ~~commonRule
>>> It may happen, that the resulting attachment rule contains one or more
>>> extension reglar expressions multiple times - this is harmless, but try to
>>> prevent it.
>>> ....
>>>
>>> Thomas
>>>
>>>
>>>
>>> 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!
>>> *******************************************************
>>>
>>>
>>> ------------------------------------------------------------
>>> ------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Assp-test mailing list
>>> Assp-test@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/assp-test
>>>
>>>
>>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test
