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. "Email not configured properly" with PTR4 issue

"Email not configured properly" with PTR4 issue

Scheduled Pinned Locked Moved Unsolved Support
ptrptr recordsmail
2 Posts 2 Posters 26 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.
  • aurelien-cA Offline
    aurelien-cA Offline
    aurelien-c
    wrote last edited by
    #1

    Hi all,

    We have in the daily logs:

    Email not configured properly:
    company.space

    PTR4 DNS record (PTR) did not match.
        Hostname: 164.172.73.196
        Expected: my.company.space
        Actual: null
    

    (I've slightly edited the values)
    This has been there for a long time.

    Now, I had a look at the configuration of our server and it indicates

    164.172.73.196
    Reverse my.company.space.

    A call to "dig -x <ip>" shows:

    ... IN PTR my.company.space.

    The troubleshooting section of the docs do not appear to bear fruit about this.
    Any clue ?

    Thanks in advance,
    Aurélien

    jamesJ 1 Reply Last reply
    0
    • aurelien-cA aurelien-c

      Hi all,

      We have in the daily logs:

      Email not configured properly:
      company.space

      PTR4 DNS record (PTR) did not match.
          Hostname: 164.172.73.196
          Expected: my.company.space
          Actual: null
      

      (I've slightly edited the values)
      This has been there for a long time.

      Now, I had a look at the configuration of our server and it indicates

      164.172.73.196
      Reverse my.company.space.

      A call to "dig -x <ip>" shows:

      ... IN PTR my.company.space.

      The troubleshooting section of the docs do not appear to bear fruit about this.
      Any clue ?

      Thanks in advance,
      Aurélien

      jamesJ Offline
      jamesJ Offline
      james
      Staff
      wrote last edited by
      #2

      Hello @aurelien-c

      When I run:

      # Ask Cloudflare about the PTR
      dig -x 164.172.73.196 +short @1.1.1.1
      # Ask Google about the PTR
      dig -x 164.172.73.196 +short @8.8.8.8
      

      I get no answer.
      This indicated that no PTR record has been set.

      From the documentation https://docs.cloudron.io/email/#ptr-record

      The PTR record is set by your VPS provider and not by your DNS provider.. For example, if your server was created in Digital Ocean, you must go to Digital Ocean to set the PTR record.

      @aurelien-c said in "Email not configured properly" with PTR4 issue:

      The troubleshooting section of the docs do not appear to bear fruit about this.

      Did you read the docs.cloudron.io/email/#ptr-record or docs.cloudron.io/email/#troubleshooting?
      And, did you configure the PTR in your Hoster?

      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