Peeped Messages Remain After Downloading From Servers To Client
Posted: Sat Apr 23, 2016 2:55 am
While continuing as a circumspect friend of PopPeeper for a considerable time, once again the program has tripped me up, this time by refusing to dismiss messages from my various email servers (external: my ISP, Hotmail, Yahoo, Gmail..) after I have retrieved them all into my email client, Outlook 2010.
My old Windows 7 profile slowed to a crawl (temporary internet files allocation stuck on 0 MB) so I created a new logon - standard user. After transferring all my files to my new profile and wrestling Outlook into co-operating with my old psts - and copying over PopPeeper's ini file from my old logon to my new, I expected PP would behave as reasonably as it had before. But now, after each 'peep' - preview of headers - and activating 'F9 Receive' on Outlook 2010, PP won't dismiss prior messages. Yes, even as POP accounts I have always left messages on their servers. The servers must know that I've taken them down to my client - because I never get duplicate messages - but PPeeper doesn't recognise that I have them.
My analysis defeats me: I see the message schema as this:
Server holding messages, unread, read, deleted, copied/downloaded
Client storing messages, unread, read, deleted
PopPeeper peeping in on server messages, unread, read, (marked to be) deleted, copied/downloaded, 'peepable'/displayable or not depending upon whether they have been retrieved by a full client (non-PP), or deleted from their server by PP, or not.
I thinking that with PP(Pro) now acting (tempo'rily or not) as an email client (compose, send, receive, read) that it might be interferring with its role as a header/message peeper.
Can anyone help me with my understanding of PP, and help me get my old ini file acting as it always has?
I expect it's simple, but it beats me.
Thx
[I tell a lie: peeping at my Yahoo accounts never dismissed previously retrieved messages; PP always displayed all my 6 million Yhoo messages...]
My old Windows 7 profile slowed to a crawl (temporary internet files allocation stuck on 0 MB) so I created a new logon - standard user. After transferring all my files to my new profile and wrestling Outlook into co-operating with my old psts - and copying over PopPeeper's ini file from my old logon to my new, I expected PP would behave as reasonably as it had before. But now, after each 'peep' - preview of headers - and activating 'F9 Receive' on Outlook 2010, PP won't dismiss prior messages. Yes, even as POP accounts I have always left messages on their servers. The servers must know that I've taken them down to my client - because I never get duplicate messages - but PPeeper doesn't recognise that I have them.
My analysis defeats me: I see the message schema as this:
Server holding messages, unread, read, deleted, copied/downloaded
Client storing messages, unread, read, deleted
PopPeeper peeping in on server messages, unread, read, (marked to be) deleted, copied/downloaded, 'peepable'/displayable or not depending upon whether they have been retrieved by a full client (non-PP), or deleted from their server by PP, or not.
I thinking that with PP(Pro) now acting (tempo'rily or not) as an email client (compose, send, receive, read) that it might be interferring with its role as a header/message peeper.
Can anyone help me with my understanding of PP, and help me get my old ini file acting as it always has?
I expect it's simple, but it beats me.
Thx
[I tell a lie: peeping at my Yahoo accounts never dismissed previously retrieved messages; PP always displayed all my 6 million Yhoo messages...]