On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

Articles in this section

See more

How to configure Postfix on Plesk server to send emails using SendGrid

Avatar
Leonid Gukhman
Updated
Follow
Plesk for Linux kb: how-to ABT: Group B

Applicable to:

  • Plesk for Linux

Question

How to configure Postfix to send emails using SendGrid?

Answer

Note: The steps below describe how to configure integration with 3rd-party service and should be performed on the server's administrator risk. Or consider this task to be handled by Plesk Professional Services

Warning: any customization made in Postfix configuration can be overwritten by Plesk update (for example, in case of bug fix, when configuration files are updated), Plesk upgrade or by mchk utility, which resets default mail server configuration.

Google Cloud Instance

Click here to expand the solution.

  1. Connect to the server using SSH.
  2. Define which MTA is installed on the server and switch to Postfix if necessary.
  3. Create a backup of original /etc/postfix/main.cf configuration file and open it with a text editor:

    # cp -a /etc/postfix/main.cf{,.original}
    # vi /etc/postfix/main.cf

  4. Adjust it in accordance to the Google documentation instructions (Run Postfix on your instance section, starting from Step 3):
    • check if there are the following parameters exist and comment them out by adding hashtag sign in the beginning of the line:

      CONFIG_TEXT: default_transport = error
      relay_transport = error

      Commented out directives

      CONFIG_TEXT: #default_transport = error
      #relay_transport = error

    • add the SendGrid SMTP service as relayhost:

      CONFIG_TEXT: relayhost = [smtp.sendgrid.net]:2525

      Note: That port 2525 is used, because the outbound connections on ports 25, 587 are not allowed on Compute Engine.

    • add the following lines at the end of the file:

      CONFIG_TEXT: smtp_tls_security_level = encrypt
      smtp_sasl_auth_enable = yes
      smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
      header_size_limit = 4096000
      smtp_sasl_security_options = noanonymous

      After the parameters set, make sure that there are no duplicate directives that can break the configuration:

      # cat /etc/postfix/main.cf | grep "relayhost\|smtp_tls_security_level\|smtp_sasl_auth_enable\|smtp_sasl_password_maps\|header_size_limit\|smtp_sasl_security_options"

      Comment out/remove duplicate directives if there are some.

    • generate the SASL password map:

      # echo [smtp.sendgrid.net]:2525 yourSendGridUsername:yourSendGridPassword >> /etc/postfix/sasl_passwd

      where:

      yourSendGridUsername is your SendGrid username.
      yourSendGridPassword is your SendGrid password.

    • use the postmap utility to generate a .db file:

      # postmap /etc/postfix/sasl_passwd

    • verify that .db file has been created:

      # ls -l /etc/postfix/sasl_passwd*
      -rw------- 1 root root ... /etc/postfix/sasl_passwd
      -rw------- 1 root root ... /etc/postfix/sasl_passwd.db

    • set the proper permissions on .db file:

      # chmod 600 /etc/postfix/sasl_passwd.db

    • remove the file containing SendGrid credentials, as it is no longer needed:

      # rm /etc/postfix/sasl_passwd

    • reload Postfix service to apply changes:

      # service postfix restart

Configure SendGrid for regular server

Click here to expand the solution. 

  1. Connect to the server using SSH.
  2. Define which MTA is installed on the server and switch to Postfix if necessary.
  3. Create a backup of original /etc/postfix/main.cf configuration file and open it with a text editor:

    # cp -a /etc/postfix/main.cf{,.original}
    # vi /etc/postfix/main.cf

  4. Adjust it in accordance to the SendGrid documentation instructions (Run Postfix on your instance section, starting from Step 3):
    • add the SendGrid SMTP service as relayhost:

      CONFIG_TEXT: relayhost = [smtp.sendgrid.net]:587

    • add the following lines at the end of the file:

      CONFIG_TEXT: smtp_tls_security_level = encrypt
      smtp_sasl_auth_enable = yes
      smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
      header_size_limit = 4096000
      smtp_sasl_security_options = noanonymous

      After the parameters set, make sure that there are no duplicate directives that can break the configuration:

      # cat /etc/postfix/main.cf | grep "relayhost\|smtp_tls_security_level\|smtp_sasl_auth_enable\|smtp_sasl_password_maps\|header_size_limit\|smtp_sasl_security_options"

      Comment out/remove duplicate directives if there are some.

    • generate the SASL password map:

      # echo [smtp.sendgrid.net]:587 yourSendGridUsername:yourSendGridPassword >> /etc/postfix/sasl_passwd

      where:

      yourSendGridUsername is your SendGrid username.
      yourSendGridPassword is your SendGrid password.

    • use the postmap utility to generate a .db file:

      # postmap /etc/postfix/sasl_passwd

    • verify that .db file has been created:

      # ls -l /etc/postfix/sasl_passwd*
      -rw------- 1 root root ... /etc/postfix/sasl_passwd
      -rw------- 1 root root ... /etc/postfix/sasl_passwd.db

    • set the proper permissions on .db file:

      # chmod 600 /etc/postfix/sasl_passwd.db

    • remove the file containing SendGrid credentials, as it is no longer needed:

      # rm /etc/postfix/sasl_passwd

    • reload Postfix service to apply changes:

      # service postfix restart

Additional information

https://cloud.google.com/compute/docs/tutorials/sending-mail/

Comments

8 comments

Sort by Date Votes
  • Avatar
    Atul Chauhan

    I have configured according to the document but how can we test that configuration working properly?

    1
    Comment actions Permalink
  • Avatar
    Anton Maslov

    Atul Chauhan try to send a test message for example with webmail, review then /var/log/maillog to see if message was sent by the server.

    0
    Comment actions Permalink
  • Avatar
    Eran Jian (Edited )

    Please provide a solution to avoid configuration overwrite by a Plesk update / upgrade. 

    An option to change default outbound SMTP port / relay port from the Plesk panel will be much better.

    0
    Comment actions Permalink
  • Avatar
    Nelson Leiva

    Hi Eran Jian,

    I see your inquiry is being addressed already in a support ticket. As for the default port suggestion, I recommend creating a feature request about this in our User Voice if you feel it is important https://plesk.uservoice.com/forums/184549-feature-suggestions. In case it will become popular it may be implemented in future Plesk versions.

    0
    Comment actions Permalink
  • Avatar
    Eran Jian

    I created a feature request:

    https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/41852380-custom-outgoing-smtp-port

    Hopefully you will accept it so there won't be an outgoing mail issue on Google Cloud VMs.

    0
    Comment actions Permalink
  • Avatar
    Artur Beqiraj

    hello, 

    it is possible to use amazon SES instead of sendgrid? 

    0
    Comment actions Permalink
  • Avatar
    Renan Genova Ferreira

    Hi, Artur Beqiraj!

    Because we're not experts in Amazon SES, I'd recommend contacting Amazon Support/community to confirm if it can be used as an alternative.

    0
    Comment actions Permalink
  • Avatar
    Jesper Heinemeier

    It is obviously not a viable solution if it isn't persistent.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles