Campaign Launch Notification Not Sent To All Campaign Owners

[timchengappa]

Use Case

A camapign(Any type) is launched and the expectation is that all campaign owners should receive a "Campaign Launch" email notification. In some scenarios, a few certifiers/owners do not receive the notification...

Pre-requisites

Please refer to the "Prerequisites for Creating Campaigns" section of our documentation.

Also, please locate relevant logs snips below...

2022-03-29 10:32:22,322 [quartzScheduler_Worker-19] DEBUG println.PrintlnToLogger - Println :: [1;31m| Error [22;39morg.springframework.mail.MailSendException: Failed to close server connection after message failures; nested exception is javax.mail.MessagingException: Can't send command to SMTP host;

  nested exception is:

 java.net.SocketException: Connection closed by remote host. Failed messages: com.sun.mail.smtp.SMTPSendFailedException: 421 4.4.2 Message submission rate for this client has exceeded the configured limit

; message exception details (1) are:[m

2022-03-29 10:32:22,322 [quartzScheduler_Worker-19] DEBUG println.PrintlnToLogger - Println :: [1;31m| Error [22;39mFailed message 1:[m

2022-03-29 10:32:22,322 [quartzScheduler_Worker-19] DEBUG println.PrintlnToLogger - Println :: [1;31m| Error [22;39mcom.sun.mail.smtp.SMTPSendFailedException: 421 4.4.2 Message submission rate for this client has exceeded the configured limit​

org.springframework.mail.MailSendException: Failed messages: com.sun.mail.smtp.SMTPSendFailedException: 432 4.3.2 Concurrent connections limit exceeded. Visit https://aka.ms/concurrent_sending for more information. [Hostname=KL1PR03MB5763.apcprd03.prod.outlook.com]
; message exception details (1) are:
Failed message 1:
com.sun.mail.smtp.SMTPSendFailedException: 432 4.3.2 Concurrent connections limit exceeded. Visit https://aka.ms/concurrent_sending for more information. [Hostname=KL1PR03MB5763.apcprd03.prod.outlook.com]

Applicable Version(s)

All

Solution

SMTP is managed by the customer the total email sent for a day exceeds the configuration limit on the customer's SMTP end, Asked the customer to increase the configured limit value and rerun the email history job.

After increasing the configured SMTP limit value issue is resolved