Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!clyde.concordia.ca!altitude!postimage!marc
From: marc@PostImage.COM (Marc Boucher)
Newsgroups: comp.protocols.appletalk
Subject: Re: "popper" POP3 server mod
Message-ID: <1990Dec28.122729.11673@PostImage.COM>
Date: 28 Dec 90 12:27:29 GMT
References: <9012121428.AA20880@aquarium.ecn.purdue.edu>
Organization: DHD PostImage Inc., Montreal QC (CANADA)
Lines: 40

moyman@ECN.PURDUE.EDU (James M Moya) writes:

>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

I did the same, and noticed no undesirable side effects.
You will probably want to do the same thing to:

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

in pop_xmit.c.

>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

Marc.

-- 
Marc Boucher                    Internet: mboucher@PostImage.COM BIX: mboucher
Dir., Informatique              Telephone: (514) 489-8989        FAX: 489-0242
(H) PostImage Inc.              6265 St-Jacques O., Montreal Qc CANADA H4B 1T8