A 4th parameter will make the syntax more complicated like it is and it is
not realy 'easy' implemented.
But I think, this would be a possible solution for that problem:
If there are no wildcards used in the definition line for the first
address (this applys also to an email request sent by user) and this full
address (for example: user\@mydomain\.com) is defined in the
BlockReportFilter and this address is the only match for the filter - the
filter will be ignored.
so:
theu...@ourdomain.org=>theu...@aourdomain.org=>1
and a BlockReportRequest via EmailInterface from theu...@ourdomain.org
will be processed, even if theuser\@ourdomain\.org is part of the
BlockReportFilter (and no other filter matches)
theu...@ourdomain.org will get his report - no other user will get report
lines for this address.
Thomas
Von: K Post <nntp.p...@gmail.com>
An: ASSP development mailing list <assp-test@lists.sourceforge.net>
Datum: 17.01.2011 16:48
Betreff: [Assp-test] BlockReportFilter
Is there any chance that we could get a 4th parameter added to the block
report syntax that would add to the BlockReportFilter for each request
Currently, I've got
*@*=>ken.p...@ourdomain.org=>1 <*@*=%3eken.p...@ourdomain.org=%3E1>
This works great, and ignores that which I have in the BlockReportFilter.
In this filter, I have a couple usernames that get thousands of bayesian
spam messages rejected a day because these people published their
addresses
online (one of which I think on a porn site). The BlockReportFilter works
wonderfully here, I don't get notices of any of their mail. Perfect.
The problem is now one of these users wants their own daily report:
theu...@ourdomain.org=>theu...@aourdomain.org=>1<theu...@ourdomain.org=%3etheu...@aourdomain.org=%3E1>
But, nothing would because theuser is in BlockReportFilter.
It would be outstanding if we could have something like:
*@*=>ken.p...@ourdomain.org=>1=>theuser|theotheruser<*@*=%3eken.p...@ourdomain.org=%3E1=%3Etheuser%7Ctheotheruser>
theu...@ourdomain.org=>theu...@aourdomain.org=>1<theu...@ourdomain.org=%3etheu...@aourdomain.org=%3E1>
That 4th parameter in line one would filter out theuser and theotheruser
in
addition to whatever's in the BlockReportFilter.
Is this a reasonable addition?
Thanks
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test
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!
*******************************************************
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test
