How To Modify an Existing Email Account in OS X 10.11

How To Set up Email in OS X 10.11
I. How To Set up a New Email Account in OS X 10.11
II. How To Modify an Existing Email Account in OS X 10.11

Pre-Flight Check

You can edit an email account that already has been configured in Mail, for example should you decide to switch between non-SSL and SSL settings or update the password.

Note: You cannot edit an existing email account to switch its account type from POP3 to IMAP or vice versa. To change the account type, you must add a new email account of the desired type (POP3 or IMAP). Adding a new account with a different connection type should not require you to delete the old one in most mail clients.

To avoid data loss, please use caution any time you change an email account’s connection type or delete an email account. Removing an email account from a mail client also will remove all messages associated with it on the device and, specifically in the case of POP accounts that are not configured to retain mail on the server, there may be no way to recover those messages. If you have any doubt or questions, please contact Heroic Support® for guidance.

Since any changes must be made on both the incoming and outgoing servers, updating the email account’s password or switching between non-SSL and SSL settings is not as simple as toggling a single setting, but the steps are easy to follow.

Step #1: Configure Incoming Server Settings

  1. You set the incoming mail server in the Internet Accounts preferences pane. To access it, select Accounts from the Mail menu.
  2. On the Internet Accounts preferences panel, select the name of your email account from the left pane to update the password or change the incoming server name or connection type.OSX 10.11 Incoming Mailserver
  3. Update the Password
    • To update the email account password, enter the new password into the Password field in the Internet Accounts preferences pane.
  4. Change the Incoming Server Name or Connection Type (SSL/non-SSL)
    • Click the Advanced button at the bottom right of the Internet Accounts preferences pane to edit the Hostname via a popup panel.
      • SSL settings will use the server’s hostname (e.g., host.yourdomainname.com)
      • Standard non-SSL settings will use the domain name (yourdomainname.com or mail.yourdomainname.com).
    • Once you have changed the Hostname, click OK.

Step #2: Configure Outgoing Server Settings

  1. Select Preferences from the Mail menu to open the Internet Accounts preferences pane, then click on the account in the left menu.
  2. On the Account Information tab, locate the Outgoing Mail Server (SMTP) row and select Edit SMTP Server List from the select menu.
    OSX 10.11 Outgoing Mailserver
  3. Change the Outgoing Server Name or Connection Type (SSL/non-SSL)
    OSX 10.11 Account Information

    • Click on your mail server’s name in the top pane to select it, then change the Server Name on the Account Information tab to the desired value.
      • SSL settings will use the server’s hostname (e.g., host.yourdomainname.com)
      • Standard non-SSL settings will use the domain name (yourdomainname.com or mail.yourdomainname.com).
    • Once you’ve changed Server Name to reflect the desired connection type, click on the Advanced tab to configure SSL settings.
      OSX 10.11 Advanced Account Settings

      • Port: This should remain 587 regardless of connection method.
      • Use SSL: If you are using secure (SSL) settings, ensure that the Use SSL box is checked. If you are using standard, non-SSL settings, Use SSL should be unchecked.
      • Authentication should be set to Password regardless of connection method.
      • Both the User Name (full email address) and Password fields should be filled out. You can update the email account password by entering the current password into the Password field.
  4. Your email account will start using the new settings as soon as you click the OK button.

 

How To Change the Root Password in WHM

The root password is the key to full control over your server, and it’s essential that it remains secure. At some point, nearly every server administrator will need to change the root password, either to revoke access to previously authorized individuals or due to an internal password policy. Additionally, the server’s root password should be changed any time a security breach is suspected.

If your server is running cPanel and you have access to WebHost Manager, changing the server’s root password is a matter of only a few clicks.

Once you’ve logged into WHM with the current root password, select Change Root Password from the list on the left, under Server Configuration.

Enter a Strong New Password

Once you’ve selected a new root password (you can use any combination of upper- and lower-case letters, numbers and special characters to increase the password strength), enter the new password twice, then click the Change Password button. That’s all there is to it; you now can close out of WHM and log back in with the new password.

Note: Any time you update the server’s root password, please also update our records in your Manage dashboard so that our Heroic Support® technicians can continue to proactively monitor your server. If you change the root password without updating our records, we won’t be able to automatically attempt to resolve any issues that occur.

 

What to Expect During a Site Migration

The Migration Team at Liquid Web is dedicated to providing customers with an efficient and as uneventful a migration as possible. It is important that we work together to ensure an effective transfer of information. No matter if you are migrating from a current Liquid Web server, or from another host, we make it as simple as possible.

Most migrations generally take two to seven days, however, individual results may vary. The time required can change depending on the size and type of migration being completed. Most delays can be minimized by maintaining communication. Our team provides frequent updates to ensure we receive the data we need to complete the process.

Migrations begin by logging into the Manage customer interface. Once you are logged in starting a Migration Request will allow you to provide necessary details. Once complete a Migrations Specialist will contact you to schedule the migration.

Step 1: Information Collection

Liquid Web will:What we need from you:
Send the Migration Form to you through our ticket system. This form provides us with vital information to begin the migration.

Some of the information we will need is:

  • Source server hostname and IP address
  • Destination server hostname and IP address
  • Domain being transferred
  • DNS information and if you are able to modify DNS records

For External Migrations, we will need additional information, such as:

  • SSH username and password
  • cPanel username and password
Note: If currently do not have a server on your LiquidWeb account, you can create one when completing the Migration Request.
Complete the Migration Form completely and inform us of any special instructions before the migration begins.

In addition, please complete the following updates on your source server prior to the migration process.

Common updates are:

  • WordPress – install the most recent version
  • Update Plugins – delete any unused
  • Notify us of any third-party software installed that we may need to help with later

Please verify that your site is compatible with PHP version 5.5 as it is the lowest version of PHP supported by cPanel.

Step 2: Data Move

Liquid Web will:What we need from you:
During this step, the Migration Specialist will begin the Initial Sync. The Initial Sync is where we access your source server and compare software versions, pull data from the server and restore your sites on the destination server.

The end goal is for your site to work the same way on the destination server as it did on the source server. If your site shows errors on the source server prior to Initial Sync, the same errors will appear on the destination server.

Please refrain from adding any new sites or changing functionality on current sites during this time. This will minimize the occurrence of any errors during the migration process.

Step 3: Validation

Liquid Web will:What we need from you:
We will log into your site on the destination server and make sure that we are able to access all of your information. We want to make sure that your site is functions the same way in the new environment as it did on the source server.During this step, we do all the work. This process gets the site ready for testing, where we ask that you test your site in the new environment.

As soon as validation is over, we will notify you that we are ready for you to start testing.

Step 4: Testing

Liquid Web will:What we need from you:
We will review any errors you send us during your testing process and fix any issues. We will also assist with installing and configuring Third-Party Software such as MongoDB or NodeJS, if needed.

Third-Party Software installation and configuration falls under our Best Effort Support.

Note: This is the part of the process which can cause the most delays – please keep an eye on your email for the notification for you to begin testing.

The only person who knows how a website should work is the owner. This is where we need you to complete a detailed testing of the site and report back to us if anything is not working. It is important that you check all pages, forms, links, and back-end access. Don’t panic if you see errors – these occur when there are differences in the server environment and completely normal during the migration process.

If you encounter errors, send us examples in your Migration Ticket so that a specialist can investigate and help resolve the issue.

Step 5: DNS Update

Liquid Web will:What we need from you:
If you are registered with Liquid Web, our Migration Specialist will update the DNS on the new server so that you can update the IP on the Name Server

Note: There is the potential of a 20 – 50 minute downtime during the DNS propagation at the end of the migration process. In many cases, downtime can be minimized by lowering TTL values, but each migration is unique and may carry with it additional downtime to address issues as they arise.

If you are coming from an external host, you will need to update the DNS. Please review the DNS Update Information for external hosts if you are not sure how to update your DNS. We will notify you when it is time to make these changes and work with you through this process to keep you update on any issues to minimize downtime as best we can.
Some migrations have the ability to complete a Final Sync. This is where we do one more transfer of data to make sure that any updates are included in the migration and that all files are up to date. Please discuss with your Migrations Specialist to see if your migration qualifies for a Final Sync of your data from the source server to the destination server.

If you have any other questions you may want to see our Site Migrations FAQ! Otherwise if you’d like to build a custom solution and then start a Migration feel free to start a Chat.

Unblocking an IP Address or Opening a Port in the Firewall

Should you discover (or suspect) that a client or customer’s IP address has been blocked by the firewall on your cPanel server, or should you just need to open or close a port, you may be able to quickly resolve the issue yourself with just a little help.

Regardless of the software firewall your cPanel server is running, we have detailed, step-by-step instructions for managing it in our Knowledge Base:

  • How To Unblock Your IP Address in Manage: If you have a Dedicated, Storm, or VPS server, and your server is running the CSF firewall, you can unblock the IP address from your Manage dashboard. Find out how at How To Unblock Your IP Address in Manage.
  • Managing the Firewall in WHM/cPanel: If you have access to WebHost Manager and your server is running the ConfigServer Firewall (CSF), you can use a graphical interface to manage the firewall. Find out how at Managing the CSF Firewall in WHM.
  • Managing IP Address Blocks in CSF: You can manage IP blocks in the CSF firewall from the command line over SSH as well. Find out how at How To Unblock an IP Address in CSF.
  • Managing IP Address Blocks in APF: If your server uses the Advanced Policy Firewall (APF), you can block or unblock IP addresses via SSH with our walkthrough at How To Unblock an IP Address in APF.
  • Managing Open Ports In Your Firewall: If you need to open or close a port on your server, or check whether a specific port is open, visit Opening Ports in Your Firewall for a walkthrough of the process using SSH, or How To Open a Port in CSF With WHM/cPanel to manage ports in WHM/cPanel.

 

Unable to Send Email

If you find that you are able to receive email but cannot send email, your email client may not be properly configured for SMTP authentication, which is required by your mail server.

SMTP authentication means that a username and password are required for outgoing mail connections as well as for incoming connections.

In the Outgoing server section of your mail client, you will want to ensure that both the full email username (user@yourdomain.com) and the email account’s password are entered, and that either the Server Requires Authentication box is checked (if present), or that the Authentication type selection is not set to None.

If you’re using a mail client such as Mac Mail and you have multiple email accounts on your server configured in the mail client, you will want to ensure that each account has its own outgoing server configured with its corresponding email account password; you will not be able to use the same outgoing server with multiple email accounts due to the SMTP authentication requirement.

Learn how to create a new email address in cPanel at Creating Email Addresses in cPanel, and find instructions to configure your email account in any email client at How to Set up any Email Client.

Setting up an Email Client

Setting up email in a client such as Outlook or Mac Mail on your cPanel server for the first time can be a bit complicated, but once you know a few key pieces of information, you can get almost any email client up and running quickly.

While each program’s setup process is going to be slightly different, the cPanel email settings below will apply to Outlook, Mac Mail, Thunderbird, Android, iOS Mail, or any other email client. You can access the specific cPanel email settings for your domain and learn how to set up specific email clients at How To Set Up Any Email Client.

Secure (SSL/TLS) Connections

  • Both the incoming and outgoing servers will use your hostname (the server name, as opposed to the domain name): host.yourdomainname.com
  • IMAP Port: 993
  • POP3 Port: 995
  • SMTP Port: 465 or 587 (the latest versions of popular mail clients such as Outlook and most Apple mail clients may require you to use port 587 for SMTP)

Standard (non-SSL) Connections

  • Both the incoming and outgoing server names will be your domain name: mail.yourdomainname.com (or simply yourdomainname.com)
  • IMAP Port: 143
  • POP3 Port: 110
  • SMTP Port: 25 or 587 (the latest versions of popular mail clients such as Outlook and most Apple mail clients may require you to use port 587 for SMTP)

Authentication Is Required for All Email Connections

  • Regardless of whether you’re using a secure or standard connection, please note that authentication is required for IMAP, POP3, and SMTP. This typically is configured in an email client by a checkbox such as “This server requires authentication”. If you have such a setting, it must be enabled.

 

Find Detailed Information in Our Knowledge Base

 

Updating DNS Records and DNS Propagation Time

The most essential concept to understand in web hosting is the Domain Name System. At its most basic level, DNS determines whether a visitor to your site sees the actual site, or a “Server not found” error. Like a telephone book, DNS matches names (your domain name) to numbers (IP addresses).

If your browser returns a “Server not found” error when visiting a new subdomain or a site you’ve recently created (or moved here), it’s likely that a DNS record has either not yet been created or has not yet had sufficient time to propagate.

When you add a new subdomain, such as store.yourdomainname.com or blog.yourdomainname.com, it’s important to ensure that you have added the appropriate DNS record for the site to resolve. In this case, you would need to add a CNAME for “store” or “blog” to the DNS record for yourdomainname.com.

If you are using Liquid Web nameservers, you can add a record for the new subdomain in your Manage interface by clicking on Domains in the left menu and then selecting the DNS tab. The record for a new subdomain would be entered in the main domain’s zone file.

Likewise, if you have set up a new domain name and chose to use Liquid Web nameservers at the registrar, you’ll want to ensure that a DNS zone has been created for the new domain in your Manage dashboard (under Domains on the DNS tab) and that a DNS “A”  record is present and pointing the site to its assigned IP on your server.

If all the DNS records are in place and the site still is unreachable, it’s possible that the DNS changes are propagating. Typically only a few hours is needed for this, but it technically can take up to 24 hours to 48 hours for a DNS change to fully propagate globally. It’s important to note any time a change is made to a DNS record, regardless of whether it’s adding a new record or changing the value of an existing one, it can take up to that 24 hours to 48 hours before the change is visible worldwide.

One external tool that you can use to confirm the presence of DNS records and track DNS record propagation is What’s My DNS.

As always, a Heroic Support® technician will be happy to help should you need any assistance.

 

A Closer Look at cPanel Notifications

In recent updates, cPanel has modified some of the notification settings for their control panel. As a result, you may find that the priority of certain notification types have changed and you may begin to receive notifications that you previously had not encountered. In particular, the notification options for Security Advisor changed with the release of WHM 56 on April 26, 2016.

The notification changes by cPanel are meant to both help users better manage their servers and also keep them informed of potential security risks, such as those posed by outdated software versions which no longer receive updates.

With some exceptions, many of the notifications are purely informational and not necessarily a cause for alarm. Here are the most common notifications followed up on via support requests:

‘New security advisor notifications with high importance’

WHM’s Security Advisor routinely performs a security scan on the server and alerts you to items it considers potential security risks. For each item flagged, the cPanel notification will clearly explain how to resolve the issue at your convenience. It’s important to note that while some recommendations, such as enabling SMTP Restrictions, Enabling Brute Force Protection, and increasing Password Strength Requirements are worthy of attention in nearly all cases, other recommendations may not be appropriate for your situation. For example, you may prefer not to disable root SSH access or SSH password authentication (and should not unless you have set up and tested SSH keys to connect to your server). To learn more about specific messages, visit our article on cPanel Security Advisor Notices. If you need guidance, feel free to contact Heroic Support®.

‘Your SSL Certificate is now available for download and installation’

Beginning with WHM version 56, cPanel now includes a free signed SSL certificate to cover the hostname (and only the hostname) of the server on which it runs. This feature eliminates warnings and notices associated with using self-signed SSL certificates and protects all connections to server services, such as email and ftp, and is automatically installed and renewed when possible. In order for the automatic installation to occur, however, the server’s hostname must resolve in a browser (that is, it must have a DNS record). Additionally, if you already have purchased an SSL to cover your hostname (either a dedicated SSL or a wildcard) cPanel will not attempt to overwrite it. Only self-signed SSLs installed on the server services (cPanel/WHM, FTP, SMTP, and the Mailserver) will be overwritten. Only if you have a purchased SSL installed on the hostname, and allow it to expire, will cPanel replace it. In any case, no action should be required on your part unless automated installation fails. In that event, you may contact Heroic Support® for assistance.

‘The system will automatically switch the mail server from Courier to Dovecot … in order to continue receiving updates.’

In cPanel/WHM versions up to 11.52, users were able to choose between two mail servers: Courier and Dovecot. Courier was selected by default, and most cPanel users never had reason to switch. However, beginning with cPanel/WHM version 54, Courier has been deprecated. cPanel will no longer support Courier in future releases, and the control panel can not be updated until the mailserver is switched.

If you want to switch the mail server yourself, you can follow our guide. Should you prefer not to switch to Dovecot and would like to continue to use Courier, you will need to change your cPanel update preferences and select the LTS (long-term support) release tier. cPanel will continue to send daily emails until one of these two actions have been taken. If you do not take any action, cPanel will automatically switch the mailserver at the time indicated in the email.

‘The server has POP3 before SMTP enabled’

This means that SMTP authentication is not being strictly enforced on the server. Effectively, any user who has successfully logged in to receive mail is treated as authenticated to also send mail from the same IP address for an hour after their successful incoming login.

The important thing to note is that it allows the IP address from which a successful email login was made to access the SMTP server, not just the specific user or device from which the successful login was made. In a modern home or office environment, a single public IP address typically is shared by many devices on that network. That’s also the case when you’re connected to a public wireless network, such as at a local coffee shop or shopping center.

With POP Before SMTP (also referred to as POP3 Before SMTP) enabled, it’s possible that a malicious user or compromised device connected to the same network — regardless of how well-secured your personal computer, workstation or mobile device may be — could relay mail through your server. Mitigating that potential security risk would be the primary reason for disabling POP Before SMTP on your server.

However, you should be aware that disabling POP Before SMTP means that any email account would be required to use SMTP authentication, and that would need to be configured in each individual mail client used with each email account in order for the account to be able to send mail.

While all modern mail clients such as recent versions of Outlook, Mac Mail and Thunderbird and any recent smartphone have that ability, the setting may not be enabled by default. If that’s the case, the account configuration would need to be adjusted in the email client.

For assistance configuring email clients, see How To Set Up Any Email Client.

‘The server has unmonitored services’/’The service has failed’

Through its ChkServd service, cPanel is able to monitor enabled services and automatically restart them when necessary. This is separate from, and unrelated to, Sonar Monitoring services which you can configure in your Manage dashboard.

While this is not a new capability, cPanel recently began notifying users of it, along with a list of any enabled cPanel services which were not configured already for monitoring. It is recommended, though completely optional, to enable monitoring for all active cPanel services to improve stability and ensure that services can be recovered as quickly as possible. You can enable monitoring in WebHost Manager at Service Manager, under the Service Configuration section in the left menu.

One thing to keep in mind is that cPanel will alert you to any service it has found to be down and automatically restarted via ChkServd, even if the service intentionally was stopped, such as during an update or a required restart of another service upon which it is dependent.

What that means is that you should not immediately assume the worst any time you receive a “Service Failed” or “Service Recovered” alert from cPanel. If you receive only a single notification of a service restarted, and not multiple alerts for the same service over an extended period of time, there generally is no cause for concern. However, should you receive multiple such alerts for a service, or should the alert indicate that the service could not automatically be restarted, please do not hesitate to contact us so that we may investigate.

‘Altered RPMs found’

While the message subject can sound somewhat ominous, it should not automatically be cause for alarm. Typically this message is generated when cPanel performs an update check and discovers that local files are out of date, have become corrupted or have been updated outside of cPanel. Occasionally, it also can occur when both the 32- and 64-bit versions of a service have been installed.

This message will contain the filename of the package it found to be incomplete, corrupted or otherwise broken; running the command referenced in the message (/usr/local/cpanel/scripts/check_cpanel_rpms –fix) should result in it re-downloading the file successfully.

Please note that anytime updates are pushed to your server outside of cPanel, for example when an important security patch is applied to multiple servers simultaneously, this notice also can be triggered. The issue can be easily rectified by updating cPanel’s operating system packages, which support is happy to help with if you’re unable to run the command specified in the cPanel notification.

‘The cPanel & WHM update process failed’

WebHost Manager/cPanel by default checks for updates to its control panel each day. Due the number of servers running cPanel, there can be times when too many servers are checking in with cPanel’s update server simultaneously, causing the request to time out. And occasionally, the cPanel update server itself may be unreachable.

Whenever that happens, cPanel will alert you and automatically try again the next day. You can, however, manually force it to check for updates (and automatically install the update, if one is available) should you prefer not to wait.

You can find instructions for manually updating cPanel at How To Upgrade and Patch cPanel and WHM.

Should a manual update also fail, or should you receive consecutive update failure messages, please do not hesitate to contact our Heroic Support® team.

‘System integrity checking detected a modified system file’

The default notification preferences beginning in WHM/cPanel version 54 can cause this notification to be sent immediately following an update to cPanel/WHM itself.

This notification may alert you to “FAILED” md5sum comparison tests on any server software (and usually on several components at a time), but should not immediately be cause for alarm.

The server message is triggered any time a core file is changed, and makes it clear that it may be the result of an OS update or application upgrade. If you have automatic updates enabled in WHM, have manually updated cPanel/WHM, or have requested that it be updated for you, then you can safely ignore this message. If you don’t have automatic updates enabled and have not recently updated cPanel, please do not hesitate to contact our Heroic Support® team.

Disabling cPanel Notifications or Changing Alert Settings

You can configure settings for all the cPanel alerts you receive in WHM under Contact Manager in the Server Contacts section of the left menu.

The first tab, Communication Type, allows you to set the alert level that will trigger a notification to each of the communication methods: AIM, email, ICQ, Post to a URL, Pushbullet, or SMS.

The second tab, Notifications, allows you to set the minimum priority for each type of event, such as Service failures (ChkServd), Unmonitored Services, or Backup Successful, which will trigger a notification. You also can disable notifications for each event type using the dropdown menu under the Importance category.
 

Is the Server Down? I Can’t Log in or Connect

Are you unable to connect to your cPanel server to send or receive email, log into cPanel or WHM, or make an FTP or SSH connection?

Are you able to view your website in your browser? If not, and the connection simply times out, it’s possible that your IP address has been blocked by the server’s firewall. Typically, this is the result of too many failed logins (through cPanel, SSH, FTP, email, etc.) in too short a period of time.

To confirm whether that may be the case, you can test your site via a web service such as Down For Everyone Or Just Me (enter the URL of your website into the search field on the page) to see whether the site appears down for everyone else, or try to visit your website via another network, such as from a phone or tablet over its cellular connection after disabling wifi on the device.

If an IP block is suspected, it can easily be removed. If you have a Dedicated, Storm, or VPS server, and your server is running the CSF firewall, you can unblock the IP address directly from your Manage dashboard. If not, we can log into the server on your behalf, search the firewall for your IP address, and unblock it. Similarly if you’re able to confirm that your IP is not blocked, we can search the server logs for any specific errors associated with your connection attempt, or investigate any possible network issues between your physical location and the server’s that could be preventing you from accessing it.

To speed up that process, when opening a ticket, calling, or chatting in with your support request, please try to include your public IPV4 IP address (which you can obtain here) so that a support technician can help resolve the issue as quickly as possible. Please also include any error messages displayed in your browser (or email, FTP or SSH client) when attempting to connect.

Most Common Support Requests

As you might expect, most support requests on managed cPanel servers fall into a few basic categories. What you might be surprised to discover is that many common problems can be resolved by following a few simple steps.

None of the common cPanel support requests listed here are server-critical issues that require an experienced system administrator to troubleshoot and resolve, and we recognize that many of our customers are curious about their servers and actively engaged in learning more about cPanel server administration.

To that end, we’ve gathered together some of our Most Common Support Requests, and we’re sharing them with you here — along with their solutions.

Should you find yourself experiencing one of these common issues, you’ll know exactly what to expect when contacting our Heroic Support® team. And while you certainly are welcome to try to resolve the issue yourself, remember that we are here to assist you 24 hours a day, seven days a week, 365 days a year.

These articles should hold the answers to a number of common questions and, if you are so inclined, provide you with the tools and resources to resolve some non-critical issues on your own. And should you ever find yourself in need of assistance with any issue, please do not hesitate to contact Heroic Support®.