Mike,
I'm no JAMES expert, but we had the same problem with James 2.2
(upgrading has been a challenge for us thus far), and though our
solution was less than elegant, it did work. This is what we did:
- create a new table like deadletter, and insert into it all mail
where repository_name = 'spam' AND error_message LIKE '%ordb%' and
that fell in between the dates that we had the problem.
- then set message_state = 'root', last_updated = NOW(),
repository_name = 'spool' so that james will reprocess the message is
if it were new and coming into the root processor the first time
- delete these messages from the deadletter table (using message_name
for joining)
- copy the contents of the new table into spool for reprocessing.
The quantity of mail this moved took james quite a while to churn
through, but at least it had the desired effect. Due to table
indexes, some of the selects could also be rather slow (depending on
the # of messages).
DK
On Apr 3, 2008, at 4:41 AM, Mike Robinson wrote:
Hi, I inherited a James instance that had been quietly doing it's
thing for some time, and I'd meant to getting around to
understanding it better one day, and it seems that day has come a
little earlier than I expected.
I got caught by the relays.ordb.org issue, and now I have a huge
amount of incorrectly tagged mail in my spam folder.
I would use the FromRepository Mailet, but I'm afraid my version of
James is 2.2, and FromRepository seems to my understanding to be a
2.3+ feature. Upgrading is not currently an option for us, due to
custom mailets that failed in tests against newer James versions.
We tried moving the contents of the spam folder into the spool for
reprocessing, but as they already had spam flags set, they all went
back to the spam folder.
The options we've come up with:
Add a DB spam repository, reprocess everything and then change the
spam flag via crafty SQLing and reprocess.
Write a script to open each message and resend it, starting it fresh
in the James processes.
Ask the James mailing list to see if someone more familiar with
James might have a better solution, or comments on our two main ideas.
I'm happy to give more information, but I don't really know what
would be relevant at this point.
m.
--
Mike Robinson
--
Senior Network Engineer
IT & Operations
Seagate Services
--
T 510.903.7302
F 510.903.7200
C 510.847.6576
--
[EMAIL PROTECTED]
http://services.seagate.com
6121 Hollis St Suite 2
Emeryville, CA 94608 USA
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
