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

Focal OSSEC alerts not delivered when SMTP server requires that the From: address match the SASL-authenticated user #5916

Closed
zenmonkeykstop opened this issue Apr 28, 2021 · 2 comments · Fixed by #5924
Milestone

Comments

@zenmonkeykstop
Copy link
Contributor

Description

OSSEC alerts are sent via email from the monitor server using postfix and an external SMTP server. By default under Xenial, the sender email address was [email protected]. In cases where the SMTP server requires that the email sender matches the authenticated user, an additional site-specific variable, ossec_from_address must be set - it's used to map the local address to the variable value.

This is failing under Focal. Even with ossec_from_address set, emails are being rejected due to a mismatch. It appears that Focal is using ossec@mon as the sender instead.

Steps to Reproduce

  • Set up a prod install using an SMTP server as described above, and setting ossec_from_address in the site-specific file before running the install playbook
  • observe mail log output in /var/log/mail.log on mon

Expected Behavior

  • Mail delivered as email address specified without issue

Actual Behavior

  • Mail rejected

Comments

Suggestions to fix, any other relevant information.

@zenmonkeykstop
Copy link
Contributor Author

Confirmed that adding an entry for ossec@mon gets alert emails flowing again.

While it would be good to understand why this is happening, it might be worthwhile setting this by default for all new installs, and eliminating the need for the ossec_from_address setting altogther, unless there's also a case where it has to be set to something other than the sender address on the SMTP server. (None spring to mind but SES, maybe?)

@eloquence eloquence added this to the 1.8.2 milestone May 3, 2021
@zenmonkeykstop
Copy link
Contributor Author

One thing to note here is that the description above assumes the Monitor Server hostname is mon - this is user-configurable, so a fix should use the actual system hostname.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants