Article View: comp.mail.pegasus-mail.misc
Article #18memory.pm
From: Peter G Higgins
Date: Mon, 10 Jan 2000 00:00
Date: Mon, 10 Jan 2000 00:00
18 lines
1681 bytes
1681 bytes
I'm trying to understand how memory.pm gets flushed. At home I download unread mail from the server at work without deleting -- that way I can still access all the mail when I get to work. Occassionally "read mail" is also downloaded. Over the recent holiday break this problem became annoying. One list was receiving bounced mail from a subscriber, causing a loop that generated hundreds of emails. For me, the problem was exacerbated on popping as all unread mail as well as new mail was also downloaded. In trying to diagnose the problem, I thought that one possibility is that the memory.pm reaches a certain size and then is automatically flushed. Hence, some previous downloads would not be in the list. Is this so? Looking forward to an interesting discussion. Peter
Technical Details
Message-ID:
<387963AE.2DF25067@swin.edu.au>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f6a29,1d92ca0cef5cc4cb,start X-Google-Attributes: gidf6a29,public X-Google-Thread: 1076a3,1d92ca0cef5cc4cb,start X-Google-Attributes: gid1076a3,public X-Google-Thread: 100ad5,1d92ca0cef5cc4cb,start X-Google-Attributes: gid100ad5,public From: Peter G Higgins <phiggins@swin.edu.au> Subject: memory.pm Date: 2000/01/10 Message-ID: <387963AE.2DF25067@swin.edu.au> X-Deja-AN: 570612465 Content-Transfer-Encoding: 7bit X-Accept-Language: en-GB,en,en-* Content-Type: text/plain; charset=us-ascii X-Complaints-To: abuse@swin.edu.au X-Trace: lucille.cc.swin.edu.au 947479486 31848 136.186.9.29 (10 Jan 2000 04:44:46 GMT) Organization: Swinburne University of Technology Mime-Version: 1.0 NNTP-Posting-Date: 10 Jan 2000 04:44:46 GMT Newsgroups: comp.mail.pegasus-mail.misc,comp.mail.pegasus-mail,bit.listserv.pmail