Dominik Sander

Can you try opening a connection to the gmail smtp server from your server? You should see output similar to this one: ``` $ telnet smtp.gmail.com 587 Trying 64.233.167.108... Connected...

It does, but it does not explain why the connection is not working from your Huginn container. Other outbound connection like HTTP request work from Huginn?

I can't tell you why this is happening on your machine. I started the docker container like this: ``` docker run -it -p 3000:3000 -e SMTP_DOMAIN=domain.com \ -e [email protected] \...

> `` Exception during check. 535-5.7.8 Username and Password not accepted. Learn more at : /usr/lib/ruby/2.5.0/net/smtp.rb:981:in `check_auth_response' /usr/lib/ruby/2.5.0/net/smtp.rb:736:in `auth_plain... | note: lost password huginn functionality works correctly. You are getting...

@StefanHos Please ensure that you are using the same environment configuration for the application server and the background processes. The only way I can imagine this happening is if the...

@mmalind That error reads to me like the configuration is just not correct. Huginn wasn't able to authenticate with your SMTP server using the configuration you provided.

Yes that is annoying, it has bitten me too. I think we could remove the `.env` in the docker container, however the problem I see is to maintain backwards compatibility....

Please double check both the callback url in the twitter application settings and your twitter log in and password. I think I remember that entering a wrong password will not...

The authentication is done via `omniauth_twitter`, its not directly related to their API. @Taffer Maybe this might help? https://github.com/arunagw/omniauth-twitter/issues/131#issuecomment-400170862 I just checked it on my Huginn instance and I had...

@TradeCrafter did you check [this comment](https://github.com/arunagw/omniauth-twitter/issues/131#issuecomment-400170862)? I made this change and can still login using twitter.