** Changed in: amavisd-new (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in Ubuntu.
https://bugs.launchpad.net/bugs/165184
Title:
amavisd-new + spamassassin: cronjob spams
** Changed in: amavisd-new (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/165184
Title:
amavisd-new + spamassassin: cronjob spams root user
To manage
In fact the problem is not fixed. It's workaround that doesn't give fix
the underlying problem.
The real solution would be to check if use_bayes is set to 0. If it is
set like that, it shouldn't run the cleaning job.
--
You received this bug notification because you are a member of Ubuntu
/usr/sbin/amavisd-new-cronjob could be changed to check if use_bayes is
set to 0:
sa-clean)
grep -q use_bayes 0 /etc/spamassassin/local.cf ||
do_amavis_cmd /usr/bin/sa-learn --sync --force-expire
;;
Or it can be checked for in cron.daily/amavisd-new in
In fact the problem is not fixed. It's workaround that doesn't give fix
the underlying problem.
The real solution would be to check if use_bayes is set to 0. If it is
set like that, it shouldn't run the cleaning job.
--
You received this bug notification because you are a member of Ubuntu
/usr/sbin/amavisd-new-cronjob could be changed to check if use_bayes is
set to 0:
sa-clean)
grep -q use_bayes 0 /etc/spamassassin/local.cf ||
do_amavis_cmd /usr/bin/sa-learn --sync --force-expire
;;
Or it can be checked for in cron.daily/amavisd-new in
This appears to be fixed in 2.6.4-2 (Debian), which needs to get merged
for Ubuntu.
I am updating the bug remote watch accordingly.
** Bug watch added: Debian Bug tracker #561311
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561311
** Changed in: amavisd-new (Debian)
Status: New =
This appears to be fixed in 2.6.4-2 (Debian), which needs to get merged
for Ubuntu.
I am updating the bug remote watch accordingly.
** Bug watch added: Debian Bug tracker #561311
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561311
** Changed in: amavisd-new (Debian)
Status: New =
See also Debian bug 447040. In my opinion, the simplest fix is
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=447040#51 :
Add dev/null directly into /etc/cron.d/amavisd-new, at the end of the
cron line.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
See also Debian bug 447040. In my opinion, the simplest fix is
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=447040#51 :
Add dev/null directly into /etc/cron.d/amavisd-new, at the end of the
cron line.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Branch linked: lp:ubuntu/ubuntu-docs
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in ubuntu.
--
Ubuntu-server-bugs mailing
** Branch linked: lp:ubuntu/ubuntu-docs
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
@sommer: Thanks for updated the documentation to a work around for
reducing the unwanted mail. Is there an intention to get an out of the
box fix for Maverick?
Thanks.
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug
** Changed in: server-papercuts
Status: Fix Committed = Fix Released
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in
** Changed in: server-papercuts
Status: Fix Committed = Fix Released
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
@Adam: I can't see the new section...
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in ubuntu.
--
Ubuntu-server-bugs mailing
@Adam: I can't see the new section...
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: server-papercuts
Status: Triaged = Fix Committed
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in ubuntu.
** Changed in: server-papercuts
Status: Triaged = Fix Committed
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I can confirm that the issue is still in Maverick. I've added a
subsection to the Amavisd-new section of the Server Guide to add the
bayes 0 check from Sylvain's patch on comment #26.
If this information solves the bug please let me know. You can see the
new section by checking out the
I can confirm that the issue is still in Maverick. I've added a
subsection to the Amavisd-new section of the Server Guide to add the
bayes 0 check from Sylvain's patch on comment #26.
If this information solves the bug please let me know. You can see the
new section by checking out the
The Debian bug reports this was fixed in package version 2.6.2-1, which
has been in Ubuntu since Jaunty. Is this still a bug on recent Ubuntu
installs?
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are
The Debian bug reports this was fixed in package version 2.6.2-1, which
has been in Ubuntu since Jaunty. Is this still a bug on recent Ubuntu
installs?
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are
** Changed in: amavisd-new (Ubuntu)
Assignee: (unassigned) = Adam Sommer (asommer)
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Changed in: server-papercuts
Assignee: (unassigned) = Adam Sommer (asommer)
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new
** Changed in: amavisd-new (Ubuntu)
Assignee: (unassigned) = Adam Sommer (asommer)
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: server-papercuts
Assignee: (unassigned) = Adam Sommer (asommer)
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: server-papercuts
Status: Confirmed = Triaged
** Changed in: server-papercuts
Milestone: None = maverick-alpha-2
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of
** Changed in: server-papercuts
Status: Confirmed = Triaged
** Changed in: server-papercuts
Milestone: None = maverick-alpha-2
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of
Back on track as part of the Maverick papercuts cycle
** Changed in: server-papercuts
Status: Won't Fix = Confirmed
** Changed in: server-papercuts
Milestone: lucid-beta-2 = None
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You
Back on track as part of the Maverick papercuts cycle
** Changed in: server-papercuts
Status: Won't Fix = Confirmed
** Changed in: server-papercuts
Milestone: lucid-beta-2 = None
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You
** Changed in: server-papercuts
Status: Confirmed = Won't Fix
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in ubuntu.
--
** Changed in: server-papercuts
Status: Confirmed = Won't Fix
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Changed in: server-papercuts
Milestone: None = lucid-beta-2
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in ubuntu.
--
** Changed in: server-papercuts
Milestone: None = lucid-beta-2
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Accepted as a papercut, for a documentation fix.
** Changed in: server-papercuts
Importance: Undecided = Low
** Changed in: server-papercuts
Status: New = Confirmed
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug
Accepted as a papercut, for a documentation fix.
** Changed in: server-papercuts
Importance: Undecided = Low
** Changed in: server-papercuts
Status: New = Confirmed
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug
** Also affects: server-papercuts
Importance: Undecided
Status: New
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in
** Also affects: server-papercuts
Importance: Undecided
Status: New
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
To get rid of the bayes: synced databases from journal emails reported
in comment 2, try this patch to /usr/bin/sa-learn. It turns off verbose
mode (forced on by --sync) which is what causes the output.
** Attachment added: Patch to turn off verbose mode when sa-learn --sync is
run
To get rid of the bayes: synced databases from journal emails reported
in comment 2, try this patch to /usr/bin/sa-learn. It turns off verbose
mode (forced on by --sync) which is what causes the output.
** Attachment added: Patch to turn off verbose mode when sa-learn --sync is
run
I think Sylvain Vallerot's patch (comment #26) addresses this properly.
Works well on my system. Please commit!
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Server Team, which
I think Sylvain Vallerot's patch (comment #26) addresses this properly.
Works well on my system. Please commit!
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Small patch, seems to solves the problem properly (my mind). Just checks about
a
line containing something like use_bayes 0 in Spamassassin config, and then
exists.
** Attachment added: no-bayes patch for amavisd-new-crontab
Small patch, seems to solves the problem properly (my mind). Just checks about
a
line containing something like use_bayes 0 in Spamassassin config, and then
exists.
** Attachment added: no-bayes patch for amavisd-new-crontab
That's not a complete solution; since the job keeps complaining if bayes
is disabled.
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
That's not a complete solution; since the job keeps complaining if bayes
is disabled.
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
You're absolutely correct, of course, it's not the complete solution,
but would fix the unwanted mails if bayes is enabled.
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Bugs,
In order to silence the bayes database sync messages that are frequently
sent via cron, could you consider fix along the lines of
--- /usr/sbin/amavisd-new-cronjob 2008-10-11 07:17:30.0 +0300
+++ /tmp/amavisd-new-cronjob2009-01-12 09:20:53.960773192 +0200
@@ -29,7 +29,7 @@
In order to silence the bayes database sync messages that are frequently
sent via cron, could you consider fix along the lines of
--- /usr/sbin/amavisd-new-cronjob 2008-10-11 07:17:30.0 +0300
+++ /tmp/amavisd-new-cronjob2009-01-12 09:20:53.960773192 +0200
@@ -29,7 +29,7 @@
So, I see three options to fix this, which one to use isn't my call to
decide:
1. patch spamassassin package, to make sure sa-learn doesn't complain if
use_bayes is set to 0
2. patch amavisd-new package, to not run sa-learn if use_bayes is set to
0. There should be a way to query SpamAssassin's
I'd buy:
2. patch amavisd-new package, to not run sa-learn if use_bayes is set to
0. There should be a way to query SpamAssassin's configuration from a
script - if there is, just use it.
Patches welcome.
--
amavisd-new + spamassassin: cronjob spams root user
So, I see three options to fix this, which one to use isn't my call to
decide:
1. patch spamassassin package, to make sure sa-learn doesn't complain if
use_bayes is set to 0
2. patch amavisd-new package, to not run sa-learn if use_bayes is set to
0. There should be a way to query SpamAssassin's
I'd buy:
2. patch amavisd-new package, to not run sa-learn if use_bayes is set to
0. There should be a way to query SpamAssassin's configuration from a
script - if there is, just use it.
Patches welcome.
--
amavisd-new + spamassassin: cronjob spams root user
My worry is that someone setting up a mail server without knowing about
this could end up receiving mail to that account without knowing.
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of
I understand. I think documentation is the best way to address it. I'm
open to a patch that's more nuanced than sending everything to dev/null.
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a
In my case, if the install scripts had added an alias for amavis to root
it should solve that worry.
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
IMHO, this bug should be added as a security issue. In my setup, the
cron script emails the amavis user. There was no alias to root added by
the installation scripts, therefore, the user who set up the system will
not receive the mail. This is a potential denial of service
vulnerability. By
DoSing yourself because you let the hard drive get full is an
administration problem not a security problem. I'll look at the docs and
see what I can do.
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because
I think, when is this package removed, this cron script should be
removed too.
Scott Kitterman napsal(a):
Pavel, I suspect you had it installed on that box at one point. You'll
just need to edit your crontab to get rid of the cron job.
--
amavisd-new + spamassassin: cronjob spams root
I think, when is this package removed, this cron script should be
removed too.
Scott Kitterman napsal(a):
Pavel, I suspect you had it installed on that box at one point. You'll
just need to edit your crontab to get rid of the cron job.
--
amavisd-new + spamassassin: cronjob spams root
I have the same issue as Daniel has at his comment
https://bugs.launchpad.net/ubuntu/+source/amavisd-
new/+bug/165184/comments/2
Amavisd-new and spamassassin are working fine in Hardy, but still outputting
the informational messages from the sa-sync cronjob:
bayes: synced databases from journal
Pavel, I suspect you had it installed on that box at one point. You'll
just need to edit your crontab to get rid of the cron job.
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Ive this problem too, but I dont have amavisd-new installed:
[EMAIL PROTECTED]:~$ dpkg -l amavisd-new
rc amavisd-new
but cron.daily script is installed after remove this package without
purge
[EMAIL PROTECTED]:~$ cat /etc/cron.daily/amavisd-new
#!/bin/sh
#
# Daily maintenance for amavisd-new
Ive this problem too, but I dont have amavisd-new installed:
[EMAIL PROTECTED]:~$ dpkg -l amavisd-new
rc amavisd-new
but cron.daily script is installed after remove this package without
purge
[EMAIL PROTECTED]:~$ cat /etc/cron.daily/amavisd-new
#!/bin/sh
#
# Daily maintenance for amavisd-new
Unchecked patch as I don't think dumping to /dev/null is the right way
to solve this.
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Spamassassin 3.2.4 is just uploaded to Hardy. I've asked to have it
backported to Gutsy and Feisty. Once you get 3.2.4, please see if this
is still a problem as there are some sa-learn related changes in the new
release.
** Changed in: amavisd-new (Ubuntu)
Status: Triaged = Incomplete
No. I think it should either be managed by changing amavisd-new or you
configuring your mail delivery agent to dump stuff you don't want to
see. I'm not sure which. I just wanted to check.
** Changed in: amavisd-new (Ubuntu)
Status: Incomplete = Triaged
--
amavisd-new + spamassassin:
There are no relevant changes from 3.2.1 (which I'm currently using) to 3.2.4
(in sa-learn).
The error is still outputted using WARN.
Do you think we should patch this in the spamassassin package?
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You
Server Team: can somebody of you take a look at this one?
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I've looked at this briefly. I'm not convinced this is the correct
solution.
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I'd second that simply discarding output (what Daniel Hahler's debdiff
does) is the wrong way.
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Ok, I agree that errors should not get discarded.
What's the better approach then?
1. Fix spamassassin to not handle/output configuration specifies 'use_bayes
0', sa-learn disabled as an error?
2. Try to find out if use_bayes is 0 before calling sa-learn?
The first one seems easier, because in
** Attachment added: debdiff for hardy
http://launchpadlibrarian.net/11087873/amavisd-new_2.5.2-2ubuntu2.dsc.diff
** Changed in: amavisd-new (Ubuntu)
Assignee: dAniel hAhler (blueyed) = (unassigned)
Status: In Progress = Triaged
** Description changed:
Binary package hint:
** Changed in: amavisd-new (Debian)
Status: Unknown = New
--
amavisd-new + spamassassin: cronjob spams root user
https://bugs.launchpad.net/bugs/165184
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
** Changed in: amavisd-new (Ubuntu)
Assignee: (unassigned) = dAniel hAhler (blueyed)
Status: Confirmed = In Progress
** Bug watch added: Debian Bug tracker #447040
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=447040
** Also affects: amavisd-new (Debian) via
Related, but with an updated amavisd-new from Hardy (on Feisty).
After having upgraded amavisd-new, I'm now getting cron mails with the
following line:
bayes: synced databases from journal in 3 seconds: 210 unique entries (350
total entries)
This gets sent from test -e
Package versions for this report:
amavisd-new1:2.4.2-6.2ubuntu1
spamassassin 3.2.3-0ubuntu1
I'm filing this as amavisd-new report since the cron scripts are part of
amavisd-new rather than spamassassin.
--
amavisd-new + spamassassin: cronjob spams root user
78 matches
Mail list logo
