Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!sdd.hp.com!ucsd!ucbvax!ECN.PURDUE.EDU!moyman
From: moyman@ECN.PURDUE.EDU (James M Moya)
Newsgroups: comp.protocols.appletalk
Subject: "popper" POP3 server mod
Message-ID: <9012121428.AA20880@aquarium.ecn.purdue.edu>
Date: 12 Dec 90 14:28:05 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 27

popper generally works in the following manner:

When the server is queried (with whatever front-end app) to download mail
for a user, it creates a temp file called ".user.pop", mode 666 (in
/usr/spool/mail for most). Reads/copies the mail from it's "normal"
location (/usr/spool/mail/user for most) into that temp file. Downloads the
mail from the temp file to the mac.  After a successful downloading of the
mail popper zeroes out the temp file. It stays there until it is used once
again to download mail. 

Not really wanting mode 666 files laying around I removed the "ifdef"s from
the following (pop_dropcopy.c):

#ifdef DEBUG
    if (!p->debug)
        unlink (p->temp_drop);
#endif DEBUG

Which then removes the temp file after it is used... I poked around a bit
and this didn't seem unreasonable (or break anything). Anybody know
something I am missing (or "feature" I am losing) for doing this...
--moya

--Mike Moya 
--Macintosh Systems and Networking
--Engineering Computer Network, Purdue University
--moyman@ecn.purdue.edu or ..!pur-ee!moyman