So it's wasn't line breaks afterall.
It turned out that OpenSMTPD passes raw SMTP data lines to filters and
raw SMTP lines have leading dot characters escaped by another dot, so
.text became ..text. Feeding it to Rspamd like that made DKIM alignment
tests fail, because body hash came out wrong.
A pull request has been submitted with a fix.
This how seems to be a problem with Rspamd:
arc=reject (signature check failed: fail, {[1] = sig:google.com:reject});
Good luck,
Reio
On 13.10.2019 17:43, Reio Remma wrote:
Things seem to have gotten worse on Google Groups front though:
ARC-Authentication-Results: i=3;
orc.mrstuudio.ee;
dkim=pass header.d=googlegroups.com header.s=20161025 header.b=HBqGik0B;
dkim=pass header.d=gmail.com header.s=20161025 header.b=PGhHBIgC;
arc=reject (signature check failed: fail, {[1] =
sig:google.com:reject});
dmarc=pass (policy=none) header.from=gmail.com;
spf=pass (orc.mrstuudio.ee: domain ofhel...@googlegroups.com
designates 209.85.215.186 as permitted
sender)smtp.mailfrom=hel...@googlegroups.com
Authentication-Results: orc.mrstuudio.ee;
dkim=pass header.d=googlegroups.com header.s=20161025 header.b=HBqGik0B;
dkim=pass header.d=gmail.com header.s=20161025 header.b=PGhHBIgC;
dmarc=pass (policy=none) header.from=gmail.com;
spf=pass (orc.mrstuudio.ee: domain ofhel...@googlegroups.com
designates 209.85.215.186 as permitted
sender)smtp.mailfrom=hel...@googlegroups.com
---
ARC-Authentication-Results: i=3;
orc.mrstuudio.ee;
dkim=fail (body hash did not verify) header.d=googlegroups.com
header.s=20161025 header.b=Q/j34gd1;
dkim=fail (body hash did not verify) header.d=gmail.com
header.s=20161025 header.b=pPw7LbVC;
spf=pass (orc.mrstuudio.ee: domain ofhel...@googlegroups.com
designates 209.85.222.184 as permitted
sender)smtp.mailfrom=hel...@googlegroups.com;
arc=reject (signature check failed: fail, {[1] = sig:google.com:reject})
Authentication-Results: orc.mrstuudio.ee;
dkim=fail (body hash did not verify) header.d=googlegroups.com
header.s=20161025 header.b=Q/j34gd1;
dkim=fail (body hash did not verify) header.d=gmail.com
header.s=20161025 header.b=pPw7LbVC;
dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com
(policy=none);
spf=pass (orc.mrstuudio.ee: domain ofhel...@googlegroups.com
designates 209.85.222.184 as permitted
sender)smtp.mailfrom=hel...@googlegroups.com
On 13.10.2019 16:37, Reio Remma wrote:
So far there's a marked improvement!
Waiting for a FB notification now - asked the wife to message me. :P
Authentication-Results: host.domain.com;
dkim=fail (body hash did not verify) header.d=gmail.com
header.s=20161025 header.b=SLB9Imr3;
dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com
(policy=none);
spf=pass (host.domain.com: domain ofm...@opensmtpd.org designates
45.76.46.201 as permitted sender)smtp.mailfrom=misc@opensmtpd.org
Authentication-Results: host.domain.com;
dkim=pass header.d=gmail.com header.s=20161025 header.b=ot9QqpYS;
dmarc=pass (policy=none) header.from=gmail.com;
spf=pass (host.domain.com: domain ofm...@opensmtpd.org designates
45.76.46.201 as permitted sender)smtp.mailfrom=misc@opensmtpd.org
---
Authentication-Results: host.domain.com;
dkim=fail (body hash did not verify) header.d=gmail.com
header.s=20161025 header.b=SLB9Imr3;
dmarc=pass (policy=none) header.from=gmail.com;
spf=pass (host.domain.com: domain ofgil...@gmail.com designates
209.85.128.45 as permitted sender)smtp.mailfrom=gil...@gmail.com
Authentication-Results: host.domain.com;
dkim=pass header.d=gmail.com header.s=20161025 header.b=ot9QqpYS;
dmarc=pass (policy=none) header.from=gmail.com;
spf=pass (host.domain.com: domain ofgil...@gmail.com designates
209.85.128.42 as permitted sender)smtp.mailfrom=gil...@gmail.com
On 13.10.2019 16:27, Reio Remma wrote:
Just restarted my daemon with the modified filter. :)
Will have to get someone message me at FB now.
On 13.10.2019 16:22, Gilles Chehade wrote:
Very likely yes, can you give it a try ?
On Sun, Oct 13, 2019, 15:15 Reio Remma > wrote:
On 13.10.2019 16:09, Reio Remma wrote:
On 13.10.2019 16:05, Gilles Chehade wrote:
I don't think that is the issue, it is probably the
filter-rspamd reconstruction of the message that is incorrect.
I was thinking along the same lines, but I'm not sure how
OpenSMTPD splits strings before passing them to the filter.
Can the filter then extract "leftover" line endings for
incoming strings and make decision based on that when joining
the strings before Rspamd?
Do you experience the same yourself?
strings.NewReader(strings.Join(s.tx.message, "\n"))
Wonder if we should use \r\n here?
Reio
On Sun, Oct 13,
