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
Last night, the same issue happened again. The automatically installed
security update misconfigured my postfix/main.cf file with exactly the
same values as posted earlier.
Will Ante Karamatić patch be included in Lucid?
--
You received this bug notification because you are a member of Ubuntu
@eiver: It looks like I can't change the Importance value of this bug.
It's greyd-out and I see no edit options..
** Changed in: dovecot (Ubuntu Lucid)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
the new package installed nice, without changing my configuration so it looks
like this patch fixes the bug.
Note: I get standard errors about an unconfigured nsd3 everytime I use apt
which is related to another bug.
Anyway, the dovecot installation went fine, without any problems and did not
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
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
I happened to have a 10.10 server in my VirtualBox and can confirm this
latest package does not change the postfix configuration.
root@ubuntu:/etc# git status
# On branch master
nothing to commit (working directory clean)
root@ubuntu:/etc# apt-get install dovecot-common
Reading package lists...
Public bug reported:
Binary package hint: dovecot-postfix
After dovecot-postfix was automatically upgraded this morning
(http://www.ubuntu.com/usn/usn-1059-1) the config in
/etc/postfix/main.cf was changed. Replacing my certificates with invalid
ones. Discovered it by Thunderbird complaining
The git diff I posted before is a complete diff from the /etc directory
before the upgrade, and after the upgrade (using the package etckeeper).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in ubuntu.
Public bug reported:
Binary package hint: munin
The amavis plugin of munin-node displays 0 for probably spam and
surely spam statistics. This is because it does the wrong `grep` on
the mail log file.
The included patch has 2 altered grep statements
sure spam is a grep for 'Blocked SPAM'
and
** 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.
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
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
Yes, thanks for the link and thoughts. I'm currently investigating if I
can leave all the SA, amavis and clamav code out of my setup by using
the blacklist feature of postscreen*.
* http://www.postfix.org/postconf.5.html#postscreen_dnsbl_sites
--
You received this bug notification because you
This user switching is for reading per-user configurations only and I
think can be mitigated by making the per-user config world readable.
Furthermore from the README.spamd.gz you've mentioned If a fault is
found in spamd or spamassassin code, any third party linked-libraries or
imported perl
Public bug reported:
I was surprised that after following
https://help.ubuntu.com/14.04/serverguide/mail-filtering.html this
leaves me with the spamassassin daemon running as root.
This is not of the same standard compared with the secure defaults that
Postfix and Dovecot use. I think this
16 matches
Mail list logo
