Search results
Results From The WOW.Com Content Network
4.XXX.XXX Persistent Transient Failure: Message as sent is valid, but persistence of some temporary conditions has caused abandonment or delay. 5.XXX.XXX Permanent Failure: Not likely to be resolved by resending the message in current form. In general the class identifier MUST match the first digit of the Basic Status Code to which it applies. [1]
If you have any combination of "AOL" in your display name, the message won't go through. It is especially important to check your Mail settings for this if your account has been recently compromised, as hackers will often change your name to make it harder for you to use your account normally even after it's secured. Clear your browser's cache
This class of status code indicates the client must take additional action to complete the request. Many of these status codes are used in URL redirection. [2]A user agent may carry out the additional action with no user interaction only if the method used in the second request is GET or HEAD.
If the delivery failure message says the account doesn't exist double check the spelling of the address you entered. A single misplaced letter could cause a delivery failure. If the message keeps getting bounced back, make sure the account is closed or hasn't been moved.
If you're repeatedly getting delivery failure errors when sending messages to AOL Mail customers, it is most likely due to spam blocking on AOL's servers. While you may be following at the rules for sending mail, it's likely the address you're sending mail from is hosted on a server our system had identified as "abusive".
The trade-off is more work and bandwidth for more exact matching of retries with original messages. [3] Rejecting a message after its content has been received allows the server to store a choice of headers and/or a hash of the message body. [citation needed] In addition to whitelisting good senders, a greylister can provide for exceptions ...
Delivery records in the full headers show when each computer received the message. The first delivery is at the bottom; the newest at the top. If you find a large time gap between delivery records, that shows which computer delayed before sending it to the next computer. 1. View the full header by following the steps above. 2.
Delivery records in the full headers show when each computer received the message. The first delivery is at the bottom; the newest at the top. If you find a large time gap between delivery records, that shows which computer delayed before sending it to the next computer. 1. View the full header as described above. 2.