IIS SMTP service on the Kaseya server takes a long time to detect bad email addresses

KB # KKB000757

 

Problem: The IIS SMTP service on the Kaseya server takes a long time to detect bad email addresses and time out attempting to deliver the messages. This can result in queuing of delivery of email from the Kaseya server, even to a local mail server.

 

Cause: This is due to the default configuration settings of SMTP in IIS. These settings are appropriate for normal mail delivery, but not necessarily correct for the time sensitive delivery of email that many Kaseya server configurations require.

 

Resolution: You can Configure Retry Tries and Intervals to increase your server output speed, but these settings affect outgoing messages only and have no effect on the rate at which other servers process incoming messages.

To configure these settings, follow these steps:

  1. In the Microsoft Management Console (MMC), click to select the SMTP virtual server, and then click Properties on the Action menu.
  2. Click the Delivery tab.
  3. For First retry interval (minutes), type a value for the time to try delivery before posting the first notification. The default is 15 minutes.
  4. For Second retry interval (minutes), type a value for the time to try delivery before posting the second notification. The default is 30 minutes, which is 30 minutes after the first retry interval.
  5. For Third retry interval (minutes), type a value for the time to try delivery before posting the third notification. The default is 60 minutes, which is 60 minutes after the second retry interval.
  6. For Subsequent retry interval (minutes), type a value for the time to try delivery before posting a notification. The default is 240 minutes.

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Contact us