Kevin Locke:
> /^X-Spam-Status: Yes.*tests=(.*) autolearn=/ REJECT Message identified as
> spam by SpamAssassin using the following tests: $1
>
> This works great, except that the message is chopped off at the first
> line break in the X-Spam-Status header.
This header_checks pattern:
/^Received: (.*)/ reject $1
Results in this SMTP reply:
550 5.7.1 from host.example.com (host.example.com [192.168.1.1])
by host.example.com (Postfix) with ESMTP id 3S3xk131J5znjb8
for <wietse@localhost>; Wed, 21 Sep 2011 19:19:29 -0400 (EDT)
Multi-line reject messages have never been supported in Postfix,
and I don't expect that to change (that would require subtle changes
to the SMTP server and to the bounce message formatter among other
things).
What happens in the above example is the result of an omission to
filter out newline characters. In the context of web applications,
I believe that this would be called a line-splitting bug.
Wietse
