Thanks, Peter and Chris, for your help. I finally figured out what it
was...I had two conflicting copies of javax.mail installed. I had it
included in my pom.xml, and I had a Debian package installed
libgnumail-java. (I'm on a Debian server). For some reason, the two
didn't play nice together.
Sounds like an issue with the server configuration, I suggest you get
the logs to work first, then you might get a better idea of why the mail
isn't working... if it works in development then chances are you are
missing a host entry or something small like that, which will pop up in
the logs.
I thought about that, but wouldn't tcpdump show the packets, even if
they were being blocked? I was looking for all packets with port 25.
Also, my code that's using javax.mail to send a message is looking for
exceptions, and writing to the log file if that happens. I haven't seen
anything in the
Hi Andy,
If exceptions aren't being thrown from the services/pages that use the
mail classes, then the javax.mail is present. Is it possible that your
server (or it's network) is blocking outbound smtp connections?
chris
Andy Huhn wrote:
> Hello,
>
> In my dev environment (running jetty6 from in
Hello,
In my dev environment (running jetty6 from inside Eclipse), I'm able to
use javax.mail classes and successfully connect to my mail server to
send a message. But when I migrate the code to my production server
(jetty6 also), everything seems to work correctly except that the app
doesn't con
