🚀 go-pugleaf

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