Sure it can be done, although this could be done everywhere, simply changing in AbstractRedirect.getSpecialAddress:
if(addressString.compareTo("unaltered") == 0) { specialAddress = SpecialAddress.UNALTERED; } to if(addressString.compareTo("unaltered") == 0) { specialAddress = null; } But at this point it would break in Redirect.getTo(Mail) the fact that if <to> is not coded, means set it as the <recipient> value (this was the old behaviour that we must maintain for compatibility), while <to>unaltered</to> means leave it as it was before, even if we set <recipients> to something else. I think that we should stress even more in the docs the adopted convention that not coding anything means null that means *no change*. Vincenzo > -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED] > Sent: martedi 24 giugno 2003 0.24 > To: James Developers List > Subject: RE: subject prefix mailet or unaltered recipients in Redirect > > > > In the 2.2.0a7 Redirect, not coding any "recipient" parameter > > means keeping it unaltered. > > I was just going to point that out, having noticed it in the > comments. But > for ease of use, and symmetry, perhaps we should allow an explicit > "unaltered", too? We already have it as a recognized special address. > > --- 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]