Hello everybody !
I have a strange problem - I can not fetch mails from my gmail account anymore !
History: Some days ago I decided to migrate to a new server. Thus I wanted to upgrade from 3.0.11 to 5.0.12
I upgraded on the old server up to 4 then I took everything over to the new server (ubuntu 16.04) and there I finished to upgrade to 5.0.12
Everything works fine (including the mail sending), but I may not fetch mails form the gmail account anymore.
- it did work before the upgrade / migration
- I did activte "less secure appplications" on gmail
- I did install fetchmail
- fetchmail has the ssl extension
- openssl s_client -connect pop.gmail.com:995
gives the right result (+OK Gpop ready for requests from ...)
But I always get this error log in otrs:
Wed Sep 7 07:40:04 2016 error OTRS-otrs.Console.pl-Maint::PostMaster::MailAccountFetch-10 There was an error executing Execute() in Kernel::System::Console::Command::Maint::PostMaster::MailAccountFetch: [Wed Sep 7 07:40:03 2016] otrs.Daemon.pl: using SSL support of Net::POP3 3.05 instead of SSLGlue at /opt/otrs/Kernel/cpan-lib/Net/SSLGlue/POP3.pm line 12.
Wed Sep 7 07:40:04 2016 error OTRS-otrs.Console.pl-Maint::PostMaster::MailAccountFetch-10 POP3S: Auth for user mygmailaccount@gmail.com/pop.gmail.com failed!
Due to the history I am quite sure that something is wrong on my side and not some blocking on gmail side.
But what do you think ? Any ideas ?
As this is a production server I would be very thankfull for any help ...
Best regards,
Fabianus
Solved - Auth for user mygmailaccount@gmail.com/pop.gmail.com failed!
Moderator: crythias
Solved - Auth for user mygmailaccount@gmail.com/pop.gmail.com failed!
Last edited by fabianus on 07 Sep 2016, 21:27, edited 1 time in total.
Re: Auth for user mygmailaccount@gmail.com/pop.gmail.com failed!
Finally I created a new gmail account and everything works fine.
It is realy strange because I am sure about the password for the old account.
Anyway - useless to continue searching for the answer - issue is solved.
It is realy strange because I am sure about the password for the old account.
Anyway - useless to continue searching for the answer - issue is solved.