Noel J. Bergman wrote:
+1. After reviewing the code with Noel's direction, the bug is pretty straight-forward and we should release with the fix ASAP.Guys,I just found and fixed a serious defect today. The failure scenario was this: - transport.connect() throws a MessagingException - failMessage returns false, so continue to loop - there are no additional MX records - the while loop exits - the return statement at the end of delivery returns true - the if (deliver(...)) statement in run() deletes the message This bug exists in all released versions of v2.1.x. I reproduced this situation quite readily today prior to fixing the bug. I have posted v2.1.2a2 for testing. PLEASE TEST IT ASAP, vote to release unless you find a problem.
--
Serge Knystautas
President
Lokitech >> software . strategy . design >> http://www.lokitech.com/
p. 1.301.656.5501
e. [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
