Troubleshooting Email Delivery Failures
See the illustration below for an overview of steps involved in delivering emails you send into your recipients inbox.
If something does go wrong, you would usually get a response message from the recipients mail server (see: step 6a) that explains what went wrong - see below the table with common error codes.
Common Errors and Responses
Below are a list of common responses you may see in your failed deliveries - and our suggestions on how to deal with them. Of course, feel free to contact our technical support if you need any help or have questions.
| Response code |
Description |
Suggested Resolution |
| 421 |
Service not available, closing transmission channel |
Retry or Notify recipient
|
| 450 |
Requested action not taken; mailbox unavilable or busy |
Retry or Notify recipient |
| 451 |
Requested action aborted, local error in processing |
Retry or Notify recipient
|
| 452 |
Requested action not taken, insufficient system storage |
Retry or Notify recipient |
| 500 |
Syntax error, command unrecognized. Also command line too long |
Notify Wild Apricot support |
| 501 |
Syntax error in paramaters or arguements |
Notify Wild Apricot support |
| 502 |
Command not implemented |
Notify Wild Apricot support |
| 503 |
Bad sequence of commands |
Notify Wild Apricot support
|
| 504 |
Command parameters not implemented |
Notify Wild Apricot support |
| 550 |
Action not taken. Mailbox unavailable. Not found, not accessible |
Retry or Notify recipient |
| 551 |
User not local, please try <suggestion> |
Retry or Notify recipient
|
| 552 |
Exceeded storage allocation |
Retry or Notify recipient
|
| 553 |
Mailbox name not allowed. Mailbox syntax may be incorrect |
Retry or Notify recipient
|
| 554 |
Transaction failed |
Retry or Notify recipient |
Home
