Gary Jarrel ha scritto: > yeah I have, and it works fine :( There are no specific restrictions for that. In fact we have some mailet using sockets to communicate with external services.
Maybe the problem is in the "closed source api" that you use to connect the remote server. Can you try connecting directly using java sockets to that port 80 from your mailet (without using the "closed source api") ? Stefano > On 9/6/07, Bernd Fondermann <[EMAIL PROTECTED]> wrote: >> Hi Gary, >> >> To narrow down your problem, did you try to get a plain connection from >> the mail server to the web server for example by issuing on the mail >> server's command line >> wget http://<webserver>:80/<resource> >> or >> telnet <webserver> 80 >> ? >> >> Bernd >> >> Gary Jarrel wrote: >>> Hi All! >>> >>> A quick questions - I've got a mailet which uses a closed source API >>> to connect to a remote server to notify users of mail coming in. The >>> connection is a simple http connection from the James server (inside >>> the mailet) to a remote server on port 80. >>> >>> All seems to function well in the test cases, and when I deploy the >>> web component of the application under tomcat - i.e. the code is able >>> to establish the connection and communicate with the remote server. >>> However when I deploy the james mailet with all the required jars, etc >>> - it always crashes out reporting that a connection to a remote server >>> can not be established. >>> >>> Is there perhaps a security setting of some sort which stops the >>> mailets from accessing the outside word or any other suggestions? >>> >>> Thank you! >>> >>> Gary --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
