Re: Exclusive-access locking of maildrop

"Michael S. Shappe" <mss1@cornell.edu> Thu, 02 June 1994 13:17 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa02891; 2 Jun 94 9:17 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa02887; 2 Jun 94 9:17 EDT
Received: from ANDREW.CMU.EDU by CNRI.Reston.VA.US id aa05518; 2 Jun 94 9:17 EDT
Received: (from postman@localhost) by andrew.cmu.edu (8.6.7/8.6.6) id JAA01783; Thu, 2 Jun 1994 09:11:50 -0400
Received: via switchmail for ietf-pop3+@andrew.cmu.edu; Thu, 2 Jun 1994 09:11:50 -0400 (EDT)
Received: from po2.andrew.cmu.edu via qmail ID </afs/andrew.cmu.edu/service/mailqs/q001/QF.khvRcWO00Uda0H7E5E>; Thu, 2 Jun 1994 09:09:55 -0400 (EDT)
Received: from postoffice3.mail.cornell.edu (POSTOFFICE3.MAIL.CORNELL.EDU [132.236.56.11]) by po2.andrew.cmu.edu (8.6.7/8.6.6) with ESMTP id JAA04888 for <ietf-pop3@andrew.cmu.edu>; Thu, 2 Jun 1994 09:09:46 -0400
Received: from Untitled (UNCLE-MIKEY.CIT.CORNELL.EDU [132.236.69.173]) by postoffice3.mail.cornell.edu (8.6.5/8.6.5) with SMTP id JAA13457; Thu, 2 Jun 1994 09:08:21 -0400
X-Sender: mss1@harper-hall.cit.cornell.edu
Message-Id: <aa13863a03021016f8a2@Untitled>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 02 Jun 1994 09:08:29 -0400
To: Michael D'Errico <Mike@software.com>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Michael S. Shappe" <mss1@cornell.edu>
Subject: Re: Exclusive-access locking of maildrop
Cc: ietf-pop3@andrew.cmu.edu

At 5:10 PM 6/1/94, Michael D'Errico wrote:
>Either way, the IMAP server has to be "POP-aware" which means there
>needs to be a standard way to lock maildrops, etc. so that different
>implementations can interact correctly.  This would require changing
>both the POP and IMAP specs. and I doubt we'd ever come up with a
>universal way to lock maildrops.  The only other ways to enforce this are
>to force people to use POP and IMAP servers from the same implementor
>(assuming that the servers cooperate) or to pick one protocol over the
>other.

I've handled this by creating a derivative of the bezerkly driver in
C-Client. The mods I've made are currently intended as part of a
'straight-jacket' IMAPD that can ONLY access a person's POP box (it's a
long story, but trust me, it's necessary for us right now). The
modifications also make use of popper's '.user.pop' drop-boxes. They're not
pretty, but so far, they seem to work...


We only bothered for two reasons. The locking was needed for that
one-in-one-sagan chance that a person making use of our 'travelers mail'
service (which is a PINE/IMAP-based straight-jacketed way to access one's
POP box via a telnet session, for the client-impaired or for people who
feel that collecting mail via POP over a v.32bis SLIP line is too slow when
they're paying by the miinute :-) also left their POP-client at work up and
running. The temp-box functionality was necessary because another use of
travelers mail is to get users out of sticky situations that cause their
POP-clients to crash (out of disk space, client choking on a message, among
others). Since unmodified popper leaves things in the temp-box upon
crashing, IMAPD needed to know to look at it if it was going to be useful
for these situations.

Of course, the details are not all that important; the point is, when
you've got source code, it's not rocket science to fix things the way you
need them to work.

Mikey

--
Michael Scott Shappe
CIT Collaboration Systems
"Me? I'm just a lawnmower. You can tell me by the way I walk."
        -- Genesis, "I Know What I Like", _Selling England by the Pound_