Receiving the same mail over and over

[Olle]

Version: 2008
Operating System: Mac OS X 10.5 (Leopard)
Processor: Intel
Email Client: pop

I get the same mails over and over to my Entourage inbox. It is just those who is on the server that are marked as read (when I access it with the webmail) though, all those marked as unread work perfectly fine. It is not every time when I use the send/receive but about three times a day.

I use the setting "leave a copy of the mail at the server" and have no rules in use at all.

Another thing I suspect but haven't been able to rule in och out (due to the randomness of when the problem occur) is that it seems as I can get these same mail even though I'm not connected to internet, but I'm unsure about this.

Grateful for help.

 

[Corentin Cras-Méneur]

I get the same mails over and over to my Entourage inbox. It is just
those who is on the server that are marked as read (when I access it
with the webmail) though, all those marked as unread work perfectly
fine. It is not every time when I use the send/receive but about three
times a day.

The mail on the server might be corrupted. I've had tht once in the past
and the only solution was to delete it from the server through webmail,

Corentin

 

[Adam Bailey]

I get the same mails over and over to my Entourage inbox. It is just those
who is on the server that are marked as read (when I access it with the
webmail) though, all those marked as unread work perfectly fine. It is not
every time when I use the send/receive but about three times a day.

I use the setting "leave a copy of the mail at the server" and have no rules
in use at all.

Using your webmail access, move the messages out of your Inbox and into
another folder. The Inbox is not meant to be a place for long term
storage.

 

[Olle]

I've found out what the problem was. We got two mail servers mirroring each other. But they are not coherrent with the references to the mails from entourage point of view so therefore one server was correct and the other corrupt. I've solved this by manually connect to just one of the servers and the error disappeared.