Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: From: Steve Fairbairn To: "'cygwin AT cygwin DOT com'" Subject: RE: mozilla displays wrong headers from uw-imap (12/31/1969, blan k subject) Date: Mon, 8 Sep 2003 16:25:05 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Apologies to Hannu, I clicked reply and not reply to all... > -----Original Message----- > From: Hannu E K Nevalainen (garbage mail) > Subject: RE: mozilla displays wrong headers from uw-imap (12/31/1969, > blank subject) > > > > Of Mr. Ali Nabavi > > Fetchmail gets my mail via pop3 and sends them to either > tmail or dmail > > (I've used both.) The logs look just fine, but says "bare > LF only" and > > I don't know if that is a problem. The mail ends up where > the uw-imap > > readme says it will, in /var/mail/. I log in successfully > > with both Mozilla and Pegasus Mail and the messages have > blank headers > > except for the date, which is 12/31/1969. When I open the > messages, the > > headers look okay, the date and time are accurate, but moving the > > message to another folder corrupts the message and, it appears, only > > moves the body over, not the headers. > > I'm no expert, but to me this looks as fetchmail and the > other (cygwin!) > tools uses LF line endings (Unix style). While Mozilla and > Pegasus Mail > (Windows executables most likely) expect it to be the Windows > way (i.e. > CR+LF). > > IMO a Mozilla and/or Pegasus Mail bug. > Not definately true. The Mail/MIME encoding RFC's state that all headers should be CRLF no matter what the platform. It is open to dispute quite whether the RFC's should still apply once the mail has finished it's journey through the ether and has been collected from the email server by such a tool as fetchmail. It seems likely that Mozilla is expecting the CRLF's to remain on the headers which would probably be true if Mozilla was collecting the emails itself. It is my guess that fetchmail is stripping the CR's from the message as it retrieves it which could well be the accepted practice for UNIX boxes, but under a cygwin text mount it should perhaps behave differently. This is purely speculation I've not looked at the sources, but it is certainly true that the pop3 server should be presenting the headers with CRLF line endings to the client. HTH, Steve Fairbairn. -- -- LONG DISCLAIMER -- ******************************************************* This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com ******************************************************* Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. ******************************************************* Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. ******************************************************* This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a ******************************************************* -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/