This bug was fixed in the package amavisd-new - 1:2.6.0-1ubuntu1
---
amavisd-new (1:2.6.0-1ubuntu1) intrepid; urgency=low
* Merge from Debian unstable. Remaining Ubuntu changes:
- Updated logcheck/ignore.d.server/amavisd-new (LP: #188754)
- Add libmail-dkim-perl (>= 0.31) to
I'll include this with the new amavisd-new 2.6 in Intrepid.
** Changed in: amavisd-new (Ubuntu)
Assignee: (unassigned) => Scott Kitterman (kitterman)
Status: Triaged => In Progress
--
rules for amavisd-new are not catching all mails
https://bugs.launchpad.net/bugs/188754
You receive
That should work. Thanks.
--
rules for amavisd-new are not catching all mails
https://bugs.launchpad.net/bugs/188754
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
I guess a possible test procedure would be:
1. install and configure amavisd-new (I presume as maintainer you probably have
servers
running it).
2. sudo apt-get install logcheck logcheck-database
3. logcheck will begin hourly checks and mail output to root. If you want it
to go elsewhere,
OK. If you can give me a test procedure that I can use to replicate the
problem and then verify that it's corrected with the new package, I
should be able to get this uploaded.
--
rules for amavisd-new are not catching all mails
https://bugs.launchpad.net/bugs/188754
You received this bug notif
** Attachment added: "updated patch solution 2"
http://launchpadlibrarian.net/14672473/solution-2-v3.patch
--
rules for amavisd-new are not catching all mails
https://bugs.launchpad.net/bugs/188754
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
bah! an extra comma went in there where it shouldn't updated patches
attached.
** Attachment added: "updated patch solution 1"
http://launchpadlibrarian.net/14672468/solution-1-v3.patch
--
rules for amavisd-new are not catching all mails
https://bugs.launchpad.net/bugs/188754
You received t
Testing solution-2 above (ie removing the OK field from the end) has
removed most of my normal mail logs. However, a few are still slipping
through:
May 23 10:10:30 robin amavis[17682]: (17682-03) Passed CLEAN, LOCAL [127.0.0.1]
[87.42.170.254] <[EMAIL PROTECTED]> -> <[EMAIL PROTECTED]>, Message
** Attachment added: "solution-2 updated"
http://launchpadlibrarian.net/14672086/solution-2.patch
--
rules for amavisd-new are not catching all mails
https://bugs.launchpad.net/bugs/188754
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Sorry I took my eye off the ball a little on this one.
As I'm sure you know logcheck uses a set of standard regexps to filter
out the "normal" log messages and send the admin the rest. amavisd-
new's filters are not quite catching all the normal mail now.
The situation seems to have changed a li
** Attachment added: "make the OK field optional in logcheck filters"
http://launchpadlibrarian.net/14671215/solution-1.patch
--
rules for amavisd-new are not catching all mails
https://bugs.launchpad.net/bugs/188754
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: "Remove the OK field in logcheck filters"
http://launchpadlibrarian.net/14671224/solution-2.patch
--
rules for amavisd-new are not catching all mails
https://bugs.launchpad.net/bugs/188754
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: "make the OK field optional in logcheck filters"
http://launchpadlibrarian.net/14671214/solution-1.patch
--
rules for amavisd-new are not catching all mails
https://bugs.launchpad.net/bugs/188754
You received this bug notification because you are a member of Ubuntu
Bugs,
Would you please show how it looks once it's fixed. For a non-logcheck
user it's kind of hard to tell exactly what you're missing.
--
rules for amavisd-new are not catching all mails
https://bugs.launchpad.net/bugs/188754
You received this bug notification because you are a member of Ubuntu
Bug
The patch was made against amavisd-new_2.5.3-1ubuntu3 - is this what you
meant?
--
rules for amavisd-new are not catching all mails
https://bugs.launchpad.net/bugs/188754
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
** Changed in: amavisd-new (Ubuntu)
Sourcepackagename: logcheck => amavisd-new
Importance: Undecided => Medium
Status: New => Triaged
--
rules for amavisd-new are not catching all mails
https://bugs.launchpad.net/bugs/188754
You received this bug notification because you are a member o
Sorry, I forgot diff -u :)
I've re-attached the patch (to /etc/logcheck/ignore.d.server/amavisd-
new), based on the original from amavisd-new v2.5.3.
** Attachment added: "Fix logcheck rule (same as previous patch, but as a
unified diff)"
http://launchpadlibrarian.net/13830047/amavisd-new-ha
logcheck files are shipped with amavisd-new itself.
$ apt-file list amavisd|grep logcheck
amavisd-new: /etc/logcheck/ignore.d.server/amavisd-new
amavisd-new: /etc/logcheck/violations.ignore.d/amavisd-new
What file is your patch against?
The bug then should get moved over to amavisd-new probably,
There are a couple more changes that I didn't catch in the last patch -
there's now an IPv6 identifier, and the 'Hits:' value may not have a '-'
prefix.
** Attachment added: "Fix logcheck rule #2 (supersedes previous version)"
http://launchpadlibrarian.net/13772188/amavisd-new-hardy.patch
--
I have a very similar problem with hardy beta (logcheck-database
v1.2.63) - it looks like the log files have changed again. The attached
patch works for me (though I only had 'CLEAN' emails to test with)
** Attachment added: "Fix logcheck rule for amavisd-new in hardy beta"
http://launchpadlib
[EMAIL PROTECTED] ~> apt-cache policy amavisd-new
amavisd-new:
Installed: 1:2.4.2-6.2ubuntu1
Candidate: 1:2.4.2-6.2ubuntu1
Version table:
*** 1:2.4.2-6.2ubuntu1 0
500 http://ie.archive.ubuntu.com gutsy/universe Packages
100 /var/lib/dpkg/status
[EMAIL PROTECTED] ~> apt-cache
21 matches
Mail list logo
