Mail indicator reporting connection errors

axilon

Hi,

I can't find anything about this issue on the forums and I'm certainly not qualified to go into the actual code to figure things out myself, so here it goes.

Someone please have a look at this screenshot I took:

Mail indicator seems to malfunction due to a connection error, while roundcube is working smoothly for both email addresses. I can send and receive mail messages from within Epesi without any trouble.
Doesn't the mail indicator copy settings from the preset email account(s) for this user ? Atleast I can't find anything that allows me to verify or edit the settings for the mail indicator.

Any help would be appreciated.

Thank you.

ethnar

Hello,

The applet uses different tools and calls than the Roundcube to access the mailboxes. It's possible something in server configuration might be blocking these calls.

I'm attaching a slightly improved applet-refresh script - it won't resolve the problem, but it should show the exact error message generated (in tooltip, when hovering over "Connection error"). If you can post that message here we can most likely move forward in resolving this issue.
To apply the fix download the file, unzip it and place it in modules/CRM/Roundcube, overwriting the old file.

Kind regards,
Arek

axilon

OK, will work on your suggestion later today.

In the meanwhile: I was wondering if I've forwarded the correct ports in my router ? Port 110 is open, but maybe the mail indicator is using some other port ?

ethnar

The applet is using port 993 for SSL connections and 143 for non-SSL connections.

axilon

Hi Arek,

I've checked the port settings on my router and it seemed that port 143 was already forwarded to the mailserver. Forwarding port 993 had no effect. I guess this is not the problem.

Even though I did exactly as you told me, I did not get a tooltip when hovering over de 'connection error' text. After some trial and error, I managed to pull this text out of $err: "Can't open mailbox {my.domain/imap/readonly/novalidate-cert:143}: invalid remote specification".
So I guess you were right, my servers configuration seems to be the problem.
I'm running a mailserver on my synology NAS, and from what I understand there is no imap-directory where Epesi expects it to be.
I know that synology software stores it's messages in the user directory, e.g. my.domain/homes/%username%/.Maildir

It's not critical for my company that we get the mail indicator to work (I'm very happy with Epesi software as it is), but it would be nice if we could.

Any idea where to go from here ?

ethnar

Hello,

I'm glad you got the error displayed. I tried my code on my local installation and it was working alright, I forgot to mention EPESI needs full refresh after the change, might have been the cause.

Anyway, on to the matter. The path where the messages are stored should be irrelevant and most likely it is. The problem is somewhere on the line of making connection. The piece of string:

{my.domain/imap/readonly/novalidate-cert:143}

Should be read as:

{[address][options]:[port]}

Where options are each started with a slash: /imap, /readonly, etc.

The most likely cause I'd expect now is the port. You can find the line in applet_refresh.php:

$port = $rec['security']=='ssl'?993:143;

Change the 143 to the port number you are supposed to use (you mentioned port 110?).
Another thing you can try is to change the line with imap_open to something like this:



$mailbox = imap_open('{'.$rec['server'].'/imap/debug/readonly/novalidate-cert'.($rec['security']?'/'.$rec['security']:'').':'.$port.'}',$rec['login'],$rec['password'],OP_READONLY || OP_SILENT);

Please note that I removed the @ char and that /debug option was added. After this change, fully refresh EPESI and check what error message you're getting, everything should be displayed in the applet. If all you get is "Failure 500" popup, you will need to enable error_reporting in php.ini (from Off to On).

Please let us know if you find anything.

Kind regards,
Arek

axilon

This is what I've done:

1) I've verified that IMAP and IMAPS are enabled on the NAS and that they're using the default ports 143 and 993 (I mentioned port 110 because I assumed that the mail indicator applet was something like a simple pop3-checker, which use port 110, right ?)
2) I've forwarded port 993 to the Synology NAS, port 143 was already forwarded correctly.
Unfortunately these action didn't resolve the issue.

Then I edited the applet_refresh.php file like you suggested and this error message appears in the applet:

[quote:1ww8a1nz] m.grootehaar - Type: 2
Message: imap_open(): Couldn't open stream {<my.domain/imap/debug/readonly/novalidate-cert:143}
File: /volume1/web/epesicrm/modules/CRM/Roundcube/applet_refresh.php
Line=18
error backtrace:
[PHP core called function]
function called: handle_epesi_error(2, "imap_open(): Couldn't open stream {my.domain/imap/debug/readonly/novalidate-cert:143}", "/volume1/web/epesicrm/modules/CRM/Roundcube/applet_refresh.php", 18, Array (#81))

File: /volume1/web/epesicrm/modules/CRM/Roundcube/applet_refresh.php
line 18
function called: imap_open("{my.domain/imap/debug/readonly/novalidate-cert:143}", "correct username", "correct password", 1)

Notice: Unknown: Can't open mailbox {my.domain/imap/debug/readonly/novalidate-cert:143}: invalid remote specification (errflg=2) in Unknown on line 0

info - Type: 2
Message: imap_open(): Couldn't open stream {my.domain/imap/debug/readonly/novalidate-cert:143}
File: /volume1/web/epesicrm/modules/CRM/Roundcube/applet_refresh.php
Line=18
error backtrace:
[PHP core called function]
function called: handle_epesi_error(2, "imap_open(): Couldn't open stream {my.domain/imap/debug/readonly/novalidate-cert:143}", "/volume1/web/epesicrm/modules/CRM/Roundcube/applet_refresh.php", 18, Array (#81))

Notice: Unknown: Can't open mailbox {my.domain/imap/debug/readonly/novalidate-cert:143}: invalid remote specification (errflg=2) in Unknown on line 0 [/quote:1ww8a1nz]

I did some googling on the imap_open syntax and I edited the $mailbox line in applet_refresh.php to this:

$mailbox = imap_open("{localhost/debug/novalidate-cert:143}", "username", "password");

But it still return the same error message.
Epesi is running on the same synology NAS as the mailserver, so 'localhost' should work, right ? And since it doesn't work, doesn't that rule out any issues with port forwarding ?

FYI: on my home computer I can connect outlook to the synology NAS just fine, using the IMAP protocol on port 143.

I don't know what else to try. Do you ?

ethnar

I've been looking for more information on this matter and it seems the one thing that can move us forward is enabling the mail log. To do that, edit your php.ini, find variable mail.log and have it set to some file - most likely all you'll have to do is to uncomment it. Make sure to restart apache afterward. Then - when you trigger the error, we should get some useful error message in that log.

Also found this thread with quite unique problem and solution, perhaps it may help:
http://forum.parallels.com/showthread.php?t=94881

If you did change the line to

$mailbox = imap_open("{localhost/debug/novalidate-cert:143}", "username", "password");

then the connection will be refused for sure, unless you have a mailbox with address username and password password. You should change that to: (also changed the order in the first argument, seems to be more widely used)

$mailbox = imap_open("{localhost:143/debug/novalidate-cert}", $rec['login'],$rec['password']);

With that code you should get meaningful message in mail log.

Kind regards,
Arek

axilon

FYI: I had learned to live with this connection error.
I recently ran some updates on my Synology NAS and somehow it has fixed my problem.
The mail indicator now indicates the number of unread message, instead of reporting the error message.
Thanks for all the help, I'm glad it got little to do with Epesi after all.

Epesi ENS | Epesi Academy | epesi.cloud PaaS | GitHub

Help Me! | Download from SourceForge