Thread View: comp.mail.pegasus-mail.misc
4 messages
4 total messages
Started by Peter G Higgins
Mon, 10 Jan 2000 00:00
memory.pm
Author: 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
Re: memory.pm
Author: Han van den Bogaerde
Date: Mon, 10 Jan 2000 00:00
Date: Mon, 10 Jan 2000 00:00
35 lines
2250 bytes
2250 bytes
In bit.listserv.pmail on Mon, 10 Jan 2000 15:44:30 +1100, Peter G Higgins <phiggins@swin.edu.au> wrote: >I'm trying to understand how memory.pm gets flushed. it's not flushed, it's rewritten on each session. >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 case of a mail loop many strange things can happen, where the mesage-id's the same or different and such? >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? No, there is no maximum restriction - as far as the author of WinPmail could tell. >Looking forward to an interesting discussion. >Peter Han van den Bogaerde - jaabogae@caiw.nl Member of the Pegasus Mail Support Group My own Pegasus Mail related web information: http://surf.to/HanPegasusMail
Re: memory.pm
Author: Peter G Higgins
Date: Thu, 13 Jan 2000 00:00
Date: Thu, 13 Jan 2000 00:00
22 lines
1821 bytes
1821 bytes
Hans, Thank you for your informative response. I gather that on either opening or closing (which?) memory.pm is written completely. As new mail arrives other entries are added. Have I got it right? I was looking at my modem activity and noted that about 400k of data was being downloaded allthough only a couple of small sized messages arrived. This seems to suggest that in checking unread messages all messages are downloaded and only the unread ones are then kept. But this seems to be at odds with another observation. When I've received very large messages (containing attachments) the download of the message takes a significant time (and the percentage download indicator becomes active), but on the next pop cycle, it is obvious that the large message is not again downloaded. Looking forward to your response. regards Peter
Re: memory.pm
Author: Peter G Higgins
Date: Thu, 13 Jan 2000 00:00
Date: Thu, 13 Jan 2000 00:00
12 lines
1225 bytes
1225 bytes
Hans, I have another query. As messages that have been popped are read and deleted what happens to memory.pm. For example, if I read and delete messages over a couple of weeks, without deleting from the pop server. Thanks in advance. regards Peter
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads