GLPI email ticketing configuration [message #102473] |
Wed, 08 May 2013 18:28  |
trent
Messages: 3 Registered: May 2013 Location: Houston, TX
|
|
|
|
I am attempting to configure the ticket by email feature of GLPI and after trying near every configuration combination I am still unable to connect to the mail server via the receiver setup page. I know that a outlook connect software is required for that client, so I assume there is something I need to do other than configure the client in a certain way. Any help would be greatly appreciated.
|
|
|
Re: GLPI email ticketing configuration [message #121990 is a reply to message #102473] |
Fri, 12 June 2015 19:02   |
Kale
Messages: 1 Registered: June 2015 Location: Senegal
|
|
|
|
Hello,
Its an old topic (2013) but maybe someone find the solution ? I have the same problem. I search the option of connection:
POP or IMAP
SSL or nothing
TLS - NO TLS - Nothing
No Validate CERT - Validate CERT - Nothing
NORSH - Nothing
SECURE - Nothing
DEBUG - Nothing
Thanks for your help.
|
|
|
|
|
|
|
Re: GLPI email ticketing configuration [message #134467 is a reply to message #102473] |
Tue, 28 February 2017 08:45  |
gobs
Messages: 2 Registered: February 2017
|
|
|
|
Hi,
thanks for sharing this problem. Yes I could authenticate through UNsecured IMAP, but not IMAPs.
I understand GLPI uses the imap_open PHP (7 here) function.
Here are the test for IMAPs :
imap_open(): Couldn't open stream {mail.subdomain.domain.net:993/imap}INBOX
Backtrace :
:
inc/auth.class.php:195 imap_open()
inc/authmail.class.php:263 Auth->connection_imap()
front/authmail.form.php:69 AuthMail::testAuth()
and :
PHP Notice(8): Unknown: [CLOSED] IMAP connection broken (server response) (errflg=2)
Backtrace :
:
I also tested with all of theses :
{mail.subdomain.domain.net:993/imap/ssl/tls}INBOX
{mail.subdomain.domain.net:993/imap/ssl/validate-cert/tls}IN BOX
{mail.subdomain.domain.net:993/imap/ssl/validate-cert/tls/no rsh/secure}INBOX
{mail.subdomain.domain.net:993/imap/ssl/novalidate-cert/tls/ norsh/secure}INBOX
and got for all:
*** PHP Notice(8): Unknown: Can't open mailbox {mail.subdomain.domain.net:993/imap/all possible seetings}INBOX: invalid remote specification (errflg=2)
Next step could be to forge a test php file with all of :
$mbox = imap_open ("{servername:995/imap/all possible seetings}", "user_id", "password");
as mentioned here in imap-open php documentation.
Of course Kerio works fine with IMAPs for all kind of mail clients since ever; and our certificate is valid (sha-2 DigiCert).
LDAPs seems also tedious, but that another story.
|
|
|