Inbound email functions fail most of the time

[blinkie]

I'm happy to see that the 5.x email module has progressed nicely, to the point where we're now trying to migrate users to using it rather than our previous webmail solution. But I've been encountering a huge problem with regard to inbound email and attachments. Unfortunately, MOST of the time the attachments are either corrupt (that is, a file is downloaded but it's not the file or even file type that corresponds to the listed attachments) or they don't show up. If I open my email box using an IMAP client (like OSX Mail.app or Thunderbird, or even our previous webmail system) everything works fine.

I suspect the problem may be related to the cache because sometimes just selecting "Clear cache files" seems to correct the problem (although selecting the same email immediately after clearing the cache results in an "Invalid link' error when attempting to the pull down the attachment, but the next attempt will succeed).

I'm baffled as to the purpose of the mail cache. I can understand that the functionality may be intended to cut down on traffic to the mail server (IMAP in our case) but if that is the purpose I just don't get it. A decent IMAP server (like courier) configured with the IDLE command is far superior to a setup that must regularly poll the server (resulting in our users wanting to hit "Check Email" when waiting for that important message to come through). But I digress.

I don't see anything written here about attachment problems.....so is everyone else not experiencing this problem? (Nothing in bug reports either, at least nothing I can find).

Centos5; Sugar 5.2.0a CE; Apache 2.2.3; PHP 5.1.6; mysql 5.0.22

[robertbmirth]

/bump

I'm having this problem in SugarOnDemand 6.0. Its rather frustrating, because its really killing my bounced email configuration, as the forwarded email that's sent with the bounce is sent as an attachment. Thus, Sugar just ignores the bounce even though technically it contains both the correct MAILER-DAEMON email address and the removeme link that it so desperately needs to use to determine that the email has, in fact, bounced. And I can't seem to find a suitable workaround.