Bug 10181 - The same mail messages arrives multiple times.
Summary: The same mail messages arrives multiple times.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: imap
Version: 7.0
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-03-15 12:31 UTC by Berd Dahlmo
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-07-30 23:23:45 UTC
Embargoed:


Attachments (Terms of Use)

Description Berd Dahlmo 2000-03-15 12:31:05 UTC
Several times customers complain that they receive the same e-mail multiple
times. (Client: OE and Netscape mail). Investigation show that messages are
not marked as read when client downloads message, and therefore is not
deleted and gets downloaded on the next poll.
Another technician found out that it was a badly formatted message that
confused pop3 and/or the client, so that it was not marked correctly when
user logged out. Sadly, he deleted the offending message without further
examination.

Comment 1 Need Real Name 2000-07-29 14:39:41 UTC
I'm encountering similar behavior. Deleted messages keep coming back marked as 
unread messages. We're using Netscape Communicator version 4.61, 4.73 for both 
Solaris and Windows 9x/nt.  It's got to be an imap problem, but I'm not sure 
how to troubleshoot.

Thanks,
Chandler
drc

Comment 2 Cristian Gafton 2000-08-09 02:28:40 UTC
assigned to the new owner


Comment 3 Indrajit Raychaudhuri 2000-09-02 19:03:03 UTC
Same behavior happen for me.  My client is Outlook Express 5.  Stangely enough, 
the problem goes away if I close OE and reopen -- this time it works.  But I 
guess it might not be OE problem since it doesn't happen with M$ Exchange for 
same set of mails and the same OE client in the same box.

Comment 4 Mike A. Harris 2001-07-30 23:22:57 UTC
This problem seems to have been fixed long ago but the bug report
was not updated.  A change of package owner may have been the cause.


Note You need to log in before you can comment on or make changes to this bug.