Comment 2 for bug 701976

Example OOPS is from spam. A reasonable behavior would be to ignore it somehow, if we can come up with a reasonable way to recognize the situation.

The OOPS tool reports 19917 OOPSes like this in the past week. However, the messages vary widely. Here's another OOPS that is in the same group:

<oops-message-87>: Found 2 competing templates with translation domain 'messages': "openerp-messages in OpenObject Web Client trunk"; "viewcalendar-messages in OpenObject Web Client trunk".
path: /srv/staging.launchpad.net/staging/launchpad/cronscripts/rosetta-approve-imports.py
script_name: translations-import-queue-gardener

That appears to be from another script entirely.

Here's another one I found, with the same signature as the one originally reported:

<oops-message-6>: No X-Launchpad-Original-To header was present in email: http://launchpadlibrarian.net/62145638/80d1f7fc-1ebd-11e0-bde1-001e0bc3957e.txt
path: /srv/launchpad.net/production/launchpad/cronscripts/process-mail.py
script_name: process-mail

That's another piece of spam.

We probably should go log trolling to make sure that all of a reasonable sample of the recorded "No X-Launchpad-Original-To header was present in email" errors are spam. If they are, the goal of this bug is to simply make the situation not cause an OOPS. We might also want to check with the LOSAs to make sure that this is not indicative of some spam hole that we need to close. Finally, we should file a bug with the OOPS tool to divide up these OOPSes better