Hi,
I continue to have a problem with DMARC reporting described in this discussion:
mailcow community Icon RSPAMD chooses wrong date when triggering a DMARC report

mailcow community Icon mailcow communityDiscussion
RSPAMD chooses wrong date when triggering a DMARC report
I IceMann
Hi, I recently set up DMARC Reporting and the reports do get generated and recorded in Redis, but whenever I try to view the latest report output or manually trigger one it always says “No reports for <2 days ago>” and not the current date, which reports exist for. It also doesn’t send the
mailcow community
6 1

Now, is it possible to reinstall or reset RSPAMD to possibly solve the issue?

Thanks a lot!

Have something to say?

Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!

Thanks for your reply.
Did docker-compose down , docker volume rm mailcowdockerized_rspamd-vol-1 and the volume got deleted successfully. The Web UI was empty, as expected.
Executed docker-compose exec rspamd-mailcow rspamadm dmarc_report. It did generate the Reports for two days ago. Upon executing that same command again, it said the same thing:

Process date 20220819
No reports for 20220819
send data for 0 domains (from 1 to 0)

Same thing. Web UI date is right, date for report is wrong.

Well, for the deleting the volume, it does kind of delete the data. The start page of the Web UI is empty but the history and learns are still there.
Weird…

To “properly” get rid of all the RSPAMD data the redis volume has to be deleted too.

Didn’t solve the issue tho.

No one is typing