Signals an error sometimes when trying to connect to imap server

Bug #5766 reported by Nicolas da Luz Duque
4
Affects Status Importance Assigned to Milestone
Mail Notification
Fix Released
Undecided
Jean-Yves Lefort

Bug Description

It is configured to connect to only 2 folders of my imap server. My imap server is a courier-imap.

I am notified of the new mails, but frequenlty it comes flashing on my screen telling me it can't read from the server. The exact message is "Impossible to read from the server: EOF" (I'm translating this from french, and I don't know the english message).

I fail to see why an end-of-file message should cause him to make him think it's an error. I think it simply means there isn't any new message.

(I have de-activated the blinking, but I find this situation frustrating as I am no longer notified of true errors.)

Revision history for this message
Jean-Yves Lefort (jylefort) wrote :

An abrupt EOF is an error since the IMAP protocol specifies that the server should send a LOGOUT response before disconnecting. That is, an EOF generally indicates that the connection was abruptly terminated and the IMAP session did not succeed.

Could you please check if this problem still occurs in the latest version of MN? If it does, please attach the output of:

  mail-notification -i

Changed in mail-notification:
assignee: nobody → jylefort
Revision history for this message
Nicolas da Luz Duque (hot-boy) wrote :

Well, since m-n supports evolution notifying, I've resorted to use only that. This way I don't have to compile the ubuntu package myself to have SSL enabled, and only one app checks my mail.

It's been so long, however, and no-one seems to have encountered the same problem since, so I think you can probably consider it fixed. Someone will probably re-open it if it occurs again.

If you're a perfectionnist (which I'd understand), I guess I could spend some time re-building a package with SSL to test it, but if you're happy like that, so am I. ;-)

Revision history for this message
Jean-Yves Lefort (jylefort) wrote :

Thanks for the update. I believe this problem was fixed in 3.0.

Changed in mail-notification:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.