Appreciate the quick response. My reading of the response is that unless I move to 2.2.0RC2, I can't really use the FromRepository or MailAttribute
I have been using AddHeaders and then manually checking the msgs in the outbound queue but the header is not showing up in the msg. I'll reverify what I am doing. (That was the initial intent w/a mailet configured in the outbound queue). Forgot about DEBUG though. Thanx. James is deployed as part of the ASP service that we provide and I am a bit timid about putting Release Candidates in production. ----- Original Message ----- From: "Noel J. Bergman" <[EMAIL PROTECTED]> To: "James Users List" <[EMAIL PROTECTED]> Sent: Sunday, April 25, 2004 3:57 PM Subject: RE: reprocessing messages > > James - 2.1.2 > > You really should update. > > > is it possible to modify the message by attaching a > > known extension field to it. > > If you were running 2.2.0RC2, you could use a Mail Attribute, which does not > effect the message content at all. In 2.1.2, you could use AddHeader and > check for the presence of the header. > > > James doesn't seem to send the msg back to the inbound queue > > even though the domains understood by James are part of the > > message (how the message originally came to James) > > Always turn on DEBUG for the spool manager if you are having issues in how > messages are directed through the pipeline. > > > What I would really like to do is file the messages under a known > > JAMES user e.g. 'UNFILED' and then reprocess them using another > > mailet thus avoiding the outbound queue completely. > > See FromRepository in James 2.2.0RC2. > > --- Noel > > > --------------------------------------------------------------------- > 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]
