I'm using fail2ban with CentOS 6.6. Something is causing fail2ban's
alerts sent to root's mail to be rejected. Here's a clip from one of the
error messages:
Message 48:
From MAILER-DAEMON at lion.protogeek.org Sun Dec 21 03:09:20 2014
Return-Path: <MAILER-DAEMON at lion.protogeek.org>
Date: Sun, 21 Dec 2014 03:09:19 -0600
From: Mail Delivery Subsystem <MAILER-DAEMON at
lion.protogeek.org>
To: postmaster at lion.protogeek.org
Content-Type: multipart/report; report-type=delivery-status;
boundary="sBL97EKS003880.1419152959/lion.protogeek.org"
Subject: Postmaster notify: see transcript for details
Auto-Submitted: auto-generated (postmaster-notification)
Status: R
Part 1:
The original message was received at Tue, 16 Dec 2014 03:09:17
-0600
from localhost
with id sBG97E83025627
----- The following addresses had permanent fatal errors
-----
<fail2ban at example.com>
----- Transcript of session follows -----
<fail2ban at example.com>... Deferred: Connection timed out with
example.com.
Message could not be delivered for 5 days
Message will be deleted from queue
..........
I used to get the messages that are now being deleted after five days.
Any suggestions?
--Doc Savage
Fairview Heights, IL
On 2014-12-26 12:39 pm, Robert G. (Doc) Savage wrote:> I'm using fail2ban with CentOS 6.6. Something is causing fail2ban's > alerts sent to root's mail to be rejected. Here's a clip from one of > the > error messages: > > > Message 48: > From MAILER-DAEMON at lion.protogeek.org Sun Dec 21 03:09:20 2014 > Return-Path: <MAILER-DAEMON at lion.protogeek.org> > Date: Sun, 21 Dec 2014 03:09:19 -0600 > From: Mail Delivery Subsystem > <MAILER-DAEMON at lion.protogeek.org> > To: postmaster at lion.protogeek.org > Content-Type: multipart/report; report-type=delivery-status; > boundary="sBL97EKS003880.1419152959/lion.protogeek.org" > Subject: Postmaster notify: see transcript for details > Auto-Submitted: auto-generated (postmaster-notification) > Status: R > > Part 1: > > The original message was received at Tue, 16 Dec 2014 03:09:17 > -0600 > from localhost > with id sBG97E83025627 > > ----- The following addresses had permanent fatal errors > ----- > <fail2ban at example.com> > > ----- Transcript of session follows ----- > <fail2ban at example.com>... Deferred: Connection timed out with > example.com. > Message could not be delivered for 5 days > Message will be deleted from queue > .......... > > > > I used to get the messages that are now being deleted after five days. > Any suggestions?I would suggest looking at the mailer daemon logs on both the sending and receiving systems. It would appear that the sending system is having difficulties at the receiving system end. You will likely find the root of your issues in the log entries for that message (or those messages) that occurred over the 5 days in question. -- Mike Burger http://www.bubbanfriends.org "It's always suicide-mission this, save-the-planet that. No one ever just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1
On 2014-12-26 12:59 pm, Mike Burger wrote:> On 2014-12-26 12:39 pm, Robert G. (Doc) Savage wrote: >> I'm using fail2ban with CentOS 6.6. Something is causing fail2ban's >> alerts sent to root's mail to be rejected. Here's a clip from one of >> the >> error messages: >> >> >> Message 48: >> From MAILER-DAEMON at lion.protogeek.org Sun Dec 21 03:09:20 >> 2014 >> Return-Path: <MAILER-DAEMON at lion.protogeek.org> >> Date: Sun, 21 Dec 2014 03:09:19 -0600 >> From: Mail Delivery Subsystem >> <MAILER-DAEMON at lion.protogeek.org> >> To: postmaster at lion.protogeek.org >> Content-Type: multipart/report; report-type=delivery-status; >> boundary="sBL97EKS003880.1419152959/lion.protogeek.org" >> Subject: Postmaster notify: see transcript for details >> Auto-Submitted: auto-generated (postmaster-notification) >> Status: R >> >> Part 1: >> >> The original message was received at Tue, 16 Dec 2014 03:09:17 >> -0600 >> from localhost >> with id sBG97E83025627 >> >> ----- The following addresses had permanent fatal errors >> ----- >> <fail2ban at example.com> >> >> ----- Transcript of session follows ----- >> <fail2ban at example.com>... Deferred: Connection timed out with >> example.com. >> Message could not be delivered for 5 days >> Message will be deleted from queue >> .......... >> >> >> >> I used to get the messages that are now being deleted after five days. >> Any suggestions? > > I would suggest looking at the mailer daemon logs on both the sending > and receiving systems. It would appear that the sending system is > having difficulties at the receiving system end. > > You will likely find the root of your issues in the log entries for > that message (or those messages) that occurred over the 5 days in > question.PS: "Connection timed out with example.com" is the first thing I'd look at. -- Mike Burger http://www.bubbanfriends.org "It's always suicide-mission this, save-the-planet that. No one ever just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1
Robert G. (Doc) Savage ????? 2014-12-26 20:39:> I'm using fail2ban with CentOS 6.6. Something is causing fail2ban's > alerts sent to root's mail to be rejected. Here's a clip from one of > the > error messages: > > > Message 48: > From MAILER-DAEMON at lion.protogeek.org Sun Dec 21 03:09:20 2014 > Return-Path: <MAILER-DAEMON at lion.protogeek.org> > Date: Sun, 21 Dec 2014 03:09:19 -0600 > From: Mail Delivery Subsystem > <MAILER-DAEMON at lion.protogeek.org> > To: postmaster at lion.protogeek.org > Content-Type: multipart/report; report-type=delivery-status; > boundary="sBL97EKS003880.1419152959/lion.protogeek.org" > Subject: Postmaster notify: see transcript for details > Auto-Submitted: auto-generated (postmaster-notification) > Status: R > > Part 1: > > The original message was received at Tue, 16 Dec 2014 03:09:17 > -0600 > from localhost > with id sBG97E83025627 > > ----- The following addresses had permanent fatal errors > ----- > <fail2ban at example.com> > > ----- Transcript of session follows ----- > <fail2ban at example.com>... Deferred: Connection timed out with > example.com. > Message could not be delivered for 5 days > Message will be deleted from queue > .......... > > > > I used to get the messages that are now being deleted after five days. > Any suggestions?Check your /etc/fail2ban/jail.local /etc/fail2ban/jail.conf. You have to provide valid email addresses for dest= and sender= parameters in sendmail-whois or mail-whois actions for enabled jails.
-----Original Message----- From: ????????? ???????? <nevis2us at infoline.su> Reply-to: CentOS mailing list <centos at centos.org> To: CentOS mailing list <centos at centos.org> Subject: Re: [CentOS] Fail2ban mail failures ??? Date: Fri, 26 Dec 2014 21:30:39 +0300 Robert G. (Doc) Savage ????? 2014-12-26 20:39:> I'm using fail2ban with CentOS 6.6. Something is causing fail2ban's > alerts sent to root's mail to be rejected. Here's a clip from one of > the > error messages: > > > Message 48: > From MAILER-DAEMON at lion.protogeek.org Sun Dec 21 03:09:20 2014 > Return-Path: <MAILER-DAEMON at lion.protogeek.org> > Date: Sun, 21 Dec 2014 03:09:19 -0600 > From: Mail Delivery Subsystem > <MAILER-DAEMON at lion.protogeek.org> > To: postmaster at lion.protogeek.org > Content-Type: multipart/report; report-type=delivery-status; > boundary="sBL97EKS003880.1419152959/lion.protogeek.org" > Subject: Postmaster notify: see transcript for details > Auto-Submitted: auto-generated (postmaster-notification) > Status: R > > Part 1: > > The original message was received at Tue, 16 Dec 2014 03:09:17 > -0600 > from localhost > with id sBG97E83025627 > > ----- The following addresses had permanent fatal errors > ----- > <fail2ban at example.com> > > ----- Transcript of session follows ----- > <fail2ban at example.com>... Deferred: Connection timed out with > example.com. > Message could not be delivered for 5 days > Message will be deleted from queue > .......... > > > > I used to get the messages that are now being deleted after five days. > Any suggestions?Check your /etc/fail2ban/jail.local /etc/fail2ban/jail.conf. You have to provide valid email addresses for dest= and sender= parameters in sendmail-whois or mail-whois actions for enabled jails. os.org/mailman/listinfo/centos ????????? ????????, I should have made it clear that this is all on one machine. The jail.conf file is the default from the fail2ban package. It used to work perfectly, but now has the mail problem. All I've had to do for years is install the fail2ban package, start it, and make it autostart whenever I reboot. Now it's misbehaving in a way that puzzles me. --Doc Savage Fairview Heights, IL