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. 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? Tim _______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
