Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

improper command pipelining after QUIT with postfix 2.11.3-1 (Debian 8.0) #145

Closed
filviu opened this issue Mar 28, 2016 · 5 comments
Closed

Comments

@filviu
Copy link

filviu commented Mar 28, 2016

Hi,

I recently upgraded to Debian 8 on my mail server and I started getting my nagios server banned by fail2ban. The issue is that the following error appears in the mail.log when check_ssmt runs:

$ /usr/local/nagios/libexec/check_ssmtp -H mail.example.com -p 465

And this appears in mail.log:

Mar 28 11:04:40 example postfix/smtpd[9460]: connect from 4-3-2-1.example.com[1.2.3.4]
Mar 28 11:04:40 example postfix/smtpd[9460]: improper command pipelining after QUIT from 4-3-2-1.example.com[1.2.3.4]:
Mar 28 11:04:40 example postfix/smtpd[9460]: disconnect from 4-3-2-1.example.com[1.2.3.4]

I updated to nagios plugins 2.1.1 but the only change is that now it only happens intermittently.

@tmcnag
Copy link
Contributor

tmcnag commented Mar 30, 2016

@jfrickson jfrickson added the Bug label Oct 31, 2016
@jfrickson jfrickson self-assigned this Oct 31, 2016
@jfrickson
Copy link
Contributor

jfrickson commented Mar 14, 2017

I looked into this a couple months ago, and couldn't find a problem or reproduce. I'll be checking it out again soon.

@jfrickson jfrickson added this to the next bugfix release milestone Apr 5, 2017
@jfrickson
Copy link
Contributor

@silviuvulcan could you run the command line again, and add -vvv like so:

$ /usr/local/nagios/libexec/check_ssmtp -H mail.example.com -p 465 -vvv

then post the output. Maybe that will provide more information.

Thanks

@filviu
Copy link
Author

filviu commented Apr 10, 2017

I tried but can't reproduce the error anymore. It seems I upgraded to nagios plugins 2.2.0 some time in the past and maybe postfix was updated on the server (it's a debian 8 kept up-to-date so if any patches were released in the debian repos they were applied). So I can't tell which fixed it.

I grep-ed the logs but can't find the error associated with a nagios check either so it's been fixed for a while now.

@jfrickson
Copy link
Contributor

Ok, great! Thanks for getting back so quickly (a lot quicker than I got to it ;-)

@jfrickson jfrickson removed this from the next bugfix release milestone Apr 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants