Until recently mail notifications were functioning without a problem. It suddenly stopped working.

IP of the PRTG server is allowed to relay. I can telnet from the PRTG server to port 25 and send a message.

This is a log message from the mail server when it was working: 2013-06-30T09:11:39.057Z,MAIL\internal SMTP mail,............................,>,250 2.1.5 Recipient OK, 2013-06-30T09:11:39.057Z,MAIL\internal SMTP mail,............................<,DATA,

This is the log message since it stopped working: 2013-07-05T13:02:26.973Z,MAIL\internal SMTP mail,............................,>,250 2.1.5 Recipient OK, 2013-07-05T13:02:26.973Z,MAIL\internal SMTP mail,............................,-,,Remote

The change is in the last phase. Instead of DATA, the log is ,,Remote.

SMTP notifications were working just fine until recently, now nothing gets through. SMTP notifications from other systems that send e-mail to the same address (servers from the same and other network segments, backup job notifications, etc...) are delivered correctly.


Article Comments

Please update to version 13.3.4.2478/2479. Then, please follow the guidelines outlined under How can I enable Notification Delivery Logging? Please forward us the generated log files to support@paessler.com, with reference to this thread.


Jul, 2013 - Permalink

This is the last part of the log wiht modified domain and username: Sent 7/11/2013 4:19:46 PM: RSET<EOL> Recv 7/11/2013 4:19:51 PM: 250 2.0.0 Resetting<EOL> Sent 7/11/2013 4:19:51 PM: MAIL FROM: <PRTG@prtguser.com><EOL> Recv 7/11/2013 4:19:51 PM: 250 2.1.0 Sender OK<EOL> Sent 7/11/2013 4:19:51 PM: RCPT TO:<user@prtguser.com><EOL> Error sending "Email": Read timed out.


Jul, 2013 - Permalink

From what we can discern in the log files provided this seems to be a tarpitting / blacklis issue. If you try using a different sender / recipient, does that work? Please also check the server settings. Beyond that, if you try using a SMTP sensor with the same settings, does it work?


Jul, 2013 - Permalink