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. Gmail - ipv6. Anyone else with this experience?

Gmail - ipv6. Anyone else with this experience?

Scheduled Pinned Locked Moved Solved Support
22 Posts 5 Posters 3.8k Views 5 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.
  • avatar1024A Offline
    avatar1024A Offline
    avatar1024
    wrote on last edited by avatar1024
    #13

    So the IP is much longer than yours:
    image.png

    As you can tell, I probably do not understand IPv6 very well...

    From my provider my server IPv6 seem to be:
    c6996231-3682-4f5f-95a3-4c0b1b643eab-image.png

    So a bit like yours and something much shorter that what Google write in the bounce error message. Bur I thought this was normal as elsewhere in the provider settings page for my server it says:
    e0f205c5-b891-4fa5-9fca-d4f4728c8dbc-image.png

    So putting top and bottom address together I get the long IP google is writing in the error message.

    1 Reply Last reply
    0
    • andreasduerenA Offline
      andreasduerenA Offline
      andreasdueren
      wrote on last edited by
      #14

      Just to clarify: take the IPv6 that is written in the google mail and compare it to the PTR record. Are they identical?

      avatar1024A 1 Reply Last reply
      0
      • andreasduerenA andreasdueren

        Just to clarify: take the IPv6 that is written in the google mail and compare it to the PTR record. Are they identical?

        avatar1024A Offline
        avatar1024A Offline
        avatar1024
        wrote on last edited by
        #15

        @andreasdueren said in Gmail - ipv6. Anyone else with this experience?:

        Just to clarify: take the IPv6 that is written in the google mail and compare it to the PTR record. Are they identical?

        Yes they are!

        1 Reply Last reply
        0
        • avatar1024A Offline
          avatar1024A Offline
          avatar1024
          wrote on last edited by
          #16

          I've now also set a PTR record against the short IPv6, it has propagated but I'm still getting the straight bounce.

          1 Reply Last reply
          0
          • avatar1024A avatar1024

            Also I spoke a bit too quickly I'm actually getting delivery issues on all domains, just on two of them, the emails do end up delivering after a couple of retry by the mail server (the retries are still because of the PTR record), whereas on the third one it's just a straight bounce.

            avatar1024A Offline
            avatar1024A Offline
            avatar1024
            wrote on last edited by
            #17

            @avatar1024 said in Gmail - ipv6. Anyone else with this experience?:

            on two of them, the emails do end up delivering after a couple of retry by the mail server (the retries are still because of the PTR record)

            Actually in some rare case, the server retries indefinitely and emails are never delivered. From the email event log:

            Delivery failure. Will retry in Xs. Upstream error: 421 4.7.23 [2a03:xxxx:xx:xxx:xxxx:7fff:fe49:51af] The IP address sending this 4.7.23 message does not have a PTR record, or the corresponding forward DNS 4.7.23 entry does not match the sending IP. To protect our users from spam, 4.7.23 mail has been temporarily rate limited. To learn more about IP 4.7.23 address requirements for sending to Gmail, visit 4.7.23 https://support.google.com/a?p=sender-guidelines-ip 4.7.23 To learn more about Gmail requirements for bulk senders, visit 4.7.23 https://support.google.com/a?p=sender-guidelines. 4fb4d7f45d1cf-5d807030e25si25472762a12.537 - gsmtp",

            Using the exact IPv6 in the error message on https://toolbox.googleapps.com/apps/dig/#PTR/ gives the correct PTR.

            1 Reply Last reply
            1
            • avatar1024A Offline
              avatar1024A Offline
              avatar1024
              wrote on last edited by
              #18

              Until this is solved, is it possible to disable IPv6 completely from the mail service? This is affecting basically all of my servers.

              1 Reply Last reply
              0
              • J Offline
                J Offline
                joseph
                Staff
                wrote on last edited by
                #19

                You can just disable ipv6 on the server. It's the OS that decides IPv4/IPv6 for outbound connections. For example, sysctl -w net.ipv6.conf.ens18.disable_ipv6=1 (replace ens18) for specific interface.

                1 Reply Last reply
                1
                • avatar1024A Offline
                  avatar1024A Offline
                  avatar1024
                  wrote on last edited by
                  #20

                  @joseph Brill, that works, thank you!! All messages are now going through 🙂

                  Is there any big drawbacks in disabling IPv6? Also since it only happens with Gmail, is there a way to tell the system with IPv6 to only use IPv4 for google MX?

                  1 Reply Last reply
                  1
                  • J Offline
                    J Offline
                    joseph
                    Staff
                    wrote on last edited by
                    #21

                    Can't think of a drawback of disabling IPv6 on the server. You should disable IPv6 on Cloudron side if this got auto-enabled Network -> IPv6 -> Diable. This way it won't configure AAAA records. You will have issues when installing new apps otherwise.

                    1 Reply Last reply
                    2
                    • BrutalBirdieB BrutalBirdie referenced this topic on
                    • avatar1024A Offline
                      avatar1024A Offline
                      avatar1024
                      wrote on last edited by avatar1024
                      #22

                      Right so we have a bunch of similar topics referencing the same problem.

                      • https://forum.cloudron.io/topic/13162/unable-to-send-emails-to-gmail
                      • https://forum.cloudron.io/topic/13145/problems-with-sending-mail
                      • https://forum.cloudron.io/topic/13122/email-sending-broken-after-updating-to-8-2-x-due-to-ipv6-issues
                      • https://forum.cloudron.io/topic/13072/gmail-ipv6-anyone-else-with-this-experience

                      Should they all be merged and/or marked as solved?

                      The solution is provided by @girish (here) and @jdaviescoates (here) which I'll compile and summarise here again:

                      1. Activate IPv6 on Cloudron via going to Network > IPv6 > Configure > Public IP
                      2. Check your IPv6 address either via reading the IPv6 address detected by Cloudron when doing 1. or via running curl https://ipv6.api.cloudron.io/api/v1/helper/public_ip on your server (via ssh).
                      3. Set an IPv6 PTR record on your VPS/server provider (not your domain provider) for the above IPv6 address. The next Cloudron release will implement a check on IPv6 PTR record like it currently does for IPv4.
                      4. If using Wildcard DNS then create a * AAAA record for the above IPv6 address.
                      5. If things still don't work, you can go to Cloudron -> Domains -> hit Sync DNS

                      If your VPS provider does not allow you to set IPv6 PTR, then disable IPv6 that way:

                      1. disable IPv6 in Cloudron (Network -> IPv6 -> Disable)
                      2. on your server via ssh run sysctl -w net.ipv6.conf.ens18.disable_ipv6=1 (replacing ens18 for your specific network interface, in my case eth0)
                      3. make it persistent by adding net.ipv6.conf.ens18.disable_ipv6=1 to /etc/sysctl.conf (replacing ens18 for your specific network interface, in my case eth0)

                      Update: I personally still faced issues with Gmail using IPv6 so I ended up disabling it persistently.

                      1 Reply Last reply
                      6
                      • J joseph has marked this topic as solved on
                      • jdaviescoatesJ jdaviescoates referenced this topic on
                      • jdaviescoatesJ jdaviescoates referenced this topic on
                      • jdaviescoatesJ jdaviescoates referenced this topic on
                      • jdaviescoatesJ jdaviescoates referenced this topic on
                      • jdaviescoatesJ jdaviescoates referenced this topic on
                      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