Mark,
You were right, ipop3d and imapd behave identically, I just had
another case today with someone who had twice received a fairly large
(600 msgs) inbox using ipop3d and the outlook client. The only thing
I noticed where the faults found with the 'mailutil check' command as
reported earlier. I mentioned that our system is Redhat 4AS, but
forgot to mention that it is itanium (64-bit
only), mabye a shot in the dark, but you never know.
I examined the INBOX file and took the same file from a backup I took
a bit earlier, so I could compare.
The files are similar, but the latest file has a new UID on every
message. There was also a multipart mime message here.
These are the lines of the original file :
25-Oct-2006 21:52:57 +0200,21483;000000000000-00000281
25-Oct-2006 21:52:57 +0200,21421;000000000000-00000281
There are the same lines after the POP3 mail check :
25-Oct-2006 21:52:57 +0200,21483;000000000000-0000024a
25-Oct-2006 21:52:57 +0200,21421;000000000000-0000024b
Now the 2 parts of the message have their own UID and also mailutil
check doesn't give any faults.
best regards,
Andres
-- Citeren Mark Crispin <[EMAIL PROTECTED]>:
ipop3d and imapd should behave identically. The repair of a broken UID
regime is done by the mailbox open code in c-client.
Are you certain that the imapd and ipop3d that you are using are from
the same release? Also, are you using dmail and tmail from the same
release as well?
I find it very suspicious that the duplicate UID messages have the same
date and size. I wonder if there may be a locking failure.
What operating system are you using? Is NFS involved?
On Thu, 26 Oct 2006, Andres Henckens wrote:
Hello,
Can anyone confirm this behaviour of imap/ipop 2006 ?
We use the INBOX.mbx format here at the campus. It is a mixed environment
with ipop3d and imapd users.
Some people use ipop3d with the 'leave mail on server' option, but sometimes
get their e-mails downloaded for a second or more time.
I noticed that mailutil check gave me corrupted mbx files
warning: Invalid UID 000023d1 in message 5, rebuilding UIDs
After check a new mbx (with 6 emails) file I noticed this
25-Oct-2006 20:25:34 +0200,19161;000000000000-000023ce
25-Oct-2006 20:25:40 +0200,19420;000000000000-000023cf
25-Oct-2006 21:41:32 +0200,16853;000000000000-000023d0
26-Oct-2006 09:06:31 +0200,41181;000000000000-000023d1
26-Oct-2006 09:06:31 +0200,41181;000000000000-000023d1
26-Oct-2006 09:36:52 +0200,7426;000000000000-000023d2
Message 4 and 5 is a multipart message, but with the same UID -> 23d1
The mailbox is not fixed by ipop3d, but when openend with imapd (horde/imp)
the mailbox gets fixed automagically. When the staff member is back on his
desk and opens his ipop3d client, he gets another full copy of his inbox.
Can someone confirm this behaviour (and how to fix it :-))
I also checked that only tmail/dmail can write into the inbox.
best regards,
Andres Henckens
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
-- Mark --
http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
