-
Bug
-
Resolution: Fixed
-
Medium
-
8.2.0, 8.2.3, 8.5.3, 8.3.4, 8.5.4, 8.6.2, 8.4.5, 8.7.2, 8.5.5, 8.5.6
-
16
-
Severity 2 - Major
-
97
-
Issue Summary
This is reproducible on Data Center: yes
After upgrading Confluence from 7.19.16 to 8.5.3, we have started to receive this error below during the daily email batch job:
com.atlassian.mail.MailException: javax.mail.MessagingException: Got bad greeting from SMTP host: <host>, port: 25, response: 421 4.3.2 The maximum number of concurrent server connections has exceeded a per-source limit, closing transmission channel (<channel>)
Steps to Reproduce
- Set up SMTP mail server
- Wait for Daily Report email batch job to run
Expected Results
All emails are sent without errors.
Actual Results
The below exception is thrown in the atlassian-confluence-outgoing-mail.log file:
2023-11-09 14:23:20,486 ERROR [atlassian.core.task.AbstractErrorQueuedTaskQueue] handleException Failed to execute task -- url: /wiki/admin/mail/resenderrorqueue.action | userName: <username> | action: resenderrorqueue | referer: https://domain.com/wiki/admin/mail/viewmailqueue.action | traceId: <traceId> com.atlassian.mail.MailException: javax.mail.MessagingException: Got bad greeting from SMTP host: <host>, port: 25, response: 421 4.3.2 The maximum number of concurrent server connections has exceeded a per-source limit, closing transmission channel (<channel>)
Workaround
To change the receive connector MessageRateLimit from X to 20 or 50 or 100, depending on your mail load.
Also, this issue is been documented by Microsoft in the Exchange Server Support forum; 421 4.4.2 Message submission rate for this client has exceeded the configured limit.
- is related to
-
-
- Closed
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
[CONFSERVER-93627] SMTP connections are not closed after upgrading from 7.19.16 to 8.5.3
A fix for this issue is available in Confluence Server and Data Center 8.9.0.
Upgrade now or check out the Release Notes to see what other issues are resolved.
A fix for this issue is available in Confluence Server and Data Center 8.5.7.
Upgrade now or check out the Release Notes to see what other issues are resolved.
Yes, that workaround should work.
But I think we agree that deviating from Microsoft's recommended settings cannot be the/a solution to this problem.
Our Exchange admin set the parameter "MaxInboundConnectionPerSource" from 20 up to 1.000. This helped.
The users get their mails and the error message vanished from the logs.
Of course this only is a workaround and I hope that Atlassian brings out a bugfixed version soon!
Our confluence system, due to being on a large instance with over 10k Users, is experiencing this exception even with normal activity emails, such as notifications about mentions, task assignments, or updates on watched pages, that are not being sent/received by the users. This problem also affects the functionality of the task reminder plugin, which is set to remind users every Monday about their open tasks. This feature is particularly crucial for several users.
While this is happening, the troubleshooting and support tools may sometimes report Confluence unable to send email through Gmail server due to 'Read timed out' during the scan