![]() ![]() In case one of the recipients has different filtering settings, we cannot "accept" or "reject" the message as the classification may differ per-recipient. The SMTP protocol only allows you to either "accept" OR "reject" the email, without distinguishing between the different recipients. Within a single SMTP connection, it is possible to deliver a message to different recipients. Mail for this domain cannot be accepted right now please retry (Unable to handle in active connection.) These limits can be entirely disabled there as well. In case the limits should be changed, they can be modified via Mail Assure for the outgoing user. This indicates that the outgoing user has exceeded the maximum amount of messages configured for that outgoing user to be sent. Please ensure that the sending mail server only opens up a maximum of 10 concurrent connections to avoid hitting this limit. There is a hard-coded limit of 10 concurrent SMTP connections per IP to protect the systems against attack. Too many connections from the sending server. The sender has exceeded his/her per-minute limit. Internal errorĪn internal error occurred, this should automatically resolve. When the sender verification option is used in the outgoing user settings, then each specific sender address must be verifiable like this. You'll have to check the sender mail-server to verify why such callouts count not be done. This means the system was unable to verify the sender using a sender callout. The logs on the destination server should show why it is not accepting the delivery attempts. ![]() You'll have to check the destination route set to ensure delivery is attempted to the correct server. This means the destination server is unreachable or temporarily rejecting the email traffic. This is to protect against brute-force attacks on your SMTP credentials. ![]() To resolve this, use the correct authentication details and wait a few moments and try again. This means that you have used incorrect outgoing authentication details too often in a short period of time. We do not apply "classical greylisting" so this should not cause any delays on your legitimate traffic. This technology is only applied to new IP addresses which do not have a (good) reputation yet in our global systems. ![]() It's always possible to whitelist the sender to disable any checks and to ensure that the message will get accepted as soon as it's retried by the sending server. Depending on the reason of the temporary reject, the message could get accepted at a subsequent delivery attempt. Legitimate mail servers always automatically retry delivery of such messages. Messages which have been temporarily rejected, stay stored on the sending mail server. In Mail Assure we use different classifications to describe why a message was rejected or temporarily rejected. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |