Bug 894185

Summary: Logwatch does not handle "improper command pipelining after (NOOP|RSET)"
Product: Red Hat Enterprise Linux 6 Reporter: Robert Scheck <redhat-bugzilla>
Component: logwatchAssignee: Jan Synacek <jsynacek>
Status: CLOSED ERRATA QA Contact: Ondrej Hudlicky <ohudlick>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3CC: ohudlick, ovasik, robert.scheck
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-10 13:40:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
[Patch] handle "improper command pipelining" message correctly none

Description Robert Scheck 2013-01-10 23:31:47 UTC
Description of problem:
Logwatch does not handle "improper command pipelining after (NOOP|RSET)" as
it is shipped right now with RHEL 6. Reproducing is easily possible, simply
add "reject_unauth_pipelining" to "smtpd_recipient_restrictions" in main.cf
and get a dumb spammer who didn't learn to behave according to SMTP RFCs.

Version-Release number of selected component (if applicable):

How reproducible:
Everytime, see above and below.
Actual results:
Logwatch does not handle "improper command pipelining after (NOOP|RSET)"

Expected results:
Logwatch should handle "improper command pipelining after (NOOP|RSET)"

Additional info:
According to logwatch upstream there seems to be a patch for this already:

Comment 2 Robert Scheck 2013-01-11 00:00:46 UTC
Actually, we see NOOP/RSET/HELO in the wild currently, the patch covers them
all - which is likely the best.

Cross-filed case 00775789 in the Red Hat customer portal.

Comment 3 Jan Synacek 2013-01-14 14:18:01 UTC
Created attachment 678237 [details]
[Patch] handle "improper command pipelining" message correctly

Comment 4 Jan Synacek 2013-01-14 14:25:07 UTC
Testing package:


Comment 5 Robert Scheck 2013-01-18 10:05:42 UTC
Applying this package removes the patch from bug #799987 - which unfortunately
still did not make it into any stable release yet.

Comment 6 Robert Scheck 2013-01-18 12:15:20 UTC
The testing RPM fixes the initially described issue for me, however comment #5
applies for that testing package.

Comment 13 errata-xmlrpc 2013-09-10 13:40:29 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.