Comment 6 for bug 266450

Originator: NO

I have looked further at the shunt queue entry
1167220351.925714+67431f92e260e4da420214c9a343ace677ca1acd.pck. Here's what
I see.

This message was a password reminder, originally generated by mailman on
May 1, 2006. It was addressed to a user whose preferred language appears to
be Korean as it is 'Content-Type: text/plain, charset="euc-kr"' with
'Subject: =?euc-kr?q?uni-koeln=2Ede_mailing_list_memberships_reminder?='.

Apparently there was some error at that time which caused the message to
be shunted. I am a bit confused about what happened next because the time
stamp on the queue entry and the received_time in the message's metadata
are 1167220351.925714 which is 11:52:31 Dec 27, 2006 +0000.

However, the message metadata says the message was originally in the 'in'
queue, so I think it must have been unshunted to the 'in' queue where it
couldn't be properly processed, causing it to be shunted again in December,
2006.

The question now is what is causing these messages to be reprocessed at
this point, and why would a message that threw an exception in trying to
flatten the message in SpamDetect be shunted with a 14+ month old time
stamp?

In any case, I think the current error with this particular message is due
to it's being unshunted to the wrong queue.