From owner-freebsd-isp Mon Oct 26 22:46:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17715 for freebsd-isp-outgoing; Mon, 26 Oct 1998 22:46:14 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from velvet.sensation.net.au (serial0-velvet.Brunswick.sensation.net.au [203.20.114.195]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17696 for ; Mon, 26 Oct 1998 22:46:08 -0800 (PST) (envelope-from rowan@sensation.net.au) Received: from localhost (rowan@localhost) by velvet.sensation.net.au (8.8.8/8.8.8) with SMTP id RAA16214 for ; Tue, 27 Oct 1998 17:41:08 +1100 (EST) (envelope-from rowan@sensation.net.au) X-Authentication-Warning: velvet.sensation.net.au: rowan owned process doing -bs Date: Tue, 27 Oct 1998 17:41:05 +1100 (EST) From: Rowan Crowe To: freebsd-isp@FreeBSD.ORG Subject: Re: Expiring old mail? In-Reply-To: <3727.909469498@gjp.erols.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 27 Oct 1998, Gary Palmer wrote: > Rowan Crowe wrote in message ID > : > > The only thing I've found wrong with cucipop so far is that it doesn't > > support the LAST command, which appears to be actually part of the POP3 > > spec. This is a bit of a surprise, since the rest of the man page mentions > > that certain commands will "break the spec" and tends to sound very > > careful about that kind of thing. Anyone know why LAST isn't implemented? > > RFC1939 (the ``standard'' for POP3) doesn't mention the LAST command, which > makes me wonder what clients use it and how badly things break. Very odd. I obviously don't have the latest RFC, however, RFC 1460 (June 1993) clearly lists LAST as part of the specification. LAST Arguments: none Restrictions: may only be issued in the TRANSACTION state. Discussion: The POP3 server issues a positive response with a line containing the highest message number which accessed. Zero is returned in case no message in the maildrop has been accessed during previous transactions. A client may thereafter infer that messages, if any, numbered greater than the response to the LAST command are messages not yet accessed by the client. Possible Response: +OK nn I guess it's for mail clients that are too lazy to keep lastread pointers. :) (I had a report from 2 users when I switched POP3 servers - one of them was running Eudora and it was easily fixed with a minor configuration change at their end). Cheers. -- Rowan Crowe Sensation Internet Services, Melbourne Aust fidonet: 3:635/728 +61-3-9388-9260 http://www.rowan.sensation.net.au/ http://www.sensation.net.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message