Keith Edmunds writes:
This would seem to suggest that the UID is valid, but if you believe I
am mistaken please tell me - I am keen to prove the problem is, as I
suspect, with the client.
You have not shown anything that indicates that the source folder has not
been modified between the first
> The UID COPY command specified a nonexistent UID. According to RFC
> 2060:
> ... A non-existent unique
> identifier within a message set range is ignored without any
> error message generated.
Thanks, I didn't know about that. However, I do
Keith Edmunds writes:
Test, server: set up a debug file. One unsuccessful copy was initiated
and showed this in the log:
READ: NUMBER: 473
READ: ATOM: UID
READ: ATOM: COPY
READ: NUMBER: 3457
READ: ATOM: INBOX.Scratch.sc1
READ: EOL
WRITE: 473 OK COPY completed.
This would appear to indicate th
