I've had the issue both with local clients and remote clients running over a very expensive MPLS network, and in all the scanning I've done I can't see any issues with connectivity.
File locking? Hm, it's possible, however there's no AV software running on the server (not live, just batched once in a while and not when these problems are happening). In terms of the sequence of events, the mail client I wrote (I can't speak to how Outlook is having the same problem, but with my program I can!) it fetches each email individually then sends the command to the server to delete it, then processes the next message. Maybe I should do it the other way? Process them all THEN go back and delete them? The duplicates happen right away too, not during the next POP3 session; that is, as soon as the user clicks "Check Mail" he/she'll get duplicates (or triplicates) of the incoming mail immediately without waiting for the next check. On 3/21/07, John Kielkopf <[email protected]> wrote: > Things to check: > 1) Thoroughly check network connectivity to the mail server from the > problem clients. > > 2) Any possible file locking conflicts? Is there anything running on > the server, possibly antivirus software, that might be locking the email > in the server's mail directory? > Thought of what could be happening here: > a) Client retrieves all mail via pop3, marking them for deletion. > b) Something on the mail server is still holding the files open for > read (on demand AV scanner maybe?) > c) Client quits the pop3 session, and the messages marked for > deletion are now supposed to be deleted > d) Because one of the email messages is locked for read (see: "b", > above), Xmail is unable to delete files, and gives up. > e) Mail has not been deleted, and will be re-downloaded on next pop3 > session. > > > Davide would be able to comment on the possibility of "2d" happening on > Xmail. I have no idea if it could even happen, so I may be way off base > here -- but short of a network connectivity issue, I can think of > nothing else at the moment. > > > Aaron Fransen wrote: > > For some folks they receive emails twice, for some it's three times, > > but not (that I've heard anyways) more than that. > > > > An example: Joe Smith comes back from holidays, and has 50 emails > > sitting there for him. He receives each and every one three times > > exactly, ending up with 150 new emails in his inbox. > > > > Jane Doe checks her email every morning, and most mornings ends up > > receiving two of every email. > > > > Note that it's not selective: If a user is going to have this happen, > > it's going to every single email they happen to be retrieving at the > > time. If it's not going to happen, it's not going to happen on ANY of > > the emails they are retrieving. > > > > Aaron > > > > > > On 3/21/07, Hal Dell <[EMAIL PROTECTED]> wrote: > > > >>> I've tracked this as much as I can and this is what I've found: At no time > >>> > >> do the messages > >> > >>> exist on the server twice...they are *only* received twice by the client. > >>> > >>> It does seem to happen to some people more than others, which leads me to > >>> > >> believe > >> > >>> it's a "double-click the Send/Receive" button issue, but when I test it > >>> > >> the second request > >> > >>> is rejected since the POP server only allows a single connection per > >>> > >> individual. > >> > >> Are you sure they are *only* received the eMails twice? NOT more then that? > >> > >> Since, I'm coming into the middle of this eMail exchange in the -- I don't > >> have > >> all of the facts of your situation.... > >> > >> I had a problem like yours and was caused by the long time standing issues > >> with > >> mail clients on Windows due to the POP3 Tail issue - the symptoms that you > >> state > >> are nearly identical. David created a filter to not allow these messages in > >> the queue. > >> If you don't already have the filter installed I would highly recommend > >> installing it. > >> (Someone on this list may be able to tell the location to download the > >> filter -- I > >> don't see it listed on xmailserver.org -- it was mailed around at the > >> time). > >> > >> POP3 Tail issue is caused by spam and other hacker attempts at DOS targeted > >> at the eMail clients by intentionally corrupting the normal double CR LF > >> at > >> the > >> bottom of the eMail message byte stream. > >> > >> An eMail that is corrupted in this way causes the email client to never > >> complete > >> downloading the eMailbox the mailbox is never cleared and then you get > >> your Emails over and over again. This is a safety mechanism in the client > >> to prevent accidental erasure of eMail messages in the case of a dropped > >> IP connection. > >> > >> I'm not sure this will help you... Let us know... > >> > >> > >> Thanks, > >> Hal Dell > >> Managing Partner > >> ePodWorks.net, Inc. > >> PO Box 22 > >> Willow Grove, PA 19090 > >> +1-215-830-0662 (phone) > >> +1-866-549-4652 (fax) > >> Need Support send eMail to [EMAIL PROTECTED] ! > >> > >> > >> - > >> To unsubscribe from this list: send the line "unsubscribe xmail" in > >> the body of a message to [EMAIL PROTECTED] > >> For general help: send the line "help" in the body of a message to > >> [EMAIL PROTECTED] > >> > >> > >> > > - > > To unsubscribe from this list: send the line "unsubscribe xmail" in > > the body of a message to [EMAIL PROTECTED] > > For general help: send the line "help" in the body of a message to > > [EMAIL PROTECTED] > > > > > > > > > > - > To unsubscribe from this list: send the line "unsubscribe xmail" in > the body of a message to [EMAIL PROTECTED] > For general help: send the line "help" in the body of a message to > [EMAIL PROTECTED] > > - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
