Hi
according to jira http://issues.apache.org/jira/browse/JAMES-302 the bug is 
fixed in version 2.1.3 my question now is there a patch that i can run 
against version 2.2.0 to fix the bug , if not how i can get 2.1.3 version ??

thanks in advance for any help

Roger

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to