I understand that using the wildcard in the block report group includes all, including those that are in the [SPAM-ONLY-RECIPIENTS] groupthat the filter is using. ASSP is working as designed, I just am looking to discuss alternatives.
The only alternative that I know of would be to have a huge list that I maintain of good addresses that's a duplicate of ValidAddresses (so again 2 lists to keep in sync). Even if I had ValidAddresses and the block report group include a singularly maintained file, our @subdomain1.OurCharity.org is a wildcard domain used by a ticketing system and others. I need to see blocked email there, but there's some addresses which are only spam. Would it be a big deal to give the option to have BlockReportFilter matches not show up on the block report. OR, even better just appear as a summary at the bottom of the report? That way I could go through the daily report without needing to skip over the filtered notification, but on days when there is extra time or curiosity, I could still see counts at the bottom of the report for stuff that's been filtered. My desire would be to have: 1) BlockReportFilter accept a group definition (which could be used elsewhere, like [SPAM-ONLY-RECIPIENTS]) 2) The block report itself showing only a summary at the bottom of the count of messages for those addresses which are filtered out Nothing urgent, just a wishlist. thanks On Thu, Apr 30, 2020 at 7:07 AM Thomas Eckardt <thomas.ecka...@thockar.com> wrote: > This group is wrong > > [block-report-gr...@ourcharity.org] > *@OurCharity.org > *@*subdomain1.OurCharity.org* <http://subdomain1.ourcharity.org/> > *@OtherCharityWeHost.org > > > it contains also (IMHO) all [SPAM-ONLY-RECIPIENTS] !!!! > > Thomas > > > > > > Von: "K Post" <nntp.p...@gmail.com> > An: "ASSP development mailing list" < > assp-test@lists.sourceforge.net> > Datum: 27.04.2020 21:44 > Betreff: Re: [Assp-test] BlockReportFilter accept groups? > ------------------------------ > > > > (sorry hit send by mistake) > > I'm sorry that I didn't explain myself well initially. I'll try again > with more detail. > > I've got a group definition of collection addresses, mailboxes that get > nothing but spam. I've got that defined as a group like this: > [SPAM-ONLY-RECIPIENTS] > olduser....@ourcharity.org > honeypot.1...@ourcharity.org > .... about 100 others > > Then in spamAddresses, I've got > [SPAM-ONLY-RECIPIENTS] > > This does a nice job of accurately keeping the corpus correct. > > I also get a block report every day for ALL spam that's rejected, for > everyone. I've got a [block-report-gr...@ourcharity.org] group defined > > [block-report-gr...@ourcharity.org] > *@OurCharity.org > *@*subdomain1.OurCharity.org* <http://subdomain1.ourcharity.org/> > *@OtherCharityWeHost.org > > The block report is defined to run at midnight like this: > > [block-report-gr...@ourcharity.org]=>m...@ourcharity.org=>1 > > > This works great, but there's so much spam that I need to go through (some > of the stuff our charity handles is very sensitive and unfortunately > contains common phrases and tops often found in spam), so it needs my > manual review. No choice there, I wish there was. > > I can put the addresses that appear in [SPAM-ONLY-RECIPIENTS] manually in > BlockReportFilter, but that means maintaining the list in 2 places, the > group and BlockReportFilter. I was hoping that BlockReportFilter would > accept a group to make things more simple. > > Also, is there an option to not display even the header for filtered out > addresses? Currently, I get lines like this for each spam-only-recipient > > spamo...@ourcharity.org no blocked <-- even though 64 emails were, > they're just filtered) > > 64 lines skipped on global defined filter regex 'BlockReportFilter' > > It would be fantastic if anything on the BlockFilter simply didn't show up > at all on the block report. > > And last, my unable to transfer to a worker issues continue and are far > more pressing than this request of convenience. Any thoughts you could > provide on that front would be most helpful. > > Thank you as always. > Ken > > > On Mon, Apr 27, 2020 at 3:32 PM K Post <*nntp.p...@gmail.com* > <nntp.p...@gmail.com>> wrote: > I'm sorry that I didn't explain myself well. > > I've got a group definition of collection addresses, mailboxes that get > nothing but spam. I've got that defined as a group like this: > [SPAM-ONLY-RECIPIENTS] > olduser....@ourcharity.org > honeypot.1...@ourcharity.org > .... about 100 others > > Then in spamAddresses, I've got > [SPAM-ONLY-RECIPIENTS] > > This does a nice job of accurately keeping the corpus correct. > > I also get a block report every day for ALL spam that's rejected, for > everyone. I've got a > > > > On Sat, Apr 25, 2020 at 4:35 AM Thomas Eckardt < > *thomas.ecka...@thockar.com* <thomas.ecka...@thockar.com>> wrote: > The most left parameter defines the list of email addresses. > Why should anyone define a wrong group/list there and tries to correct > this mistake using the BlockReportFilter. > > Thomas > > > > Von: "K Post" <*nntp.p...@gmail.com* <nntp.p...@gmail.com>> > An: "ASSP development mailing list" < > *assp-test@lists.sourceforge.net* <assp-test@lists.sourceforge.net>> > Datum: 24.04.2020 16:56 > Betreff: [Assp-test] BlockReportFilter accept groups? > ------------------------------ > > > > Should BlockReportFilter be able to accept [GROUP] definitions? > > I've got a group of email addresses defined that I use in the > spamAddresses configuration file. That works great. Spam to these > addresses are always spam. I no longer want to have them show in my master > block report. I know I can copy those addresses to the BlockReportFilter, > but I am hoping to have that same group just listed in the filter. When I > do that, I get a regex error. > • - regex error in: BlockReportFilter > > I'm guessing BlockReportFilter isn't groups aware. Would it be difficult > to add that in a future release? > > Thanks_______________________________________________ > Assp-test mailing list > *Assp-test@lists.sourceforge.net* <Assp-test@lists.sourceforge.net> > *https://lists.sourceforge.net/lists/listinfo/assp-test* > <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! > ******************************************************* > > _______________________________________________ > Assp-test mailing list > *Assp-test@lists.sourceforge.net* <Assp-test@lists.sourceforge.net> > *https://lists.sourceforge.net/lists/listinfo/assp-test* > <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 > > > > > 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
