Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#35470 - [fail2ban] sendmail way of sending e-mail need to be rewriting

Attached to Project: Community Packages
Opened by Xoib68 (Xoib) - Saturday, 25 May 2013, 08:57 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Sunday, 02 June 2013, 13:19 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Bartłomiej Piotrowski (Barthalion)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Some e-mails are not sent because of a certain way to deal with sendmail.

Log : ./fail2ban.log:459:2013-05-17 18:29:56,647 fail2ban.actions.action: ERROR printf %b "Subject: [Fail2Ban] SSH: stopped
./fail2ban.log:479:2013-05-17 18:30:49,580 fail2ban.actions.action: ERROR printf %b "Subject: [Fail2Ban] SSH: started

Solution : change the /usr/bin/sendmail -f <sender> <dest> in all ./action.d/*.conf who use sendmail to /usr/bin/sendmail -f <sender> -t <dest>

Additional info:
* package version(s) : latest 0.8.9-1
* config and/or log files etc. :
Log : ./fail2ban.log:459:2013-05-17 18:29:56,647 fail2ban.actions.action: ERROR printf %b "Subject: [Fail2Ban] SSH: stopped
./fail2ban.log:479:2013-05-17 18:30:49,580 fail2ban.actions.action: ERROR printf %b "Subject: [Fail2Ban] SSH: started

Steps to reproduce:
Stop and start fail2ban and check the fail2ban.log to see the e-mails was not sent.
This task depends upon

Closed by  Bartłomiej Piotrowski (Barthalion)
Sunday, 02 June 2013, 13:19 GMT
Reason for closing:  Not a bug
Comment by Xoib68 (Xoib) - Wednesday, 29 May 2013, 16:16 GMT
Ok, it's working. I suspect that it's not working at halting // starting the server because fail2ban halt after // launch before the network daemon.
This is the most plausible explanation for now. The second explanation is that sometimes gmail smtp server think that two e-mail within the same second is spam so it drop it.
Sorry to began an issue for this. I will close the issue after someone confirm this.

Loading...