Freron MailMate

Comments and changes to this ticket

• 

  benny February 28th, 2015 @ 03:35 PM

  Thanks for the detailed report. The message itself does not appear to be a problem. I can import and view it.

  To learn more I need server connection logs, but before we do that I need to know which revision of MailMate you are using. I recommend trying the latest beta available via the Software Update preferences pane.

• You flagged this item as spam.
  

  Peter Mienes March 1st, 2015 @ 07:54 AM

  I've now updated the software to 1.9 build 5066, and the symptoms remain unchanged. Where do I find the connection log? Or is it the contents of the Activity viewer that you're interested in?

• 

  benny March 1st, 2015 @ 08:38 AM

  Thanks for trying. You can generate log files like this:

  • Open the Activity Viewer (this enables logging).
  • Trigger the problem -- if necessary, relaunch MailMate.
  • Use “Help ▸ Send Server Logs” to send me the logs of the activity.

  I should then be able to see why it goes to “unavailable”.

  (All kinds of errors make MailMate go to the temporary “unavailable” state. This is done because many servers have various (buggy) temporary problems and many users were annoyed when MailMate told them about it every time.)

• 

  benny March 1st, 2015 @ 09:27 AM

  Thanks for the logs.

  This is the problem:

  08:42:26 C: E8 UID FETCH 1 (UID BODY.PEEK[HEADER] RFC822.SIZE)  
  08:42:26 Error: TCP socket was unexpectedly closed.  
  08:42:26 S:
  

  Every time MailMate asks for the headers of this message then the server cuts the connection. Clearly a server problem, but the server does not even return an error which means that for MailMate it looks like an unstable connection and not a specific problem with a specific message (in that case MailMate might have asked if you wanted to ignore it).

  This is a Dovecot server which is usually very reliable. I did notice something which could trigger a bug though. MailMate asks for the headers. Headers and body are separated by a blank line, but there is a problem in the message:

  X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3  
  Return-Path: ron.bloksma@hetnet.nl  
  This is a multi-part message in MIME format.
  
  ------=_NextPart_000_0068_01BF2FBF.50758000
  

  There should be a blank line after the Return-Path line. In any case, this should not make Dovecot crash (which I guess is what happens). I suggest you contact your IMAP provider and tell them about this ticket.

• You flagged this item as spam.
  

  Peter Mienes March 1st, 2015 @ 10:06 AM

  Thanks, I'll contact Polarismail.

• 

  benny March 1st, 2015 @ 02:52 PM

  • State changed from “new” to “closed”