Long delay receiving Recovered messages

[Tim Thompson]

When Recovering several mis-categorized messages from the spamtrap, they re-appeared in the "Sort Messages" page. After changing them from spam to not spam and clicking on the "Process" button, nothing happened. Several minutes later - still nothing and the worry starts to set in. Many, many minutes later, once you've forgotten about it, they might show up. (I'm still waiting for the latest batch) Why the really long delay?

-Tim

[Eric S. Johansson (esjh)]

would you please look at the headers for a couple of the long-delayed messages and attach the complete headers to the bug report. At the very least, I need to know the message ID and a twopenny blue ID so I can track a message through the system.

---eric

[Tim Thompson (tbt)]

Here is the header from one long-delayed message:

Return-Path: <email address hidden>
X-Original-To: <email address hidden>
Delivered-To: <email address hidden>
Received: from ycrdi.com (relay.ycrdi.com [192.168.9.2])
 by po.ycrdi.com (Postfix) with ESMTP id 9621FE1C060
 for <email address hidden>; Fri, 26 Oct 2007 12:30:42 -0400 (EDT)
Received: from relay.ycrdi.com (localhost [127.0.0.1])
 by ycrdi.com (Postfix) with ESMTP id 7210FD31188
 for <email address hidden>; Fri, 26 Oct 2007 12:30:43 -0400 (EDT)
X-Mailbox-Line: From nobody Mon Oct 22 15:34:14 2007
Received: from relay.ycrdi.com (localhost [127.0.0.1])
 by relay.ycrdi.com (Postfix) with ESMTP id 73253D310C1
 for <email address hidden>; Mon, 22 Oct 2007 15:34:14 -0400 (EDT)
Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [63.240.77.83])
 by relay.ycrdi.com (Postfix) with ESMTP
 for <email address hidden>; Mon, 22 Oct 2007 15:34:14 -0400 (EDT)
Received: from smailcenter60.comcast.net ([204.127.205.160])
          by comcast.net (sccrmhc13) with SMTP
          id <2007102219341301300942ime>; Mon, 22 Oct 2007 19:34:13 +0000
Received: from [207.190.198.130] by smailcenter60.comcast.net;
 Mon, 22 Oct 2007 19:34:12 +0000
From: <email address hidden>
To: Tim Thompson <email address hidden>, <email address hidden>
Subject: test
Date: Mon, 22 Oct 2007 19:34:12 +0000
Message-Id: <102220071934<email address hidden>>
X-Mailer: AT&T Message Center Version 1 (Oct 4 2006)
X-Authenticated-Sender: dGltYW5hQGNvbWNhc3QubmV0
X-Two-Penny-Blue: spamtrap_ID; 74dd22a351379d04
X-Two-Penny-Blue: recipient; <email address hidden>
X-Two-Penny-Blue: tpblue_ID; tbt
X-Two-Penny-Blue: passed filter; user released
X-Two-Penny-Blue: dumpster injection state; None
X-Two-Penny-Blue: originator; <email address hidden>
X-Two-Penny-Blue: xforward; 63.240.77.83
X-Crm114-score: 23.0413
X-Priority: 4

[Eric S. Johansson (esjh)]

working hypothesis is the delay comes from time it takes to process messages on the training queue. If this is correct, the two solutions are released "good" messages to the end-user at the same time as injecting the message on the training queue. The second option is optimizing the queue to pull "good" messages off first for training.