Search results
Results from the WOW.Com Content Network
If you see an image challenge question when sending mail, you should just be able to complete the challenge then send mail. If, however, you correctly answer the image challenge and still can't send mail, it could be a sign of a more serious issue with your account, which may require additional steps to secure your account.
If your third-party email app is having issues connecting, sending, or receiving emails, you may need to reconfigure your account or update the app. Use these steps to identify and fix the source of the problem. Troubleshoot any problems with your account
If possible, ask the sender to resend the message to see if you can get the message a second time. Check for emails in your Spam folder. If you find emails in your Spam folder that don't belong there, you'll need to mark the messages as "not spam." 1. Sign in to AOL Mail. 2. Click the Spam folder. 3. Select the message that isn't spam. 4.
Get answers to your AOL Mail, login, Desktop Gold, AOL app, password and subscription questions. Find the support options to contact customer care by email, chat, or phone number.
Get answers to your AOL Mail, login, Desktop Gold, AOL app, password and subscription questions. Find the support options to contact customer care by email, chat, or phone number.
If you recently changed your AOL password, you'll need to update it in the email client you use. Find your application's "Email Accounts" or "Account Settings" section, select your AOL Mail account, then update to your new password.
Verified for version 4.4 and later. 1. Open the Settings app. 2. Tap Apps. 3. Tap AOL. 4. Tap Force Stop. 5. If prompted, tap Force Stop again to confirm. 6. Relaunch the app and attempt to reproduce the issue.
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".