Real people, on-site in Ireland.
If your email client can receive but not send on one connection, and works on another, your broadband provider may be blocking the outgoing mail port. The usual fix is to send through port 587 or 465 with authentication, or through your ISP's own outgoing server. Here is how to work out which problem you have.
Test the same mailbox on a different network. If you can send over your phone's mobile data but not on home or office broadband, the connection is the likely culprit. If it fails everywhere, the cause is probably the account: a wrong password, the wrong server name, or authentication turned off for outgoing mail. Webmail is a useful check too, since it runs through a browser on standard web ports. Our guide to webmail versus an email client explains the difference.
Some broadband providers restrict outgoing port 25, the traditional port for server to server mail, to cut down on spam sent from infected computers. The broadband providers do not all publish their policies clearly, so the current position for each line is best confirmed with the provider. One Irish provider's support page (Magnet Plus), checked in October 2026, says an increasing number of broadband providers restrict port 25 and names Smart, Magnet, Vodafone and parts of Eircom's network. It also says some customers on parts of that network are blocked on port 587 as well.
Treat that as one provider's account, not a definitive list. Policies change, and they can differ by region or by whether you are on a business plan. If your ISP's support pages or helpdesk will tell you, ask them directly whether outgoing SMTP ports are restricted on your line.
For a mailbox on your own domain, use your mail provider's outgoing server name, not your ISP's, with SMTP authentication switched on, and your full email address as the username. Port 587 with STARTTLS or port 465 with SSL/TLS is the normal modern setup. Port 25 is intended for server to server delivery and should not be used by an email client on a home connection. Your provider's mailbox settings page lists the exact server name and ports for your account, so use those rather than guessing.
If you are setting up a mailbox in cPanel, cPanel email accounts shows where the settings are, and IMAP versus POP3 covers the incoming side.
The Magnet Plus page suggests that when port 25 is restricted you may need to send through your broadband provider's own outgoing server instead, which recipients should not notice. That works for some people, but it has a catch: the ISP server may only accept mail from addresses it recognises, and each ISP's rules differ, so check their documentation.
Other options are to try 465 if 587 fails, to send over a different network such as mobile data while you wait for a fix, or to send through webmail. If you need a permanent solution, ask the ISP to unblock the port or move that line to a provider that does not restrict it.
That is a different problem. A message that leaves your computer but is rejected or filtered afterwards is usually down to your domain's SPF, DKIM and DMARC records, or a blacklisting. See email deliverability explained, and test with the blacklist checker. If you want a mailbox on your own domain with Webmail and spam protection, professional email is the place to start. This is general troubleshooting; your ISP and mail provider can confirm what applies to your line.
HostBible offers professional email with IMAP, POP3, Webmail and spam protection, and the team can migrate your existing mailboxes with a hosting plan.
See professional email