On Sun, Dec 13, 2015 at 04:48:10PM +0300, Alexander Inyukhin wrote: > "spamc --headers" should not alter Content-Type header. > > When spamd is confugured to add report to messages > the resulting Content-Type is something like > > Content-Type: multipart/mixed; boundary="----------=_566D759A.5F0A72E0" > > Replacing this header in the original message breaks it, especially > when the message is multipart itself, since the boundary is changed.
This is the documented behavior. From the spamc(1) man page, when
describing the --headers option:
Note that this only makes sense if you are using "report_safe 0" in the
scanning
configuration on the remote end; with "report_safe 1", it is likely to
result in corrupt
messages.
The default value of "report_safe" in spamd is 1, so you will need to
modify that setting if you want "spamc --headers" to work correctly.
noah
signature.asc
Description: Digital signature
