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

Maldet Not Sending Email Report #192

Open
vwesisolak opened this issue Feb 1, 2017 · 6 comments
Open

Maldet Not Sending Email Report #192

vwesisolak opened this issue Feb 1, 2017 · 6 comments

Comments

@vwesisolak
Copy link

Hello,

I have maldet running on RHEL 6.8 and have found that despite configuring an email address and email_alert="1" it does not send a report. Maldet does not log sending the report (or any errors), nor is there a log of the attempt in maillog.

This is a duplicate of #156, which had been closed. I verified that the fixed mentioned there is in place. As noted in that ticket the --report option does send a mail.

--Eric

@rfxn
Copy link
Owner

rfxn commented Feb 2, 2017

Is there any hit events in the email? LMD will not send an email alert for scans that have no events.

@vwesisolak
Copy link
Author

Ah, hmm. I think I read the email_ignore_clean option as sending even with 0 hits, but I see now that it clearly indicates cleaned hits.

In that case, It would be awesome to be able to configure sending a report for all scans, even with no hits.

@rfxn
Copy link
Owner

rfxn commented Feb 2, 2017

That should be fairly easy to accommodate. I will see about getting that into 1.6 release. Thanks for all your feedback and issues :)

@Mattoje
Copy link

Mattoje commented Jul 19, 2017

Any news on this subject ? I'm interested too

@vkush
Copy link

vkush commented Apr 19, 2024

Do we have an update 2024 here? Looks like maldet v1.6.5. still has this problem - when malware is detected (hit) via "inotify-tools" in monitoring mode and moved to quarantine no mails are sent, only notification in the log file is written - /usr/local/maldetect/logs/event_log with events like {hit}, {quar}, {clean}.

If maldet scanning is started manually [maldet --scan-all path-to-folder], then mails are sent properly in case of hit. And in the log file above no new message (event) is created.

Config in /usr/local/maldetect/conf.maldet:
email_alert="1"
email_ignore_clean="0" or email_ignore_clean="1" - does not play any role here, for both cases no emails are sent

Because such parameters above are about "reports", and log file is about "events" - maybe we have to configure somehow, that in case of "hit" some new report is generated and then mailing will start to work?

Related issue with some advice: #424

@ZocStorm
Copy link

ZocStorm commented Sep 3, 2024

Hi, I am facing the same problem with email notifications not working properly.
Any info on possible workaround or solution?

Regards

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

No branches or pull requests

5 participants