You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SMTP errors are not reported as reported by the SMTP host which makes it difficult to debug issues. For example when there is a 4.7.1 error this is the reported "Server Response":
{
"code": 422,
"message": "SMTP Error: data not accepted.",
"errors": [
"SMTP Error: data not accepted."
]
}
However at the server end the error is:
milter-reject: END-OF-MESSAGE from unknown[xxx.xxx.xxx.xxx]: 4.7.1 Service unavailable - try again later;
The error code is always 422 and the messages are not the actual error. The information provided here should be the actual server response or the full transcript of the SMTP exchange.
The text was updated successfully, but these errors were encountered:
Version: 2.2.81
SMTP errors are not reported as reported by the SMTP host which makes it difficult to debug issues. For example when there is a 4.7.1 error this is the reported "Server Response":
{
"code": 422,
"message": "SMTP Error: data not accepted.",
"errors": [
"SMTP Error: data not accepted."
]
}
However at the server end the error is:
milter-reject: END-OF-MESSAGE from unknown[xxx.xxx.xxx.xxx]: 4.7.1 Service unavailable - try again later;
The error code is always 422 and the messages are not the actual error. The information provided here should be the actual server response or the full transcript of the SMTP exchange.
The text was updated successfully, but these errors were encountered: