-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, December 16, 2002, Peter Palmreuther wrote...
> The trouble the OP might "be run into" will likely be: the > POP3-server does not generate the same UID for the same message > every time. This is a known, but not wide spread problem which can > only be fixed on server side. Technically this isn't a 'problem'... well... it is a problem in respect to downloading mail, as you get duplicates, however it isn't a problem in respect to what is defined as the rules for the protocol. ,----- [ UIDL ] | While it is generally preferable for server implementations to store | arbitrarily assigned unique-ids in the maildrop, this specification is | intended to permit unique-ids to be calculated as a hash of the | message. Clients should be able to handle a situation where two | identical copies of a message in a maildrop have the same unique-id. `----- By definition of the RFCs [1], I don't think UIDL is even a required command based on the "minimum" list of commands, and "additional" commands they provide. [1] http://www.ietf.org/rfc/rfc1939.txt - -- Jonathan Angliss ([EMAIL PROTECTED]) -----BEGIN PGP SIGNATURE----- iQA/AwUBPgJLYSuD6BT4/R9zEQIu5QCglHEUR/+2+rMR5JUt+AIh7cCMqMMAniN8 GBfD2Ocl8n+bHNE2bkdsec+k =XL/g -----END PGP SIGNATURE----- ________________________________________________ Current version is 1.62 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
