-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dz-Jay, [DJ] wrote:
DJ> If this is the case, then I agree with you that TB should have an DJ> automatic mechanism to handle dupes. Most mail clients keep track of DJ> all UIDL (or Message-IDs) of the messages downloaded and use this to DJ> avoid re-downloading, and still offer some "advance" mechanism to DJ> allow this messages to be downloaded in the special case the user DJ> wants them to (i.e. Download *all* messages on server, as opposed to DJ> *new* messages). Why TB does not have this already surprises me, TB! does have this feature or else using the Account option to leave messages on the server would be quite chaotic. If a POP session ends unexpectedly, then TB! will be able to correctly tell which mail was previously downloaded and will, at the next POP session, work as if the mail downloaded during the previously interrupted POP session hadn't been downloaded. - -- -= allie_M =- | List Moderator _ -----BEGIN PGP SIGNATURE----- Version: PGP SDK 3.0.2 iQA/AwUBPyP+P1fJ62ArBxfiEQK3cQCgxPK6aIYuGVKWwgwWSi9fj4NuMxkAoKOR Cr1AA8kfXSO7uCbz3XBVkFTm =EgrO -----END PGP SIGNATURE----- ________________________________________________ Current version is 1.62r | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
