Hello teams, 

I'm using a Xeams mail server, recently, I have setup a NextCloud instance on the same server. I wanted to configure a mail account on NextCloud but somewhat, NextCloud can't manage to retrieve the mails from Xeams.

I also opened a ticket on NextCloud side. But I'm not so confident that the problem are on their side, considering that same problem has been found an echo on the internet with another user using Xeams. (and the mail client was not NextCloud)

Here my Xeams logs (same on NC side)

2020-07-31 10:58:14,546 - - [ 13167] ************** New Connection from: 127.0.0.1 **************
2020-07-31 10:58:14,546 - - [ 13167] S <-- * OK Synametrics IMAP4rev1 server ready 7/31/20 10:58 AM
2020-07-31 10:58:14,596 - - [ 13167] C --> 1 CAPABILITY
2020-07-31 10:58:14,596 - - [ 13167] S <-- * CAPABILITY IMAP4rev1 IDLE
2020-07-31 10:58:14,596 - - [ 13167] S <-- 1 OK CAPABILITY completed
2020-07-31 10:58:14,597 - - [ 13167] C --> 2 LOGIN xxxxxxxxx@xxxxx.com xxxxxx
2020-07-31 10:58:14,597 - - [ 13167] S <-- 2 OK LOGIN completed
2020-07-31 10:58:14,597 - - [ 13167] C --> 3 CAPABILITY
2020-07-31 10:58:14,597 - - [ 13167] S <-- * CAPABILITY IMAP4rev1 IDLE
2020-07-31 10:58:14,597 - - [ 13167] S <-- 3 OK CAPABILITY completed
2020-07-31 10:58:14,598 - - [ 13167] C --> 4 EXAMINE INBOX
2020-07-31 10:58:14,599 - - [ 13167] S <-- * FLAGS (\Seen \Deleted)
2020-07-31 10:58:14,599 - - [ 13167] S <-- * 83 EXISTS
2020-07-31 10:58:14,599 - - [ 13167] S <-- * OK [UIDNEXT 85] Predicted next UID
2020-07-31 10:58:14,599 - - [ 13167] S <-- * 0 RECENT
2020-07-31 10:58:14,599 - - [ 13167] S <-- * OK [PERMANENTFLAGS (\Deleted \Seen)]
2020-07-31 10:58:14,599 - - [ 13167] S <-- 4 OK [READ-ONLY] SELECT completed
2020-07-31 10:58:14,600 - - [ 13167] C --> 5 UID SEARCH ALL
2020-07-31 10:58:14,600 - - [ 13167] S <-- 5 BAD Selection of mail box is required before this command
2020-07-31 10:58:14,604 - - [ 13167] C --> 6 LOGOUT
2020-07-31 10:58:14,604 - - [ 13167] S <-- * BYE IMAP4rev1 IDLE Server logging out
2020-07-31 10:58:14,604 - - [ 13167] S <-- 6 OK LOGOUT completed
2020-07-31 10:58:14,604 - - [ 13167] ~~~~~~~~~~~~~~ Connection closed: 127.0.0.1 (58 ms)~~~~~~~~~~~~~~

( https://github.com/nextcloud/mail/issues/3407 )

So here my question, is there kind of logic to the need of specify a "mail box" when we are performing an "UID SEARCH ALL" command. 

If the problem is on Xeams side, can we fix this?

If the problem is on NextCloud side, what kind of command should they send to the Xeams server before performing the "UID SEARCH ALL" command in this case?

 

For information: the mailbox on Xeams Side is a default one with no special folder created. It's a default mail box.

 

We have been able to recreate this problem on our end. It's a bug in Xeams. The problem is not with SEARCH but with EXAMINE. Most IMAP clients use the SELECT command, instead of EXAMINE. Please contact us via email (support@synametrics.com) and we will send you an updated patch within a few days that will take care of this problem.

I have installed newest backend version of XEAMS and cannot have stable connection of IMAP server to Nextcloud mail. Here are the errors and warnings in nextcloud mail client:

Gery,

A message that says "Undefined array key" appears to be a syntax error in one of the PHP files rather than a communication problem with IMAP server, and, therefore, is not related to Xeams

To see the communication log for IMAP, check IMAPConversation.log in Xeams.