Many major internet service provides (ISP's) may block outgoing mail server ports to prevent their services being used to send spam emails. The most common port that are blocked is port 25, but for non-SSL settings we do recommend that you use port 26. You should review your email account details (in Outlook / Mac Mail etc.) and adjust if necessary.
Using Port 26 but this still does not work
Some ISP's may block port 26 as well as port 25. When this happens, you may wish to contact your ISP and discuss whether they can enable a port for you or alternatively receive instructions on what SMTP port or servers you can use that will work through their network. Most commonly, this information will be able in your ISP's FAQ section on their website.
You cannot receive emails or send emails
If you are unable to send or receive any emails, it is likely that your email account details haven't been set up correctly or they may have changed (especially if you use SSL which has a specific server setup which may have changed). You should review your mail configuration settings as follows:
Your Mail Configuration Settings
Log into your cPanel account. If you are unsure on how to do this, please view the following help article - 'How to log into cPanel'.
Once you have successfully logged in, either type email into the search box or scroll down to the 'Email' section as per the below. Select the first option shown 'Email Accounts'.
You should find that you are in your email accounts management section. If you scroll down, you should find the email account that you are struggling with. Against that record, you should see an option shown as 'Configure Mail Client' which you need to select.
Scrolling down to the 'Manual Settings' heading, you will locate the manual settings required for the email account. It is important to review these settings to compare to them to what you are using on your email client. Please note that there are two settings available, secure SSL/TLS and non-SSL. It's important to choose the correct settings that you have opted for.
If you are still struggling with any of the suggestions raised, please log into your 'Client Area' and contact us via the 'Support Ticket' system for further help.
Truth be told, it’s difficult for a web application that doesn’t have some kind of identification, even if you don’t see it as a security measure in and of itself. The Internet is a kind of lawless land, and even on free services like Google’s, authentication ensures that abuses will...
Although data persistence is almost always a fundamental element of applications, Node.js has no native integration with databases. Everything is delegated to third-party libraries to be included manually, in addition to the standard APIs. Although MongoDB and other non-relational databases are the most common choice with Node because if you...