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 Wekan, "failed to send email"

    Wekan
    wekan
    4
    6
    299
    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.
    • yusf
      yusf last edited by girish

      Translated from my locale, an error that roughly reads

      failed to send email
      

      is displayed whenever a user is added to a board. So there seems to be some issue with email routing? Or that the LDAP connection doesn't provide email to Wekan?

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

        This is an old topic but indeed email is not configured in wekan properly. @nebulon is working on an update to fix the problem.

        1 Reply Last reply Reply Quote 3
        • nebulon
          nebulon Staff last edited by

          This is now fixed with package v4

          1 Reply Last reply Reply Quote 3
          • E
            eddowding last edited by

            Wekan isn't sending email for me.

            nebulon 1 Reply Last reply Reply Quote 0
            • nebulon
              nebulon Staff @eddowding last edited by

              @eddowding if you head over to the wekan admin panel and send a test email, does that go through? Also once done, check the mail server event logs via the Cloudron dashboard if the mail was processed.

              Further you could install a fresh wekan instance and just send the test email there. At least on my test instance this worked fine just now for both a quite old instance as well as a freshly installed one.

              E 1 Reply Last reply Reply Quote 1
              • E
                eddowding @nebulon last edited by

                @nebulon sorted & found it in spam -- I guess because it was set to a subdomain

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