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 healthcheck notification: "Relay error: Connect to smtp.live.com timed out"

Email healthcheck notification: "Relay error: Connect to smtp.live.com timed out"

Scheduled Pinned Locked Moved Solved Support
emailoutbound
33 Posts 11 Posters 4.3k Views 9 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.
  • nebulonN Offline
    nebulonN Offline
    nebulon
    Staff
    wrote on last edited by
    #24

    Can you run telnet port25check.cloudron.io 25 via SSH on your server to see if it works?

    1 Reply Last reply
    0
    • J Offline
      J Offline
      jayonrails
      translator
      wrote on last edited by
      #25

      Hi,

      it does work on my server:

      telnet port25check.cloudron.io 25
      Trying 165.227.67.76...
      Connected to api.cloudron.io.
      Escape character is '^]'.
      works
      Connection closed by foreign host.
      

      Is it important? I am using Postmark as a mail relay on all my outgoing mails, so I think it is not neccesary to have port 25 open in general, because it is never used?

      1 Reply Last reply
      0
      • nebulonN Offline
        nebulonN Offline
        nebulon
        Staff
        wrote on last edited by
        #26

        If you use a mail relay for all your domains, then this should not be relevant. I do wonder why it tests for it then and also why the check fails, since the code also just checks like that. Can you open the mail status tabs on all domains to see if this was just a temporary issue?

        J 1 Reply Last reply
        0
        • nebulonN nebulon

          If you use a mail relay for all your domains, then this should not be relevant. I do wonder why it tests for it then and also why the check fails, since the code also just checks like that. Can you open the mail status tabs on all domains to see if this was just a temporary issue?

          J Offline
          J Offline
          jayonrails
          translator
          wrote on last edited by
          #27

          @nebulon said in Email healthcheck notification: "Relay error: Connect to smtp.live.com timed out":

          If you use a mail relay for all your domains, then this should not be relevant.

          Thanks for clarification!

          @nebulon said in Email healthcheck notification: "Relay error: Connect to smtp.live.com timed out":

          an you open the mail status tabs on all domains to see if this was just a temporary issue?

          I will check and let you know if I found something.

          1 Reply Last reply
          0
          • RoundHouse1924R Offline
            RoundHouse1924R Offline
            RoundHouse1924
            wrote on last edited by
            #28

            I had one domain using an external relay and having port 25 closed on the VPS. The above error was present, but disappeared when port 25 was opened.

            So, the port 25 check seems to be unnecessary and confusing for domains that use external relays.

            girishG 1 Reply Last reply
            0
            • RoundHouse1924R RoundHouse1924

              I had one domain using an external relay and having port 25 closed on the VPS. The above error was present, but disappeared when port 25 was opened.

              So, the port 25 check seems to be unnecessary and confusing for domains that use external relays.

              girishG Offline
              girishG Offline
              girish
              Staff
              wrote on last edited by
              #29

              @RoundHouse1924 said in Email healthcheck notification: "Relay error: Connect to smtp.live.com timed out":

              So, the port 25 check seems to be unnecessary and confusing for domains that use external relays.

              The port 25 check is skipped for domains with a relay. If you find otherwise, please let us know, cause it's a bug. I just tested it with a relay and it is skipped.

              RoundHouse1924R 1 Reply Last reply
              0
              • girishG girish

                @RoundHouse1924 said in Email healthcheck notification: "Relay error: Connect to smtp.live.com timed out":

                So, the port 25 check seems to be unnecessary and confusing for domains that use external relays.

                The port 25 check is skipped for domains with a relay. If you find otherwise, please let us know, cause it's a bug. I just tested it with a relay and it is skipped.

                RoundHouse1924R Offline
                RoundHouse1924R Offline
                RoundHouse1924
                wrote on last edited by RoundHouse1924
                #30

                @girish
                The situation I described was with v7.3.6 when I had only one outgoing domain and it used an external relay.

                Now with v7.4.1, I have 3 outgoing domains. One via the same external relay; the other 2 using the internal SMTP. Port 25 is open on the VPS and all 3 status lights are green.

                So, in order to test your answer, I blocked outgoing Port 25 on the VPS firewall.

                As expected, the 2 direct domains go red.

                However, the external relay domain's Cloudron status page shows:-
                MX record = Current value: [not set]
                DMARC record = Current value: [not set]
                SMTP Status Outbound SMTP (Relay) = Connection timeout

                Looks to me that, with Port 25 closed, the SMTP check is made, but times out.

                The puzzler is to know what could be causing the MX and DMARC record checks to fail --- just because Port 25 is closed.

                EDIT:
                With Port 25 closed, Uptime Kuma and Tiny Tiny RSS cannot do their stuff, so I've now reopened it.

                1 Reply Last reply
                0
                • girishG Offline
                  girishG Offline
                  girish
                  Staff
                  wrote on last edited by
                  #31

                  Strange, why would Uptime Kuma and TTRSS fail with port 25 closed ?

                  Here's what I did:

                  • Block the outbound port 25 - iptables -A OUTPUT -p tcp --destination-port 25 -j DROP

                  • Check status:
                    image.png

                  • Unblock - iptables -D OUTPUT 1

                  • Check status again:
                    image.png

                  1 Reply Last reply
                  0
                  • girishG Offline
                    girishG Offline
                    girish
                    Staff
                    wrote on last edited by
                    #32

                    And when a relay is configured:

                    image.png

                    1 Reply Last reply
                    0
                    • RoundHouse1924R Offline
                      RoundHouse1924R Offline
                      RoundHouse1924
                      wrote on last edited by
                      #33

                      Strange indeed, but I blocked the VPS Port 25. Whilst blocked, I restarted Kuma and Tiny but to no avail.

                      All up and running now with 25 unblocked.

                      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