Bobcares

Connect Email to DigitalOcean Droplet with Ease

by | Nov 22, 2022

Connecting email to DigitalOcean Droplet is an easy job with this handy guide by our experts. Our DigitalOcean Support Services team specializes in solving issues and helping with queries. Read on to find out more. 

How to connect Email to DigitalOcean Droplet

Connecting email to a DigitalOcean Droplet can be easily accomplished with these steps by our experts. Before we begin, we have to ensure we have a Digital Ocean droplet running any modern Linux operating system. We also need to note down the droplet’s hostname with this command before we start:

hostname -f

Alternatively, we can also set the FQDN manually by running this command:

sudo hostnamectl set-hostname newname

where newname has to be replaced with what we prefer the email address to be.

Steps: Connect Email to DigitalOcean Droplet

Now let’s dive into the process of connecting our email to a DO droplet:

Connect Email to DigitalOcean Droplet
  1. First, we will register an account at SendGrid.
  2. Then create a Sender Identity. Our experts recommend choosing “Authenticate a domain instead” in order to set up a mail server with our domain.
  3. Next, choose a DNS host on the next screen.
  4. At this point, we have to enter the FQDN.
  5. Then update the DNS records with the DNS host. Now, SendGrid offers CNAME entries for the DNS host. For instance, if we have subdomain.bobcares.com, it may get updates to subdomain.bocares.com.bobcares.com. This can be fixed by removing fqdn.com from the end of the DNS name.

    If we set up the mail server on a subdomain, we have to set it to subdomain.mail.

  6. After that, we will generate an API key. This involves choosing SMTP Realy and entering an API key name. Our experts recommend keeping this key handy as we will need it in upcoming steps.
  7. Now, we have to configure Postfix. The commands to install Postfix depend on the OS running on the droplet

    sudo apt-get update
    sudo apt-get install postfix -y

  8. After installing Postfix, we have to configure it. Choose the type of mail configuration from the options. If you are not sure, our experts recommend selecting Internet site.
  9. In the next screen, enter the system mail name. This would be the FQDN. It appears after the @ symbol in the email address.
  10. Then, run the following commands to open the required inbound port:

    sudo ufw allow 25/tcp

  11. Next, we have to edit the edit /etc/postfix/main.cf to add these lines:

    smtp_sasl_auth_enable = yes
    smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
    smtp_sasl_security_options = noanonymous
    smtp_sasl_tls_security_options = noanonymous
    smtp_tls_security_level = encrypt
    header_size_limit = 4096000
    relayhost = [smtp.sendgrid.net]:587

  12. THen, create the /etc/postfix/sasl_passwd file and add the following line to it:

    [smtp.sendgrid.net]:587 apikey:API_KEY

    where API_KEY is the key we created in Step 6.

  13. Next, we have to update the file permissions and update the hashtables in Postfix:

    sudo chmod 600 /etc/postfix/sasl_passwd

    sudo postmap /etc/postfix/sasl_passwd

    sudo systemctl restart postfix

Testing the Mail Server Setup

Finally, we can test our mail server setup as part of connecting email to DigitalOcean Droplet. This is done via SendGrid or by running the following command on the droplet:

echo “hello world” | sendmail email@address.com

If we receive the email, the setup is successful. In case the mail has not been received, we have to check the Spam folder. If it is not there either, check the contents of the following file:

cat /var/mail/root

This will let us know if there is an error in our mail server setup.

Let us know in the comments if you have any further concerns about connecting an email server to a DigitalOcean droplet.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In conclusion, our experts took us through connecting an email with a DigitalOcean droplet. We also got a look at how to configure the mail server so that the email address ends in our domain name.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF