Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. Using alternative MX

Using alternative MX

Scheduled Pinned Locked Moved Solved Support
mail
3 Posts 2 Posters 858 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T Offline
    T Offline
    teamcrw
    wrote on last edited by girish
    #1

    Hi all,

    we're using N-able Mail Assure for Spam Filtering, so naturally the MX records are set to:

    mx1-eu.mtaroutes.com (priority 10)
    mx2-eu.mtaroutes.com (priority 20)
    mx3-eu.mtaroutes.com (priority 30)
    mx4-eu.mtaroutes.com (priority 40)

    Now, obviously Cloudron doesn't like this and throws out an error on the status page.

    As i don't like error notifications even though everything works as expected, i looked for a solution and stumbled upon this in the documentation:

    https://docs.cloudron.io/email/#alternate-mx

    So, i have added mtaroutes.com to the SPF record, but honestly i do not understand how the SPF record should change anything in this situation.

    Can someone explain like i'm 5 how this would actually work?
    And i guess, i'll still not be able to get rid of the MX error on the status page right, at least i do not see a connection here?

    Thanks in advance everyone!

    murgeroM 1 Reply Last reply
    2
    • T teamcrw

      Hi all,

      we're using N-able Mail Assure for Spam Filtering, so naturally the MX records are set to:

      mx1-eu.mtaroutes.com (priority 10)
      mx2-eu.mtaroutes.com (priority 20)
      mx3-eu.mtaroutes.com (priority 30)
      mx4-eu.mtaroutes.com (priority 40)

      Now, obviously Cloudron doesn't like this and throws out an error on the status page.

      As i don't like error notifications even though everything works as expected, i looked for a solution and stumbled upon this in the documentation:

      https://docs.cloudron.io/email/#alternate-mx

      So, i have added mtaroutes.com to the SPF record, but honestly i do not understand how the SPF record should change anything in this situation.

      Can someone explain like i'm 5 how this would actually work?
      And i guess, i'll still not be able to get rid of the MX error on the status page right, at least i do not see a connection here?

      Thanks in advance everyone!

      murgeroM Offline
      murgeroM Offline
      murgero
      App Dev
      wrote on last edited by murgero
      #2

      @teamcrw With the mx record and spf matching cloudron will see that and probably either suppress or remove the errors.

      To quote:

      Cloudron has a anti-spoof feature to ensure that only it can generate emails for the incoming domains. This feature will prevent the external MX from forwarding emails to it. However, Cloudron skips this spoof check for servers listed in the domain's SPF record. So, white list the MX's IP address block in the domain's SPF record. Note that it is necessary to specifically whitelist the server(s).

      This means Cloudron uses the SPF record to confirm emails sent from a domain cloudron controls uses the right server(s). Add the N-able MX servers to SPF and call it day I'd say

      --
      https://urgero.org
      ~ Professional Nerd. Freelance Programmer. ~

      T 1 Reply Last reply
      2
      • murgeroM murgero

        @teamcrw With the mx record and spf matching cloudron will see that and probably either suppress or remove the errors.

        To quote:

        Cloudron has a anti-spoof feature to ensure that only it can generate emails for the incoming domains. This feature will prevent the external MX from forwarding emails to it. However, Cloudron skips this spoof check for servers listed in the domain's SPF record. So, white list the MX's IP address block in the domain's SPF record. Note that it is necessary to specifically whitelist the server(s).

        This means Cloudron uses the SPF record to confirm emails sent from a domain cloudron controls uses the right server(s). Add the N-able MX servers to SPF and call it day I'd say

        T Offline
        T Offline
        teamcrw
        wrote on last edited by
        #3

        @murgero thank you!

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Bookmarks
        • Search