Commons Email
  1. Commons Email
  2. EMAIL-91

Incorrect SMTP Port number shown in error message when an email fails to send due to a blocked port and SSL is used.


    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.0, 1.1, 1.2
    • Fix Version/s: 1.3
    • Labels:
    • Environment:

      Windows XP, JRE 1.6.0_16, JavaMail 1.4.1, Commons Email 1.2 [latest from svn], jaf 1.1.1


      An incorrect error message is being returned from the email class when a message fails to send due to a blocked port and SSL is specified. Specificaly, the port number in the error message is incorrect; it will show the stmp port that is set on the object (normally 25), when it should be showing the port that was set in the session when the session was created [465 when SSL is used].

      This issue is only visible to the user if the email fails to send because the SSL port is blocked.

      The following code reproduces the issue:
      public void testErrorMessage(){
      HtmlEmail email = new HtmlEmail();

      { email.addTo(""); email.setSubject("Testing Apache Error message "); email.setFrom(""); email.setMsg("Sending through gmail"); email.setSSL(true); email.setHostName(""); email.send(); }

      catch (EmailException e)

      { e.printStackTrace(); }


      If port 465 is blocked, then you wil ge the following stacktrace:

      org.apache.commons.mail.EmailException: Sending the email to the following server failed :
      at org.apache.commons.mail.Email.sendMimeMessage(
      at org.apache.commons.mail.Email.send(
      at EmailTester.testErrorMessage(
      at EmailTester.main(
      Caused by: javax.mail.MessagingException: Could not connect to SMTP host:, port: 465;
      nested exception is: Connection refused: connect
      at com.sun.mail.smtp.SMTPTransport.openServer(
      at com.sun.mail.smtp.SMTPTransport.protocolConnect(
      at javax.mail.Service.connect(

      Note that the port is listed correctly in the inner exception, but it is incorrect in the topmost exception.

      I have fixed this issue in my sandbox, and will attach the patch to this issue.

      1. issue-91_patch.txt
        2 kB
        Kevin Lester
      2. issue-91a_patch.txt
        3 kB
        Siegfried Goeschl

        Issue Links


          No work has yet been logged on this issue.


            • Assignee:
              Siegfried Goeschl
              Kevin Lester
            • Votes:
              0 Vote for this issue
              0 Start watching this issue


              • Created:

                Time Tracking

                Original Estimate - 24h
                Remaining Estimate - 24h
                Time Spent - Not Specified
                Not Specified