From owner-freebsd-questions Tue Jan 16 12: 3:31 2001 Delivered-To: freebsd-questions@freebsd.org Received: from clmboh1-smtp3.columbus.rr.com (unknown [65.24.0.112]) by hub.freebsd.org (Postfix) with ESMTP id F15A637B401 for ; Tue, 16 Jan 2001 12:03:11 -0800 (PST) Received: from mail.iowna.com (dhcp065-024-023-038.columbus.rr.com [65.24.23.38]) by clmboh1-smtp3.columbus.rr.com (8.11.2/8.11.2) with ESMTP id f0GK0d722122; Tue, 16 Jan 2001 15:00:43 -0500 (EST) Message-ID: <3A64A833.6D157AE6@mail.iowna.com> Date: Tue, 16 Jan 2001 14:59:47 -0500 From: Bill Moran X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Christopher Farley Cc: Drew Sanford , "Hudson, Henrik H." , "'questions@freebsd.org'" Subject: Re: qpopper References: <3A646359.89989A21@mail.iowna.com> <20010116102024.C32412@northernbrewer.com> <3A647570.5030307@planetwe.com> <3A647DB5.D0EB69EE@mail.iowna.com> <20010116111334.A34019@northernbrewer.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christopher Farley wrote: > > Bill Moran (wmoran@mail.iowna.com) wrote: > > Personally, I've never called them stupid. I will, however, accuse them > > of breaking protocol support in their applications in order to promote > > 100% use of Microso~1 protocols & software to their potential clients. > > > > Let's see ... if POP3 does strange things with Outlook, the uninitiated > > will fall for propaganda that it's because POP3 doesn't work right, then > > we can convince everyone that they should be using Exchange servers ... > > > > Gee, Microso~1 has never done anything like that, have they? > > I think we're all in agreement that Microsoft is *evil*. But I'm > still quite certain that Outlook implements the POP3 protocol pretty > well, at least with respect to tracking message IDs, and preventing > the repeated download of previously fetched messages. I don't use Outlook so I can't vouch that it does or doesn't work. The only clients I have that are using it don't use the "leave messages on server" option, so I can't vouch for the workingness or non-workingness of that either. If you've used it and got it working, I'll simply have to take your word for it. I'm simply saying that the odd behaviour described is a sounds like the weird inconsistencies that Mircoso~1 puts in their products to break compatibility without "officially" violating a protocol. It could be a bug, intentional misfeature or simply a misconfig on the part of the person using it, I don't know. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message