locked
Issue with sending email notifications via internal SMTP server RRS feed

  • Question

  • Hi,

    We have configured SMTP settings on one of our new devices which is a MultiSensor SmartScan for body temperature measurement.

    SMTP settings on the device are as follows:

    Sender Address: donotreply@mydomain.com
    Server Address: smtp.mydomain.com (also tried entering IP address of the SMTP server)
    Encryption Mode: No Encryption (also tried SSL and STARTTLS)
    Port: 25 (tried port 485 in case of SSL and 587 in case of STARTTLS)

    While sending a test message I am getting following information: Remote access denied

    Messages from this device should be sent only internally to mydomain.com domain so I guess this address do not need to be whitelisted in the Exchange -> Mail Flow -> Receive connectors settings.

    Basically, we have loads of different devices (printers, applications etc.) which are using exactly the same SMTP settings and these devices are working fine. This is the first one which is having problems with SMTP.

    What I have tried so far:

    1. Added this device IP address to the "Allowed relay" receive connector on Exchange servers (we only do that for devices which need to send messages externally like I mentioned few lines above) - No luck
    2. Moved the device to the same VLAN which working HP printers are actually using - No luck
    3. Verified logs located in: C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\Hub\ProtocolLog\SmtpSend - did not even find any denied connections from the affected device
    4. Changed SMTP settings to point out to an old SMTP server configured on Lotus Notes which was recently decomissioned - it works fine

    Exchange server version: Exchange Server 2013 CU22

    Any advise would be much appreciated.

    Thanks.

    Regards.


    • Edited by TrapMusicJunkie Thursday, July 16, 2020 1:31 PM added Exchange version
    Thursday, July 16, 2020 1:25 PM

Answers

  • Hi,

    What changes have been made to SMTP settings?

    Protocol logging records the SMTP conversations that occur between messaging servers as part of message delivery. So you could run the follow command to enable the protocol log and send a test message again, then check whether related errors are recorded in the Log.

    Set-ReceiveConnector <> -ProtocolLoggingLevel Verbose

    For more information:Protocol logging.

    You could use ExRCA to test SMTP mail. If an error occurs, ExRCA will provide a detailed error report. Please share it with us. This will help us determine the cause of the error, but please pay attention to covering your personal information.

    About ExRCA: Microsoft Remote Connectivity Analyzer.

    This Exchange Server 2013 - Administration, Monitoring, and Performance Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details.

    Regards,

    Lucas Liu


    Exchange Server 2013 - Administration, Monitoring, and Performance forum will be migrating to a new home on Microsoft Q&A! We invite you to post new questions in the new forum.

    For more information, please refer to the sticky post.

    Friday, July 17, 2020 6:54 AM
  • Hi,

    Seems like issue was solved. I have updated device firmware and used SMTP IP address instead of DNS name.

    Thread can be closed.

    Thank you.

    Regards.

    Wednesday, July 22, 2020 7:52 AM

All replies

  • Hi,

    What changes have been made to SMTP settings?

    Protocol logging records the SMTP conversations that occur between messaging servers as part of message delivery. So you could run the follow command to enable the protocol log and send a test message again, then check whether related errors are recorded in the Log.

    Set-ReceiveConnector <> -ProtocolLoggingLevel Verbose

    For more information:Protocol logging.

    You could use ExRCA to test SMTP mail. If an error occurs, ExRCA will provide a detailed error report. Please share it with us. This will help us determine the cause of the error, but please pay attention to covering your personal information.

    About ExRCA: Microsoft Remote Connectivity Analyzer.

    This Exchange Server 2013 - Administration, Monitoring, and Performance Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details.

    Regards,

    Lucas Liu


    Exchange Server 2013 - Administration, Monitoring, and Performance forum will be migrating to a new home on Microsoft Q&A! We invite you to post new questions in the new forum.

    For more information, please refer to the sticky post.

    Friday, July 17, 2020 6:54 AM
  • Hi,

    Seems like issue was solved. I have updated device firmware and used SMTP IP address instead of DNS name.

    Thread can be closed.

    Thank you.

    Regards.

    Wednesday, July 22, 2020 7:52 AM
  • Hi,

    I’m pleased to know that your issue is resolved.

    You could share your solution and mark them or the helpful reply as answer, this will make answer searching in the forum easier and be beneficial to other community members as well.

    Thanks for your understanding.

    This Exchange Server 2013 - Administration, Monitoring, and Performance Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details.

    Regards,

    Lucas Liu


    Exchange Server 2013 - Administration, Monitoring, and Performance forum will be migrating to a new home on Microsoft Q&A! We invite you to post new questions in the new forum.

    For more information, please refer to the sticky post.

    Wednesday, July 22, 2020 8:03 AM
  • Hi,

    If the issue has been resolved, please mark the helpful replies as answers, this will make answer searching in the forum easier.

    This Exchange Server 2013 - Administration, Monitoring, and Performance Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details.

    Regards,

    Lucas Liu


    Exchange Server 2013 - Administration, Monitoring, and Performance forum will be migrating to a new home on Microsoft Q&A! We invite you to post new questions in the new forum.

    For more information, please refer to the sticky post.

    Monday, July 27, 2020 9:27 AM