Closed schmueller closed 2 months ago
Can not confirm that. DMARC reporting is working on my maschines (testing + prod).
Can you try manually triggering the DMARC reports by running:
docker compose exec rspamd-mailcow bash
rspamadm dmarc_report
This is the result:
root@intern:~# cd /opt/mailcow-dockerized/
root@intern:/opt/mailcow-dockerized# docker compose exec rspamd-mailcow bash
root@rspamd:/# rspamadm dmarc_report
call to rspamadm lua script failed (2): /usr/share/rspamd/lualib/rspamadm//dmarc_report.lua:386: bad argument #1 to 'ipairs' (table expected, got string); trace: [1]:{/usr/share/rspamd/lualib/rspamadm//dmarc_report.lua:386 - rcpt_list [Lua]}; [2]:{/usr/share/rspamd/lualib/rspamadm//dmarc_report.lua:522 - prepare_report [Lua]}; [3]:{/usr/share/rspamd/lualib/rspamadm//dmarc_report.lua:607 - process_report_date [Lua]}; [4]:{/usr/share/rspamd/lualib/rspamadm//dmarc_report.lua:703 -
Can you show me your dmarc.conf?
reporting { enabled = true; email = 'dmarc@xxx.com'; bcc_addrs = 'root@xxx.com'; domain = 'xxx.com'; org_name = 'Muster'; helo = 'rspamd'; smtp = 'postfix'; smtp_port = 25; from_name = 'Muster DMARC Report'; msgid_from = 'rspamd.mail.xxx.com'; max_entries = 2k; keys_expire = 2d; }
When mailcow send DMARC Aggregate Reports, some of them are not scored in rspamd and not signed. In rspamd web interface> History, column "Pass-through module" shows "Unknown lua". This happens not every day, but a few times on a week. This behavior start after the last update to 2024-08a.
When the receiving mta analise the message it responds with "554 5.7.1 rejected by SPF policy for mail.moohooooooo.com and DMARC policy for moohooooooo.com with invalid ARC result. postmaster@receivingserver.com: Recipient address rejected: Message rejected due to: SPF fail - not authorized."
@dragoangel Opinion on that? Or any idea why this is happening?
Mailcows instructions are okay, problem is somewhere in new Rspamd. I would recommend open issue at upstream. And provide redis dump with only dmarc related records in it if possible for easier debug.
UPD: actually user not follow configuration instructions, and Rspamd works as expected.
When mailcow send DMARC Aggregate Reports, some of them are not scored in rspamd and not signed. In rspamd web interface> History, column "Pass-through module" shows "Unknown lua". This happens not every day, but a few times on a week. This behavior start after the last update to 2024-08a.
When the receiving mta analise the message it responds with "554 5.7.1 rejected by SPF policy for mail.moohooooooo.com and DMARC policy for moohooooooo.com with invalid ARC result. postmaster@receivingserver.com: Recipient address rejected: Message rejected due to: SPF fail - not authorized."
Are you using force actions? Or you speaking about outgoing dmarc report being rejected?
If about outgoing one, not sure how issue with lua & redis related to wrong spf
Are you using force actions? Or you speaking about outgoing dmarc report being rejected? If about outgoing one, not sure how issue with lua & redis related to wrong spf
I'm not using forced actions - just default configuration with a few rspamd scores changed, for more accurate SPAM recognition. I'm speaking about outgoing DMARC records, yes. But they are rejected not from my own rspamd in mailcow, but from the receiving mail server (because of message not signed), for which domain this DMARC report i s about.
@schmueller you config is wrong 😅
bcc_addrs = 'root@xxx.com';
While it should be:
bcc_addrs = ["root@xxx.com"];
You lost array. Even if there is 1 email - it still should be array and not string. Please follow docs properly: https://docs.mailcow.email/post_installation/firststeps-dmarc_reporting/?h=dmarc#send-a-copy-reports-to-yourself
@w64 your issue also sounds like configuration issue, not like something wrong in Mailcow or Rspamd. Better write in community telegram to properly check the case.
@dragoangel Sorry, I didn't spot that. Thanks for pointing me into the right direction. Now it is working
Contribution guidelines
I've found a bug and checked that ...
Description
Logs:
Steps to reproduce:
Which branch are you using?
master
Which architecture are you using?
x86
Operating System:
Debian 12.5
Server/VM specifications:
16 GB RAM, 4 Cores
Is Apparmor, SELinux or similar active?
no
Virtualization technology:
VMWare
Docker version:
26.1.3
docker-compose version or docker compose version:
v2.27.0
mailcow version:
2024-08a
Reverse proxy:
nginx
Logs of git diff:
Logs of iptables -L -vn:
Logs of ip6tables -L -vn:
Logs of iptables -L -vn -t nat:
Logs of ip6tables -L -vn -t nat:
DNS check: