SMTP settings: A guide to sending emails without a hitch

17 min read

A single poorly chosen port number or a missing encryption protocol is enough to ensure that even your most important business emails end up in the spam folder or are simply bounced back by the recipient. You’ve probably encountered that frustrating situation yourself, where you get stuck in a maze of encryption types and complex technical details whilst configuring your email client. You’re not alone, as incorrect SMTP settings are most often the cause of failed email deliveries, which directly undermines the effectiveness of business communication and the sender’s server’s credibility.

In this guide, you’ll learn about the correct SMTP settings, how to use secure ports and how to troubleshoot the most common sending errors. We’ll walk you through the differences between ports 587 and 465 – which are set to become the industry standard in 2026 – step by step, help you integrate the most popular email systems, and show you how to ensure a high delivery rate via the cPanel interface. Our aim is to ensure that technical details do not hinder, but rather reliably support, your professional email traffic.

What is SMTP and why are the settings so crucial?

The cornerstone of internet email is the Simple Mail Transfer Protocol, or SMTP for short. Think of this system as the internet’s digital postman. Whilst the IMAP and POP3 protocols are responsible for organising and downloading incoming emails, SMTP is solely responsible for forwarding emails from the sender’s device to the recipient’s server. Without the correct SMTP settings, the postman won’t know which route to take, or worse still, the recipient’s gatekeeper – that is, the spam filter – will simply refuse entry.

Many people confuse the roles of incoming and outgoing servers. IMAP synchronises messages across your devices, whilst POP3 downloads them to your computer. SMTP, on the other hand, is a one-way channel. It does not store emails, but actively transfers data packets across the network. By 2026, sending emails anonymously or without authentication had become almost entirely impossible. Major service providers immediately reject any messages that do not come from an authenticated source, which is why specifying security parameters is a mandatory part of the configuration process.

SMTP vs. PHP Mail: Why choose a dedicated protocol?

The default PHP mail() function for websites may seem convenient, but it harbours serious risks. This method does not require a separate password to send emails, so, in theory, anyone could generate traffic on behalf of the server. This security vulnerability is the reason why a significant proportion of messages sent via PHP mail() often end up in the spam folder. Modern email systems require an authenticated SMTP connection. This protocol guarantees that the email actually originates from you, and is not an attempt by an automated bot. Using SMTP drastically improves deliverability, as the receiving server sees the valid login credentials and the encrypted channel.

The benefits of authenticated email in 2026

The main advantage of sending authenticated emails is that it preserves the server’s reputation and protects the IP address. If you send emails without authentication in a professional web hosting environment, a single security vulnerability on the server could ruin the reputation of the entire IP range. The username and password specified during the correct SMTP configuration accurately identify the sender. This process effectively prevents spoofing – that is, the technique whereby fraudsters send malicious content by forging your email address. Authentication therefore not only helps ensure that emails reach their destination, but also safeguards your brand and domain in the digital space.

Video: What is SMTP - Simple Mail Transfer Protocol (PowerCert Animated Videos)

The most important SMTP parameters and ports: What goes where?

To ensure successful configuration, you must enter four essential pieces of information accurately in your email client. The first and most important is the outgoing mail server, i.e. the SMTP server address. In aWh’s systems, this almost always follows the format mail.domainnev.hu, where you must replace “domainnev.hu” with your own registered domain. The most common mistake made during authentication is that users only enter the username prefix. Please note: your username is always your full email address (for example: info@sajatdomain.hu), and your password is the secret code associated with it.

The basis of secure communication is actively enabling outgoing server authentication. In most software, this option must be specifically ticked under the menu item ‘Outgoing server requires authentication’ or a similar name. According to the NIST definition, SMTP is a protocol that enables reliable and efficient message delivery; however, in a modern environment, it only operates reliably with strict authentication. By applying the correct SMTP settings, you can avoid the server rejecting your send request on the grounds of unauthorised access.

Which SMTP port should we choose? (25, 465, 587)

The port number you choose determines the channel through which your message leaves your computer. Port 25 dates back to the early days of the internet, but by 2026 it will be best avoided. Most local and international internet service providers (ISPs) block this port for security reasons, to prevent the mass sending of unsolicited advertising emails. If you use this port, there is a high chance your emails will not even be sent.

Port 465 is part of the so-called SMTPS standard. This port uses mandatory SSL encryption, which means that the connection is encrypted from the moment it is established. If you select the SSL/TLS option in your email client, you must enter this port. Port 587 is the current standard for modern email sending. It uses the STARTTLS protocol, which first establishes a plaintext connection and then immediately switches to a secure, encrypted channel. This is the most flexible solution and is recommended by most experts.

SSL vs. TLS encryption: The key to secure data transmission

Encryption is not merely an optional convenience feature, but the foundation for protecting business secrets. Having a valid SSL certificate on the server side ensures that the content of your emails and your login details cannot be intercepted whilst travelling over the network. TLS (Transport Layer Security) is the successor to SSL, using more advanced algorithms to guard against vulnerabilities. You will often see the terms SSL/TLS or STARTTLS in your email client’s settings. Always select the option that corresponds to the specified port number; otherwise, the client and server will not be able to communicate, resulting in a ‘timeout’ or ‘connection error’ message. If you’re looking for a stable and fast solution, aWh’s professional email hosting services come with all the necessary parameters pre-configured.

Once you have the precise technical details, the next step is practical implementation. Although the basic technical framework and the system of error codes are defined by the RFC 2821 protocol, the user interfaces of individual email clients can vary significantly. For aWh customers, the quickest way is via the cPanel hosting control panel, where, under the ‘Email Accounts’ menu, clicking the ‘Connect Devices’ option immediately displays the customised server details. On mobile devices, such as those running iOS or Android, it is advisable to avoid the automatic setup. By choosing manual configuration, you can ensure that your phone does not attempt to use the unencrypted port 25, which is often blocked when you’re out and about on public Wi-Fi networks.

Before finalising your account, never forget to use the ‘Test Settings’ function. This quick process sends a test message to the server, so you’ll find out straight away if you’ve mistyped your password or chosen the wrong encryption type. This way, you can avoid realising only hours later that your outgoing emails never actually left your computer.

Step-by-step guide to configuring Outlook and Thunderbird

In Outlook, the most important step is to locate the ‘Advanced settings’ button when setting up your account manually. Here, under the “Outgoing Mail Server” tab, you must tick the option “My outgoing mail server (SMTP) requires authentication”. If this is not done, the server will identify you as an unknown sender and refuse to forward the email. Things are slightly simpler for Thunderbird users, but you must still ensure that the correct SMTP settings are listed in the outgoing server settings, paying particular attention to STARTTLS encryption and port 587. If you use multiple email addresses, check that each address is assigned its own dedicated SMTP server.

Setting up WordPress SMTP: Goodbye, lost emails!

Many website owners find that messages sent via contact forms or registration emails never arrive. This is because WordPress uses the PHP mail() function by default, which modern servers often treat as spam. The solution is to install a dedicated plugin, such as WP Mail SMTP. By selecting the ‘Other SMTP’ option here, you can enter the details of the aWh SMTP server. With this method, your website does not attempt to send emails ‘anonymously’, but logs in to the mail server properly. This change results in a delivery rate of nearly 100 per cent almost immediately and ensures that your customers receive automatic confirmations.

Common SMTP error codes and how to improve deliverability

When an email client displays an error message, most users are left baffled by the three-digit numbers. Yet these codes tell you exactly what the problem is with the outgoing server. Error 550, or ‘Relay denied’, is one of the most common occurrences. This means that the server has refused to relay the message for security reasons, because you have not authenticated yourself properly. The solution is simple: check the SMTP settings discussed earlier to ensure that outgoing server authentication is enabled. Without this, the server cannot determine whether you are a genuine user or a spam-sending bot.

Error 535 (Authentication failed) clearly refers to your login details. In this case, it’s worth resetting your password and making sure you’re using your full email address as your username. If, on the other hand, the program stops due to a ‘Timeout’, it is likely that a local firewall or your internet service provider is blocking communication. If your emails are being sent but end up in the recipients’ spam folders, it’s worth checking your domain against public blacklists, as your reputation may have been damaged by previous unsolicited messages.

Network issues and firewall settings

It often happens that, even though the software’s SMTP settings are correct, emails still fail to send. In such cases, the fault lies with the local network. The email protection feature of installed antivirus software can sometimes be overzealous and block outgoing traffic. Try temporarily disabling this feature whilst you’re testing. If a connection cannot be established on port 465, switch to port 587, as some networks prefer one type of encryption over another. You can also use a simple Telnet test from the command line to check whether your computer can reach the remote server via that port at all.

The role of DNS records: setting up SPF, DKIM and DMARC

By 2026, it will no longer be enough for just the SMTP parameters to be correct. Receiving servers (such as Gmail or Outlook.com) carry out strict DNS checks. If the SPF record is missing from your domain’s settings, the server will not be able to verify whether aWh’s servers are authorised to send emails on your behalf. A DKIM signature is a digital seal on the email that guarantees the content has not been altered in transit. DMARC policies, meanwhile, tell the recipient what action to take if the above two checks fail. These records can be automatically generated via the aWh cPanel hosting interface, which is crucial for a professional business image.

If you’re fed up with constant error messages and want to ensure your emails reach their destination, choose a reliable solution: try our professional dedicated email hosting service, which guarantees a high delivery rate.

Reliability is the cornerstone of business communication, and this can only be guaranteed by a provider with a stable technological infrastructure. aWh’s email hosting solutions are not merely simple mailboxes, but a complex ecosystem in which the deliverability of outgoing emails is a top priority. The SMTP settings detailed in previous sections can be configured quickly and easily with us, as we provide clear instructions and pre-configured parameters for all our customers via the cPanel interface. If you have specific requirements – for example, if you’re looking for a solution for high-volume newsletter campaigns – our dedicated SMTP servers ensure that your messages aren’t held up by the limitations of shared IP addresses.

The aWh Knowledge Base plays a central role in answering technical questions and troubleshooting. Here you’ll find detailed guides, illustrated with screenshots, for the most popular email clients, such as Outlook and Thunderbird, as well as for various mobile devices. You don’t need to spend hours searching the internet for the correct port numbers; here, you’ll find all the information you need in one place, ranging from encryption types to the correct configuration of DNS records, including SPF and DKIM settings.

Security and speed: aWh’s email infrastructure

Email speed is a critical factor for us. Our infrastructure is built on modern AMD Epyc processors and lightning-fast NVMe storage, which guarantees that managing accounts containing thousands of emails and sending emails takes just a matter of seconds. On the server side, we carry out continuous, 24-hour monitoring and proactive spam filtering, thereby effectively protecting our customers from unwanted content. Why choose aWh over the international giants? The answer lies in our direct approach and in-depth knowledge of local networks. We know exactly how to circumvent any restrictions imposed by local internet service providers to ensure secure email delivery.

We’ll help you get set up: Support

For many business owners, the most daunting task is the email account migration or configuring SMTP settings correctly for the first time. aWh’s team of experts takes this burden off your shoulders: we help with the complete migration of your data from other providers, so you don’t have to worry about losing any messages. We provide free technical support during the configuration process, whether it’s for a desktop client or automatic notifications from a WordPress-based online shop. To ensure a consistent and professional business image, we recommend that you set up your email service at the same time as registering your domain. This way, you can manage all technical settings via a single central interface, which significantly simplifies your daily workflow and enhances security in the long term.

Stabilise your business email with the right configuration

In 2026, using the correct SMTP settings will no longer be merely a technical detail, but the key to business credibility. The guide revealed that using secure ports (587 or 465), authenticating the outgoing server and correctly configuring DNS records (SPF, DKIM) are essential for ensuring emails reach their destination. By paying attention to these details, you can minimise the risk of emails being bounced back or ending up in the spam folder.

A stable email system is built on a foundation of reliable hardware infrastructure and expert technical support. With over 10 years’ professional experience and 99.9% uptime, aWh supports the growth of your business. Our team of experts is always on hand should you get stuck with technical details or server-side fine-tuning. Don’t let incorrect configuration slow down your business processes.

Choose professional email hosting with aWh! and enjoy all the benefits of seamless, encrypted communication. You can build your customer relationships with confidence, knowing that all your important messages will reach their destination instantly and securely.

Frequently Asked Questions

What is the SMTP server address at aWh?

By default, the outgoing server address in aWh’s systems follows the format mail.domainname.hu, where you must replace ‘domainname.hu’ with your own domain name registered with us. You can check this information at any time via the cPanel interface under ‘Manage Email Accounts’, where you will find all the parameters required for manual configuration.

Which is the most secure SMTP port in 2026?

In 2026, the most secure option is to use port 465 with SSL/TLS encryption, or port 587 supplemented with STARTTLS encryption. Both options ensure that your outgoing messages and authentication data are transmitted via an encrypted channel, protecting them from unauthorised interception.

Why am I getting an ‘Authentication Failed’ error message even though I’m using the correct password?

This error most commonly occurs if you have not entered your full email address in the username field, or if the encryption type does not match the specified port. Check that outgoing server authentication is enabled in your client program, and make sure that the password does not contain any accidental spaces after copying it.

Can I use a free SMTP service (e.g. Gmail) for my business emails?

Whilst technically possible, this solution is not recommended from a business perspective. Free service providers impose strict daily sending limits, and emails sent from a company domain but routed via a third-party server are far more likely to be caught by spam filters due to authentication discrepancies.

Why is my internet service provider blocking port 25?

Internet service providers restrict port 25 on residential networks for security reasons and to curb the flood of spam. As this is an older standard that does not require encryption, fraudsters can easily exploit it; therefore, when configuring modern SMTP settings, you should always select port 587 or 465.

How can I check if my SMTP server is working?

The simplest method is to use your email client’s ‘Test Settings’ function before saving. More advanced users can also check the server’s availability on a specific port via the command line using the Telnet or Ping commands, but sending a test email provides the most reliable indication of how the system is functioning.

What is the difference between SMTP and SMTPS?

SMTP is the basic protocol for transmitting messages, whilst SMTPS is the secure version, enhanced with SSL/TLS encryption. When using SMTPS, the connection is protected from the very start, which is a fundamental requirement for professional business communication and for maintaining a server’s reputation.

Do I need separate SMTP settings if I run an online shop?

Yes, for online shops, it is crucial that transactional emails – such as order confirmations and invoices – reach their intended recipients. This requires dedicated SMTP settings within the online shop’s platform; in the case of WordPress, you can achieve this using a third-party plugin, thereby avoiding the use of the unreliable PHP mail() function, which is often flagged as spam.

Back to the blog