inetlib/javamail logging/debug changes

Hi,

I have finally overhauled inetlib to get rid of the proprietary Logger
implementation and use java.util.logging exclusively. This is good news
for inetlib users, but slightly less good news for javamail users, since
javamail has a very simplistic view of logging which doesn't fit into
the model employed by java.util.logging.

For the moment therefore, I have made javamail use java.util.logging and
the Session.setDebugOut and Session.getDebugOut methods do nothing and
return null, respectively.

Is this going to cause problems? An alternative would be to use the
simplistic javamail xxxDebugOut model just for javamail (i.e. just the
output of the Session constructor), and java.util.logging for everything
else. What do people think? Any other ideas?
-- 
Chris Burdess