Spam Report Mails aren't DKIM signed

[pixelbar]

Hello,

we are signing all outgoing mails with a DKIM signature. Unfortunately the spam reports don't have this signature. Is this intended?

FYI: we are sending the report manually via /usr/bin/pmgqm in the crontab. We've checked every option and parameter but we can't find any solution.

Thank you.

 

[mfederanko]

It should sign the messages, but proceeds to send unsigned messages on signing errors. Did you check the system log? journalctl -b for hints at what might be going wrong? What version are you using?

 

[pixelbar]

I'm using PMG 7.2-1

No errors in the logs. But I also don't see those e-mails in the trackingcenter.

 

[mfederanko]

DKIM signing of PMG report emails is available since PMG 8.2, see [0]. Here [1] is the documentation for enabling DKIM, which also touches upon how to set this up for reports.

[0] https://bugzilla.proxmox.com/show_bug.cgi?id=3423
[1] https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_mailproxy_dkim

 

[pixelbar]

Thank you, didn't knew that!

 

[pietroaretino]

Hello I am encountering the same issue.
My domains have been DKIM signed since this PMG instance was setup still in version 7.X
It is currently at version 8.2.10 however my daily and weekly spam reports have stopped sending.
Running the command:
journalctl -u pmgspamreport.service -n 100
Results in hundreds of these outputs:
Feb 20 17:00:38 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''
Feb 20 17:00:38 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''
Feb 20 17:00:38 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''
Feb 20 17:00:38 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''
Feb 20 17:00:38 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''
Feb 20 17:00:39 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''
Feb 20 17:00:39 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''
Feb 20 17:00:39 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''
Feb 20 17:00:39 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''
Feb 20 17:00:39 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''
Feb 20 17:00:39 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''
Feb 20 17:00:39 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''
Feb 20 17:00:40 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''
Feb 20 17:00:40 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''
In Configuration --> Mail Proxy --> DKIM, this is my configuration:
Enable DKIM Signing YES
Selector PRIVATE
Signing Domain Source Envelope
Sign all Outgoing Mail Yes

SIGN DOMAINS
[My list of domains that should be signed]

In fact all my email sent out is DKIM signed I have verified this. So I am unsure why the daily spam report is looking at DKIM and failing at looking up the correct domain list?

I have tried resyncing the templates using
pmgconfig sync
Then restarting the services

systemctl restart pmgdaemon
systemctl restart pmgproxy
systemctl restart pmgspamreport.service

If I run the command:
pmgqm send
OR
pmgqm send --timespan yesterday
The daily spam reports get sent out without issue. I may just have to setup a cronjob for this in the interim until I figure out why systemd isn't sending this out or what the issue is with the DKIM.

In pmg.conf I see that the mailfrom address is correct "mailgate@mydomain.com".
Double-checked the DKIM domains that need to be signed and "mydomain.com" is part of that list.

 

[Stoiko Ivanov]

So I am unsure why the daily spam report is looking at DKIM and failing at looking up the correct domain list?

This is explained in the docs, which @mfederanko linked:

1] https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_mailproxy_dkim

Mails generated by Proxmox Mail Gateway itself, like notifications and reports, usually have an empty envelope. Thus they will only be signed if you have selected header as the source of the signing domain

you need to change the signing domain source to 'header' instead of envelope.

I hope this helps!

 

[pietroaretino]

This is explained in the docs, which @mfederanko linked:




you need to change the signing domain source to 'header' instead of envelope.

I hope this helps!

I saw that but didn't think it pertained to this particular problem
Thank you very much for pointing it out. I have changed it to Header now and after restarting the pmgspamreport.service, I am no longer seeing those errors. I will check on it again once it runs its scheduled tasks.

UPDATE:

Unfortunately even after updating the DKIM settings to use "Header" instead of "Envelope" did not work. I am still getting the DKIM signing error:

mailgate:~# journalctl -u pmgspamreport.service -n 100
Feb 20 17:00:34 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''
Feb 20 17:00:35 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''
Feb 20 17:00:35 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''
Feb 20 17:00:35 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''
Feb 20 17:00:35 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''
Feb 20 17:00:35 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''
Feb 20 17:00:35 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''
Feb 20 17:00:35 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''
Feb 20 17:00:35 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''
Feb 20 17:00:36 mailgate pmgqm[1086939]: DKIM signing: no domain found in ''

In the interim I am simply going to schedule a cronjob to run pmgqm send as that works.
I ran it as pmgqm send --timespan yesterday --debug and I saw it send out all the reports correctly.