Good workaround for the time being. I guess I could schedule a cron job to
parse the log on a daily basis too. - thanks for considering adding this
in your free time :)
On Sat, Feb 18, 2017 at 12:49 AM, Thomas Eckardt <thomas.ecka...@thockar.com
> wrote:
> >Add an option to show messages marked with the Spam prefix - messages
> that are probably spam but fell below the threshold - to the blockreport
> I don't see a chance to add this to the blockreport, because the mails
> were not blocked. They should be reported every time as what they are
> (spam/ham).
> The blockreport function is a chain of queries and selections. Even the
> first query instance will not catch these events - so complete chain of
> query instances must be rewritten to process these events.
>
> find "[lowlimit]" maillog.txt
>
> will do it. Using the MaillogTail function is also possible. There you
> have also the option to act on the IP, sender and the eml file (with a
> single click).
>
> >report sent to the admin of error reports (mail sent to the EmailSpam
> and EmailNotSpam addresses)?
>
> This would require a complete new report function. For now use someting
> like:
>
> find "X-Assp-Reported-By:" *.*
> find "X-Assp-Reported-By:" *.*|find "X-Assp-Reported-By:"
>
> at commandline
>
> or in MaillogTail - search for: report message written to
> for example make all selections in the MaillogTail, do the query, copy the
> URL to the clipboard - create a new link on your desktop -> daily report on
> one click
>
> http://127.0.0.1:55555/maillog?wrap=2&color=1&;
> tailbyte=10000&search=report+message+written+to&order=0&
> nohighlight=1&size=2&files=files&limit=100#MlTop
> <http://127.0.0.1:55555/maillog?wrap=2&color=1&tailbyte=10000&search=report+message+written+to&order=0&nohighlight=1&size=2&files=files&limit=25#MlTop>
>
> an instant blockreport may look like
>
> http://127.0.0.1:55555/maillog?wrap=2&color=1&tailbyte=10000&search=[spam+
> found]&order=0&nocontext=1&nohighlight=1&size=2&files=
> files&limit=100#MlTop
>
> to prevent the login popup, define the user:passord in the URL - or store
> this information in your browser.
>
>
> I'll think about this feature request.
>
> Thomas
>
>
>
>
> Von: K Post <nntp.p...@gmail.com>
> An: ASSP development mailing list <assp-test@lists.sourceforge.net>
> Datum: 17.02.2017 20:36
> Betreff: Re: [Assp-test] Feature request: Daily report of error
> reports
> ------------------------------
>
>
>
> And while I'm at it, I'll request this too:
> Add an option to show messages marked with the Spam prefix - messages that
> are probably spam but fell below the threshold - to the blockreport (noted
> as not needing to be resent if not spam)
>
> Again, something like this would help an admin improve ASSP accuracy.
>
> Thanks
>
> On Fri, Feb 17, 2017 at 2:26 PM, K Post <*nntp.p...@gmail.com*
> <nntp.p...@gmail.com>> wrote:
> I find the nightly report that I get of all blocked mail to be
> *incredibly* helpful. I use it to resend mail and see how the server's
> doing in general.
>
> Would it be possible to have a similar report sent to the admin of error
> reports (mail sent to the EmailSpam and EmailNotSpam addresses)? That
> would let us see what people are reporting in one shot and to easily be
> able to act on them - either by undoing the report or by further tweaking
> settings like senderbase.
>
> I know that we can get copies of the reports sent in realtime, but
> ignoring the fact that this doesn't seem to work for messages reported
> through Outlook - at lest for me, having a single digest report would be
> preferable to me and I assume others.
>
> Just a thought.
> ------------------------------------------------------------
> ------------------
> 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
>
>
>
>
> 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
