|
Difference between IMAP and SMTP
|
When you encounter the "Bad Login or Username/Password" error, the first step is to check your Cpanel or Plesk of your hosting account to see if the email address was set up properly. Otherwise, that email address may not have been successfully created. Next, check whether you are using the correct username. Usually email username is your full email address- meaning your yourname@domain. Using an incorrect username will definitely result to an unsuccessful login or bad login. Finally, determine if you are using the correct password. The way to do this is to go to your Cpanel or Plesk and see the correct password for each email account created. It is easy to get mixed up, especially if you have already created several email accounts. Another Internet SMTP Problem for sending email is when you encounter the "Server not found" error. The first thing you have to do is check if you are connected to the Internet. Access to your SMTP of course requires that you have a live Internet connection. If you're using a newly registered domain name, note that it usually takes a day or two for the domain to propagate on the Internet. This means that pointing your email client to mail.youdomain will still not work. And yes, in that case you will get the "Server not found" error. If you have determined that the above are not the cause of the error, check your email client settings to see if you are using the correct SMTP servers. Usually the right SMTP server is mail.yourdomain. However, many ISPs now require you to use their own SMTP server. Check with your ISP technical support what their policy is. Still another Internet SMTP Problem for sending email is when you get an almost immediate reply saying "Mailbox full/Quota Exceeded/Could not create output file". This clearly is not your problem. It only means that your addressee's inbox is full and has exceeded quota. There is nothing you can do about it but to advise him or her. IMTP: Setting up your email accounts to use IMAP has some benefits but you may eventually come across a problem with multiple IMAP connections opened simultaneously or even when not open simultaneously. I'm not certain of the cause of this problem. I assume the root is somewhere due to a mail server problem. I currently host with Bluehost. Let me first describe the problem as it may be a reflection of the problem you may be encountering. With one client I had to set up email accounts for several (around 20) persons and it seemed to be growing. I set up every account as IMAP as this will allow the recipients to view and send email from any computer and yet have all their emails synched. This is a good feature. However, this seemed to bring down the entire account (meaning all the websites associated with this account) went offline. Actually, one of the side effects was a completely blank screen. No page errors displayed; no 404 error pages or any other errors. Just a blank screen was displayed for the websites associated with the account. After I inquired as to the Setting up your email accounts to use IMAP has some benefits but you may eventually come across a problem with multiple IMAP connections opened simultaneously or even when not open simultaneously. I'm not certain of the cause of this problem. I assume the root is somewhere due to a mail server problem. I currently host with Bluehost. Let me first describe the problem as it may be a reflection of the problem you may be encountering. With one client I had to set up email accounts for several (around 20) persons and it seemed to be growing. I set up every account as IMAP as this will allow the recipients to view and send email from any computer and yet have all their emails synced. This is a good feature. However, this seemed to bring down the entire account (meaning all the websites associated with this account) went offline. Actually, one of the side effects was a completely blank screen. No page errors displayed; no 404 error pages or any other errors. Just a blank screen was displayed for the websites associated with the account. After I inquired as to the cause of the problem with the Bluehost techs they found that there were multiple processes or connections to the server.
|
|
|