Hello Jonathan,
Thursday, December 19, 2002, 5:42:36 PM, you wrote:
JA -BEGIN PGP SIGNED MESSAGE-
JA Hash: SHA1
JA 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.
JA Technically this isn't a 'problem'... well... it is a problem in
JA respect to downloading mail, as you get duplicates, however it isn't a
JA problem in respect to what is defined as the rules for the protocol.
JA ,- [ UIDL ]
JA | While it is generally preferable for server implementations to store
JA | arbitrarily assigned unique-ids in the maildrop, this specification is
JA | intended to permit unique-ids to be calculated as a hash of the
JA | message. Clients should be able to handle a situation where two
JA | identical copies of a message in a maildrop have the same unique-id.
JA `-
JA By definition of the RFCs [1], I don't think UIDL is even a required
JA command based on the minimum list of commands, and additional
JA commands they provide.
JA [1] http://www.ietf.org/rfc/rfc1939.txt
JA - --
JA Jonathan Angliss
JA ([EMAIL PROTECTED])
JA -BEGIN PGP SIGNATURE-
JA iQA/AwUBPgJLYSuD6BT4/R9zEQIu5QCglHEUR/+2+rMR5JUt+AIh7cCMqMMAniN8
JA GBfD2Ocl8n+bHNE2bkdsec+k
JA =XL/g
JA -END PGP SIGNATURE-
JA
JA Current version is 1.62 | Using TBUDL information:
JA http://www.silverstones.com/thebat/TBUDLInfo.html
Clearly, though, they state that it is preferable this be handled via
server, though a client should be able to handle identical copies
with the same unique-id [oxymoron there, huh?].
While these are, truly, listed as optional, this makes for some
pretty strange science in any situation where mail is left on the
server. I know *I'm* tired of hitting the Kill Dupes button! ;-)
--
Best regards,
Craftsmanmailto:[EMAIL PROTECTED]
Current version is 1.62 | Using TBUDL information:
http://www.silverstones.com/thebat/TBUDLInfo.html