A lot of thanks to you and Ned Freed.
Happy to see that cyrus is so profesional.
A 10:51 01/07/2003 -0400, vous avez écrit :
Ken Murchison wrote:
OK. After talking with Rob and with Mark Crispin (author of UW IMAP),
the problem comes down to an unfortunate implementation decision in
Eudora and
Ken Murchison wrote:
OK. After talking with Rob and with Mark Crispin (author of UW IMAP),
the problem comes down to an unfortunate implementation decision in
Eudora and a change in the wording of the MIME specification from RFC
1521 to RFC 2046.
Technically, there is nothing syntactically i
t tell all Eudora senders to change their habits and/or migrate
to Mulberry, Outlook...
- Original Message -
From: "Ken Murchison" <[EMAIL PROTECTED]>
To: "Laurent LAVAUD" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, June 27, 2003 1:15 PM
On Fri, 27 Jun 2003, Laurent LAVAUD wrote:
> huge bug for us...
> [...]
> What make me think it's a cyrus bug is that if we send exactly the same
> message to the same server that runs wu imap instead of cyrus,
> everything is fine!
I don't know about 5.02 verus 5.2, but the second patch in the f
D" <[EMAIL PROTECTED]>
To: "David Chait" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, June 27, 2003 1:53 PM
Subject: Re: huge bug
A 13:30 27/06/2003 -0700, vous avez écrit :
>Correct, it is a known bug with a lot of Eudora versions. Qualcomm has it's
ra senders to change their habits and/or migrate to
Mulberry, Outlook...
- Original Message -
From: "Ken Murchison" <[EMAIL PROTECTED]>
To: "Laurent LAVAUD" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, June 27, 2003 1:15 PM
Subject: Re:
ED]>
Sent: Friday, June 27, 2003 1:15 PM
Subject: Re: huge bug
> If you want to send the message as it sits in the Cyrus and UW
> mailstores (gzip it so that the mailer doesn't munge it) and possibly
> capture the protocol log of the client trying to fetch the message, we
> _might_
If you want to send the message as it sits in the Cyrus and UW
mailstores (gzip it so that the mailer doesn't munge it) and possibly
capture the protocol log of the client trying to fetch the message, we
_might_ be able to figure out what is happening.
My guess would be that Eudora is not forma
