Forum GLPI-Project

strojniak

Member

Registered: 2010-03-10

Posts: 19

Zimbra receiver IMAP configuration problem

I cant configure Zimbra IMAP account as receiver in GLPI (v10.0.3)

First of all I tried to connect Zimbra mail server via linux console / openssl:

openssl s_client -crlf -connect *************:993

CONNECTED(00000003)

[some certs verifications]

verify return:1
---
Certificate chain

[more certs infos]

   v:NotBefore: Sep 11 12:00:00 2014 GMT; NotAfter: Jun  9 10:46:39 2027 GMT
---
Server certificate
-----BEGIN CERTIFICATE-----
[...]
-----END CERTIFICATE-----
subject=[...]---
No client certificate CA names sent
Peer signing digest: SHA256
Peer signature type: RSA-PSS
Server Temp Key: ECDH, prime256v1, 256 bits
---
]SSL handshake has read 4870 bytes and written 451 bytes
Verification: OK
---
New, TLSv1.2, Cipher is ECDHE-RSA-AES128-GCM-SHA256
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : ECDHE-RSA-AES128-GCM-SHA256
    Session-ID: 32A516DC055C69C98013F5D8B0C4FF370FC26F2F70926854515F28A8380F27B5
    Session-ID-ctx:
    Master-Key: [........]
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    TLS session ticket lifetime hint: 300 (seconds)
    TLS session ticket:
    
    [...]

    Start Time: 1667756860
    Timeout   : 7200 (sec)
    Verify return code: 0 (ok)
    Extended master secret: yes
---
* OK IMAP4rev1 proxy server ready
tag login [user] [pass]
tag OK [CAPABILITY IMAP4rev1 ACL BINARY CATENATE CHILDREN CONDSTORE ENABLE ESEARCH ESORT I18NLEVEL=1 ID IDLE LIST-EXTENDED LIST-STATUS LITERAL+ LOGIN-REFERRALS MULTIAPPEND NAMESPACE QRESYNC QUOTA RIGHTS=ektx SASL-IR SEARCHRES SORT THREAD=ORDEREDSUBJECT UIDPLUS UNSELECT WITHIN XLIST] LOGIN completed
tag LIST "" "*"
* LIST (\HasNoChildren \Drafts) "/" "Drafts"
* LIST (\HasNoChildren) "/" "INBOX"
* LIST (\NoInferiors \Junk) "/" "Junk"
* LIST (\HasNoChildren \Sent) "/" "Sent"
* LIST (\HasNoChildren \Trash) "/" "Trash"
tag OK LIST completed
tag logout
* BYE ********* Zimbra IMAP4rev1 server closing connection
tag OK LOGOUT completed
closed

As you see I successfully connected to zimbra mail server. Protocol IMAP / SSL / TLS I think.

So I set connection (Setup - Receivers - Add) as {[ip add]:993/imap/ssl/novalidate-cert/tls}INBOX. No success.
Then I tried many variations - more no success .

Finally I set up unencrypted pure IMAP on port 143. Still no luck.

When I try to read incoming mail folders I see in php-errors.log:

[2022-11-07 19:30:58] glpiphplog.CRITICAL:   *** Uncaught Exception Laminas\Mail\Protocol\Exception\RuntimeException: cannot read - connection closed? in /var/www/html/glpi/vendor/laminas/laminas-mail
/src/Protocol/Imap.php at line 110
  Backtrace :
  .../laminas/laminas-mail/src/Protocol/Imap.php:125 Laminas\Mail\Protocol\Imap->nextLine()
  ...r/laminas/laminas-mail/src/Protocol/Imap.php:87 Laminas\Mail\Protocol\Imap->assumedNextLine()
  ...r/laminas/laminas-mail/src/Storage/Imap.php:223 Laminas\Mail\Protocol\Imap->connect()
  src/Toolbox.php:2155                               Laminas\Mail\Storage\Imap->__construct()
  src/MailCollector.php:1375                         Toolbox::getMailServerStorageInstance()
  src/MailCollector.php:393                          MailCollector->connect()
  ajax/mailcollector.php:83                          MailCollector->displayFoldersList()

which suggests timeout on connection trial.

Firewall disabled. SELinux too.
Php-imap extenstion installed.

Heeelp, any suggestions ??

strojniak

Member

Registered: 2010-03-10

Posts: 19

Re: Zimbra receiver IMAP configuration problem

Anyone ? Any idea ?

comunelevico

Member

Registered: 2023-02-12

Posts: 1

Re: Zimbra receiver IMAP configuration problem

I have no resolution, but I have the same problem !

SKDJ

Member

Registered: 2023-08-04

Posts: 4

Re: Zimbra receiver IMAP configuration problem

That is a long time ago. I wonder why these questions stay unanswered. I have the same problem using nginx php-fpm in docker. I have been pulling my hairs out which is very hard for me to do (too). I can see many people struggle with finding the logs and then understanding how the data in the forms, is used in laminas to actually send the email.

I will put the answer of what happens here as soon as I have an idea. It's very strange since at least sending this email has worked for me before. I can't trace-back what has changed except restarting the docker-compose. I may be wrong there and some other thing has also changed but too many things have been tried since it stopped working and now.

Fact is that no matter what I do the SMTP trigger does not even try to contact the server. Same happens to IMAP. The very same. I got it to work and then it stopped.

In both situations I was debugging the default cron-jobs that did not seem to trigger the -at that time- manual triggered actions that did work. Selecting a notification and sending, Importing IMAP mail manually or sending test-emails. Very frustrating since none of my effort is of any use for a servicedesk without email. Makes me wonder if this is the business-model. It does not adhere to my understanding of the open-source model.

I do want to contribute from my skills, but now I am learning PHP  Mailer/ Laminas PHP code as an infrastructure specialist.

I will not give up but I am less and less impressed.