Mark/All, An allnighter of research into this some months ago led me to conclude that Outlook's code for UIDL caching is broken (big surprise). Basically, a good MUA saves its UIDL cache until it has a full, error-free POP3 session in which no messages are reported and a clean QUIT is issued. Then it kills its cache and starts over.
Conversely, Outlook has a tendency to kill its cache during aborted POP3 sessions--in other words, it connects to the server on some basic level, but then backs out of the transaction at some point, tries to pull itself together and see if it got any new messages, thinks there wasn't anything (new *or* old) waiting, resets the UIDL cache, and you're in duplicate hell the next time you connect. That next time can be part of the same POP3 check, incidentally. I haven't seen this with The Bat!. I have seen it with Outlook and other mail servers. I haven't really seen in with OE. A mjor architectural diff between OL and OE in this regard is that OE keeps the UIDL cache in a separate file, so it's easier to manage in memory. OL keeps it in that big ol' PST. Sandy Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
