Search results
Results from the WOW.Com Content Network
The Basic Status Codes have been in SMTP from the beginning, with RFC 821 in 1982, but were extended rather extensively, and haphazardly so that by 2003 RFC 3463 rather grumpily noted that: "SMTP suffers some scars from history, most notably the unfortunate damage to the reply code extension mechanism by uncontrolled use.
If you're having problems sending mail, there are a few troubleshooting steps you can take to fix the problem. Restart your computer:. If you haven't shut down your computer in a while, we recommend that you begin troubleshooting by restarting your computer.
If your account is working on a web browser and you made sure you're using the right server settings, then update your email app to the newest version available. If you're still experiencing issues with your app, contact the manufacturer. Also, access your AOL Mail on a web browser. Keep in mind - For two-step verification, generate an app ...
Update your email client application If you're using an older version of your email client, it could be outdated and no longer compatible with the latest security settings. We recommend updating to the latest version of your email client, then removing and re-adding your AOL Mail account.
Get AOL Mail for FREE! Manage your email like never before with travel, photo & document views. Personalize your inbox with themes & tabs. You've Got Mail!
For example, the client uploads an image as image/svg+xml, but the server requires that images use a different format. 416 Range Not Satisfiable The client has asked for a portion of the file (byte serving), but the server cannot supply that portion. For example, if the client asked for a part of the file that lies beyond the end of the file.
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 current SMTP specification (RFC 5321) clearly states that "the SMTP client retains responsibility for delivery of that message" (section 4.2.5) and "mail that cannot be transmitted immediately MUST be queued and periodically retried by the sender." (section 4.5.4.1). Most MTAs will therefore queue and retry messages, but a small number do not.