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


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Solved SMTP default settings

    Listmonk
    3
    8
    323
    Loading More Posts
    • 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.
    • timconsidine
      timconsidine App Dev last edited by

      Hope this is not dumb question.
      Are the default SMTP settings on app install supposed to work ?

      Just trying the app out.
      Looks really nice.
      But can't get an email sent.
      Port seems strange : 2465
      And host just says mail - I was expecting something like my.mycloudron.tld

      Do we need to configure default settings ?
      I get we can add an extra 'messenger'.
      Just wondering about the default one added.

      robi 1 Reply Last reply Reply Quote 0
      • robi
        robi @timconsidine last edited by

        @timconsidine mail is correct as the internal container network DNS for the mail server. Port does seem off.

        Life of Advanced Technology

        timconsidine 1 Reply Last reply Reply Quote 1
        • timconsidine
          timconsidine App Dev @robi last edited by

          @robi some trial and error testing shows that mail and 2465 probably are correct.
          But I'm getting authentication failed.

          I changed the password to the one I set for the admin of the app.
          And tried my cloudron admin password.
          Neither work.
          Password field always resets to showing 8 stars ********
          Maybe just a default display but makes me suspicious whether the password change is being put into effect.

          Buy hey, I've probably screwed it up along the way with my trial & error testing.

          timconsidine 1 Reply Last reply Reply Quote 0
          • timconsidine
            timconsidine App Dev @timconsidine last edited by timconsidine

            @timconsidine still struggling with outbound email from Listmonk

            Whatever I try, I get :
            2022/05/31 11:28:30error sending message in campaign Test campaign: subscriber 86eeee23-7dc5-4112-b237-c2967d78f340: 535 5.7.8 Authentication failed
            Or in some test configs connection refused

            I might trash it and start over.
            But what password should be used for the mail host ?
            I thought the password for the Cloudron email user (Cloudron admin) but doesn't seem to be so.
            So I tried Listmonk admin but no joy with that either.

            timconsidine 1 Reply Last reply Reply Quote 0
            • Topic has been marked as a question  timconsidine timconsidine 
            • timconsidine
              timconsidine App Dev @timconsidine last edited by

              @timconsidine Interesting : in app logs say :
              2022/05/31 13:50:25reading config: /run/listmonk/config.toml

              But /run/listmonk/config.toml is zero-length file.

              Is that ok ?

              girish 1 Reply Last reply Reply Quote 0
              • girish
                girish Staff @timconsidine last edited by girish

                @timconsidine The zero length file is fine, it doesn't start without it.

                The SMTP default settings are also correct. Port 2465 is the internal SMTPS port (https://docs.cloudron.io/packaging/addons/#sendmail). Go apps don't work without TLS even if it's all totally internal (which is why we have this semi-deprecated SMTPS port in the first place).

                Just to double check, can you restart the app? Restarting the app will re-inject the up to date SMTP credentials. I did try to send a mail campaign before I published and it did work.

                timconsidine 1 Reply Last reply Reply Quote 1
                • timconsidine
                  timconsidine App Dev @girish last edited by timconsidine

                  @girish YAY !!

                  I did restart the app a few times, but maybe changed the mail password before trying another send.

                  The fact that restarting the app re-inject the credentials may also explain why an alternative config got deleted.
                  Bit strange because other settings persist.

                  Restarting then produced another message in the campaign.
                  UI allows you to customise the FROM address .... but if it is not the app mail address, there is a different failed authentication error.
                  So it seems that (for now at least) a campaign must have the FROM address as the app mail address. At least the same actual address, but the "friendly name" can be changed. Which is good.
                  But it should not suggest that the mail address can be changed.
                  I appreciate that is an upstream issue, not Cloudron.
                  Maybe just need to document this.

                  Anyway, SOLVED ! Thank you @girish. 🍾
                  Now I can explore further.

                  girish 1 Reply Last reply Reply Quote 0
                  • Topic has been marked as solved  timconsidine timconsidine 
                  • girish
                    girish Staff @timconsidine last edited by

                    @timconsidine said in SMTP default settings:

                    So it seems that (for now at least) a campaign must have the FROM address as the app mail address. At least the same actual address, but the "friendly name" can be changed. Which is good.

                    Good points. So, if you let Cloudron manage the email address, then you have to change it from Cloudron Dashboard -> App -> Email -> From address setting. This will fixup the config accordingly. You can also change the setting there to have Cloudron not manage the email at all (if you want to relay using some other provider from inside listmonk).

                    The name is not configurable but it should be, will fix the package (or the box code).

                    1 Reply Last reply Reply Quote 2
                    • First post
                      Last post
                    Powered by NodeBB