Home Email Hosting

Email Hosting

Email Hosting
Dennis Nind
By Dennis Nind
28 articles

How to configure Email Routing and MX records for Google Mail

If you're planning to use your domain with Google Mail, you'll need to make a few configuration changes. This guide will walk you through the process. Setting Your Mail Routing to Remote Mail Exchanger 1. Access cPanel: Log into your cPanel account. 2. Navigate to Email Routing: Click 'Email Routing' in the EMAIL section of cPanel. 3. Select Your Domain: Choose the domain you'd like to use with Google Mail/GSuite from the dropdown list. 4. Select Remote Mail Exchanger: Click the 'Remote Mail Exchanger' radio button. 5. Save Changes: Click the 'Change' button to finish. Setting Up Google MX Records The next steps involve making changes to DNS records. We have a separate guide on using the cPanel DNS Zone Editor to make these changes. 1. Remove Existing MX Records: Remove any existing non-Google MX records. 2. Add Google MX Records: You can find the required Google's MX records here (external link opens in a new window). 3. Setup SPF, DKIM, and DMARC: These steps improve mail deliverability. Remove any existing non-Google SPF, DKIM, or DMARC DNS TXT records before adding the Google entries. The following Google guides detail the required SPF, DKIM, and DMARC entries: - Google article detailing SPF DNS entry details (external link opens in a new window) - Google article detailing DKIM DNS details (external link opens in a new window) - Google article on setting up DMARC entry (external link opens in a new window) Remember, if you're unsure about something, don't hesitate to reach out to our Brixly support team. We're here to help!

Last updated on Jun 12, 2025

How to solve '550 sender verify failed' error message?

Problem: When you try to send an e-mail message, you may receive the following SMTP error message: 550 Sender verify failed. Cause: This error message occurs when the sender's e-mail account does not exist in cPanel, or when the domain's MX entry records are misconfigured in cPanel. For example: suppose when you add a parked domain, an addon domain, or even an entire cPanel account (if you are a reseller) and If your domain's MX records (as set at the domain registrar) point to an external e-mail provider, you must also configure the MX entries in cPanel to use the external e-mail provider. Additionally, in cPanel you must create the e-mail accounts that you want to use to send messages. Solutions: Make sure the e-mail account you are using to send messages actually exists in cPanel, and that you are using the correct username and password for SMTP authentication.      1 Log in to cPanel.      2 Email accounts >> Manage       If the domain uses a remote e-mail provider, make sure the MX entries are set correctly in cPanel:      1 Log in to cPanel.      2 Under Zone editor >> select domain >>manage >>Email Routing configuration      3 select "RemoteMail Exchanger" 9ee3ce8eda2385672d2644d160c3c02e18a4a776ffd9566e77861a3feccd5698bcb4785fd1e70e88?t=d6c2741e31acc8d2470ae1c26bdc77c5 If the domain uses a local e-mail provider, make sure the routing has set to "Local Mail Exchanger"

Last updated on Jun 12, 2025

Creating Autoresponders Using cPanel

Autoresponders are a valuable tool for any business, saving you time by automatically sending a reply to any email sent to a specific address. They're ideal for acknowledging customer inquiries or letting people know you're unavailable. Here's how you can set up an autoresponder in cPanel. Creating an Autoresponder 1. Log into cPanel: Access your cPanel account. 2. Navigate to Autoresponders: Under the "Email" header, click the "Autoresponders" option. 3. Add Autoresponder: Click on "Add Autoresponder". 4. Configure Your Autoresponder: Fill in the necessary fields, including the email address for the autoresponder, the message you want to send, and the interval between responses. You can also set a specific start and stop time for the autoresponder. Autoresponder Configuration Options - Character Set: This is usually set to utf-8. It's recommended to leave this as default. - Interval: This controls the number of hours to wait between responses to the same email address. To avoid flooding inboxes with automatic replies, it's suggested to set this to "1" to wait one hour between automatic replies. - Email: This is the email address you are setting up the autoresponder for. - Domain: This option lets you decide the domain the autoresponder will be used for. - From: This will let you choose the "From" address your reply will be sent from. It's generally suggested to match this to the same email address you have entered in the "Email" option. - Subject: This is where you select the subject line of the reply. - HTML: Select this option if you want to include HTML in the body of your email. - Body: Your autoresponder message will go here. - Start: This decides when your autoresponder begins replying. This can either be immediate or set to a specific date/time. - Stop: This decides when your autoresponder stops replying. This can either be "Never" or a custom date/time. Using Tags in Your Autoresponder cPanel's autoresponder includes several custom tags that you can include in the body of your reply: - %subject%: The subject of the message sent to the autoresponder. - %from%: The name of the sender of the initial email received by the autoresponder if available. - %email%: The incoming email sender's address.

Last updated on Jun 12, 2025

Connecting an Email Client to a Mailbox

Introduction:  This Knowledge Base (KB) article provides a comprehensive guide on how to connect an email client to a cPanel or DirectAdmin mailbox. The process involves gathering the necessary information and configuring the email client settings. Please note that the steps may vary slightly depending on your specific email client software. SettingDescriptionRecommended PortsAccount TypeChoose between IMAP or POP3-Incoming Mail ServerServer that receives incoming emails143 (IMAP), 110 (POP3) or 993 (IMAP with SSL/TLS), 995 (POP3 with SSL/TLS)Outgoing Mail ServerServer that sends outgoing emails587 (STARTTLS) or 465 (SSL/TLS)SecurityEncryption options for secure connectionNone (unencrypted), SSL/TLS (encrypted)UsernameEmail account username-PasswordPassword for the email account- Step 1: Gather the Required Information  Before starting the setup process, ensure you have the following information at hand: - Email Address: The full email address you want to connect to (e.g., example@example.com). - Incoming Mail Server: The server that receives incoming emails, which can be an IP address or domain name (e.g., mail.example.com). - Outgoing Mail Server: The server that sends outgoing emails, also specified by an IP address or domain name. - Username: Your email account username (usually your full email address). - Password: The password associated with your email account. Step 2: Launch your Email Client  Open your preferred email client software on your computer, such as Microsoft Outlook, Mozilla Thunderbird, or Apple Mail. Step 3: Add a New Email Account 1. Locate the option to add a new email account within your email client. This option is typically found under the "Account Settings" or "Preferences" menu. 2. Click on it to begin the setup process. Step 4: Choose Account Type  Select the appropriate account type for your email client software. For cPanel and DirectAdmin mailboxes, the most common options are IMAP or POP3. IMAP allows email synchronization across multiple devices, while POP3 downloads emails to a single device. Step 5: Enter Your Account Information 1. Your Name: Enter your full name or the name you wish to display as the sender. 2. Email Address: Input your complete email address. 3. Password: Provide the password associated with your email account. 4. Incoming Mail Server: Enter the incoming mail server address provided by your hosting provider or system administrator. 5. Outgoing Mail Server: Specify the outgoing mail server address given by your hosting provider or system administrator. 6. Username: Input your email account username, usually your full email address. Step 6: Configure Server Ports and Security  Configure the server ports and security settings based on the recommendations below: Incoming Mail Server (IMAP): - Port: 143 (unencrypted) or 993 (SSL/TLS encrypted) - Security: None (unencrypted) or SSL/TLS (encrypted) Incoming Mail Server (POP3): - Port: 110 (unencrypted) or 995 (SSL/TLS encrypted) - Security: None (unencrypted) or SSL/TLS (encrypted) Outgoing Mail Server (SMTP): - Port: 587 (unencrypted) or 465 (SSL/TLS encrypted) - Security: STARTTLS (unencrypted) or SSL/TLS (encrypted) Step 7: Test the Connection  To ensure the configuration is accurate, follow these steps: 1. Click on the "Test Account Settings" or "Verify" button within your email client software. 2. This test will verify the connection to your cPanel or DirectAdmin mailbox. 3. If successful, you will see a confirmation message. Step 8: Finish the Setup  Upon successfully testing the connection, finalize the setup process: 1. Click on the "Finish" or "Done" button within your email client software. 2. Your email client should now be connected to your cPanel or DirectAdmin mailbox, allowing you to send and receive emails. Conclusion:  By following these steps, you can easily connect your email client to a cPanel or DirectAdmin mailbox. Remember to input the correct server details and ensure the port and security settings match the recommended configurations.

Last updated on Jun 12, 2025

How to Change Your Email Account Password or Mailbox Quota in cPanel

Managing your email account effectively includes tasks such as changing your email password and adjusting your mailbox quota. This guide will walk you through these processes using cPanel. Changing an Email Account Password 1. Access cPanel: Log into your cPanel account. If you do not know your direct cPanel login, you can also login through the Client Area > Services > My Services > and click "Launch cPanel" next to your hosting plan. 2. Navigate to Email Accounts: Within the cPanel Email section, click 'Email Accounts'. 3. Select Email Account: Click 'Manage' next to the email address you'd like to change. 4. Enter New Password: Enter a new password in the 'New Password' field. Clicking the eye icon hides or reveals the password as you type. The 'Generate' button will create a password for you - you can click the drop-down arrow to change the password length and included characters - you will need to copy the generated password from the 'Password' field to the 'Password Again' field before clicking 'Change Password'. 5. Update Email Settings: Click 'Update email settings' to complete the process. Changing an Email Account Quota Please note that disk space used by your mailbox counts towards your overall package disk limit. If a user is over quota, you can either have them remove email from their mailbox in their email client or webmail; or you can use the 'Email Disk Usage' tool to prune older emails from the server. 1. Access cPanel: Log into your cPanel account. 2. Navigate to Email Accounts: Within the cPanel Email section, click 'Email Accounts'. 3. Select Email Account: Click 'Manage' next to the email address you'd like to change. 4. Change Storage Space Quota: Change the 'Storage Space' quota or set to unlimited as required. Please note that disk space used by your mailbox counts towards your overall package disk limit. 5. Update Email Settings: Click 'Update email settings' to complete the process.

Last updated on Jun 12, 2025

Setting Up Branding and Custom URL for Your Brixly Workspace: A Detailed Guide

Brixly Workspace is a powerful tool that allows you to manage your email services. One of its features is the ability to set up branding for your workspace and add a custom URL. This guide will walk you through the process. Understanding Brixly Workspace Branding By default, Brixly Workspace is provided under an unbranded, white-label domain: https://mail.hostns.io. This URL can be used to access the webmail interface and as the incoming/outgoing mail servers to provide a secure SSL connection to the mail service. However, you may want to use your own URL, such as 'mail.yourdomain.com' or 'webmail.yourdomain.com'. To do this, you need to create an administrative user who can access the Workspace Branding configuration. Creating an Administrative User 1. Access Brixly Workspace: Go to the client area and navigate to 'Services' > 'My Services' > Select the Brixly Workspace service. 2. Manage Email Accounts: From here, select the 'Manage Email Accounts' option. 3. Create Email Account: Click 'Create Email Account', then enter 'admin' as the mailbox user. Make a note of the password you set, as you'll need it to access the administrative/branding interface of the Workspace. Accessing the Administrative Area 1. **Log in to Brixly Workspace: **Use the administrative user details to log in to the Brixly Workspace interface at https://mail.hostns.io. 2. Navigate to Branding: Once logged in, you'll see an additional option in the menu on the left-hand side: 'Admin' > 'Branding'. Configuring Your Branding and URL 1. Add Branding: Once you've selected 'Branding', click the '+' button in the bottom-right corner of your screen. 2. Enter Brand Details: On this screen, you can enter the details of your brand. The 'Host' is the URL that will be used for webmail access, and the 'SMTP / IMAP / POP3 Host' is the hostname that would be used for incoming/outgoing connections. You can use the same value for both if preferred. 3. Add CNAME Record: To use a custom record for host or SMTP hosts, you need to add a CNAME record to your DNS that points to mail.hostns.io. 4. Save Changes: After adding the CNAME record, save the changes. Within a few minutes, an SSL certificate will be automatically applied to the subdomain, and your branding configuration will be applied. By following these steps, you can set up branding for your Brixly Workspace and add a custom URL, providing a more personalized experience for your users.

Last updated on Jun 12, 2025

Brixly Workspace - How do I add an additional domain alias to my service?

The Brixly Workspace is purchased per-domain, with the ability to host mail under a single domain. However, you can add additional 'alias' addresses to the account. An example of this may be that you have 'brixly.uk' as the main domain of the service, however, you also want to have emails from a secondary domain, such as 'brixly.co.uk' or 'brixly.com'.  Please note, any alias domains added will also have access to emails from the main domain, so this is not to be used as a 'resold' service, or for hosting multiple clients. Each individual client would require their own package. To add a new Domain Alias Brixly Workspace / Email Hosting service, you can do so via our client area (https://client.brixly.uk). From here, click on 'Services -> My Services' and select the appropriate service. 72b892e4a06549a53fd27a3f83e2f579776ee69fe23c06653560e6821d20c0db696f753b64dcc340?t=fe9e1a2d77d74b3e3e00d1d86729eff8 Once you have selected the service, you will see a screen similar to the following... a765f1a2f6cf6b15fd863f4237aba965f00e980337df2fa52abc711c86cf6818184a9bc2b7e7101d?t=4388380d3209097db8dc739aab3b9a47 To add a new Domain Alias, scroll down and click 'Domain Aliases'... d2ab0117fde4c29001861b20d6506216644673bf6c25732bb342c1c1ef9dc593ffaf6be2568eb673?t=894132f646e248a4a86ab268612b1b36 Click 'Create Domain Alias' from here and follow the steps provided.  At this point, we would recommend setting up an 'Email Forwarder' for your new alias domain so that you can forward any incoming mail to the 'Domain Alias' to the relevant mailbox under the primary domain.  To do this, click 'Email Forwarders' on the screen above, and follow the steps provided. 

Last updated on Jun 12, 2025

What are my Email Sending Limits / How many emails can I send from Brixly?

All outbound emails are delivered through a premium relay service, included free of charge with every account. This ensures reliable delivery, even if your hosting IP address is blacklisted. Hourly Sending Limits by Hosting Plan Hourly email sending limits vary by service. These limits apply per domain unless stated otherwise: - cPanel Reseller Hosting: 150 emails/hour - DirectAdmin Reseller Hosting: 150 emails/hour - Infinity Hosting: 150 emails/hour - Infinity+ Hosting: 150 emails/hour - Brixly Workspace: 250 emails/hour - Premium Hosting - Pro: 150 emails/hour - Premium Hosting - Business: 250 emails/hour - Premium Hosting - Enterprise: 350 emails/hour - Premium Hosting - Platinum: 500 emails/hour - Premium Reseller: 250 emails/hour Additional Sending Policies - A daily sending limit of 4,000 emails per domain applies across all plans and tiers. - We do not impose a global daily limit per account, only per domain. - A 25% buffer is allowed above hourly limits. Messages exceeding this buffer will be queued. - Exceeding the hourly or daily limit may result in outbound emails being rejected or a temporary block on sending. - If an account sends to 250 or more recipients in a one-hour period, a warning email will be issued and a block may be applied. - If more than 500 emails are sent in a 24-hour period from one domain, a warning may be issued, and a block may follow (within the 4,000 daily limit). - Emails sent through PHP scripts or Mailman mailing lists count toward the domain’s hourly and daily quota. - Email marketing is not allowed using our mail systems. Use a third-party provider (e.g. MailChimp, SendGrid) for newsletters and bulk mail. - Email archiving is not supported, and mailbox storage is subject to our Fair Usage Policy (see our [Terms and Conditions] for full details).

Last updated on Jul 21, 2025

How to Obtain Email Headers: A Step-by-Step Guide

Email headers provide valuable information about the journey of an email from the sender's server to the recipient's inbox. They can be useful for troubleshooting email delivery issues or for identifying the source of spam emails. This guide will show you how to obtain the email headers for a particular email in various email clients. Gmail 1. Open the Email: Log into your Gmail account and open the email for which you want to see the headers. 2. Click on the Three Dots: In the top right corner of the email, click on the three vertical dots to open a drop-down menu. 3. Select 'Show Original': From the drop-down menu, select 'Show original'. This will open a new tab displaying the email headers at the top. Outlook 1. Open the Email: Log into your Outlook account and open the email for which you want to see the headers. 2. Click on the Three Dots: In the top right corner of the email, click on the three horizontal dots to open a drop-down menu. 3. Select 'View Message Source': From the drop-down menu, select 'View message source'. This will open a new tab displaying the email headers. Apple Mail 1. Open the Email: Open Apple Mail and select the email for which you want to see the headers. 2. Click on 'View': In the menu bar at the top of the screen, click on 'View'. 3. Select 'Message': From the drop-down menu, hover over 'Message' to open a side menu. 4. Click on 'All Headers': From the side menu, click on 'All Headers'. The headers will now be displayed in the email window. Thunderbird 1. Open the Email: Open Thunderbird and select the email for which you want to see the headers. 2. Click on 'View': In the menu bar at the top of the screen, click on 'View'. 3. Select 'Headers': From the drop-down menu, hover over 'Headers' to open a side menu. 4. Click on 'All': From the side menu, click on 'All'. The headers will now be displayed in the email window. Remember, email headers can contain sensitive information, so be careful when sharing them. If you're sending headers to a support team for troubleshooting, make sure you trust the recipient and that your method of sharing is secure.

Last updated on Jun 12, 2025

Email – What is the difference between SSL, TLS, and STARTTLS?

Overview The terms SSL, TLS, and STARTTLS are often used in relation to securing a connection, but not everyone knows what these mean. This article should help provide some basic information about each term. SSL SSL stands for “Secure Sockets Layer”, and utilized SSL certificates to help identify the server you are connecting to and start encryption. This was one of the recommended protocols used by services that required encryption until 2015. In 2015, the latest version of the SSL protocol (SSL v3.0) was considered insecure due to a flaw that could allow secret information to be read (called the POODLE attack). Because of this, no versions of the SSL encryption protocols have been enabled by default since cPanel 11.46. Although the protocols specifically defined as SSL are no longer in general use, the term “SSL” can still be used to refer to a secured connection that uses either the SSL or TLS protocols. TLS TLS stands for “Transport Layer Security” and is the successor for the SSL protocol. As the successor, it is still compatible with SSL certificates. TLS has several similarities with SSL, but it had enough internal differences that the protocol was given its own name instead of SSL v4. With this change, the developers also switched the way versioning was done and only change the minor version with each new release. Version 1.0 of TLS is also considered insecure at this time (due to the BEAST exploit) and should be avoided if possible. As of cPanel 68, we enable only TLS 1.2 by default. This helps ensure a secure connection to the server and its services. TLS 1.3 has been proposed, and future secured connections will likely continue to utilize newer versions of the TLS protocol. STARTTLS Unlike the previous items, STARTTLS is not a protocol, but rather a command recognized by other protocols (like SMTP, IMAP, and POP3 for example). This command is used to take an existing non-encrypted connection and encrypt it without requiring a separate secure port. This can use any encryption protocol that is enabled on the server, and it is not necessarily limited to TLS. Usage Connecting to a service implicitly encrypted by SSL or TLS is done using a separate port. For example, port 465 is used for encrypted SMTP connections and port 993 is used for encrypted IMAP connections. When the initial connection is made, the server itself and the connecting client negotiate on which encryption protocol and version to use. Once the negotiation is complete, all data exchanged between the server and client is encrypted using the agreed upon format. Connecting to a non-encrypted service also uses its own defined port. For example, port 25 is used for non-encrypted SMTP connections and port 143 is used for non-encrypted IMAP connections. This connection is sent via plain text to the service, and thus considered insecure. It is possible, however, to upgrade this connection to a secure one using the STARTTLS command. Once the command is called by the connecting client, the same negotiation regarding the protocols takes place between the client and server. Upon successful negotiation, the data between the server and client is encrypted. This connection will continue to utilize the standard port, and does not force a change to the SSL port. Summary SSL (Secure Sockets Layer) and TLS (Transport Layer Security) are both encryption protocols used for encrypting the data between services. All versions of SSL have been deprecated and are considered insecure at this time. TLS is the newer protocol, and (at the time of writing) we would recommend using TLS 1.2 on your production servers. STARTTLS is a command used to upgrade an existing standard (non-encrypted) connection into an encrypted one. This allows for secure connections over the non-encrypted port for a service.    

Last updated on Jun 12, 2025

Understanding and Resolving the "550 This message was classified as SPAM" Error

When sending emails, you may occasionally encounter an error message stating, "550 This message was classified as SPAM and may not be delivered." This error occurs when the email you're trying to send is flagged by our spam detection procedures. This guide will help you understand why this happens and how to resolve it. Why Does This Error Occur? To combat the global issue of spam, we have implemented spam detection procedures on all emails before they leave our servers. Each email is evaluated and rated according to spam rules to determine how likely they are to be actual spam. Emails that fail the test are returned to the original sender with the "550 This message was classified as SPAM" error message. We screen outbound emails to help preserve the reputation of our server’s IP addresses. Once a mail IP gets enough spam complaints against it, it can be reported to a company that maintains a blacklist. Any email server that subscribes to that particular service will then block any incoming email from that IP address. How to Resolve the Error If you encounter this error, there are a couple of solutions you can try: Solution #1 – Enable SMTP Authentication in Outlook If you are using the Microsoft Outlook email client, not having SMTP Authentication will cause several points to be added to the spam score. This can cause emails that otherwise would be allowed through to be classified as spam. You can enable SMTP Authentication by following the instructions in our Invalid HELO name article. Solution #2 – Evaluate Email Content As our outgoing servers are using a spam evaluation software set at the most lenient levels, it is difficult for your emails to be tagged as spam and prevented from going out unless they have a lot of features of a spam message. If you are getting caught by the filter, evaluate both the title and body content of the message to ensure there are few, if any, references to popular spamming terms. By understanding the cause of the "550 This message was classified as SPAM" error and following these solutions, you can improve your email deliverability and reduce the likelihood of your messages being incorrectly marked as spam.

Last updated on Jun 12, 2025

Understanding and Resolving the "550 Please turn on SMTP Authentication" Error

When sending emails, you may occasionally encounter an error message stating, "550 Please turn on SMTP Authentication." This error occurs when the email you're trying to send is flagged by our spam detection procedures. This guide will help you understand why this happens and how to resolve it. Why Does This Error Occur? SMTP authentication is a security measure used by mail servers to verify that incoming messages are from authorized users. If SMTP authentication is not enabled, the server may reject incoming messages, resulting in the "550 Please turn on SMTP Authentication" error. How to Enable SMTP Authentication Enabling SMTP authentication can often resolve this issue. Here's how to do it in various email clients: Outlook Express 1. From the Tools menu, choose “Accounts.” 2. Select the “Mail” tab. 3. Double-click the email account you need to update. 4. Select the “Servers” tab. 5. Check the box next to “My Server Requires Authentication.” 6. Click “Ok.” Outlook ’98 and 2000 1. From the Tools menu, choose “Accounts.” 2. Select email account you need to update. 3. Click “Properties.” 4. Select the “Servers” tab. 5. Check the box next to “My Server Requires Authentication.” 6. Click “Ok.” Outlook 2002 and 2003 1. From the Tools menu, select “Email Accounts.” 2. Select “View or change existing email accounts” and click “Next.” 3. Select your Email account and click the “Change” button on the right. 4. Click the “More Settings” button in the bottom-right corner of the E-Mail Accounts window. 5. In the Internet Email Settings window, click the “Outgoing Server” tab. 6. Check the box next to “My outgoing server (SMTP) requires authentication.” Outlook 2007 1. From the Tools menu, select “Account Settings.” 2. Select your Email account and click the “Change” button. 3. Click the “More Settings” button in the bottom-right corner of the E-Mail Accounts window. 4. In the Internet Email Settings window, click the “Outgoing Server” tab. 5. Check that the box next to “My outgoing server (SMTP) requires authentication” is checked and “use same settings as my incoming mail server” is selected. Outlook 2010 1. From the File menu, select “Info” and choose “Account Settings.” 2. Select your Email account and click the “Change” button. 3. Click the “More Settings…” button in the bottom-right corner of the E-Mail Accounts window. 4. In the Internet Email Settings window, click the “Outgoing Server” tab. 5. Check that the box next to “My outgoing server (SMTP) requires authentication” is checked and “use same settings as my incoming mail server” is selected. Mac Mail for OS X 1. Open Mac Mail. 2. From the “Mail” menu, choose “Preferences.” 3. Click the “Accounts” icon at the top of the window. 4. Next to “Outgoing Mail Server (SMTP):” click on the drop-down menu and go to “Edit SMTP Server List” 5. Check to make sure you have the correct SMTP server selected at the top. 6. Verify that “Authentication” is set to “Password.” 7. If the “User Name” and “Password” fields are not set, enter your full email address as the username, and your password. 8. Click “Ok.” 9. Close the accounts window by clicking on the red circlein the far upper left hand corner of the “Accounts” window. 10. Mac Mail will ask you if you wish to save your changes, make sure to click the “Save” button. Other Possible Causes of the 550 Error While enabling SMTP authentication can often resolve this issue, there are other potential causes to consider: Improper DNS Configuration Domain migrations can sometimes lead to issues with SMTP authentication. If the migration is not properly done, it can happen that the customer’s MX setting does not get updated to the new server. This could cause the mails to be sent to the old server, and the connections will be rejected. Another possibility is when the customer uses a third-party mail solution such as Google Apps as their mail exchange. For mail servers that validate email sending domains using SPF records, this can pose an issue if the records are not updated to allow these external MX to deliver mails. Mail server will reject the mails from those domains citing authentication issues. Missing Local Domain Configuration For a domain’s mail to work, it should have entries in the corresponding mail server config files. For instance, in Exim servers, there are two files – localdomains and remotedomains – to determine the domain’s mail server. An account that uses local mail server should have its domain name listed in localdomains file. For domains with remote MX, there has to be entry in remotedomains file. Due to any configuration mistake, the required entries can get messed up in these config files, leading to mail errors such as '550 Please turn on SMTP Authentication'. To resolve it, we do a custom configuration allowing the mail gateway to relay mails to the destined mail server. By understanding the cause of the "550 Please turn on SMTP Authentication" error and following these solutions, you can improve your email deliverability and reduce the likelihood of your messages being incorrectly marked as spam.

Last updated on Jun 12, 2025

Why are my emails being marked as SPAM?

Emails being marked as spam is a common issue faced by many users. This can occur due to various reasons, from the originating domain name being blacklisted to the recipient mail host requiring additional validation. This guide will help you understand why this happens and how to resolve it. Common Reasons for Emails Being Marked as Spam Your Domain is Blacklisted If your domain name has been blacklisted, it can cause issues with email delivery. You can check if your domain has been blacklisted using tools like MX Toolbox. If your domain is blacklisted, you would need to find out the reason behind this and resolve it as a matter of urgency to avoid your messages being marked as spam. Your Server's IP Address is Blacklisted If your server's IP address has been blacklisted, the receiving mailbox may consider your message as spam. This is a common problem in shared hosting environments, as your IP address is shared with multiple users. If you have any issues with an IP RBL causing delivery issues, please reach out to our support team for assistance.  The Recipient Mail Host Requires Additional Validation The recipient mail host might require additional validation, such as the existence of SPF or DKIM for your domain. You can use online services like Mail Tester or Experte's Spam Checker to diagnose if this is the cause of your emails being marked as spam. Custom Anti-Spam Filters Applied by the Recipient Email Host Custom anti-spam filters applied by the recipient email host might also end up rejecting an email based on its contents (subject, body, attachments, etc.). This issue would need to be addressed by the recipient, to ensure the contents of your emails are no longer filtered. Diagnosing Why a Message Has Been Marked as Spam If you are still unsure as to why your emails are being marked as spam, ask the recipient to provide you with the email headers for the email received. When raising a support ticket regarding your outbound messages being received as spam by a third party, please ensure you also provide the details of the email, such as the sender, recipient, subject, and time/date. You must also include the email headers for us to be able to attempt to diagnose the cause for the message being received as spam. Please note, however, that not all providers will store sufficient detail within the email headers themselves and may need to be raised with the third-party/recipient provider for further information. Using Mail-Tester.com Mail Tester is an online service that provides a comprehensive analysis of your emails. It checks for potential issues that could lead to your emails being marked as spam, such as problems with your SPF records, DKIM signature, and content. To use Mail Tester: 1. Visit the Mail Tester website. 2. You will be provided with a temporary email address. Send a test email to this address. 3. Go back to the Mail Tester website and click on "Then check your score." 4. You will be provided with a score out of 10 and a detailed report of your email. The report will inform you whether the issue is relating to SPF under the 'Authentication' section. Note: when using mail-tester.com, please ensure you enter some valid content in your message being sent, to ensure the score isn’t negatively impacted due to missing or spam-related content. By using Mail Tester, you can gain insights into why your emails might be marked as spam and take steps to improve your email deliverability. By understanding the cause of your emails being marked as spam and following these solutions, you can improve your email deliverability and reduce the likelihood of your messages being incorrectly marked as spam.

Last updated on Jun 12, 2025

Enabling PHPMail() on Your Account

PHPMail() is a function used by PHP to send emails directly from a server. However, due to its frequent misuse by malicious users to send spam and other unsolicited emails, we have decided to disable this function by default. This measure is taken to protect the reputation of our IP addresses and network and to ensure that your domains stay off RBLs and blacklists. Why We Recommend Against Using PHPMail() When an email is sent from a PHP application using PHP mail, such as a contact form, the message is relayed via the server hostname. However, your PHP application will likely be set to send emails from an alternative email address. Many recipient mailboxes recognise this discrepancy as 'spoofing', which may flag the message as SPAM. Using SMTP Instead of PHPMail() We recommend our customers to use an email library or plugin to send emails via SMTP. Enabling PHPMail() on Your Account Important: Sending messages via PHPMail() have an incredibly low chance of delivery, and therefore enabling PHPMail() over utilizing SMTP is strongly discouraged. While we strongly discourage it, if you require PHP mail to be enabled on your domain, you can do so via the PHP Selector in cPanel. Here are the steps: 1. Login to your cPanel. 2. Click 'Select PHP Version'. 3. Select 'Options'. 4. Change 'sendmail_path' to '/usr/sbin/sendmail -t -i'. Please note that enabling PHPMail() may increase the likelihood of your emails being marked as spam by recipient mailboxes. Therefore, it's recommended to use SMTP for sending emails whenever possible.

Last updated on Jun 12, 2025

Why am I not able to send mail via my PHP script or application?

If you're having trouble sending emails from your PHP script or application, it could be due to the way your application is configured to send emails. By default, many PHP applications use a protocol called PHPMail(), which can lead to several issues, including emails being marked as spam. This guide will help you understand why this happens and how to resolve it. Understanding PHPMail() PHPMail() is a function used by PHP to send emails directly from a server. However, it has a number of disadvantages and is often the reason why emails end up in the recipient's spam folder. When an email is sent from a PHP application using PHPMail(), it uses an email address similar to youruser@your.servername.com. However, your application's configuration might be set to send emails from a different, more user-friendly email address, such as you@yourdomain.com. This discrepancy can be recognized as 'spoofing' by many recipient mailboxes, which may flag the message as spam. Due to these issues, PHPMail() is disabled on our servers by default. Using SMTP Instead of PHPMail() We recommend using SMTP (Simple Mail Transfer Protocol) to relay all messages from your PHP script or application. SMTP is a protocol for sending emails reliably and efficiently. SMTP uses proper authentication, which increases the chances of your emails being successfully delivered to the recipient's inbox. It also allows you to send emails from a user-friendly email address without being flagged as spam. How to Configure Your Application to Use SMTP The process of configuring your application to use SMTP instead of PHPMail() will depend on the specific application you're using. Many applications have settings or plugins that allow you to easily switch to SMTP. You'll typically need to provide the SMTP server name, port, and authentication details. By understanding the cause of your email sending issues and switching to SMTP, you can improve your email deliverability and reduce the likelihood of your messages being incorrectly marked as spam.

Last updated on Jun 12, 2025

The cPanel Default Address and Why Catch-All Mailboxes Are a Bad Idea

When managing your email accounts through cPanel, you might come across the concept of a "catch-all" mailbox. While it might seem convenient to have all emails sent to non-existent addresses on your domain redirected to a single mailbox, this practice can lead to several issues. Understanding the Default Settings By default, your cPanel account is set to reject emails sent to an address that you have not already set up with a mailbox or forwarder. These emails are referred to as "unroutable." We strongly recommend leaving these default settings as they are. The Problem with Catch-All Addresses While it's possible to redirect all unroutable emails to a catch-all address, we advise against this practice. Catch-all addresses are prime targets for spammers. Once your domain becomes known, spammers will target random usernames at your domain. This makes it harder for us to filter spam, as your account will no longer reject emails for unknown recipients. If You Must Use a Catch-All Address If using a catch-all email address is unavoidable for you, and you wish to read such emails using a third-party system such as Hotmail, Gmail, Yahoo, etc., we recommend you configure a LOCAL mailbox to receive the messages. Then, collect mail from that mailbox using the third-party's POP3 collection tools. 1. Create Your Catch-All Mailbox: Follow the guide on how to create a mailbox in cPanel to create your catch-all mailbox. A catch-all mailbox is no different from any other mailbox. 2. Set the Default Address: Click the Default Address icon in the EMAIL section of cPanel. Under the Default Address Maintenance heading, select your domain from the drop-down list and then select the Forward to email address radio button. Enter the address of your catch-all mailbox in the Forward to email address box. Click the Change button to save your changes. 3. Read Your Catch-All Email: If you wish to read your catch-all email using a third-party system such as Hotmail, Gmail, Yahoo, etc., then you must use the tools made available to you on their system. A Note About the System Account We strongly recommend you do not forward all mail to the system account unless you have a very good reason. Again, this option will make your account a prime target for spammers. Remember, if you're unsure about something, don't hesitate to reach out to our support team. We're here to help!

Last updated on Jun 12, 2025

How do I configure my 'Email Routing' in cPanel?

Mail Exchanger Options Explained: Unless you have a particular setup that needs these explicitly stated, you are able to select "Automatically Detect Configuration". Please note, however, this setting can cause inconsistencies - it would always be recommended to explicitly select one of the alternative options.  - **Local Mail Exchanger: **Handle all mail sent from the server to this domain locally; i.e., deliver it to the mailbox that is on the server rather than remote mail service. - **Backup Mail Exchanger: **Handle all emails like a remote mail exchanger unless the remote service is unreachable, in that case, handle it like a local mail exchanger. (For example, if you have Google as the domain's mail service, send the emails to Google’s servers like the remote mail exchanger. If, for some reason, Google’s servers are inaccessible, then deliver the mail locally, as in the local mail exchanger option.) - Remote Mail Exchanger: Handle all mail sent to this domain remotely, i.e., deliver it to the mail service determined by the domain’s MX record. (For example, if you have Google set up as your mail service, deliver the emails to the mailbox on Google’s servers rather than your local mailbox.) What is Email Routing?  Email routing is a feature in cPanel that allows you, as a domain owner, to choose how your incoming Email messages are processed, or routed, by the Email server.  This can either be your hosting provider’s local Email server or the Email server of your chosen Email provider, e.g. G Suite, Office365 or others.  How to change Email routing in cPanel  1. log in to your cPanel account.  2. Navigate to the Email section and click on Email Routing.  210bccf880671c00659b839981ec7689ba2ff18469e737fe63e18da618fea5346c49c60ec711c87f?t=4ae567d971c466801c82f2f0dcb06436 3. From the Domain section, choose the domain you wish to apply these settings for. If you only have one domain, it will be selected automatically.  4. From the Configure Email Routing section, you can see the four available options. Click on the small arrows for each one to read each description. 5. Choose the desired routing option from the list and click on Change to enable it.  If you still have questions, please get in touch with us.

Last updated on Jun 12, 2025

Enmail Gateway - Managing Outgoing Emails in cPanel

The Enmail Gateway is a powerful tool integrated into cPanel to help you monitor, manage, and control your outgoing emails. With detailed logs, quarantine management, and actionable insights, the Enmail Gateway ensures better transparency and control over your email delivery processes. This article will guide you through accessing and using the Enmail Gateway interface. Accessing the Enmail Gateway 1. Log in to your cPanel account. 2. Navigate to the Email section. 3. Click on Enmail - Outgoing Emails. When you first access the Enmail Gateway, you will be presented with a list of domains associated with your account. 4. Select a domain to load its email logs and delivery data. The interface will then display detailed metrics and logs for the chosen domain. Understanding the Dashboard After selecting a domain, you will see: - Delivery Metrics: - Total Sends (30 Days) - Successful Sends (30 Days) - Failed Sends (30 Days) - Success Rate (30 Days) - Email Logs: A detailed view of individual email deliveries, including: - ID: Unique identifier for each email. - Date: Timestamp of when the email was sent. - Sender: The sender's email address. - Recipient: The recipient's email address. - Subject: The subject line of the email. - Details: Status information, including explanations for failures or quarantines. - Actions: Options for managing quarantined emails. Using the Enmail Gateway Releasing Quarantined Emails If an email is flagged as potential SPAM, it may be quarantined. Quarantined emails are those that exceed a scoring threshold but are not blocked outright. To release a quarantined email: 1. Locate the email in the log. 2. Click the Release button in the “Action” column. - This will immediately re-deliver the email. - The system will also automatically learn the email as HAM (non-SPAM), refining future SPAM filtering rules. Note: Emails exceeding the quarantine threshold will be blocked entirely and cannot be released. Reporting an Issue to Support If you encounter an issue with an email, you can report it to our support team for further investigation: 1. Click the copy icon next to the email's ID in the log. - This copies all relevant details, including the email ID and delivery information. 1. Share the copied details with our support team when raising a ticket. Failed Email Deliveries For emails that failed to send, the “Details” column provides an explanation of the issue in plain language. Use this information to: - Troubleshoot and resolve the issue. - Take corrective action, such as updating SPF records, verifying recipient addresses, or ensuring email content complies with SPAM policies. Performance Notes - Data Loading: The Enmail Gateway processes large amounts of data, so the interface may take some time to load. Please be patient as the logs and metrics populate. - Domain Selection: Ensure you have selected the correct domain to view the corresponding logs and delivery data. - Real-Time Updates: The logs are updated in real-time, allowing you to monitor the status of recent email deliveries. Key Features of the Enmail Gateway - Domain-Based Insights: Select domains to view their specific email delivery logs and metrics. - Detailed Visibility: View comprehensive logs of all outgoing emails, including successes, quarantines, and failures. - Quarantine Management: Release quarantined messages and train the system to improve filtering accuracy. - Clear Explanations: Understand why emails failed and take action with easy-to-read failure messages. - Support Integration: Quickly report issues to support by copying the email ID and related details. Conclusion The Enmail Gateway is a significant step forward in email delivery management, offering greater transparency, control, and troubleshooting tools. With the ability to release quarantined messages, investigate delivery failures, and train the SPAM filter, you can ensure smooth and reliable email communication. If you have additional questions or need assistance, please contact our support team.

Last updated on Jun 12, 2025

Understanding SPF Records for Email Deliverability

Understanding SPF Records for Email Deliverability Description: This guide explains what SPF records are, why they're important for email authentication, and how Brixly automatically manages SPF configurations for customers using our nameservers. It’s tailored for shared hosting clients with basic technical knowledge. What Is an SPF Record? SPF (Sender Policy Framework) is a type of DNS record that helps prevent email spoofing and improves your email deliverability. It tells recipient mail servers which servers are allowed to send emails on behalf of your domain. Why is SPF important? - Protects your domain from being used in spam or phishing attacks. - Reduces the risk of your legitimate emails being marked as spam. - Increases trust in emails sent from your domain. How SPF Works When you send an email, the recipient’s mail server checks your domain’s SPF record. If the email comes from an approved server, it’s more likely to be delivered to the inbox. If not, it may be rejected or sent to spam. How Brixly Manages SPF Records If you use Brixly’s nameservers for your domain, SPF records are automatically managed for you. This means: - Default SPF records are set up to authorize Brixly mail servers. - No manual configuration is required for standard email usage. - Our system updates SPF records automatically if changes are needed. Example of a Default Brixly SPF Record: v=spf1 a mx ip4:your_server_ip include:spf.hostns.io -all Replace your_server_ip with the IP address in your hosting welcome email. Checking or Updating Your SPF Record in cPanel If you need to check or add custom SPF entries (e.g., third-party mail services), you can do so via cPanel: Step 1: Access DNS Zone Editor 1. Log in to your cPanel account. 2. Go to the Domains section. 3. Click Zone Editor. Step 2: Locate or Edit Your SPF Record - Find your domain and click Manage. - Look for an existing TXT record starting with v=spf1. - To edit: Click Edit next to the record. - To add: Click Add Record and select TXT. Step 3: Update the SPF Value - Make changes as needed (see below for adding services). - Save the record. Example: Adding Google Workspace to SPF v=spf1 a mx ip4:your_server_ip include:spf.hostns.io include:_spf.google.com -all Always keep -all at the end. Troubleshooting SPF Issues My Emails Are Still Marked as Spam - Check SPF Syntax: Only one SPF record is allowed per domain. Merge multiple entries into a single record. - Propagation: DNS changes can take up to 24 hours to update globally. - Other Authentication: Ensure you also have DKIM and DMARC records configured for best results. How to Test Your SPF Record You can use free online tools such as MXToolbox SPF Checker to verify your SPF record. Frequently Asked Questions Do I need to set up SPF if I use only Brixly’s email? No, if you use our nameservers, it’s automatically managed. What if I use another email provider? You’ll need to update your SPF record to include their servers. Refer to their instructions and merge the necessary include: statements into your SPF. Need More Help? If you have issues or questions not covered here, please submit a support ticket from your Brixly client area. Our team is here to assist you. Last updated: June 2025

Last updated on Jul 24, 2025

Troubleshooting Email Client Configuration: Common Setup and Migration Errors

Troubleshooting Email Client Configuration: Common Setup and Migration Errors Description: This comprehensive guide will help you identify and resolve common email client configuration issues during domain transfers or email migrations. It covers IMAP/SMTP settings, authentication errors, and compatibility problems, tailored for shared hosting customers using cPanel. Table of Contents - Introduction - Essential Email Client Settings - Step-by-Step: Configuring Your Email Client - Common Configuration Errors & Solutions - Troubleshooting Migration Issues - Helpful Tools & Where to Find Settings - Further Assistance Introduction When transferring domains or migrating email accounts, you may encounter issues connecting your email client (such as Outlook, Thunderbird, Apple Mail) to your mailbox. This guide provides practical solutions for the most frequent problems faced by shared hosting users. Essential Email Client Settings Before configuring your email client, gather the following details from your cPanel or welcome email: | Setting | Description | Common Value/Example | |-----------------------|-------------------------------|--------------------------------------------------| | Email Address | Full address | user@yourdomain.com | | Username | Email address (usually same) | user@yourdomain.com | | Password | Email password | (set in cPanel) | | Incoming Server | Server for incoming mail | mail.yourdomain.com or server hostname | | IMAP Port | For IMAP (recommended) | 993 (SSL/TLS) or 143 (non-SSL) | | POP3 Port | For POP3 | 995 (SSL/TLS) or 110 (non-SSL) | | Outgoing Server | Server for outgoing mail | mail.yourdomain.com or server hostname | | SMTP Port | For sending mail | 465 (SSL/TLS) or 587 (STARTTLS) | | Encryption | Connection security | SSL/TLS or STARTTLS | Step-by-Step: Configuring Your Email Client 1. Log in to cPanel - Navigate to Email Accounts. - Locate your email address and click Set Up Mail Client for configuration details. 2. Open Your Email Client (e.g., Outlook, Thunderbird). 3. Add a New Account. - Choose Manual Setup if available. 4. Enter Account Information: - Name, Email Address, and Password. 5. Specify Incoming Server Settings: - Choose IMAP (recommended) or POP3. - Use the correct server name and port (see table above). 6. Specify Outgoing Server (SMTP) Settings: - Enter server name and port. - Enable authentication (use same login as incoming). 7. Set Encryption Method: - Choose SSL/TLS or STARTTLS if offered. 8. Finish Setup and Test Connection. Example (IMAP, SSL): Incoming Server (IMAP): mail.yourdomain.com Port: 993 Encryption: SSL/TLS Outgoing Server (SMTP): mail.yourdomain.com Port: 465 Encryption: SSL/TLS Authentication: Yes (same as incoming) Common Configuration Errors & Solutions 1. Authentication Failed / Incorrect Password - Solution: - Double-check the password in cPanel (Email Accounts > Manage > Change Password). - Ensure you are using your full email address as the username. 2. Cannot Connect to Server / Server Not Responding - Solution: - Verify you are using the correct mail server (mail.yourdomain.com or server hostname). - Ensure your domain's DNS records (MX, A, CNAME) point to your hosting server. - Try connecting via webmail to confirm mailbox works: https://yourdomain.com/webmail 3. SMTP Authentication Required / "Please turn on SMTP Authentication" - Solution: - In your email client, ensure “My outgoing server (SMTP) requires authentication” is enabled. - Use the same username and password for SMTP as for IMAP/POP3. 4. SSL Certificate Warnings - Solution: - Use the server hostname (found in cPanel or your welcome email) instead of your domain if SSL mismatch occurs. - Accept the certificate if you trust the server. 5. Mails Not Received After Migration - Solution: - Confirm MX records are updated to the new hosting provider. (Check in cPanel > Zone Editor) - Propagation may take up to 24 hours. 6. Emails Missing After Migration - Solution: - Use the IMAP Migration tool in cPanel’s Migration Center. - Ensure all email accounts are created on the new server before migrating. Troubleshooting Migration Issues Emails Delivering to Old Server - Check: - MX records may still point to the old server. - Use online tools like MXToolbox to verify. Email Client Still Shows Old Emails Only - Check: - Remove and re-add the account in your email client after migration. - Use IMAP for real-time sync with the server. "550 Sender Verify Failed" or "Relaying Denied" - Solution: - Ensure correct SMTP authentication is enabled. - If using third-party providers (e.g., Google Workspace), update SPF records accordingly. Helpful Tools & Where to Find Settings - cPanel: - Email account creation, password resets, and configuration details. - Webmail: - Access email directly: https://yourdomain.com/webmail - File Manager: - (Advanced) Download/upload mailbox files if needed. - Migration Center: - For IMAP email migrations. Further Assistance If you continue to experience issues: - Double-check all settings and DNS records. - Refer to our Email Hosting Knowledge Base for more guides. - Open a support ticket through your client area with detailed steps you’ve taken, error messages, and affected email addresses for efficient help. By following this guide, most email client configuration and migration issues can be resolved independently. For persistent issues, our support team is ready to assist!

Last updated on Jul 24, 2025

Troubleshooting Email Spam Rejection: How to Improve Domain Email Deliverability

Troubleshooting Email Spam Rejection: How to Improve Domain Email Deliverability Description: A comprehensive guide designed for Brixly shared hosting customers to identify and resolve issues that cause emails to be marked as spam or rejected. This article details SPF record setup, essential email authentication methods, best practices, and practical troubleshooting steps using tools such as cPanel and Mail Tester. Table of Contents - Understanding Email Spam Filtering - How Brixly Relays Outbound Email - SPF Records: What They Are and How to Set Them Up - Other Authentication Methods: DKIM & DMARC - General Best Practices for Avoiding Spam Filtering - Using Mail-Tester.com for Diagnosis - Troubleshooting Common Issues - When to Contact Support Understanding Email Spam Filtering Modern email providers use advanced spam filtering to protect users from unwanted messages. If your emails are ending up in spam folders or being outright rejected, typical causes include: - Missing or misconfigured authentication records (SPF, DKIM, DMARC) - Blacklisted server or domain IP addresses - Problematic sending habits or email content - Attachments, links, or formatting that trigger spam filters By understanding these causes, you can take targeted action to improve your email deliverability. How Brixly Relays Outbound Email All outbound emails from domains hosted on Brixly’s shared platform are processed through our secure email infrastructure. This setup ensures that: - Emails are dispatched using both your domain’s settings and our mail servers - Our systems enforce robust anti-spam measures - Proper authentication is used to maximize deliverability > Tip: > If you experience issues with email delivery, always begin by checking your domain’s SPF records. SPF Records: What They Are and How to Set Them Up SPF (Sender Policy Framework) is a DNS record that helps stop spammers from sending emails that appear to be from your domain. Without an accurate SPF record, your emails are more likely to be rejected or land in spam folders. The Correct SPF Record for Brixly To authorize Brixly’s mail servers, add this SPF record to your domain’s DNS: v=spf1 a mx ip4:your_server_ip include:spf.hostns.io -all - Where to add: In cPanel, go to Zone Editor > select your domain > Manage > Add Record (or edit the existing SPF TXT record). Step-by-Step: Adding an SPF Record in cPanel 1. Log in to your cPanel account. 2. Navigate to Zone Editor. 3. Click Manage next to the domain you want to update. 4. Search for the existing SPF record or click Add Record > Add TXT Record. 5. Enter the following: - Name: yourdomain.com. (replace with your actual domain) - Type: TXT - TTL: 14400 - Record: v=spf1 a mx ip4:your_server_ip include:spf.hostns.io -all 6. Save your changes. > Note: > If you use additional email services (e.g., Microsoft 365, Google Workspace), you must include their SPF mechanisms as well. For example: > > > v=spf1 a mx ip4:your_server_ip include:spf.hostns.io include:_spf.google.com -all > Other Authentication Methods: DKIM & DMARC DKIM (DomainKeys Identified Mail) and DMARC (Domain-based Message Authentication, Reporting & Conformance) provide additional layers of email authentication. DKIM - Purpose: Ensures emails are not tampered with during transit by adding a digital signature. - How to Enable: In cPanel, use the Email Deliverability section. Locate your domain and click Manage to enable and copy the required DKIM record into your DNS. DMARC - Purpose: Allows domain owners to specify how unauthenticated emails should be handled (quarantine, reject, or monitor only). - How to Enable: Create a TXT record in your DNS: - Name: _dmarc.yourdomain.com. - Type: TXT - Value: v=DMARC1; p=quarantine; rua=mailto:you@yourdomain.com Adjust the policy (p=) and reporting address as needed. General Best Practices for Avoiding Spam Filtering To maximize deliverability, follow these proven guidelines: - Authenticate all outgoing email with SPF, DKIM, and DMARC records. - Keep content clean: Avoid using spam-triggering language, excessive links, or suspicious attachments. - Use consistent formatting and avoid large images or attachments that can trip filters. - Send from reputable domains and maintain a healthy sending reputation. - Monitor blacklists: Regularly check if your domain or server IP is listed on major blacklists (e.g., MX Toolbox). - Never purchase mailing lists and always use opt-in email lists. - Personalize emails and include a clear unsubscribe option. Using Mail-Tester.com for Diagnosis Mail-Tester.com is a free online tool to check your email’s spam score and diagnose deliverability issues. How to Use Mail Tester 1. Go to Mail-Tester.com. 2. Copy the temporary email address displayed. 3. Send a test email from your domain to this address. 4. Return to the Mail-Tester page and click “Then check your score.” 5. Review your score and detailed report, which will highlight any SPF/DKIM/DMARC issues, blacklistings, or content-related problems. Use the feedback to resolve any issues before sending emails to your real recipients. Troubleshooting Common Issues If you’re still having trouble with email deliverability, consider these steps: - SPF/DKIM/DMARC Errors: Double-check that all authentication records are properly configured and have propagated. - Blacklisted IP/Domain: Run your domain and server IP through blacklist checkers. If listed, follow the delisting instructions provided by the blacklist. - Content Issues: Use Mail Tester or similar tools to identify problematic words, formatting, or attachments. - Third-party Email Providers: If you’re routing email through services like Microsoft 365 or Google Workspace, ensure their records are included in your SPF entry. - SMTP Authentication: Always use SMTP authentication when sending email from email clients. Lack of authentication can result in rejections. - Recipient Filters: Sometimes, issues are on the recipient’s side. Ask them to whitelist your email address or domain. When to Contact Support If you have followed all the troubleshooting steps and your emails are still being marked as spam or not delivered, reach out to our support team. Please provide: - The sender and recipient email addresses - The email subject and approximate send time - Any error messages received (copy the full message) - The full email headers (if available) - Steps you have already taken to troubleshoot Our team will investigate further and guide you to a resolution. Need additional help? If you’re still experiencing difficulties, please raise a support ticket with all the relevant details. Our team is here to help ensure your email deliverability is as reliable as possible.

Last updated on Jul 24, 2025

Resolving and Understanding Email Forwarding Rate Limit Errors

Resolving and Understanding Email Forwarding Rate Limit Errors **Description:**This article explains how email forwarding impacts your sending limits, how to diagnose and resolve Google rate limit errors, and best practices for managing email routing on Brixly shared hosting. Forwarded emails count towards your domain’s hourly sending quotas, so efficient management is essential to maintain deliverability. Table of Contents - What Are Email Forwarding Rate Limit Errors? - How Forwarding Affects Sending Limits - Common Rate Limit Error Messages - Diagnosing Rate Limit Issues - Best Practices for Email Forwarding - Step-by-Step Solutions - Troubleshooting Forwarding to Google (Gmail) - Useful Tools & Resources - Further Assistance What Are Email Forwarding Rate Limit Errors? A rate limit error occurs when too many emails are sent or forwarded from your domain in a short period, exceeding the allowed threshold set by either Brixly or the recipient (such as Gmail). This is a common issue when using cPanel forwarders to redirect incoming mail to third-party addresses. Key points: - All forwarded emails count towards your domain's outgoing email limits. - Exceeding these limits will temporarily block further outbound emails, including forwards, until the limit resets. How Forwarding Affects Sending Limits When you set up a forwarder in cPanel, every message forwarded is counted as an outgoing email. For example, if 100 emails arrive in your inbox and are forwarded to Gmail, that’s 100 outgoing emails. Brixly’s Shared Hosting Email Limits: - Sending limits are enforced per hour, per domain. - Exceeding the hourly quota will result in a rate limit error, blocking further outbound messages until the next hour. > For full details on limits, see:Brixly Email Sending Limits Common Rate Limit Error Messages You may see errors similar to: Domain has exceeded the max emails per hour (250/250) 550 5.4.5 Daily sending quota exceeded 421 4.7.0 Temporary System Problem - try again later Or, when forwarding to Gmail/Google: The user you are trying to contact is receiving mail at a rate that prevents additional messages from being delivered. Diagnosing Rate Limit Issues Step 1: Check Your Forwarders - Log in to cPanel. - Go to Email > Forwarders. - Review the list of active forwarders. - Check if you have forwards set to Gmail, Outlook, Yahoo, etc. Step 2: Review Outgoing Email Volume - Go to Email > Track Delivery in cPanel. - Filter by “Successful” and “Deferred” to see outgoing activity. - Look for spikes in outgoing mail volume, especially to your forwarder addresses. Step 3: Check for Email Loops - Ensure you do not have circular forwarding (e.g., A → B → A), which can quickly hit limits. Best Practices for Email Forwarding - Limit Forwarders: Only use forwarding when absolutely necessary. - Use Mailbox Instead: Access mail directly using IMAP/POP3 rather than forwarding. - Set Up Filters: Use cPanel Email Filters to minimize unnecessary forwards (e.g., only forward specific types of emails). - Avoid Forwarding to Gmail for Bulk Inboxes: Gmail aggressively rate-limits forwarded mail; set up a dedicated mailbox and fetch with Gmail’s “Check mail from other accounts” feature instead. - Monitor Usage: Regularly check your outgoing mail logs and adjust forwarding rules if you approach limits. Step-by-Step Solutions 1. Remove or Reduce Forwarders To remove a forwarder: 1. Log in to cPanel. 2. Go to Email > Forwarders. 3. Find the forwarder and click Delete. 2. Use Gmail’s Fetch Feature Instead of forwarding, let Gmail fetch your emails: 1. Log in to your Gmail account. 2. Go to Settings > Accounts and Import. 3. Under Check mail from other accounts, click Add a mail account. 4. Enter your Brixly-hosted email address, then provide your mailbox details (IMAP/POP3, username, and password). 5. Complete the setup. > This avoids forwarding and will not count towards your outbound limits. 3. Set Up Email Filters To only forward emails matching specific criteria: 1. In cPanel, go to Email Filters. 2. Select the relevant account. 3. Click Create a New Filter. 4. Set conditions (e.g., Subject contains “Invoice”). 5. Under Actions, select Redirect to Email and enter the destination address. 6. Click Create. 4. Monitor Outgoing Email Activity 1. In cPanel, go to Track Delivery. 2. Review the delivery reports and check for high outgoing volumes. Troubleshooting Forwarding to Google (Gmail) Gmail imposes strict rate and spam filtering on forwarded emails: - Limit the number of emails forwarded to Gmail accounts. - Avoid forwarding newsletters, mailing lists, or large volumes. - If Gmail blocks emails, you may see bounces or delays—stop forwarding and switch to mailbox fetching. - If forwarding is essential, consider using a professional email service (e.g., Google Workspace or Microsoft 365) for better deliverability. Useful Tools & Resources - cPanel Forwarders: Manage forwarding rules quickly. - cPanel Track Delivery: Monitor outgoing/incoming email activity. - cPanel Email Filters: Filter or route specific emails. - Webmail: Access your mailbox directly online. - Mail Tester: Check your email reputation and spam score. Further Assistance If you continue to experience rate limit errors after following the above steps: - Double-check all forwarders and reduce usage where possible. - Review your outgoing mail logs for abnormal activity. - Consult our Email Hosting Knowledge Base for additional guides. For unresolved issues, please raise a support ticket with details of your setup and affected addresses. Our support team will be happy to help. By understanding how forwarding impacts your sending limits and following these best practices, you can maintain reliable email delivery on your Brixly shared hosting account.

Last updated on Aug 08, 2025

Troubleshooting Outlook Email Synchronization Issues in Shared Hosting

Troubleshooting Outlook Email Synchronization Issues in Shared Hosting **Description:**A comprehensive guide to resolving email synchronization problems between webmail and Microsoft Outlook for shared hosting customers. This article covers client configuration, server settings, and common troubleshooting steps, with practical solutions you can implement independently. Table of Contents - Introduction - Essential Email Synchronization Concepts - Step-by-Step: Correct Outlook Email Setup - Common Synchronization Issues & Solutions - 1. Emails Appear in Webmail But Not Outlook - 2. Outlook Not Sending or Receiving Emails - 3. Sync Issues After Hosting Migration - 4. SSL Certificate Warnings in Outlook - General Troubleshooting Steps - Useful Tools & Where to Find Settings - When to Contact Support Introduction Synchronization issues between Outlook and webmail are common in shared hosting environments. These issues can often be resolved by reviewing email client settings, verifying DNS records, or reconfiguring the client. This guide is intended for shared hosting customers using cPanel-based email. Essential Email Synchronization Concepts - IMAP vs. POP3: - IMAP is recommended, as it keeps messages synchronized between the server (webmail) and your local device (Outlook). - POP3 downloads messages and usually removes them from the server, causing sync issues. - **Webmail:**Access your email at https://yourdomain.com/webmail to verify messages directly on the server. Step-by-Step: Correct Outlook Email Setup 1. Gather Required Settings from cPanel - Log in to cPanel - Navigate to Email Accounts - Locate your email address, click Connect Devices or Set Up Mail Client for configuration details Typical settings: | Setting | Example Value | | ------- | ------------- | | Email Address | user@yourdomain.com | | Username | user@yourdomain.com | | Incoming Server (IMAP) | mail.yourdomain.com or server hostname | | IMAP Port (SSL/TLS) | 993 | | Outgoing Server (SMTP) | mail.yourdomain.com or server hostname | | SMTP Port (SSL/TLS) | 465 | | Encryption | SSL/TLS | 2. Add Account in Outlook 1. Open Outlook and go to File > Add Account 2. Choose Manual setup or additional server types 3. Select POP or IMAP 4. Enter your account information using the settings above 5. Click More Settings - Under Outgoing Server, check My outgoing server (SMTP) requires authentication - Select Use same settings as my incoming mail server - Under Advanced, set the correct ports and select SSL/TLS as the encryption method 6. Click Next and Outlook will test the connection Incoming Server (IMAP): mail.yourdomain.com Port: 993 Encryption: SSL/TLS Outgoing Server (SMTP): mail.yourdomain.com Port: 465 Encryption: SSL/TLS Authentication: Yes (same as incoming) Common Synchronization Issues & Solutions 1. Emails Appear in Webmail But Not Outlook Causes & Solutions: - **Incorrect Protocol:**Ensure Outlook is set up as IMAP, not POP3.Solution: Remove and re-add the account as IMAP if needed. - **Outdated Configuration:**Double-check server names, ports, and encryption settings. - **Offline Mode:**Make sure Outlook is not in "Work Offline" mode (check in the Send/Receive tab). 2. Outlook Not Sending or Receiving Emails Checklist: - **Authentication:**Ensure "My outgoing server (SMTP) requires authentication" is checked. - **Password Issues:**Reset the password in cPanel if you suspect it's incorrect. - **SSL Certificate Warnings:**Use the server hostname instead of your domain if you get SSL mismatch errors. 3. Sync Issues After Hosting Migration Steps: 1. **Check DNS Propagation:**Ensure MX records point to your current hosting server. - Use cPanel > Zone Editor to verify. - Use MXToolbox to check externally. 2. **Remove and Re-add Account:**After migration, remove the old account from Outlook and re-add it using current settings. 3. **IMAP Migration Tool:**If emails are missing, use cPanel's Migration Center > IMAP Migration Tool to transfer messages from the old server. 4. SSL Certificate Warnings in Outlook Resolution: - Use the server’s hostname (found in cPanel or your welcome email) as the mail server address, not your domain, for both incoming and outgoing servers. - Accept the certificate if you trust the server and connection. General Troubleshooting Steps - **Test Webmail:**Log in via https://yourdomain.com/webmail to confirm mailbox functionality. - **Update Outlook:**Ensure you are using the latest version of Outlook. - **Firewall/Antivirus:**Temporarily disable any local firewall or antivirus that may block ports 993 or 465. - **Mailbox Quota:**Check in cPanel that your mailbox is not over quota. Useful Tools & Where to Find Settings - cPanel: - Email account creation and configuration - Password resets - DNS Zone Editor for record management - **Webmail:**Direct web access to your mailbox - **File Manager:**Advanced users may use this to manage mailbox files if necessary - **MXToolbox:**External DNS and MX record checker When to Contact Support If issues persist after following these steps, please raise a support ticket with: - Your email address and affected domain(s) - The exact error message (if any) - Screenshots of Outlook settings and errors - Steps you've already tried Our team will assist you further to resolve any remaining issues. By following this guide, most Outlook synchronization problems with shared hosting email accounts can be resolved quickly and independently. For persistent or complex issues, our support team is always here to help!

Last updated on Aug 08, 2025

Resolving SSL/Server Identity Verification Errors in Email Clients

Resolving SSL/Server Identity Verification Errors in Email Clients **Description:**This guide provides step-by-step instructions for resolving SSL certificate and server identity verification errors in email clients when connecting to your mailbox on Brixly shared hosting. It’s designed for shared hosting customers with basic technical knowledge and focuses on solutions you can implement without server admin access. Table of Contents - Introduction - Why Do SSL/Server Identity Errors Occur? - Quick Checklist - Step-by-Step Troubleshooting - 1. Confirm Your Email Client Settings - 2. Use the Correct Server Hostname - 3. Accept or Trust the Certificate - 4. Update or Remove and Re-Add the Account - 5. Check DNS and Propagation - Examples of Correct Settings - Common Error Messages and Solutions - Advanced: Checking the Certificate Manually - Further Assistance Introduction SSL/Server Identity Verification errors in email clients (such as Outlook, Thunderbird, Apple Mail, or mobile apps) are common when your email client cannot confirm the identity of the mail server. This can happen after domain changes, migrations, or using incorrect settings. Resolving these errors ensures your emails remain secure and deliverable. Why Do SSL/Server Identity Errors Occur? - Your domain’s SSL certificate does not match the mail server’s hostname - The mail server uses a shared SSL certificate (typical in shared hosting) - You are using mail.yourdomain.com, but the SSL is issued to the hosting server (e.g., xxxxx.hostns.io) - DNS changes have not yet propagated Quick Checklist - [ ] Are you using the server hostname as the mail server address? - [ ] Have you accepted/trusted the SSL certificate in your email client? - [ ] Do your DNS records (MX, A) point to the correct hosting server? - [ ] Is your domain’s SSL certificate valid and not expired? Step-by-Step Troubleshooting 1. Confirm Your Email Client Settings Check the configuration in your email client: - Username: Your full email address (e.g., user@yourdomain.com) - Password: Set in cPanel for your email account - Incoming Mail Server: Use the provided server hostname (see below) - Outgoing Mail Server: Use the provided server hostname - Ports: - IMAP: 993 (SSL/TLS) - POP3: 995 (SSL/TLS) - SMTP: 465 (SSL/TLS) or 587 (STARTTLS) - Authentication: Enabled for SMTP and IMAP/POP3 2. Use the Correct Server Hostname **Important:**The SSL certificate is valid for the server’s hostname, not your domain.Find your server hostname in cPanel (usually in the right-hand sidebar or in your welcome email). **Example:**If your server hostname is absinthe.hostns.io, use: Incoming/Outgoing server: absinthe.hostns.io How to change this in your client: - Go to the account’s server settings - Replace mail.yourdomain.com with your actual server hostname 3. Accept or Trust the Certificate Most email clients will prompt you to accept or trust the certificate if there’s a mismatch. - Click Trust, Accept, or Continue (wording varies by client) - Optionally, check “Always trust” if available > You should only do this if you are connecting to the official server hostname provided by Brixly. 4. Update or Remove and Re-Add the Account If errors persist: - Remove the email account from your client - Add it again using the correct settings and server hostname 5. Check DNS and Propagation If you recently updated DNS records or migrated your domain: - Use tools like MXToolbox to check if MX and A records point to your Brixly server - DNS changes can take up to 24 hours to propagate Examples of Correct Settings IMAP (Recommended): Incoming Server (IMAP): absinthe.hostns.io Port: 993 Encryption: SSL/TLS Outgoing Server (SMTP): absinthe.hostns.io Port: 465 Encryption: SSL/TLS Authentication: Yes (use full email address and password) Common Error Messages and Solutions | Error Message | Solution | | ------------- | -------- | | "The certificate does not match the host you are connecting to." | Use the server hostname as mail server address. | | "Server identity cannot be verified." | Trust the certificate or update to the server hostname. | | "SSL Handshake failed." | Confirm correct port, encryption, and hostname. | | "Untrusted certificate" | Trust the certificate, or re-add account properly. | Further Assistance If you’ve followed all steps and continue to experience SSL/server identity errors: - Double-check all settings and DNS records - Try connecting via webmail to ensure the mailbox is working:https://your-server-hostname/webmail - Consult our Email Hosting Knowledge Base **Still having trouble?**Please open a support ticket with: - The exact error message you receive - Your domain name and email address - The steps you’ve already taken Our team will be happy to assist further! By following these steps, most SSL and server identity verification issues with email clients can be resolved by updating your settings and using the correct server hostname.

Last updated on Aug 08, 2025