Zimbra do not copy sended email to the send folder

[newemotion]

Zimbra do not copy sended email to the send folder, how can i do, that zimbra do so.

Prefernces/Composing/Send Messages/Save a copy to Send folder : dosn't work

thx

[uxbod]

Is this in the HTML, AJAX or Desktop client ?

[newemotion]

i'm sorry

it is Desktop

and an IMAP4 miscellaneous account (kolab)

thx

[sjoachim]

I recently updated to Zimbra Desktop for Windows 0.90 build 1251 on July 25th using IMAP with three accounts including a gmail account, and two standard IMAP accounts.

The gmail account is inserting sent messages into the sent massage table for the gmail account.

However, two accounts using standard IMAP to other mail servers are not showing in the Sent folder for all sent messages since the update (July 25th). I do not recall which build I was using previously(it was working), but it appears to be a regression nonetheless.

scott

[y@w]

Yes, that's a bug in the new Zimbra Desktop. Are you using a POP server? That's the type that's been mentioned the most. Apparently it's happening in standard IMAP accounts as well. I don't use the standard POP or IMAP for anything and I haven't seen it on my gmail or Zimbra accounts.

[jjzhuang]

Bug 30362 – pop account doesn't save to sent

[pamindic]

Originally Posted by y@w

Yes, that's a bug in the new Zimbra Desktop... ... I haven't seen it on my gmail or Zimbra accounts.

So is Zimbra only really good for Gmail, Yahoo and Zimbra accounts? Someone should let the user know, so he can settle on an email client that's committed to catering for his needs.

[pamindic]

Originally Posted by jjzhuang

Bug 30362 – pop account doesn't save to sent

That bug report says it's fixed, but it's not. I haven't tried POP3 but IMAP4 wont save sent emails to the Sent folder. I've seen that reported with Outlook - the fix used to be to set up a filter sending the sent emails to the sent folder, filtered on sender name. But that doesn't work with Zimbra either. A email client that doesn't save sends - without at least a workaround - is not that wonderful. This needs fixing.

[phoenix]

Originally Posted by pamindic

That bug report says it's fixed, but it's not.

The bug is fixed but it's not been through QA or Verified and therefore it's not in any build, yet. Click on the Resolution or Status keywords in the bug report to see what they mean.