--
You received this message because you are subscribed to the Google Groups "Wazuh mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wazuh+un...@googlegroups.com.
To post to this group, send email to wa...@googlegroups.com.
Visit this group at https://groups.google.com/group/wazuh.
To view this discussion on the web visit https://groups.google.com/d/msgid/wazuh/f8ca55f3-d851-4d3b-9776-5b5a55f51c69%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to wazuh+unsubscribe@googlegroups.com.
Hi Aleksandr
You are right the aspmx.l.google.com is no authentication required, but this service needs an extra configuration on your side to make it works, from the same link: https://support.google.com/a/answer/176600?hl=en
If your device or application doesn’t support SSL, you can only send mail to Gmail or G Suite users.
Use the restricted SMTP server aspmx.l.google.com.
Connect to aspmx.l.google.com on port 25.
Configure an SPF record for your domain with the IP address of the device or application to ensure that recipients don’t reject mail sent from it.
In your Google Admin console, add this IP address to the Email Whitelist box.
For example, if your sending device sends from 123.45.67.89, add that address to your SPF record without removing the G Suite mail servers from the record: v=spf1 ip4:123.45.67.89 include:_spf.google.com ~all.
Do you have the previous configuration done in your site/domain?
On the other hand, can run the following command cat /var/ossec/logs/ossec.log | grep ossec-maild and verify if you have any error?
Did you receive any mail from Ossec? Like Ossec server started, this email is always sent no matter which level setup in the configuration.
The Report is generated and sent once at midnight, and these reports are not stored in the disk, if you want to simulate the report you can run the following command:
cat /var/ossec/logs/alerts/alerts.log | /var/ossec/bin/ossec-reportd -f level 10
cat /var/ossec/logs/ossec.log | grep ossec-maild and verify if you have any error?Ok so,
If you are using aspmx.l.google.com you did the configuration in your Gmail site?
Connect to aspmx.l.google.com on port 25.
Configure an SPF record for your domain with the IP address of the device or application to ensure that recipients don’t reject mail sent from it.
In your Google Admin console, add this IP address to the Email Whitelist box.
For example, if your sending device sends from 123.45.67.89, add that address to your SPF record without removing the G Suite mail servers from the record: v=spf1 ip4:123.45.67.89 include:_spf.google.com ~all.
--
You received this message because you are subscribed to the Google Groups "Wazuh mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wazuh+un...@googlegroups.com.
To post to this group, send email to wa...@googlegroups.com.
Visit this group at https://groups.google.com/group/wazuh.
To view this discussion on the web visit https://groups.google.com/d/msgid/wazuh/7b16a2a2-25f4-4f65-b789-2fa7de8162ba%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to wazuh+unsubscribe@googlegroups.com.
If i understan you have your configuration like:
<global>
<jsonout_output>yes</jsonout_output>
<alerts_log>yes</alerts_log>
<logall>no</logall>
<logall_json>no</logall_json>
<email_notification>yes</email_notification>
<smtp_server>localhost</smtp_server>
<email_from>replaced1</email_from>
<email_to>replaced2</email_to>
<email_maxperhour>12</email_maxperhour>
</global>
……
<alerts>
<log_alert_level>3</log_alert_level>
<email_alert_level>9</email_alert_level>
</alerts>
<email_alerts>
<email_to>replaced3</email_to>
<group>attacks|exploit_attempt</group>
</email_alerts>
Try to do the next steps:
1- Stop ossec and verify that all services are stopped: 1 the server with /var/ossec/bin/ossec-control stop and ps axu | grep ossec
2- Start again the manager with /var/ossec/bin/ossec-control start and verify that the services are running ps axu | grep ossec
3- If you are using localhost verify that postfix is enabled systemctl status postfix
3- Search any error in ossec.log cat /var/ossec/logs/ossec.log | grep ERROR and cat /var/ossec/logs/ossec.log | grep ossec-maild
4- Verify if you have any error in maillog
To unsubscribe from this group and stop receiving emails from it, send an email to wazuh+un...@googlegroups.com.
To post to this group, send email to wa...@googlegroups.com.
Visit this group at https://groups.google.com/group/wazuh.
To view this discussion on the web visit https://groups.google.com/d/msgid/wazuh/744704c7-c17c-43f9-9396-623c401cfe05%40googlegroups.com.
In the end I got it fixed by ...reinstalling wazuh from the scratch (and also removed all temp files and conf). I saved and restored all config files and history files and got it working with no data loss in the end.