I use Kmail for my email, but I also collect my emails on the fly with my blackberry. This is important for my business. I have a copy archived on my puter and I get the message instantly on my blackberry. Sounds simple enough and it should be.

To accomplish this, I have set my accounts to "keep a copy of the message on the server" on both device collection settings, to ensure that both devices have an opportunity to collect the message. I have also specified that the server should keep the message for 7 days.

Everything works perfect except for a really annoying anomaly. Every once in a while (and no... not every 7 days) the server will dump all of my previous messages to my accounts. Leaving me with a plethora of duplicates. In fact, every message is duplicated with the exception of the ones I deleted on the devices after receipt (obviously).

Why am I get dumped on? Why is the server not comprehending the settings?Also, I am collecting from 3 different accounts on 2 different servers. They all do the same thing. So I am hesitant to blame the server and am thinking there might be a bug in the Kmail code which tags the messages on the server.

Anyone else having this problem or know how to solve it?

BTW... went 100% Linux/Kubuntu at home and at my business and LOVING it!

Thanks in advance for any insight.

Oh.. they are simple pop3 accounts and the blackberry is not getting dumped... just KMail is. Its also going to the correct inbox folder. Its like it's collecting all of the previous emails again.

Very vanilla setup and this is the only prob on the puter (which is a lot more than I can say about the old windows setup).

Regards,

Jason

This sounds like a bug in KMail unfortunately, as it should be able to detect if you have already downloaded a message from the headers. Please file the bug, if it hasn't already at bugs.kde.org

( This is proven, given that your Blackberry has no problems with either server, yet KMail has problems with both )

Thanks,

Bug was searched and filed. I'll keep the board posted as progress is made.

Could you please post a link to the bug here, so future searchers can easily track the issue? Thanks in advance.

Here is the link as per your request.

https://bugs.kde.org/show_bug.cgi?id=187070

Regards,
Jason