Open nsteinmetz opened 8 years ago
ok sorry. i didnt even know there is a activation email sent. mh. like you said... maybe its just the best to inform about this in the readme.
i just merged a pull request to allow email server configuration. maybe you want to check it out.
So, this still seems to be an issue for me. I attempted to configure wallabag to use mailgun, like v1 used to do. @xsteadfastx saw your PR in #10 . Does the installation default to using smtp as the mail transport?
It's by default smtp (and it doesn't seems to be configurable in this docker version). For using mailgun, you just need to update the host, user & password I think.
im working right now on it... the problem is still the bug that prevents paremeters.yml to use environment variables. if the container starts up the first time the email settings can be set through environment variables.
like this it would send a link on creating new users... but with the first wallabag user im unsure.
i created a PR.
the PR is merged. its not possible again to set email server. but... the activation link... i think that doesnt solve that problem for a fresh installation of wallabag on a first run.
Hello,
I have the same issue here. I have installed the Docker package of Wallbag (2.3.2) on my QNAP (via Container Station) but I cannot receive the email.
Should I configure the email server manually? If so, where to look at?
@giopas Probably years too late but there is now an environment variable you can use to disable the link, or you can set the flag manually in the database to enable your first new user.
At the end of the account creation process, activation link is not sent by email. Even if it's not a blocking issue as you can authenticate with your login/password, it may be seen as "deceptive".
Maybe the workaround is just to inform people about this in the readme - as adding some smtp is not really expected (even some as basic as
ssmtp
)