Sorry, didn't know where else to ask.

Is PHP 8 now the minimum requirement?

If so, what is the last version to support PHP 7.3?

Thanks

Hello,

it would be awesome if rspamd could check for BIMI and add headers BIMI-Location and BIMI-Indicator.

BIMI RFC:

• https://www.ietf.org/archive/id/draft-blank-ietf-bimi-02.txt
• https://bimigroup.org/
  • Especially interesting: The Receivers Guidance for Implementing: https://bimigroup.org/supporting-documents/

Some other milters/MTAs already support this:

• https://github.com/fastmail/authentication_milter/blob/master/lib/Mail/Milter/Authentication/Handler/BIMI.pm
• https://halon.io/blog/adding-bimi-to-your-mailbox-service-to-improve-security-and-user-experience/
  • https://github.com/halon-extras/bimi

Emails having a valid BIMI and a validated VMC (which costs around 1000$) might indicate a serious sender who paid for it, and has a logo which is trademarked. Not many spammers will pay for it and get a certificate assigned.

Hi,

I'm using rspamd 3.1-1~bionic.

I had a cronjob each day to send DMARC reports, like this:

17 9 * * * /usr/bin/rspamadm dmarc_report

@RealSebFox and I were confiused because sometimes we received DMARC-reports from each other, sometimes not. It looked like not all DMARC reports were sent, but we were not able to find out why.

After hours of investigation and checking Redis-contents (SMEMBERS dmarc_idx;20220201, SMEMBERS dmarc_idx;20220202) we found the solution inside the "--help":

$ rspamadm dmarc_report --help
Usage: rspamadm dmarc_report [-h] [-c <cfg>] [-v] [-n] [-b <number>]
       [<YYYYMMDD>] ...

Dmarc reports sending tool

Arguments:
   date                       Date to process (today by default)

Options:
   -h, --help                 Show this help message and exit.
         -c <cfg>,            Path to config file (default: /etc/rspamd/rspamd.conf)
   --config <cfg>
   -v, --verbose              Enable dmarc specific logging
   -n, --no-opt               Do not reset reporting data/send reports
             -b <number>,     Send reports in batches up to <batch-size> messages (default: 10)
   --batch-size <number>

Date to process (today by default)

If you just call rspamadm dmarc_report in your cronjob, it sends the reports for the current day, which means if you run it at 09:17, it only sends reports for mails between 00:00 and 09:17...

We both were expecting that by default it sends the reports of the day before (that makes the most sense in a cronjob, then you cover the whole day).

With the current behaviour you have 2 possibilities:

1. Run the Cronjob at 23:59 to cover the whole day... But it's ugly if all people in this world send emails during one minute, It should be spread over the whole day (everyone should choose a random time), so the recipients don't have problems with their "receive-rate-limit".
2. Run the cronjob with the date of yesterday as parameter, like this: 17 2 * * * /usr/bin/rspamadm dmarc_report -v $(date --date yesterday "+\%Y\%m\%d") >> /tmp/dmarc_report.log 2>&1

This strange behaviour of rspamadm dmarc_report explains the problem in Issue #4053 .

I guess most people who have a cronjob for sending rspamd DMARC reports don't know about this behaviour, and only send for a few hours per day (because they just run rspamadm dmarc_report without a date parameter)

If the default date ("today") will not be changed, then I would definitely recommend to add this important information to the documentation, and even provide an example of a correct cronjob with the date of yesterday (see above).

Currently in the documentation it says:

From Rspamd 3.0 you should use "rspamadm dmarc_report" tool called manually (e.g. via cron or systemd timers) to send reports, this should be done either daily or hourly depending on traffic.

Kind regards Michael

Hi,

I'm using rspamd 3.1-1~bionic.

I had a cronjob each day to send DMARC reports, like this:

17 9 * * * /usr/bin/rspamadm dmarc_report

@RealSebFox and I were confiused because sometimes we received DMARC-reports from each other, sometimes not. It looked like not all DMARC reports were sent, but we were not able to find out why.

After hours of investigation and checking Redis-contents (SMEMBERS dmarc_idx;20220201, SMEMBERS dmarc_idx;20220202) we found the solution inside the "--help":

$ rspamadm dmarc_report --help
Usage: rspamadm dmarc_report [-h] [-c <cfg>] [-v] [-n] [-b <number>]
       [<YYYYMMDD>] ...

Dmarc reports sending tool

Arguments:
   date                       Date to process (today by default)

Options:
   -h, --help                 Show this help message and exit.
         -c <cfg>,            Path to config file (default: /etc/rspamd/rspamd.conf)
   --config <cfg>
   -v, --verbose              Enable dmarc specific logging
   -n, --no-opt               Do not reset reporting data/send reports
             -b <number>,     Send reports in batches up to <batch-size> messages (default: 10)
   --batch-size <number>

Date to process (today by default)

If you just call rspamadm dmarc_report in your cronjob, it sends the reports for the current day, which means if you run it at 09:17, it only sends reports for mails between 00:00 and 09:17...

We both were expecting that by default it sends the reports of the day before (that makes the most sense in a cronjob, then you cover the whole day).

With the current behaviour you have 2 possibilities:

1. Run the Cronjob at 23:59 to cover the whole day... But it's ugly if all people in this world send emails during one minute, It should be spread over the whole day (everyone should choose a random time), so the recipients don't have problems with their "receive-rate-limit".
2. Run the cronjob with the date of yesterday as parameter, like this: 17 2 * * * /usr/bin/rspamadm dmarc_report -v $(date --date yesterday "+\%Y\%m\%d") >> /tmp/dmarc_report.log 2>&1

This strange behaviour of rspamadm dmarc_report explains the problem in Issue #4053 .

I guess most people who have a cronjob for sending rspamd DMARC reports don't know about this behaviour, and only send for a few hours per day (because they just run rspamadm dmarc_report without a date parameter)

If the default date ("today") will not be changed, then I would definitely recommend to add this important information to the documentation, and even provide an example of a correct cronjob with the date of yesterday (see above).

Currently in the documentation it says:

From Rspamd 3.0 you should use "rspamadm dmarc_report" tool called manually (e.g. via cron or systemd timers) to send reports, this should be done either daily or hourly depending on traffic.

Kind regards Michael

Hi

Have you planed that your tool can analyze the report from mta-sts (TLSRPTv1) too?

Or do you know another software for this?

Thank you for help

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Read about bug reporting in general: https://rspamd.com/doc/faq.html#how-to-report-bugs-found-in-rspamd
  • Enabled relevant debugging logs: https://rspamd.com/doc/faq.html#how-to-debug-some-module-in-rspamd
  • Checked the FAQs about Core files in case of fatal crash: https://rspamd.com/doc/faq.html#how-to-figure-out-why-rspamd-process-crashed
  • Tried ASAN package and obtained the ASAN report (if possible): https://rspamd.com/doc/faq.html#asan-builds
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=%E2%9C%93&q=is%3Aissue+user%3Arspamd
  • Checked that there is not already an experimental package or master branch

Describe the bug I've enabled dmarc reporting on my mailcow instance, and I've noticed its playing DMARC ping pong, where my server and another email server is sending dmarc reports back and forth everyday even though no actual emails are being sent. So their server is reporting back my dmarc deliveries and rspamd is doing the same to them. Unless I do something this will go on forever, until one side does something to stop it.

I personally believe this is a bug, as I can't see why you would want this ping pong of dmarc reporting to be happening.

Steps to Reproduce

1. Setup mailcow or your own rspamd environment.
2. Enable DMARC Reporting LINK
3. Send an email to [email protected] which should start the ping pong.

Expected behavior rspamd to only report non Report Domain emails, or some form of excluded emails list on the reporting config.

Versions

Docker Image: mailcow/rspamd:1.79 Rspamd daemon version 3.1 Debian 11 VM running on Proxmox 7.1

Additional Information

my reporting config

reporting {
    enabled = true;
    email = '[email protected]';
    domain = 'mydomain.com';
    org_name = 'myorg';
    helo = 'rspamd';
    smtp = 'postfix';
    smtp_port = 25;
    from_name = 'myorg DMARC Report';
    msgid_from = 'rspamd.mail.mydomain.com';
    max_entries = 2k;
    keys_expire = 2d;
}

my rua address is [email protected]

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Read about bug reporting in general: https://rspamd.com/doc/faq.html#how-to-report-bugs-found-in-rspamd
  • Enabled relevant debugging logs: https://rspamd.com/doc/faq.html#how-to-debug-some-module-in-rspamd
  • Checked the FAQs about Core files in case of fatal crash: https://rspamd.com/doc/faq.html#how-to-figure-out-why-rspamd-process-crashed
  • Tried ASAN package and obtained the ASAN report (if possible): https://rspamd.com/doc/faq.html#asan-builds
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=%E2%9C%93&q=is%3Aissue+user%3Arspamd
  • Checked that there is not already an experimental package or master branch

Describe the bug I've enabled dmarc reporting on my mailcow instance, and I've noticed its playing DMARC ping pong, where my server and another email server is sending dmarc reports back and forth everyday even though no actual emails are being sent. So their server is reporting back my dmarc deliveries and rspamd is doing the same to them. Unless I do something this will go on forever, until one side does something to stop it.

I personally believe this is a bug, as I can't see why you would want this ping pong of dmarc reporting to be happening.

Steps to Reproduce

1. Setup mailcow or your own rspamd environment.
2. Enable DMARC Reporting LINK
3. Send an email to [email protected] which should start the ping pong.

Expected behavior rspamd to only report non Report Domain emails, or some form of excluded emails list on the reporting config.

Versions

Docker Image: mailcow/rspamd:1.79 Rspamd daemon version 3.1 Debian 11 VM running on Proxmox 7.1

Additional Information

my reporting config

reporting {
    enabled = true;
    email = '[email protected]';
    domain = 'mydomain.com';
    org_name = 'myorg';
    helo = 'rspamd';
    smtp = 'postfix';
    smtp_port = 25;
    from_name = 'myorg DMARC Report';
    msgid_from = 'rspamd.mail.mydomain.com';
    max_entries = 2k;
    keys_expire = 2d;
}

my rua address is [email protected]