Freron MailMate

Comments and changes to this ticket

• 

  benny March 15th, 2013 @ 07:40 AM

  I'm guessing this is triggered by a bad IMAP implementation. MailMate can, at times, be a bit strict about which erroneous replies it accepts from the server. The above error can be harmless, but it could also indicate that MailMate or the server is in a state where bad things could happen -- such as deleting the wrong message. Therefore MailMate chooses to bail out.

  You can hold down ⇧ when clicking “Retry” and MailMate should create a log file on the desktop which you can send to me. Then I can confirm whether or not the server is to blame and determine if anything can be done about it.

• You flagged this item as spam.
  

  Chris Bradfield March 15th, 2013 @ 02:10 PM

  Hello,
  Find the file attached

  • MailMate_imapsecureservernet_INBOX.txt 1.4 KB
• 

  benny March 17th, 2013 @ 07:40 PM

  The log confirms that the server is to blame and it is not a subtle error:

  C: C3 SELECT INBOX  
  S: * FLAGS (\Draft \Answered \Flagged \Deleted \Seen \Recent)  
  S: * OK [PERMANENTFLAGS (\Draft \Answered \Flagged \Deleted \Seen)] Limited  
  S: * 1892 EXISTS  
  S: * 0 RECENT  
  S: * OK [UIDVALIDITY 1] Ok  
  S: * OK [UIDNEXT 23946] Predicted next UID  
  S: C3 OK [READ-WRITE] SELECT completed.  
  C: C4 NOOP  
  S: * 788 EXISTS  
  Error: An EXISTS response decreased the number of messages. This should never happen.
  

  MailMate selects the mailbox and is told that it contains 1892 messages. MailMate then sends a NOOP (no-operation) which is actually a workaround for other buggy servers. At this point the servers says that only 788 messages exist. The IMAP RFC says (section 4.2):

  Special rules exist for server notification of a client about the
  removal of messages to prevent synchronization errors; see the
  description of the EXPUNGE response for more detail.  In particular,
  it is NOT permitted to send an EXISTS response that would reduce the
  number of messages in the mailbox; only the EXPUNGE response can do
  this.
  

  I think you should try contacting your IMAP provider. The above is an obvious server error. The IMAP server type is Courier which is pretty good, but I guess it's not up-to-date at GoDaddy.

  Alternatively I can implement some kind of hidden setting for ignoring illegal EXISTS responses, but we don't really know why the server reports the wrong number of messages and it could lead to other problems.

• 

  benny October 10th, 2013 @ 09:45 AM

  • State changed from “new” to “closed”