Hi,
we are using the Outlook Connector for the personal accounts and IMAP for as a workaroung for "public" folders.
The problem that mails are not saved in the sent folder should be solved with the 4.0.5 version of Zimbra.
But the error still occurs here.
Anything else there must be done to get this working?
Thanks.
Christian
Still problems with snet mails in imap accounts
Still problems with snet mails in imap accounts
bug 7826 was fixed in 4.5, not 4.0.5
Still problems with snet mails in imap accounts
Well, this is from the mail anouncing 4.0.5:
[QUOTE]Zimbra Collaboration Suite version 4.0.5 is now available for download. We recommend that all users upgrade to this release.
Customers and Partners may download it at:
This">http://www.zimbra.com/support
This release has over 50 bug fixes and enhancements including:
Improved Outlook Delegated Access
"Open Shared Calendar" link in Outlook now working correctly
HTML formatted messages sent from Zimbra Web Client to Windows Mobile 5 devices now renders correctly in Outlook view
Performance enhancement to Outlook Connector sync
Mail sent from POP/IMAP accounts with Outlook Connector now saved in Sent folder
[/QUOTE]
I think the last point is clear enough.
Is this an error in the mail then?
[QUOTE]Zimbra Collaboration Suite version 4.0.5 is now available for download. We recommend that all users upgrade to this release.
Customers and Partners may download it at:
This">http://www.zimbra.com/support
This release has over 50 bug fixes and enhancements including:
Improved Outlook Delegated Access
"Open Shared Calendar" link in Outlook now working correctly
HTML formatted messages sent from Zimbra Web Client to Windows Mobile 5 devices now renders correctly in Outlook view
Performance enhancement to Outlook Connector sync
Mail sent from POP/IMAP accounts with Outlook Connector now saved in Sent folder
[/QUOTE]
I think the last point is clear enough.
Is this an error in the mail then?
Still problems with snet mails in imap accounts
Yes, we yanked it at the last minute and probably forgot to update the release notes.