-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pop3 issue 9.5.1 #7757
Comments
Hi, Do you use a self-signed certificate ? Regards |
I use a certificate created by Let’s encrypt (https://letsencrypt.org/fr/certificates/)
De : Cédric Anne <notifications@github.com>
Envoyé : jeudi 23 juillet 2020 10:09
À : glpi-project/glpi <glpi@noreply.github.com>
Cc : Maxime PREAULT <maxime.preault@omdm.fr>; Author <author@noreply.github.com>
Objet : Re: [glpi-project/glpi] Pop3 issue 9.5.1 (#7757)
Hi,
Do you use a self-signed certificate ?
Regards
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#7757 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQMAJFVBICZ53DIKV6GLOETR47VZ7ANCNFSM4PFO4AAA>.
|
In GLPI 9.5, we removed dependency to PHP imap-ext which is unmaintained from a while and we replaced it by usage of We recently figure out that the I do not know if your problem comes from this point or not. Maybe you should try to debug on your side to see if anything can lead to a certificate refusal from your GLPI server. |
Hi! Please try change server field value to an external name of mailserver. It helped me. |
Hi!
The issue can be closed. I modified the spectrum of the certificate to include my pop server. It was exclude before.
Thank you for the help !
De : aagz <notifications@github.com>
Envoyé : vendredi 31 juillet 2020 09:44
À : glpi-project/glpi <glpi@noreply.github.com>
Cc : Maxime PREAULT <maxime.preault@omdm.fr>; Author <author@noreply.github.com>
Objet : Re: [glpi-project/glpi] Pop3 issue 9.5.1 (#7757)
I use a certificate created by Let’s encrypt (https://letsencrypt.org/fr/certificates/) De : Cédric Anne notifications@github.com<mailto:notifications@github.com> Envoyé : jeudi 23 juillet 2020 10:09 À : glpi-project/glpi glpi@noreply.github.com<mailto:glpi@noreply.github.com> Cc : Maxime PREAULT maxime.preault@omdm.fr<mailto:maxime.preault@omdm.fr>; Author author@noreply.github.com<mailto:author@noreply.github.com> Objet : Re: [glpi-project/glpi] Pop3 issue 9.5.1 (#7757<#7757>) Hi, Do you use a self-signed certificate ? Regards — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#7757 (comment)<#7757 (comment)>>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQMAJFVBICZ53DIKV6GLOETR47VZ7ANCNFSM4PFO4AAA.
Hi! Please try change server field value to an external name of mailserver. It helped me.
Before update glpi knew local mailserver name, after 9.5.0 mailcollector works with external name only, for me.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#7757 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQMAJFUPK22WEJXR5GU3ED3R6JY3TANCNFSM4PFO4AAA>.
|
Hello, what is the work around? What did you do? |
Hi, Log from mail server : We rolled back to GLPI 9.4.3 which works fine with the exact same setup and configuration. Is there a known workaround to this problem ? |
You should take a look on your certificate. Even if backend code changed on GLPI 9.5 for POP/IMAP connections, it should not affect certificate validity. Regards |
Thanks for the answer. |
Hundreds of lines of code have been changed in different files, so no, it is not really possible. |
Of course I understand. We'll keep 9.4 for now since we'll stop using the mail server for GLPI auth in a few months. |
Describe the bug
Since the update to GLPI 9.5 and 9.5.1, my pop3 mail collector is crashing. I can't connect to my mail server. THe configuration below was ok with glpi 9.4
Collector config
{srv-mail.xx.xxxx.local:537/pop/ssl/validate-cert/notls}
I tried with the options validate-cert and no-validate-cert but the behavior is still the same
Logs
Here are some lines of my php-errors.log
[2020-07-23 09:50:01] glpiphplog.ERROR: MailCollector::collect() in /var/www/html/glpi/inc/mailcollector.class.php line 691
An error occured trying to connect to collector. cannot connect to host ; error = fsockopen(): unable to connect to ssl://srv-mail.cc.omdm.local:537 (Connection refused) (errno = 0 )
#0 /var/www/html/glpi/vendor/laminas/laminas-mail/src/Storage/Pop3.php(149): Laminas\Mail\Protocol\Pop3->connect('ssl://srv-mail....', '537', 'ssl')
#1 /var/www/html/glpi/inc/toolbox.class.php(2324): Laminas\Mail\Storage\Pop3->__construct(Object(stdClass))
#2 /var/www/html/glpi/inc/mailcollector.class.php(1309): Toolbox::getMailServerStorageInstance('pop', Array)
#3 /var/www/html/glpi/inc/mailcollector.class.php(685): MailCollector->connect()
#4 /var/www/html/glpi/inc/mailcollector.class.php(1740): MailCollector->collect(8)
#5 /var/www/html/glpi/inc/crontask.class.php(847): MailCollector::cronMailgate(Object(CronTask))
#6 /var/www/html/glpi/front/cron.php(83): CronTask::launch(2, '5')
#7 {main} {"user":"@srv-glpi"}
Screenshots
Your GLPI setup (you can find it in Setup > General menu, System tab)
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: