On 02.05.24 12:53, Tim Coote via Postfix-users wrote:
I think that I’ve now fixed this in my domain, so I thought I’d just note
the route to finding it, more as a comment on the complexity of working
out what’s going on.
After making a simple robot to send emails with long headers and
demonstrating how they broke in my production environment, I rebuilt that
env on a Vagrant box. It worked properly (ie it didn’t replace “,” with
“,<cr><lf><space>”) until I’d added in the old spambayes filter that I’d
been ‘using’.
Removing Spambayes fixed the issue. Dunno whether this will have an effect
on the amount of spam, but I suspect that it hadn’t done anything useful
for some time.
This looks like someone is signing headers they should not sign. Can you
look at that?
Is fo, you can also check DKIM signature before you sign or before you check
for spam.
What would have helped - and I’ve no idea how feasible this is - would be
some tooling to pull out different versions of the message as they flow
through the queues.
Interesting how long latent bugs can lie around, isn’t it?
--
Matus UHLAR - fantomas, [email protected] ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Honk if you love peace and quiet.
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
