Comment 8 for bug 701976

> For this last problem, then, I recommend that, if we don't find the X-Launchpad-Original-To header in the proper place, we look in the body for it. If we find it in the body, we should silently ignore the problem, without an OOPS, perhaps merely logging that we are regarding it as spam. If we do *not* find it in the body, we should continue to generate an OOPS, because this caught a legitimate configuration error.

Gary, if I understand correctly, all incoming mail will get an x-l-original-to added before it's processed. This should happen for both spam and non-spam messages. If that header is missing, there is definitely a configuration problem.

Having the string "X-Launchpad-Original-To" in the body of the message isn't a reliable indication that the message is spam. It occurs in many of the messages about this bug.

I'm not sure how you can have an extra newline in the middle of rfc2822 headers, and unfortunately all the example files seem to have expired. If spam is being sent in a weird format that confuses our parser maybe we can detect that directly.

hth