RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

+++ This bug was initially created as a clone of Bug #1388335 +++

Description of problem:
* traceback happens when email alerts are enabled and local mail servers are down
* SELinux denials are analyzed as expected, but email alerts are not sent

Version-Release number of selected component (if applicable):
setroubleshoot-server-3.2.27.2-3.el7.x86_64
setroubleshoot-3.2.27.2-3.el7.x86_64
setroubleshoot-plugins-3.0.64-2.1.el7.noarch

How reproducible:
* always

Steps to Reproduce:
0. echo "root@localhost filter_type=never" >> /var/lib/setroubleshoot/email_alert_recipients
1. stop all local mail servers
2. trigger an SELinux denial
3. look into journal or /var/log/messages

Actual results:
Oct 25 02:49:49 unused-4-245 setroubleshoot: Exception during AVC analysis: [Errno 111] Connection refused

Expected results:
 * all exceptions are handled

I'd say that exceptions are handled by the code. They are caught and resent to syslog: 

```
    def run(self):
        while True:
            try:
                avc, report_receiver = self.queue.get()
                self.analyze_avc(avc, report_receiver)
            except Exception as e:
                syslog.syslog(syslog.LOG_ERR, "Exception during AVC analysis: %s" % e)
            except ValueError as e:
                syslog.syslog(syslog.LOG_ERR, "Exception during AVC analysis: %s" % e)
```


Milos, is this acceptable for you?

Yes, it is.