SMTP Transport: SendFailedException

Question

Currently, our company is in the implementation/testing stage of
several servlets which process sales from internet customers.
One of a servlet's functions is to send a "confirmation / thank you" email
to the customer upon successful credit card verification of purchase.
Our "TransportMail" class ends with an exception after successfully (seemingly,
because "opened" ConnectionEvent is fired) opening a connection to the SMTP
server.
Then, execution is terminated with a SendFailedException. The output of a
test (below the code snippet) shows the result of a System.out of the MimeMessage's methods.
A nested exception states that it could not connect. A process called TCPView shows that the
connection was successful and timed-out on the send(msg).
The test is run from a DOS Prompt.
What's wrong? Why won't the message send?
Thanx much in advance for any suggestions or solutions.
All message values are set properly per the API specs. The message is sent via the following snippet:
Transport tr = session.getTransport("smtp");
tr.addTransportListener(new TransportAdapter() {
public void messageDelivered(TransportEvent e) {System.out.println("\nmessageDelivered: " + e.toString());}
public void messageNotDelivered(TransportEvent e) {System.out.println("\nmessageNotDelivered: " +                                 e.toString());}
public void messagePartiallyDelivered(TransportEvent e) {System.out.println("\nmessagePartiallyDelivered: " +                                      e.toString());}
tr.addConnectionListener(new ConnectionAdapter() {
     public void closed(ConnectionEvent e) {System.out.println("\nclosed: " + e.toString());}
     public void disconnected(ConnectionEvent e) {System.out.println("\ndisconnected: " + e.toString());}
     public void opened(ConnectionEvent e) {System.out.println("\nopened: " + e.toString());}
tr.connect(     "<smtp server>",
          -1,
          "<user id>",
          "<password">     );
tr.send(msg);          // executes msg.saveChanges() prior to send (per API specs)
tr.close();          
C:\TEMP\test>java testSendMail [email protected] BMSCreditMgr
fromaddr= [email protected]
toaddr= [email protected]
msg.getFrom= [email protected]
msg.getAllRecipients= [email protected]
msg.getSubject= Thank you for ordering BMSCreditMgr !
msg.getSentDate= Wed Jan 21 14:37:14 PST 2004
thisMessage= Business Management Systems, Inc. is developing many more
software packages that will enable the individual investor to
manage their investments and make money with their hard-earned dollars.
It is hoped that you find BMSCreditMgr to be a very useful product and that
you make money with it.
Again, thank you very much for your purchase.
opened: javax.mail.event.ConnectionEvent[source=smtp://bmstahoe%[email protected]]
SendFailedException :javax.mail.SendFailedException: Sending failed;
nested exception is:
class javax.mail.MessagingException: 530 authentication required - for help go to http://help.yahoo.com/help/us/sbc/dsl/mail/pop/pop-11.html
C:\TEMP\test>

Answer 1

Your conclusion seems to be correct, however, I send many emails (10-20) daily via either Netscape or IE6 with the exact same SMTP server, UserID, and password. Also, other office personnel send emails via Netscape or IE through our LAN using the exact same server, uid, and password.
The code snippet of the TransportMail class (see original) uses the exact same server, uid, and password. A freeware program called TCPView that runs as a process during testing shows that the object connects to port 25 of the server (as expected) and the 'opened' ConnectionEvent is fired (see output in original). The SendMailException has a nested exception saying that it can't connect or sometimes authentication required followed by an additional nested exception: java.net.ConnectException: Connection timed out: connect.
So, if the 'opened' ConnectionEvent is fired and a ConnectException indicates a timeout for the connection, such conditions seem to indicate that a connection was made. The MessagingException stating that authentication is required no longer occurs since the password parm is passed via tr.connect.
I was thinking that maybe the server is possibly attempting to prompt for password instead of taking the password from the program. That might explain why the connection holds for about 20 secs before timeout. I could test that theory with a dialog.