If the configuration instructions did not make reference to SSL, TLS, or StartTLS then make sure the option for the SSL/TLS settings in the Security tab is set to None.
Also confirm that he is using his full email address for his username.
Finally, a web search found some conflicting information about whether the host should be smtpa.bellaliant.net or smtp.bellaliant.net. That could be just typos but it might be worth testing with smtp.
If those aren't it, you may need him to have him create an internet session log and send it to you for analysis. It should identify the point of failure. I would test using the smtpa host name for the first go. Be sure he turns internet session logging back off.
One other thought. I've never seen port 2225 used so wonder if it is a port that needs to be unblocked in the firewall.
<p>If the configuration instructions did not make reference to SSL, TLS, or StartTLS then make sure the option for the SSL/TLS settings in the Security tab is set to None.&nbsp; </p><p>Also confirm that he is using his full email address for his username.</p><p>Finally, a web search found some conflicting information about whether the host should be smtpa.bellaliant.net or smtp.bellaliant.net.&nbsp; That could be just typos but it might be worth testing with smtp.
</p><p>If those aren't it, you may need him to have him create an internet session log and send it to you for analysis.&nbsp; It should identify the point of failure.&nbsp; I would test using the smtpa host name for the first go. Be sure he turns internet session logging back off.</p><p>One other thought.&nbsp; I've never seen port 2225 used so wonder if it is a port that needs to be unblocked in the firewall.</p><p>&nbsp;</p>