(I'm sending these through JAMES... the telling sign is the .. at the
end of the message :)
More seriously, I had to upgrade the mail.jar to the latest (the version
in place was 1.1.1 I think, and 1.1.3 was released with several bug
fixes). The most notable problem was that I couldn't deliver to
cgi.clearink.com (list.working-dogs.com) because of how it or the client
handle NOOP commands from JavaMail. Anyway, put JavaMail 1.1.3 in
place, and it works. As I replaced mail.jar, I also renamed it to
mail_1_1_3.jar to follow the xerces.jar convention (which I think is
good). The DNS code also has minor fixes which seem non-critical, and
I'm not sure about activation.jar. Xerces is now at 1.1.1 (we're using
1.0.1)... can we upgrade this, or would this require too many changes
just now?
Anyway, getting closer. If someone else doesn't know what's going on,
I'll hopefully find the problem before too long. I'm wondering if it's
the CharTerminatedInputStream as the problem seems to have existed since
that code was introduced many months ago.
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/>
Problems?: [EMAIL PROTECTED]
