Dipl-Inform. Frank Gadegast:
On 27.07.21 14:18, David Bürgin wrote:
Dipl-Inform. Frank Gadegast:
Seems to be, that spamass-milter simply strippes out any X-Spam* header lines,
not caring, if the own call to spamd sets them, hm.
Im really not getting, why spamass-milter should strip X-Spam-lines of the
header AFTER SA was running. If Im right, SA is stripping them of anyway,
before running or modifying anything ...
Anybody an idea how to get arround this ?
There is an alternative milter (which I maintain) that adds
all X-Spam-* headers received from spamd.
https://crates.io/crates/spamassassin-milter
Looks like your milter needs to fork a spamc, wich then talks to the spamd.
This will start lots of spamc processes and is not recommened.
Would then not be any different to call spamc dirctly f.e. via procmail.
You should rewrite your milter to talk directly to the spamd via socket or port.
Yes, it communicates using spamc, just like spamass-milter.
I have been told that it has been working fine in a somewhat larger
deployment. I didn’t mean to derail the thread so will leave it at that.
Ciao,
David
