okay, thanks. I thought that if I didn't define a block for an address,
that it would just assume no block.

So to allow everything and anything to an address I would need to do:
ale...@ourcharity.org => block => .nonsense, good => .*
right?  Assuming there would never be a file with a .nonsense extension.
using your explanation, wouldn't that be the same as
ale...@ourcharity.org => block => .nonsense
without the good definition?


On Tue, Jan 22, 2019 at 1:13 AM Thomas Eckardt <thomas.ecka...@thockar.com>
wrote:

> The logic behind is (and ever was) - block any bad OR any not good.  IF
> (there is a bad rule AND the attached is bad) OR (there is a good rule AND
> the attached is NOT good) .
>
> simple example:
>
> *@domain => block => .jar, good => .*
>
> This blocks all .jar and passes all other.
> good =>.* is the same like not defining 'good'.
>
> 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!
> *******************************************************
>
> _______________________________________________
> Assp-test mailing list
> Assp-test@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/assp-test
>
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to