Announcement

Collapse
No announcement yet.

Error sending Mail from 3.2.1 since updating from 2.2.3

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Error sending Mail from 3.2.1 since updating from 2.2.3

    Dear people,
    one of our clients (not all) has the following problem:

    Some emails that should be sent from Mirth to an internal (not localhost) email server are being rejected/not sent.
    Most of these errors are 'transient' meaning: when our channel retries sending the email it is sent without a problem.

    There is ONE email address that keeps on errorring.

    When we change the addres to something else (on eour our addresses) the email goes through without a hitch.
    When we change the address to someone else (a collegue of the original recipient) the email errors, consistently.

    When we send email via the same emailserver, but from an email client (like outlook), the mail is sent normally.

    I have found an issue (3134) that look a bit like our problem, but with some differences.
    (see also topic:9976)

    our error:
    SMTP Sender error
    ERROR MESSAGE: Error sending email message
    org.apache.commons.mail.EmailException: Sending the email to the following server failed : 10.94.253.124:25
    at org.apache.commons.mail.Email.sendMimeMessage(Emai l.java:1401)
    at org.apache.commons.mail.Email.send(Email.java:1428 )
    at com.mirth.connect.connectors.smtp.SmtpDispatcher.s end(SmtpDispatcher.java:241)
    at com.mirth.connect.donkey.server.channel.Destinatio nConnector.handleSend(DestinationConnector.java:74 7)
    at com.mirth.connect.donkey.server.channel.Destinatio nConnector.process(DestinationConnector.java:445)
    at com.mirth.connect.donkey.server.channel.Destinatio nChain.call(DestinationChain.java:155)
    at com.mirth.connect.donkey.server.channel.Channel.pr ocess(Channel.java:1656)
    at com.mirth.connect.donkey.server.channel.Channel.di spatchRawMessage(Channel.java:1155)
    at com.mirth.connect.donkey.server.channel.SourceConn ector.dispatchRawMessage(SourceConnector.java:191)
    at com.mirth.connect.donkey.server.channel.SourceConn ector.dispatchRawMessage(SourceConnector.java:169)
    at com.mirth.connect.connectors.jdbc.DatabaseReceiver .processRecord(DatabaseReceiver.java:200)
    at com.mirth.connect.connectors.jdbc.DatabaseReceiver .processResultSet(DatabaseReceiver.java:160)
    at com.mirth.connect.connectors.jdbc.DatabaseReceiver .poll(DatabaseReceiver.java:117)
    at com.mirth.connect.donkey.server.channel.PollConnec tor$PollConnectorTask.run(PollConnector.java:131)
    at java.util.TimerThread.mainLoop(Unknown Source)
    at java.util.TimerThread.run(Unknown Source)
    Caused by: javax.mail.MessagingException: Exception reading response;
    nested exception is:
    java.net.SocketTimeoutException: Read timed out
    at com.sun.mail.smtp.SMTPTransport.readServerResponse (SMTPTransport.java:2204)
    at com.sun.mail.smtp.SMTPTransport.issueSendCommand(S MTPTransport.java:2089)
    at com.sun.mail.smtp.SMTPTransport.finishData(SMTPTra nsport.java:1889)
    at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTr ansport.java:1120)
    at javax.mail.Transport.send0(Transport.java:254)
    at javax.mail.Transport.send(Transport.java:124)
    at org.apache.commons.mail.Email.sendMimeMessage(Emai l.java:1391)
    ... 15 more
    Caused by: java.net.SocketTimeoutException: Read timed out
    at java.net.SocketInputStream.socketRead0(Native Method)
    at java.net.SocketInputStream.socketRead(Unknown Source)
    at java.net.SocketInputStream.read(Unknown Source)
    at java.net.SocketInputStream.read(Unknown Source)
    at com.sun.mail.util.TraceInputStream.read(TraceInput Stream.java:124)
    at java.io.BufferedInputStream.fill(Unknown Source)
    at java.io.BufferedInputStream.read(Unknown Source)
    at com.sun.mail.util.LineInputStream.readLine(LineInp utStream.java:89)
    at com.sun.mail.smtp.SMTPTransport.readServerResponse (SMTPTransport.java:2184)
    ... 21 more


    If someone can help, please...
    If more data is needed, just ask (but please explain how to get at the data)

    Thanks,
    Jurjan

  • #2
    Unfortunately this seem sto stump the experts, seeing as there are quite a few views, but no answers / suggestions.

    Looking through the forum I seem to find quite a few people having this issue (probably caused by using a new JavaMailversion), but no solution / workaround.
    Even though is seems like it's over a year old?

    Does anyone have any suggestions as to how to solve this?
    Thanks very much!

    Jurjan

    Comment


    • #3
      I just looked at the logging, an alert (goes off every 15 minutes, this is for testing purposes), errors a few times (this night 3) during the night (see copied logging):

      ERROR 2015-05-08 02:04:16,163 [pool-1-thread-1968] com.mirth.connect.server.alert.DefaultAlertWorker: Error sending alert email.
      org.apache.commons.mail.EmailException: Sending the email to the following server failed : 10.94.253.124:25
      at org.apache.commons.mail.Email.sendMimeMessage(Emai l.java:1401)
      at org.apache.commons.mail.Email.send(Email.java:1428 )
      at com.mirth.connect.server.util.ServerSMTPConnection .send(ServerSMTPConnection.java:152)
      at com.mirth.connect.server.util.ServerSMTPConnection .send(ServerSMTPConnection.java:156)
      at com.mirth.connect.server.util.ServerSMTPConnection .send(ServerSMTPConnection.java:160)
      at com.mirth.connect.server.alert.AlertWorker$ActionT ask.call(AlertWorker.java:181)
      at com.mirth.connect.server.alert.AlertWorker$ActionT ask.call(AlertWorker.java:97)
      at java.util.concurrent.FutureTask.run(Unknown Source)
      at java.util.concurrent.ThreadPoolExecutor.runWorker( Unknown Source)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run (Unknown Source)
      at java.lang.Thread.run(Unknown Source)
      Caused by: javax.mail.MessagingException: Exception reading response;
      nested exception is:
      java.net.SocketTimeoutException: Read timed out
      at com.sun.mail.smtp.SMTPTransport.readServerResponse (SMTPTransport.java:2204)
      at com.sun.mail.smtp.SMTPTransport.issueSendCommand(S MTPTransport.java:2089)
      at com.sun.mail.smtp.SMTPTransport.finishData(SMTPTra nsport.java:1889)
      at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTr ansport.java:1120)
      at javax.mail.Transport.send0(Transport.java:254)
      at javax.mail.Transport.send(Transport.java:124)
      at org.apache.commons.mail.Email.sendMimeMessage(Emai l.java:1391)
      ... 10 more

      but the rest go through without a problem.

      Does anyone have any suggestions as to how to try and find the root cause (and solve it)?

      Thanks!

      Comment


      • #4
        Don't know, but just started happening to my engine today. Upgraded java and mirth to 3.4.1 and still occurring. Emails appear to actually be going through and any channels set to redeliver on failure manage to deliver multiple emails annoying the end users.
        Same error:
        org.apache.commons.mail.EmailException: Sending the email to the following server failed : xx.xx.xx.xx:25
        at org.apache.commons.mail.Email.sendMimeMessage(Emai l.java:1401)
        at org.apache.commons.mail.Email.send(Email.java:1428 )
        cmc

        Comment


        • #5
          So this is an open, unresolved issue?

          http://www.mirthcorp.com/community/i...wse/MIRTH-3134
          cmc

          Comment


          • #6
            Yeah,
            looks like it.
            That's the issue I also found when originally creating this thread.

            Comment


            • #7
              So did you just stop using the smtp sender?
              cmc

              Comment


              • #8
                nope,
                client learned to live with it.

                And as far s I know, the situation has improved.

                Comment


                • #9
                  It's a bit unnerving ignoring all the smtp sender failures and I've had to turn off all my alerts due to failures for these channels too.
                  cmc

                  Comment


                  • #10
                    FYI the problem described in this thread does not look like the issue in MIRTH-3134. It's just a socket timeout, indicating that the e-mail server is too slow to respond, or some other networking/latency issue is going on. Perhaps try increasing the timeout on the destination settings.

                    Also consider using queuing so that messages will retry if a timeout like that happens. Connectivity issues can happen for a variety of issues on any TCP-based connection.
                    Step 1: JAVA CACHE...DID YOU CLEAR ...wait, ding dong the witch is dead?

                    Nicholas Rupley
                    Work: 949-237-6069
                    Always include what Mirth Connect version you're working with. Also include (if applicable) the code you're using and full stacktraces for errors (use CODE tags). Posting your entire channel is helpful as well; make sure to scrub any PHI/passwords first.


                    - How do I foo?
                    - You just bar.

                    Comment


                    • #11
                      Thanks for your reply narupley!
                      I can't use queuing because the messages ARE actually getting to the email server, but showing as failure in Mirth. Therefor queuing causes multiple duplicate email messages.
                      I will increase the timeout and follow up with the result.
                      cmc

                      Comment


                      • #12
                        By the way, if I just 'test' the smtp sender during setup, it fails.
                        if I test from the 'settings' page, it fails.
                        cmc

                        Comment


                        • #13
                          Good grief, the timeout was set at 5000 seconds, I increased to 10000 and was successful, thank you VERY much for your suggestion!!!
                          cmc

                          Comment

                          Working...
                          X