Is there any consensus on what needs to be done here? I'll gladly apply
a patch upstream if there is agreement on what must be done.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in Ubuntu.
Tim, your patch in comment #1 is definitely an improvement but I think
the definition of a probable spam (SPAMMY) should be revised as that
is configurable in Amavis. Would it be possible to grep for 'Passed
SPAMMY' instead ?
Passed SPAMMY is used by Amavis for messages with hits between
Simon, I have never seen the string Passed SPAMMY in my logs, are you
also using amavisd-new 1:2.6.4-1ubuntu5 shipped with 10.04 and are these
strings appearing in your /var/log/mail.log?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
reported to munin-monitoring.org bug tracker: http://munin-
monitoring.org/ticket/1104
** Bug watch added: munin-monitoring.org/ #1104
http://munin-monitoring.org/ticket/1104
** Also affects: munin via
http://munin-monitoring.org/ticket/1104
Importance: Unknown
Status: Unknown
** Changed in: munin
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in Ubuntu.
https://bugs.launchpad.net/bugs/720071
Title:
munin-node amavis spam stats
To manage notifications about this bug go
the previous attachment was a reverse patch, now it should apply.
** Attachment removed: change graph label
https://bugs.launchpad.net/ubuntu/+source/munin/+bug/720071/+attachment/1865698/+files/amavis_label.patch
** Patch added: more objective labels
** Changed in: munin (Ubuntu)
Status: Incomplete = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in ubuntu.
https://bugs.launchpad.net/bugs/720071
Title:
munin-node amavis spam stats
--
Ubuntu-server-bugs
Marking as Triaged.
Please note that you can easily add required information to a bug using
apport-collect $BUGNR.
Apart from that, this should get submitted to the upstream bug tracker,
if it still affects the current upstream release - which is the case
apparently: http://munin-
I have now looked at the log format/output.
Looking for Blocked SPAM is clearly a good idea when counting blocked spams,
which the other pattern depends on the configuration.
Would it be possible to get the barrier for spam easily from the amavis conf,
and then use this for the maybe spam
Tim, do you feel like forwarding it to the upstream tracker at http
://munin-monitoring.org/newticket (requires an account there), or should
I do this for you?
Daniel, the reason I didn't submit it there was idd because I had to
register and didn't find any links to do so at the time. So
Hi there!
Thank you for reporting bugs and trying to make Ubuntu better.
Can you please specify which Ubuntu versions are affected by this and
what version of the software in question?
For now, I'll be marking this bug as incomplete as the required
information is obtained.
Thank you again!
**
I'm using Ubuntu 10.04.1 and munin-node 1.4.4-1ubuntu1 from the default
repositories without customizations.
as a side note. I think it would be more appropriate to change the line
in the graph containing surely spam to blocked as spam, see the
attached patch.
** Patch added: change graph label
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in ubuntu.
https://bugs.launchpad.net/bugs/720071
Title:
munin-node amavis spam stats
--
Ubuntu-server-bugs mailing list
** Attachment added: altered grep for probably and surely spam
https://bugs.launchpad.net/bugs/720071/+attachment/1853838/+files/amavis.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in ubuntu.
14 matches
Mail list logo
