From: "Hannu E K Nevalainen \(garbage mail\)" <garbage_collector@telia.com>
To: <cygwin@cygwin.com>
Subject: RE: mozilla displays wrong headers from uw-imap (12/31/1969, blank subject)
Date: Mon, 08 Sep 2003 20:03:00 -0000 [thread overview]
Message-ID: <NGBBLLIAMFLGJEOAJCCEOEMGDDAA.garbage_collector@telia.com> (raw)
In-Reply-To: <D721826DEE793D49BC49582C121EDD3E3F54D1@exchange.perwill.com>
> From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com]On Behalf
> Of Steve Fairbairn
> Apologies to Hannu, I clicked reply and not reply to all...
:-] Well, I wish I knew how to set "reply-to:" for certain folders in
Outlook. I'm not sure it is possible.
<SNIP>
> > 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.
IMO "the Standard", RFC, IEEE, ISO, CCITT or whatever may say whatever they
want in the matter - what really counts is whether the actual application
does its job or not.
i.e. The user wants a _stable_ application, that does what its supposed
to - no matter what.
Here this boils down to; Accept line endings in any way they are.
... and now I realize that this has grown into something off topic ;-)
> 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.
IMO this shouldn't matter; parsing line endings is so basic stuff that a
piece of software that doesn't adjust for "current situation" is less usable
than it could be.
/Hannu E K Nevalainen, B.Sc. EE - 59°16.37'N, 17°12.60'E
--END OF MESSAGE--
--
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/
next prev parent reply other threads:[~2003-09-08 20:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-08 15:25 mozilla displays wrong headers from uw-imap (12/31/1969, blan k subject) Steve Fairbairn
2003-09-08 20:03 ` Hannu E K Nevalainen (garbage mail) [this message]
[not found] <1065278968.17167.ezmlm@cygwin.com>
2003-10-04 15:27 ` mozilla displays wrong headers from uw-imap (12/31/1969, blank subject) Aaron
-- strict thread matches above, loose matches on Subject: below --
2003-09-08 14:04 Mr. Ali Nabavi
2003-09-08 15:12 ` Hannu E K Nevalainen (garbage mail)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=NGBBLLIAMFLGJEOAJCCEOEMGDDAA.garbage_collector@telia.com \
--to=garbage_collector@telia.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).