Hi again,
correction on this. It happens also for "untagged" spam; the information
below is wrong. I made a mistake while testing.
This is strange - all i do for non-spam is adding a few X-headers in
filter_end.
I will have to set up a test installation and play around in order to figure
out what exactly is causing this.
any ideas where to look/what to test would be great. I do not have any
errors in any logs, which confuses me a little.
kind regards,
/Dan
Hi,
Thanks for the reply! The behaviour does not occur for messages not marked
as spam (passed through unmodified, the only difference is that a few
X-headers are added).
It seems to me, that it's the "building of the new message" that causes the
problem, somehow the curly braces being incorrectly parsed.... or?
Kind regards,
/Dan
Neat! You mentioned that the original attached email doesn't have the
issue. Does this behavior occur even for emails not marked as spam?
Regards,
KAM
_______________________________________________
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID. You may ignore it.
Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list [email protected]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
