Displaying 20 results from an estimated 3000 matches similar to: "Bug#392034: spamd: s/SIGCHHLD/SIGCHLD/"
2007 Oct 29
1
Bug#448510: logcheck-database: revised pattern for spamd
Package: logcheck-database
Version: 1.2.63
Severity: normal
Tags: patch
spamassassin is now reporting Unix domain sockets in the rport field.
I'm not exactly sure what changed to cause this to happen; it started
after an upgrade whose only remotely relevant package was razor.
I think the following pattern in ignore.d.server/spamd will work
^\w{3} [ :0-9]{11} [._[:alnum:]-]+
2006 Feb 21
2
Bug#353868: logcheck-database: no longer ignores "spamd: checking message ..."
Package: logcheck-database
Version: 1.2.43a
Severity: minor
Since last weekend's upgrade of logcheck-database from 1.2.42 to
1.2.43a, logcheck stopped ignoring routine SpamAssassin messages of
the form
Feb 20 21:36:16 tux64 spamd[4665]: spamd: checking message <20060220190721.0E0B41C5207 at llwb563.servidoresdns.net> for amu:7286
Could you please edit the second pattern in
2011 Jul 02
1
Bug#632471: logcheck-database: spamd child cleanup message broken after upgrade to squeeze
Package: logcheck-database
Version: 1.3.13
Severity: normal
Tags: patch
After upgrading to debian squeeze I get several messages a day in the form of:
Jul 2 15:05:15 hostname spamd[21286]: spamd: handled cleanup of child pid [28609] due to SIGCHLD: exit 0
This is due to an update in spamd, that makes the message more detailed (includes exit code)[1]. Therefore messages including exit code 0
2008 Aug 31
0
Bug#474239: marked as done (spamassassin: spamd logcheck file doesn't work with shortcircuit enabled)
Your message dated Sun, 31 Aug 2008 19:32:06 +0000
with message-id <E1KZsec-00064d-FQ at ries.debian.org>
and subject line Bug#474239: fixed in logcheck 1.3.0
has caused the Debian Bug report #474239,
regarding spamassassin: spamd logcheck file doesn't work with shortcircuit enabled
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
2008 May 15
1
Bug#471936: setting package to logcheck-database logtail logcheck, tagging 473619, tagging 478334, tagging 472368 ...
# Automatically generated email from bts, devscripts version 2.10.27
#
# logcheck (1.2.64) unstable; urgency=low
#
# * ignore.d.server/dhcp
# - Adding dhcp rules for DNS updates by ddns_remove_a()
# (closes: #459875, #472368)
# - Added dhcp "removed reverse map" rule, which occurs on DHCPRELEASE.
# * ignore.d.server/spamd
# - deal with socket connections by e.g. evolution
2014 Aug 11
3
Use postfix and spamd on CentOS 6 - looking for a shortest guide
Hello fellow CentOS-users,
on the net there are lots of Spamassassin related HOWTOs - describing how
to create a shell script for Postfix and how to install Spamassassin and
start its spamd daemon - step by step. Additionally antivirus setups are
described...
But I have a strong feeling, that this is unneeded on CentOS 6 - because
there are already preconfigured stock packages for postfix and
2008 Aug 31
1
Bug#491694: setting package to logcheck-database logtail logcheck, tagging 491694, tagging 474239, tagging 489172 ...
# Automatically generated email from bts, devscripts version 2.10.35
# via tagpending
#
# logcheck (1.3) unstable; urgency=low
#
# * Formalise the dropping of violations.d/logcheck. Please see
# /usr/share/doc/logcheck-database/NEWS.Debian.gz for more information
# (closes: #471072).
# * Add Auto-Submitted header to outgoing mails (closes: #489172).
# * ignore.d.server/kernel:
# -
2008 Jun 24
1
Bug#483214: setting package to logcheck-database logtail logcheck, tagging 487208, tagging 484546, tagging 482523 ...
# Automatically generated email from bts, devscripts version 2.10.30
# via tagpending
#
# logcheck (1.2.65) unstable; urgency=low
#
# * ignore.d.server/postfix:
# - ignore connection messages for anonymous TLS connections; thanks to
# Justin Larue (closes: #486440).
# - ignore hostname verification due to DNS name not found; thanks to
# Justin Larue (closes: #486440).
# *
2008 Mar 16
2
Bug#448510: logcheck-database: revised pattern for spamd
# Commit a3169ad6defc5ea28992a786387e345cb91c14a3
tag 448510 pending
thanks
In article <20071029165738.32481.50847.reportbug__39564.2398893417$1193677404$gmane$org at corn.betterworld.us> you wrote:
> spamassassin is now reporting Unix domain sockets in the rport field.
I take it you are using --socketpath in /etc/default/spamassassin?
> I'm not exactly sure what changed to
2006 Oct 06
0
Bug#391458: logcheck: Please provide a way to configure niceness of log scanning process
Package: logcheck
Version: 1.2.47
Severity: wishlist
I'm running logcheck with an extended set of regular expressions on a
desktop system. The CPU load of this system is normally very low, around
3%-5%. When logcheck starts scanning the logs, the CPU usage increases
to 100% for several minutes and working on the system becomes difficult.
I would therefore be very happy about if a
2004 Aug 31
1
Bug#269318: logcheck: /etc/logcheck/ignore.d.server (add spamassassin)
Package: logcheck
Version: 1.2.26
Severity: wishlist
Please add ignore for Spamassasin's "check" messages like:
Aug 16 19:27:54 ns spamd[23853]: checking message <20040816150710.86ADA708A8 at smtp-out.hotpop.com> for nobody:65534.
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.26.20040601
Locale: LANG=C, LC_CTYPE=C (ignored: LC_ALL
2013 Mar 25
1
Bug#703936: logcheck-database: SSH Bad Protocol Version Idenitifcation Rule is incomplete
Package: logcheck-database
Version: 1.3.13
Severity: normal
The rule for SSH ignoring "Bad protocol version identification" assumes there are no single quotes
inside the version string ('[^']'). I am however getting mails including those lines:
Mar 25 22:57:04 Debian-60-squeeze-64-minimal sshd[12144]: Bad protocol version identification
2010 May 25
1
Bug#583155: logcheck-database: Please create rules for amavis(d-new)
Package: logcheck-database
Version: 1.3.8
Severity: wishlist
HI,
can you please create a rule/some rules for amavis(d-new).
I get for every mail this mesage:
May 25 19:55:40 data amavis[9603]: (09603-15) Passed CLEAN, [::1] [213.165.64.22] <xxx at yyy.zz> -> \
<aaa at localhost>, Message-ID: <20100525175015.29677page1 at mx002.bbb.ccc>, mail_id: MM7upJv6se1Z, \
Hits:
2006 Aug 11
0
Bug#382440: logcheck-database: Postfix rule missing in violations.ignore.d
Package: logcheck-database
Version: 1.2.47
Severity: normal
Tags: patch
Without the following logcheck line in
/etc/logcheck/violations.ignore.d, lines such as the following are
reported:
postfix/smtp[30054]: 824E9A2C1E: to=<nooneisillegal at someplace.net>,
relay=0.0.0.0[0.0.0.0], delay=1, status=sent (250 2.6.0 Ok, id=30274-22,
from MTA: 250 Ok: queued as 15140A2D0A)
This is because
2008 Sep 11
1
Bug#498613: ignore.d.server/kernel rules have a missing escape
Package: logcheck-database
Version: 1.3.1
Severity: important
Tags: patch
All kernel rules include the pattern
( [ *[[:digit:]]+\.[[:digit:]]+\])?
which is supposed to match timestamps. Here, the initial [ lacks an escape, it
should be \[.
Best,
Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194
2007 Aug 17
2
Help in starting spamassassin
I have installed spamassassin, per the instructions on Scalix's wiki,
and it is working, with some important caviats. So I asked for help on
the spamassassin user list, and got some, but I think I am butting up
against some Centos specific issues...
This is what I am seeing in the maillog:
Aug 17 14:39:59 z9m9z sendmail[13082]: l7HIdvGf013082: Milter add:
header: X-Spam-Checker-Version:
2006 Oct 31
0
Bug#396407: logcheck-database: Amandad line not ignored.
Package: logcheck-database
Version: 1.2.47
Severity: normal
The ignore.d.server/amandad file only ignores connections from hosts that cannot be found in DNS.
My hosts are found in DNS, resulting in connection reports including host names as well as IP addresses.
I would like to ask that connections to amandad with a hostname also be ignored. Below is an example
of such a log (changed the hostname
2000 Dec 12
1
reinstalling SIGCHLD handler before wait()
HP-UX 11 is looping on SIGCHLD/sigchld_handler2() when exiting a
protocol 2 session apparently because we don't call wait before
reinstalling the handler. Any thoughts on this issue or how to address
it?
serverloop.c from latest snapshots:
void
sigchld_handler2(int sig)
{
int save_errno = errno;
debug("Received SIGCHLD.");
child_terminated = 1;
signal(SIGCHLD,
2002 Jun 11
0
[Bug 271] New: SSHD should unblock SIGCHLD - POSIX signal blocks survive exec()
http://bugzilla.mindrot.org/show_bug.cgi?id=271
Summary: SSHD should unblock SIGCHLD - POSIX signal blocks
survive exec()
Product: Portable OpenSSH
Version: -current
Platform: Other
OS/Version: other
Status: NEW
Severity: enhancement
Priority: P2
Component: sshd
AssignedTo:
2002 Mar 22
0
[Bug 182] New: ssh should still force SIGCHLD to be SIG_DFL when calling ssh-rand-helper
http://bugzilla.mindrot.org/show_bug.cgi?id=182
Summary: ssh should still force SIGCHLD to be SIG_DFL when
calling ssh-rand-helper
Product: Portable OpenSSH
Version: 3.1p1
Platform: ix86
OS/Version: All
Status: NEW
Severity: normal
Priority: P3
Component: ssh
AssignedTo: