From: Morris J. <mo...@wh...> - 2005-03-16 22:12:32
|
Does anyone make use of the "Probable spam: " cleanup report for anything interesting? Mojo -- Morris Jones Monrovia, CA http://www.whiteoaks.com Old Town Astronomers: http://www.otastro.org |
From: Michel B. <mi...@bo...> - 2005-03-16 22:15:34
|
Le Mercredi 16 Mars 2005 22:43, Morris Jones a =E9crit : > > Does anyone make use of the "Probable spam: " cleanup report for > anything interesting? I use them for log analysis. Please leave them in ;-) --=20 Michel Bouissou <mi...@bo...> OpenPGP ID 0xDDE8AC6E |
From: Morris J. <mo...@wh...> - 2005-03-16 22:19:21
|
Michel Bouissou wrote: > Le Mercredi 16 Mars 2005 22:43, Morris Jones a =E9crit : >=20 >>Does anyone make use of the "Probable spam: " cleanup report for >>anything interesting? >=20 > I use them for log analysis. Please leave them in ;-) That's interesting enough. :) Mojo --=20 Morris Jones Monrovia, CA http://www.whiteoaks.com Old Town Astronomers: http://www.otastro.org |
From: Lionel B. <lio...@bo...> - 2005-03-16 22:44:39
|
Morris Jones wrote the following on 16.03.2005 23:19 : > Michel Bouissou wrote: > >> Le Mercredi 16 Mars 2005 22:43, Morris Jones a =E9crit : >> >>> Does anyone make use of the "Probable spam: " cleanup report for >>> anything interesting? >> >> >> I use them for log analysis. Please leave them in ;-) > > > That's interesting enough. :) > > Mojo Funny logging is mentionned now : I'm currently reworking the logging and adding categories in the process=20 so as to allow users to choose what they want to log more precisely. |
From: Michael S. <Mic...@lr...> - 2005-03-17 11:38:50
|
On Wed, 16 Mar 2005, Lionel Bouton wrote: > Funny logging is mentionned now : > I'm currently reworking the logging and adding categories in the process > so as to allow users to choose what they want to log more precisely. > Don't forget to implement logging for the cleanup of from_awl und domain_awl. I would wish a minimal logging => logging of records deleted and a maximum logging => number of records and exactly which records were deleted. We would use the first information for a graphical representation of the cleanup of the various tables and would use the second for debugging purposes. Michael Storz ------------------------------------------------- Leibniz-Rechenzentrum ! <mailto:St...@lr...> Barer Str. 21 ! Fax: +49 89 2809460 80333 Muenchen, Germany ! Tel: +49 89 289-28840 |
From: Michael S. <Mic...@lr...> - 2005-03-17 11:40:36
|
On Wed, 16 Mar 2005, Lionel Bouton wrote: > Funny logging is mentionned now : > I'm currently reworking the logging and adding categories in the process > so as to allow users to choose what they want to log more precisely. Could you describe what the new model of logging looks like? Maybe we'll have suggestions what to include based on our needs. Michael Storz ------------------------------------------------- Leibniz-Rechenzentrum ! <mailto:St...@lr...> Barer Str. 21 ! Fax: +49 89 2809460 80333 Muenchen, Germany ! Tel: +49 89 289-28840 |
From: Lionel B. <lio...@bo...> - 2005-03-17 12:40:28
|
Michael Storz wrote the following on 17.03.2005 12:40 : >On Wed, 16 Mar 2005, Lionel Bouton wrote: > > > >>Funny logging is mentionned now : >>I'm currently reworking the logging and adding categories in the process >>so as to allow users to choose what they want to log more precisely. >> >> > >Could you describe what the new model of logging looks like? Maybe we'll >have suggestions what to include based on our needs. > > Nothing is carved in stone yet, but the idea is to split logging into categories. I've made a quick pass on the existing log() statements and have identified several preliminary categories: greylisting: decisions based on greylisting algos whitelist: decisions based on whitelists dbaccess: db upgrades, db access errors, martians: things coming from Postfix we aren't expecting, mail: mails sent to the administrator, spam: detected spam attempts perf: time spent in most intensive operations system: forks conf: conf loading/reloading other: ... My current plan is to continue using a default loglevel but to allow overriding it for each of these categories. Instead of "debug", "verbose", "normal", "quiet", ... There will be something like: default_loglevel = 2 loglevel_override = perf:4,mail:0 with 0:silent -> 4:debug Lionel. |