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. Feature Requests
  3. Automated server reboot

Automated server reboot

Scheduled Pinned Locked Moved Feature Requests
feature-request
37 Posts 7 Posters 5.5k Views 7 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.
  • girishG Offline
    girishG Offline
    girish
    Staff
    wrote on last edited by
    #12

    You can use swaks like this:

    First get the IP of the mail container:

    # docker inspect --format '{{ .NetworkSettings.Networks.cloudron.IPAddress }}' mail
    172.18.0.2
    

    Then, you need the "token" which is the auth to send mails:

    # docker inspect --format '{{ .Config.Env }}' mail | tr ' ' '\n' | grep CLOUDRON_RELAY_TOKEN | sed 's/^.*=//'
    9e000daa7ba34f29ed975d54b880f30794c2cebcd795f124
    

    Now, you can send using swaks (replace IP and token below):

    # swaks -s 172.18.0.2 -p 2525 --au no-reply@cloudron.space --ap 9e000daa7ba34f29ed975d54b880f30794c2cebcd795f1241 -f 'no-reply@cloudron.space' -t 'test@cloudron.io' --h-Subject "Test mail"
    
    potemkin_aiP 1 Reply Last reply
    0
    • girishG girish

      You can use swaks like this:

      First get the IP of the mail container:

      # docker inspect --format '{{ .NetworkSettings.Networks.cloudron.IPAddress }}' mail
      172.18.0.2
      

      Then, you need the "token" which is the auth to send mails:

      # docker inspect --format '{{ .Config.Env }}' mail | tr ' ' '\n' | grep CLOUDRON_RELAY_TOKEN | sed 's/^.*=//'
      9e000daa7ba34f29ed975d54b880f30794c2cebcd795f124
      

      Now, you can send using swaks (replace IP and token below):

      # swaks -s 172.18.0.2 -p 2525 --au no-reply@cloudron.space --ap 9e000daa7ba34f29ed975d54b880f30794c2cebcd795f1241 -f 'no-reply@cloudron.space' -t 'test@cloudron.io' --h-Subject "Test mail"
      
      potemkin_aiP Offline
      potemkin_aiP Offline
      potemkin_ai
      wrote on last edited by
      #13

      @girish thank you so much!

      I love automation and one-liners, so I guess it could be all combined into one command:

      swaks -s `docker inspect --format '{{ .NetworkSettings.Networks.cloudron.IPAddress }}' mail` -p 2525 --au $MY_LOCAL_MAILBOX --ap `docker inspect --format '{{ .Config.Env }}' mail | tr ' ' '\n' | grep CLOUDRON_RELAY_TOKEN | sed 's/^.*=//'` -f '$MY_LOCAL_MAILBOX' -t '$MY_PERSONAL_MAIL' --h-Subject "Test mail"
      

      The only problem - is that it doesn't work - please, find the output below:

      === Trying 172.18.0.5:2525...
      === Connected to 172.18.0.5.
      <-  220 my.domain ESMTP Haraka/2.8.27 ready
       -> EHLO localhost
      <-  250-my.domain Hello [172.18.0.1]Haraka is at your service.
      <-  250-PIPELINING
      <-  250-8BITMIME
      <-  250-SMTPUTF8
      <-  250-SIZE 26214400
      <-  250 AUTH LOGIN PLAIN
       -> AUTH LOGIN
      <-  334 VXNlcm5hbWU6
       -> YWxleEBwb3RlbWtpbi5jbw==
      <-  334 UGFzc3dvcmQ6
       -> $TOKEN==
      <** 535 5.7.8 Authentication failed
       -> AUTH PLAIN AGFsZXhAcG90ZW1raW4uY28A$TOKEN==
      <** 535 5.7.8 Authentication failed
      *** No authentication type succeeded
       -> QUIT
      <-  221 my.domain closing connection. Have a jolly good day.
      === Connection closed with remote host.
      

      Any thoughts what could went wrong?

      girishG 1 Reply Last reply
      0
      • nebulonN nebulon

        @potemkin_ai maybe we can take a closer look for the next release. So far the automatic reboot wasn't a pressing issue, so if you need this anytime soon, I guess a simple bashscript doing all this for you will be best. Would be nice if you could share it here, since I currently wouldn't even know how to figure out if any of the packages would have failed to notify.

        Also we do not have any generic email route to just send out custom text to the admins via the mail configuration since there was no use-case for this either.

        Further with Ubuntu 20 and ongoing I think there is also a possibility to avoid reboots altogether for kernel updates, so maybe this would be a better solution in the long run anyways?

        potemkin_aiP Offline
        potemkin_aiP Offline
        potemkin_ai
        wrote on last edited by
        #14

        @nebulon did you mean manual configuration for that service?
        https://ubuntu.com/tutorials/enable-the-livepatch-service#1-overview

        nebulonN 1 Reply Last reply
        0
        • potemkin_aiP potemkin_ai

          @nebulon did you mean manual configuration for that service?
          https://ubuntu.com/tutorials/enable-the-livepatch-service#1-overview

          nebulonN Offline
          nebulonN Offline
          nebulon
          Staff
          wrote on last edited by
          #15

          @potemkin_ai yes I was referring to this, but I haven't really had a deeper look into that topic yet and to which extent this is free or a paid addon in ubuntu.

          potemkin_aiP 1 Reply Last reply
          0
          • potemkin_aiP potemkin_ai

            @girish thank you so much!

            I love automation and one-liners, so I guess it could be all combined into one command:

            swaks -s `docker inspect --format '{{ .NetworkSettings.Networks.cloudron.IPAddress }}' mail` -p 2525 --au $MY_LOCAL_MAILBOX --ap `docker inspect --format '{{ .Config.Env }}' mail | tr ' ' '\n' | grep CLOUDRON_RELAY_TOKEN | sed 's/^.*=//'` -f '$MY_LOCAL_MAILBOX' -t '$MY_PERSONAL_MAIL' --h-Subject "Test mail"
            

            The only problem - is that it doesn't work - please, find the output below:

            === Trying 172.18.0.5:2525...
            === Connected to 172.18.0.5.
            <-  220 my.domain ESMTP Haraka/2.8.27 ready
             -> EHLO localhost
            <-  250-my.domain Hello [172.18.0.1]Haraka is at your service.
            <-  250-PIPELINING
            <-  250-8BITMIME
            <-  250-SMTPUTF8
            <-  250-SIZE 26214400
            <-  250 AUTH LOGIN PLAIN
             -> AUTH LOGIN
            <-  334 VXNlcm5hbWU6
             -> YWxleEBwb3RlbWtpbi5jbw==
            <-  334 UGFzc3dvcmQ6
             -> $TOKEN==
            <** 535 5.7.8 Authentication failed
             -> AUTH PLAIN AGFsZXhAcG90ZW1raW4uY28A$TOKEN==
            <** 535 5.7.8 Authentication failed
            *** No authentication type succeeded
             -> QUIT
            <-  221 my.domain closing connection. Have a jolly good day.
            === Connection closed with remote host.
            

            Any thoughts what could went wrong?

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

            @potemkin_ai said in Automated server reboot:

            -> $TOKEN==
            <** 535 5.7.8 Authentication failed
            -> AUTH PLAIN AGFsZXhAcG90ZW1raW4uY28A$TOKEN==
            <** 535 5.7.8 Authentication failed
            *** No authentication type succeeded

            Something wrong in the script. It's sending $TOKEN

            potemkin_aiP 1 Reply Last reply
            0
            • nebulonN nebulon

              @potemkin_ai yes I was referring to this, but I haven't really had a deeper look into that topic yet and to which extent this is free or a paid addon in ubuntu.

              potemkin_aiP Offline
              potemkin_aiP Offline
              potemkin_ai
              wrote on last edited by
              #17

              @nebulon got it, makes sense, but from what I see it requires extra configuration anyway and most probably won't be available out of the box, so an automatic reboot would be of great help; especially for the next two years while 18.04LTS is supported

              1 Reply Last reply
              0
              • girishG girish

                @potemkin_ai said in Automated server reboot:

                -> $TOKEN==
                <** 535 5.7.8 Authentication failed
                -> AUTH PLAIN AGFsZXhAcG90ZW1raW4uY28A$TOKEN==
                <** 535 5.7.8 Authentication failed
                *** No authentication type succeeded

                Something wrong in the script. It's sending $TOKEN

                potemkin_aiP Offline
                potemkin_aiP Offline
                potemkin_ai
                wrote on last edited by
                #18

                @girish thank you.

                I re-did all the steps manually as per your original message and got the same error.

                The only major difference between your and my setup - it's token length - it's 257 characters long in my case.

                Any clue?

                girishG 1 Reply Last reply
                0
                • potemkin_aiP potemkin_ai

                  @girish thank you.

                  I re-did all the steps manually as per your original message and got the same error.

                  The only major difference between your and my setup - it's token length - it's 257 characters long in my case.

                  Any clue?

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

                  @potemkin_ai command below works for me. One thing is the no-reply@mydomain.com is important! You cannot change the mailbox name. The mail server does not allow sending emails as any other name for security from localhost.

                  # swaks -s `docker inspect --format '{{ .NetworkSettings.Networks.cloudron.IPAddress }}' mail` -p 2525 --au no-reply@cloudron.space --ap `docker inspect --format '{{ .Config.Env }}' mail | tr ' ' '\n' | grep CLOUDRON_RELAY_TOKEN | sed 's/^.*=//'` -f no-reply@cloudron.space -t 'test@cloudron.io' --h-Subject "Test mail"
                  === Trying 172.18.0.3:2525...
                  === Connected to 172.18.0.3.
                  <-  220 my.cloudron.space ESMTP Haraka/2.8.28 ready
                   -> EHLO upgrade-test
                  <-  250-my.cloudron.space Hello [172.18.0.1]Haraka is at your service.
                  <-  250-PIPELINING
                  <-  250-8BITMIME
                  <-  250-SMTPUTF8
                  <-  250-SIZE 26214400
                  <-  250 AUTH LOGIN PLAIN
                   -> AUTH LOGIN
                  <-  334 VXNlcm5hbWU6
                   -> bm8tcmVwbHlAY2xvdWRyb24uc3BhY2U=
                  <-  334 UGFzc3dvcmQ6
                   -> OWZmOGU4MWI4NTJmNjMxOWVlNWI4NjM0NDQ1ZDE1ZTliYTI5ZWY3NjE5N2UwZWE0MmM5OGJlMTI0ZjQ4NjFhM2EzZmEyNDQ2Yzk2MzVmODYzMDNiNTUwNjRiMDRjOGYwNjc1M2U3NjIxZGJhOGFmZGY1YWJlODUyYmVmMTVmZWVjNmFiOTVjYmE1MDJhNGY5OGZiMjBjMWZiZDA3YjBlMDFjOTBhOTE4NTRhOGY4ZDNhYWI2ZmYyMGJkMjUzZjY1NDAwNmE0YmRjZGVhMmM2ZGYzYTY0YjcxMWRjZmQxODE5Y2FiZDJhMmMyMTY2YTJhYmE5MjA4NGNjNDhmN2E1ZQ==
                  <-  235 2.7.0 Authentication successful
                   -> MAIL FROM:<no-reply@cloudron.space>
                  <-  250 sender <no-reply@cloudron.space> OK
                   -> RCPT TO:<test@cloudron.io>
                  <-  250 recipient <test@cloudron.io> OK
                   -> DATA
                  <-  354 go ahead, make my day
                   -> Date: Fri, 22 Oct 2021 18:59:51 +0000
                   -> To: test@cloudron.io
                   -> From: no-reply@cloudron.space
                   -> Subject: Test mail
                   -> Message-Id: <20211022185951.169923@upgrade-test>
                   -> X-Mailer: swaks v20190914.0 jetmore.org/john/code/swaks/
                   -> 
                   -> This is a test mailing
                   -> 
                   -> 
                   -> .
                  <-  250 Message Queued (0741EB98-48BA-4A23-AB22-FB67C176AF7B.1)
                   -> QUIT
                  <-  221 my.cloudron.space closing connection. Have a jolly good day.
                  === Connection closed with remote host.
                  
                  potemkin_aiP 1 Reply Last reply
                  0
                  • girishG girish

                    @potemkin_ai command below works for me. One thing is the no-reply@mydomain.com is important! You cannot change the mailbox name. The mail server does not allow sending emails as any other name for security from localhost.

                    # swaks -s `docker inspect --format '{{ .NetworkSettings.Networks.cloudron.IPAddress }}' mail` -p 2525 --au no-reply@cloudron.space --ap `docker inspect --format '{{ .Config.Env }}' mail | tr ' ' '\n' | grep CLOUDRON_RELAY_TOKEN | sed 's/^.*=//'` -f no-reply@cloudron.space -t 'test@cloudron.io' --h-Subject "Test mail"
                    === Trying 172.18.0.3:2525...
                    === Connected to 172.18.0.3.
                    <-  220 my.cloudron.space ESMTP Haraka/2.8.28 ready
                     -> EHLO upgrade-test
                    <-  250-my.cloudron.space Hello [172.18.0.1]Haraka is at your service.
                    <-  250-PIPELINING
                    <-  250-8BITMIME
                    <-  250-SMTPUTF8
                    <-  250-SIZE 26214400
                    <-  250 AUTH LOGIN PLAIN
                     -> AUTH LOGIN
                    <-  334 VXNlcm5hbWU6
                     -> bm8tcmVwbHlAY2xvdWRyb24uc3BhY2U=
                    <-  334 UGFzc3dvcmQ6
                     -> OWZmOGU4MWI4NTJmNjMxOWVlNWI4NjM0NDQ1ZDE1ZTliYTI5ZWY3NjE5N2UwZWE0MmM5OGJlMTI0ZjQ4NjFhM2EzZmEyNDQ2Yzk2MzVmODYzMDNiNTUwNjRiMDRjOGYwNjc1M2U3NjIxZGJhOGFmZGY1YWJlODUyYmVmMTVmZWVjNmFiOTVjYmE1MDJhNGY5OGZiMjBjMWZiZDA3YjBlMDFjOTBhOTE4NTRhOGY4ZDNhYWI2ZmYyMGJkMjUzZjY1NDAwNmE0YmRjZGVhMmM2ZGYzYTY0YjcxMWRjZmQxODE5Y2FiZDJhMmMyMTY2YTJhYmE5MjA4NGNjNDhmN2E1ZQ==
                    <-  235 2.7.0 Authentication successful
                     -> MAIL FROM:<no-reply@cloudron.space>
                    <-  250 sender <no-reply@cloudron.space> OK
                     -> RCPT TO:<test@cloudron.io>
                    <-  250 recipient <test@cloudron.io> OK
                     -> DATA
                    <-  354 go ahead, make my day
                     -> Date: Fri, 22 Oct 2021 18:59:51 +0000
                     -> To: test@cloudron.io
                     -> From: no-reply@cloudron.space
                     -> Subject: Test mail
                     -> Message-Id: <20211022185951.169923@upgrade-test>
                     -> X-Mailer: swaks v20190914.0 jetmore.org/john/code/swaks/
                     -> 
                     -> This is a test mailing
                     -> 
                     -> 
                     -> .
                    <-  250 Message Queued (0741EB98-48BA-4A23-AB22-FB67C176AF7B.1)
                     -> QUIT
                    <-  221 my.cloudron.space closing connection. Have a jolly good day.
                    === Connection closed with remote host.
                    
                    potemkin_aiP Offline
                    potemkin_aiP Offline
                    potemkin_ai
                    wrote on last edited by
                    #20

                    @girish thank you - tried that, but authentification is still failing at 334 step.

                    My primary concern remains token, because mine is muuuuch longer than yours (hope it sounds right in the context of token comparison....), and authentication is failing right after mail service gets it.

                    Any way to troubleshoot that?

                    humptydumptyH girishG 2 Replies Last reply
                    0
                    • potemkin_aiP potemkin_ai

                      @girish thank you - tried that, but authentification is still failing at 334 step.

                      My primary concern remains token, because mine is muuuuch longer than yours (hope it sounds right in the context of token comparison....), and authentication is failing right after mail service gets it.

                      Any way to troubleshoot that?

                      humptydumptyH Offline
                      humptydumptyH Offline
                      humptydumpty
                      wrote on last edited by
                      #21

                      @potemkin_ai Can't you use something like "Uptime Kuma" to monitor site status instead?

                      It has "Notifications via Webhook, Telegram, Discord and email (SMTP)" so it should work for your use-case.

                      potemkin_aiP 1 Reply Last reply
                      0
                      • humptydumptyH humptydumpty

                        @potemkin_ai Can't you use something like "Uptime Kuma" to monitor site status instead?

                        It has "Notifications via Webhook, Telegram, Discord and email (SMTP)" so it should work for your use-case.

                        potemkin_aiP Offline
                        potemkin_aiP Offline
                        potemkin_ai
                        wrote on last edited by
                        #22

                        @humptydumpty I probably could, but what's the point?
                        There is a working solution from Cloudron, we just need to figure out where exactly it's failing.

                        humptydumptyH 1 Reply Last reply
                        0
                        • potemkin_aiP potemkin_ai

                          @girish thank you - tried that, but authentification is still failing at 334 step.

                          My primary concern remains token, because mine is muuuuch longer than yours (hope it sounds right in the context of token comparison....), and authentication is failing right after mail service gets it.

                          Any way to troubleshoot that?

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

                          @potemkin_ai the long token is fine, i had just pruned it for pasting here.

                          potemkin_aiP 1 Reply Last reply
                          0
                          • girishG girish

                            @potemkin_ai the long token is fine, i had just pruned it for pasting here.

                            potemkin_aiP Offline
                            potemkin_aiP Offline
                            potemkin_ai
                            wrote on last edited by
                            #24

                            @girish right... why doesn't mine working then?

                            girishG 1 Reply Last reply
                            0
                            • potemkin_aiP potemkin_ai

                              @humptydumpty I probably could, but what's the point?
                              There is a working solution from Cloudron, we just need to figure out where exactly it's failing.

                              humptydumptyH Offline
                              humptydumptyH Offline
                              humptydumpty
                              wrote on last edited by
                              #25

                              @potemkin_ai said in Automated server reboot:

                              I probably could, but what's the point?

                              It's two birds with one stone. You end up having app/site monitoring too but I'm not against your method. I'm just suggesting alternatives for consideration.

                              potemkin_aiP 1 Reply Last reply
                              1
                              • humptydumptyH humptydumpty

                                @potemkin_ai said in Automated server reboot:

                                I probably could, but what's the point?

                                It's two birds with one stone. You end up having app/site monitoring too but I'm not against your method. I'm just suggesting alternatives for consideration.

                                potemkin_aiP Offline
                                potemkin_aiP Offline
                                potemkin_ai
                                wrote on last edited by
                                #26

                                @humptydumpty thank you, but my server is already monitored - both from inside (with the monitoring agent) and from the outside (via http ping), so my only task now, it’s to ensure I can drop an e-mail notification to myself, so that if my monitoring shows that the server is not available, I can see an e-mail next to the monitoring saying, that the server was going to reboot itself, which will help me to understand and fix that in no time, instead of guessing what could went wrong.

                                1 Reply Last reply
                                3
                                • potemkin_aiP potemkin_ai

                                  @girish right... why doesn't mine working then?

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

                                  @potemkin_ai We can try it step by step:

                                  docker inspect --format '{{ .Config.Env }}' mail | tr ' ' '\n' | grep CLOUDRON_RELAY_TOKEN
                                  CLOUDRON_RELAY_TOKEN=71df0df31cb3512bfe8fad02561cda813c6db4f94d2cb7137bbc162e9c1775058887606e5c37b8013df08498e3c609f52f1147cbb5a9ad96b7f4c5e848a235c44569510c37ab25eaaa67d50641481843cad93c7221893a869e34411d3e8edf6f55e3b7d8fa3ab1ce7632e0fd3bf65a8050549fe4d43d50e3ddb1c2c6b0eaca0d
                                  root@upgrade-test:~# echo "71df0df31cb3512bfe8fad02561cda813c6db4f94d2cb7137bbc162e9c1775058887606e5c37b8013df08498e3c609f52f1147cbb5a9ad96b7f4c5e848a235c44569510c37ab25eaaa67d50641481843cad93c7221893a869e34411d3e8edf6f55e3b7d8fa3ab1ce7632e0fd3bf65a8050549fe4d43d50e3ddb1c2c6b0eaca0d" | wc -c
                                  257
                                  

                                  So, mine is also 257 characters long.

                                  # docker inspect --format '{{ .NetworkSettings.Networks.cloudron.IPAddress }}' mail
                                  172.18.0.3
                                  

                                  The final command:

                                  # swaks -s 172.18.0.3 -p 2525 --au no-reply@cloudron.space --ap "71df0df31cb3512bfe8fad02561cda813c6db4f94d2cb7137bbc162e9c1775058887606e5c37b8013df08498e3c609f52f1147cbb5a9ad96b7f4c5e848a235c44569510c37ab25eaaa67d50641481843cad93c7221893a869e34411d3e8edf6f55e3b7d8fa3ab1ce7632e0fd3bf65a8050549fe4d43d50e3ddb1c2c6b0eaca0d" -f no-reply@cloudron.space -t 'test@cloudron.io' --h-Subject "Test mail"
                                  

                                  Can you paste your entire sequence like above? Note that it has to be no-reply@yourdomain.com for both the --au argument and the -f argument.

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

                                    Also, maybe someone else can try the above too πŸ™‚ Just to be sure I am not missing something obvious.

                                    fbartelsF 1 Reply Last reply
                                    0
                                    • girishG girish

                                      Also, maybe someone else can try the above too πŸ™‚ Just to be sure I am not missing something obvious.

                                      fbartelsF Offline
                                      fbartelsF Offline
                                      fbartels
                                      App Dev
                                      wrote on last edited by
                                      #29

                                      @girish I can confirm that the following works for me:

                                      swaks -s `docker inspect --format '{{ .NetworkSettings.Networks.cloudron.IPAddress }}' mail` -p 2525 --au no-reply@9wd.eu --ap `docker inspect --format '{{ .Config.Env }}' mail | tr ' ' '\n' | grep CLOUDRON_RELAY_TOKEN | sed 's/^.*=//'` -f no-reply@9wd.eu -t 'test@9wd.eu' --h-Subject "Test mail"
                                      
                                      potemkin_aiP 1 Reply Last reply
                                      1
                                      • fbartelsF fbartels

                                        @girish I can confirm that the following works for me:

                                        swaks -s `docker inspect --format '{{ .NetworkSettings.Networks.cloudron.IPAddress }}' mail` -p 2525 --au no-reply@9wd.eu --ap `docker inspect --format '{{ .Config.Env }}' mail | tr ' ' '\n' | grep CLOUDRON_RELAY_TOKEN | sed 's/^.*=//'` -f no-reply@9wd.eu -t 'test@9wd.eu' --h-Subject "Test mail"
                                        
                                        potemkin_aiP Offline
                                        potemkin_aiP Offline
                                        potemkin_ai
                                        wrote on last edited by
                                        #30

                                        @fbartels @girish something is wrong here..

                                        Note that it has to be no-reply@yourdomain.com for both the --au argument and the -f argument.

                                        --au no-reply@9wd.eu ... -f no-reply@9wd.eu

                                        those two contradicts to each other...

                                        @fbartels does this command actually deliver an e-mail to test@9wd.eu?

                                        fbartelsF 1 Reply Last reply
                                        0
                                        • girishG girish

                                          @potemkin_ai We can try it step by step:

                                          docker inspect --format '{{ .Config.Env }}' mail | tr ' ' '\n' | grep CLOUDRON_RELAY_TOKEN
                                          CLOUDRON_RELAY_TOKEN=71df0df31cb3512bfe8fad02561cda813c6db4f94d2cb7137bbc162e9c1775058887606e5c37b8013df08498e3c609f52f1147cbb5a9ad96b7f4c5e848a235c44569510c37ab25eaaa67d50641481843cad93c7221893a869e34411d3e8edf6f55e3b7d8fa3ab1ce7632e0fd3bf65a8050549fe4d43d50e3ddb1c2c6b0eaca0d
                                          root@upgrade-test:~# echo "71df0df31cb3512bfe8fad02561cda813c6db4f94d2cb7137bbc162e9c1775058887606e5c37b8013df08498e3c609f52f1147cbb5a9ad96b7f4c5e848a235c44569510c37ab25eaaa67d50641481843cad93c7221893a869e34411d3e8edf6f55e3b7d8fa3ab1ce7632e0fd3bf65a8050549fe4d43d50e3ddb1c2c6b0eaca0d" | wc -c
                                          257
                                          

                                          So, mine is also 257 characters long.

                                          # docker inspect --format '{{ .NetworkSettings.Networks.cloudron.IPAddress }}' mail
                                          172.18.0.3
                                          

                                          The final command:

                                          # swaks -s 172.18.0.3 -p 2525 --au no-reply@cloudron.space --ap "71df0df31cb3512bfe8fad02561cda813c6db4f94d2cb7137bbc162e9c1775058887606e5c37b8013df08498e3c609f52f1147cbb5a9ad96b7f4c5e848a235c44569510c37ab25eaaa67d50641481843cad93c7221893a869e34411d3e8edf6f55e3b7d8fa3ab1ce7632e0fd3bf65a8050549fe4d43d50e3ddb1c2c6b0eaca0d" -f no-reply@cloudron.space -t 'test@cloudron.io' --h-Subject "Test mail"
                                          

                                          Can you paste your entire sequence like above? Note that it has to be no-reply@yourdomain.com for both the --au argument and the -f argument.

                                          potemkin_aiP Offline
                                          potemkin_aiP Offline
                                          potemkin_ai
                                          wrote on last edited by
                                          #31

                                          @girish sure, here it is:

                                          root@anabelle:~# docker inspect --format '{{ .Config.Env }}' mail | tr ' ' '\n' | grep CLOUDRON_RELAY_TOKEN
                                          CLOUDRON_RELAY_TOKEN=818e705168cd0605a63ee69228bdcdec7def1d170054c14281f27c3b986486adcdd447bf161f1f6b4eb858037abc19558cf8877bc1603c4a152db20c94aa9dd7eabb68a9da950b8e54684fcb75a531c808254c0a60165f20a825170b24b1b06bb833955750412d769257a3607cc5637e40dca57402be4ef67a1d4f91df329c22
                                          root@anabelle:~# echo "818e705168cd0605a63ee69228bdcdec7def1d170054c14281f27c3b986486adcdd447bf161f1f6b4eb858037abc19558cf8877bc1603c4a152db20c94aa9dd7eabb68a9da950b8e54684fcb75a531c808254c0a60165f20a825170b24b1b06bb833955750412d769257a3607cc5637e40dca57402be4ef67a1d4f91df329c22" | wc -c
                                          257
                                          root@anabelle:~# docker inspect --format '{{ .NetworkSettings.Networks.cloudron.IPAddress }}' mail
                                          172.18.0.5
                                          
                                          root@anabelle:~# swaks -s 172.18.0.5 -p 2525 --au no-reply@cloudron.space --ap "818e705168cd0605a63ee69228bdcdec7def1d170054c14281f27c3b986486adcdd447bf161f1f6b4eb858037abc19558cf8877bc1603c4a152db20c94aa9dd7eabb68a9da950b8e54684fcb75a531c808254c0a60165f20a825170b24b1b06bb833955750412d769257a3607cc5637e40dca57402be4ef67a1d4f91df329c22" -f no-reply@cloudron.space -t 'mypersonal@email.com' --h-Subject "Test mail"
                                          === Trying 172.18.0.5:2525...
                                          === Connected to 172.18.0.5.
                                          <-  220 my.serveddomain.com ESMTP Haraka/2.8.27 ready
                                           -> EHLO localhost
                                          <-  250-my.serveddomain.com Hello [172.18.0.1]Haraka is at your service.
                                          <-  250-PIPELINING
                                          <-  250-8BITMIME
                                          <-  250-SMTPUTF8
                                          <-  250-SIZE 26214400
                                          <-  250 AUTH LOGIN PLAIN
                                           -> AUTH LOGIN
                                          <-  334 VXNlcm5hbWU6
                                           -> bm8tcmVwbHlAY2xvdWRyb24uc3BhY2U=
                                          <-  334 UGFzc3dvcmQ6
                                           -> ODE4ZTcwNTE2OGNkYTYwMTY1ZjIwYTgyNTE3MGIyM2IxYjA2YmI4MzM5NTU3NTA0MTQwMmJlNGVmNjdhMWQ0ZjkxZGYyZDc2OTI1N2EzNjA3Y2M1NjM3ZTQwZGNhNTc4YmRjZGVjN2RlZjFkMTcwMDUyMjU1OGNmODg3N2JjMTYwMmM0YTE1MmNiMjljOTRhYTlkZDdlYTRjMTQyODFmMjdjM2I5ODY0ODZhZDA2MDVhNjNlZTY5YmI2OGE5ZGE5NTBiOGU1NDU4NGVjYjc1YTUzMGM4MDgyNTRjMGNkZDQ0N2JmMTYxZjFmNmI0ZWI4NTgwMzdhYmMxODMyOWMyMg==
                                          <** 535 5.7.8 Authentication failed
                                           -> AUTH PLAIN AG5vLXJlcGx5QGNsb3Vkcm9uLnNwYWNlADgxOGU3MDUxNjhjZGE2MDE2NWYyMGE4MjUxNzBiMjNiMWIwNmJiODMzOTU1NzUwNDE0MDJiZTRlZjY3YTFkNGY5MWRmMmQ3NjkyNTdhMzYwN2NjNTYzN2U0MGRjYTU3OGJkY2RlYzdkZWYxZDE3MDA1MjI1NThjZjg4NzdiYzE2MDJjNGExNTJjYjI5Yzk0YWE5ZGQ3ZWE0YzE0MjgxZjI3YzNiOTg2NDg2YWQwNjA1YTYzZWU2OWJiNjhhOWRhOTUwYjhlNTQ1ODRlY2I3NWE1MzBjODA4MjU0YzBjZGQ0NDdiZjE2MWYxZjZiNGViODU4MDM3YWJjMTgzMjljMjI=
                                          <** 535 5.7.8 Authentication failed
                                          *** No authentication type succeeded
                                           -> QUIT
                                          <-  221 my.serveddomain.com closing connection. Have a jolly good day.
                                          === Connection closed with remote host.
                                          
                                          girishG 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