5.2.0 and above - email atatchments csv, txt stripped

[johnsopaul]

I'm now at 5.2.f (on a hosted LAMP server), using IMAP for personal folders and a group folder and have noticed that:

1. emails are no longer related to existing contacts automatically when imported from personal or group accounts
2. using quick create no longer populates the email field with the emailer's address
3. csv and txt file attachments are stripped from email (the original emails are deleted from the server)
4. when selecting multiple email to import from a personal account, if you select delete from server, you get a duplicate mail error for all but the first email which is handled OK - the rest are consigned to oblivion.


These are all a major pain in the arse for a production service. Is anybody else finding this or have an idea why this is happening or how to fix them. Bugs 1,2 and 3 above "seem" to have been introduced with 5.0 and I just found that a number of auditable attachments are simply gone. This is quickly becoming the straw that broke the camel's back with Sugar. I can no longer sell this to the customer (and Sugar would like us to move to Pro!)

[johnsopaul]

Could someone confirm this is not a problem for them?

Cheers

[salesagility]

Since you obviously can't be bothered ... then neither can I ... have you:

1. checked the release notes to see if these "issues" have been addressed in releases above 5.2f?
2. looked in bug tracker?

[ComputerHQ]

I can confirm this issue, and it does not happen to all emails only a few and from specific people. I can confirm the email attachments r there cause i can pick them in in Thunderbird.

I was also getting issues when attachments of the same name (l_print.pdf) all opened the same pdf document regardless of which date the email was send. Eventually got around this by using imap instead of pop3.

But the problem of missing attachments is fast becoming a sticky point for us. I dont see any error messages in the diagnostic files.

[johnsopaul]

Since you obviously can't be bothered ... then neither can I ... have you:

1. checked the release notes to see if these "issues" have been addressed in releases above 5.2f?
2. looked in bug tracker?

er yeah...i bothered to look everywhere i could to find any reason for the above but then my search skills aint at "hero" status. the latter existed in 5.5 at the time and probably still does in 6.0. what would have been good is someone with the requisite skills to have a quick look and confirm there actually was a problem and not just me missing something - power of the forum and all that. i suppose i could have filled bug tracker with a whole lot of potential rubbish without bothering to ask.

sorry to waste your time...but then again i suppose i didn't

btw - i still can't find any mention of the problem(s), let alone a fix, in bug tracker, the forums, or the release notes