similar to: Bug#387000: Missing DATA in postfix

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

Package: logcheck Version: 1.2.41 Severity: minor man (8) logcheck says: For hints on how to maintain rules, see README.logcheck-database.gz, but this file is not included in /usr/share/doc/logcheck. micah -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel:

Package: logcheck-database Version: 1.2.63 Severity: wishlist Tags: patch The bad address syntax bounce message was previously logged by postfix/qmgr, but in the current version of Postfix in lenny is (at least sometimes) logged by postfix/error instead. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1,

Package: logcheck-database Version: 1.2.42 Severity: normal Tags: patch Index: postfix =================================================================== --- postfix (revision 1097) +++ postfix (working copy) @@ -44,7 +44,7 @@ # Postfix < 2.1 ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postfix/smtp\[[0-9]+\]: connect to [^[:space:]]+: server dropped connection without sending the initial greeting

Package: logcheck-database Version: 1.2.39 Severity: normal The rule for postfix/smtp read timeout (port 25) doesn't match the actual log message: ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postfix/smtp\[[0-9]+\]: connect to [^[:space:]]+ \[[.0-9]+\]: read timeout \(port 25\)$ A sample log line is: May 17 17:38:16 dp postfix/smtp[12256]: connect to smtpv1.ihs.gov[198.45.3.65]: read timeout (port

Package: logcheck-database Version: 1.2.39 Severity: wishlist Hi, I'd like to add the following rule to /etc/logcheck/violations.ignore.d/logcheck-postfix : ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postfix/smtpd?\[[0-9]+\]: NOQUEUE: reject: RCPT from [._[:alnum:]-]+\[[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\]: 554 <[._[:alnum:]-]+\[[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\]>:

Package: logcheck-database Version: 1.2.51 Severity: normal Messages such as these are no longer being filtered by logcheck ('hostname' used to replace actual hostname; 'hostname.com' used to replace actual domain): Dec 23 12:02:58 hostname postfix/lmtp[5047]: 38BE4C21ED: to=<root at hostname.com>, relay=127.0.0.1[127.0.0.1]:10024, delay=4.1, delays=2/0.16/0.05/1.8,

Package: logcheck-database Version: 1.2.44 Severity: minor Tags: patch Please change the following line in violations.ignore.d/logcheck-postfix: -^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postfix/smtp\[[0-9]+\]: [[:upper:]0-9]+: to=<[^[:space:]]+>, relay=[._[:alnum:]-]+\[[0-9.]{7,15}\], delay=[0-9]+, status=(deferred|bounced) \(host [._[:alnum:]-]+\[[0-9.]{7,15}\] said: [45][0-9][0-9] .* \(in

Package: logcheck-database Version: 1.3.13 Severity: normal Tags: patch Hi, after examining the code for postfix/smtpd, the following parameters for that specific log line can be present: client, sasl_method, sasl_username, sasl_sender, orig_queue_id, orig_client "client" is always present, the others are added where applicable, but always in the order explained above. There have been

Package: logcheck Version: 1.2.54 When Postfix is configured to listen on port tcp/587 by uncommenting the "submission" line in the postfix master.cf, logcheck does not ignore the anvil statistics log entries - attached is a patch from the current SVN trunk. -------------- next part -------------- A non-text attachment was scrubbed... Name: logcheck_1531.diff Type: text/x-patch Size:

also sprach Jamie L. Penman-Smithson <lists at silverdream.org> [2006.07.02.0012 +0200]: > >As far as I can tell, Postfix adds extended status codes, so instead > >of "250", you now get "250 2.0.0". > > Most of the rules have been updated to include these. If you find > any which have not been, file a bug. Are you sure? If I look at e.g.

commit 81496d0cf7b161bf981d51f0b96f860d68f3f6e3 Author: Micah Anderson <micah at debian.org> Date: Fri Aug 24 17:51:31 2007 -0400 Enable alternate temporary directory to be set in the configuration file On servers where the logfiles are very large and grow quickly, the logcheck processes may run into space issues in /tmp resulting in the email such as the following to be

Package: logcheck-database Version: 1.2.36 Severity: wishlist Hello, I recently blew away my old logcheck-databse and lost a number of changes that i had made to postfix entries. The default database for postfix reports the following errors that do not seem to be important... Apr 2 13:00:19 terminus postfix/local[29516]: 574B9B3B9F: to=<doug at localhost>, relay=local, delay=13,

Package: logcheck-database Version: 1.3.13 Severity: wishlist Hi, after upgrading Postfix from 2.7.1-1 to 2.8.1-1 (using testing) parts of the log format from postfix/smtpd have changed. This problem only seems to trigger when accepting connections in smtpd using XFORWARD (http://www.postfix.org/XFORWARD_README.html), for example when Amavisd-new reinjects mail to postfix. The new log lines

Package: logcheck-database Severity: normal Dear Maintainer, When configured to use an smtpd_proxy_filter (e.g. with spampd), postfix reports the status of the proxy request when it receives the proxy's END-OF-DATA reply. The log message is generated in data_cmd() at around src/smtpd/smtpd.c:3133 and is logged for each email message. For successfully delivered emails, this message is

Package: logcheck-database Severity: normal postfix has changed log formats, now it includes sasl_sender in log lines. The rule at ./ignore.d.server/postfix:109 ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ postfix/smtpd\[[[:digit:]]+\]: [[:alnum:]]+: client=[^[:space:]]+, sasl_method=[-[:alnum:]]+, sasl_username=[-_.@[:alnum:]]+$ must be updated with: ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+

Processing commands for control at bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.9.20 > package logcheck logcheck-database logtail Ignoring bugs not assigned to: logcheck-database logtail logcheck > tags 354820 + pending Bug#354820: rules to filter out entries caused by ssh scanners Tags were: patch Tags added: pending > tags 355085 + pending

Package: logcheck-database Version: 1.2.53 Severity: minor On my mailserver i've got some message like the following (user infos obscured): Jan 21 08:01:01 lorien postfix/smtp[3005]: 39D2315533A: to=<someuser at somedomain.org>, relay=mail.somedomain.org[11.22.33.44]:25, conn_use=2, delay=1.3, delays=0.06/0/0.44/0.83, dsn=2.0.0, status=sent (250 Message queued) This is a normal

Package: logcheck-database Version: 1.2.44 Severity: wishlist -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When using postfix smtpd_helo_restrictions / check_helo_access, the lines attched in 'postfix-helo.log' appear. The following rule can be used to filter them out: ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postfix/smtpd\[[0-9]+\]: NOQUEUE: reject: HELO from [^[:space:]]+: 553

Your message dated Tue, 24 Jun 2008 20:13:35 +0100 with message-id <20080624191335.GA18136 at lapse.rw.madduck.net> and subject line closed ages ago has caused the Debian Bug report #252165, regarding postfix: Messages from queuemanager flood logcheck to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility