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.
1. Sign into AOL Mail on a web browser. 2. Compose an email and add your own email address in the "To" field. 3. Send the email and check if it arrives.
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.
214 Help message (A response to the HELP command) 220 <domain> Service ready 221 <domain> Service closing transmission channel 221 2.0.0 Goodbye [1] 235 2.7.0 Authentication succeeded [3] 240 QUIT 250 Requested mail action okay, completed 251 User not local; will forward 252 Cannot verify the user, but it will try to deliver the message anyway
Outlook: Scroll right past 'sent mail' to a folder marked 'junk.' Hotmail: Beneath 'inbox,' find a category called 'folders;' the 'junk' folder should be first. You know how good it feels to clean ...
Sign in to your AOL account.; Once you've signed in to your account, go to our Contact Us page on AOL Help. If the account you're signed in to is eligible for chat support, "Chat with AOL Customer Care" will be displayed as a support option near the top of the page.
Many email services also offer filters (and advanced filters) that let you search the messages in your spam folder by sender, date, attachment and more. Second, look for a box next to each email ...
It alerts the client to wait for a final response. The message consists only of the status line and optional header fields, and is terminated by an empty line. As the HTTP/1.0 standard did not define any 1xx status codes, servers must not [note 1] send a 1xx response to an HTTP/1.0 compliant client except under experimental conditions. 100 Continue