View Single Post
  #8 (permalink)  
Old 11-27-2009, 11:25 PM
mmorse mmorse is offline
Moderator
 
Posts: 6,237
Default

Ok, so that 'folder location conflict on /Inbox' error is probably due to Bug 40033 - Disallow multiple data sources against the same folder as discussed in Bug 42690 - External POP account cannot download emails to Inbox for more than one account re a duplicate key problem mentioned in Bug 39633 - Error message is displayed when 'Get External Mail' button is clicked after changing the account name for the added comcast.net account.

(BTW before I ramble further, it sounds like most of you here will also be interested in setting something like: zmprov mc COSname zimbraDataSourcePop3PollingInterval 45m.)

~

Obviously there's a strong desire to have the ability to combine account into one inbox - whether using a mobile device that can only do one location, or just suffering from 'too many accounts overload'. (ie: Stick items in the main /Inbox like you 'could' with pop in ZCS 5.0) ZD 2.0 will actually use a virtual global inbox via a special search that can be turned on or off (the accounts data/datasources aren't really in one folder - technically folders are just metadata groupings in the DB anyways). Bug 30869 - Aggregated Inbox

For ZCS, external IMAP/POP accounts are/were more like one-way aggregation (storing into your Zimbra account) rather than a true sync client. (Thus POP behaved pretty much as expected in terms of 'leave on server/remove' while IMAP moves, deletes syncing upwards were another matter.) Seen some other RFE's on this besides Bug 30716 - manage external IMAP folder subscriptions but don't remember where, and I must confess I haven't played with them much lately to see if some of this has changed, so I'll have to test everything before filing RFE's. There's also a demand for 'backporting' ZD's easy special account configuration; from mapped folder names to the ability to connect to regular Yahoo accounts via IMAP rather than just the POP provided in Y! plus accounts. Repeat for other special mail/calendar/contacts cases like Exchange/Gmail/AOL/MobileMe/Hotmail. Bug 33886 - IMAP/POP account aggregation setup should be simpler doesn't quite encompass all of what's needed for this to happen it's more about using Bug 18870 - Prepopulate some pop/imap accounts combined with all the new stuff we've developed since, but I've mentioned it there/dependency linked it for now.

We did implement a 'reload all rss feeds' so we could do the same to solve micronaet's desire not to have to click 'get mail' on each POP account. Someone check latest/bugzilla/file a new enhancement request.

If your not a fan of setting up fetchmail on everyone, we actually have polling built-in, to enable on one datasource:
Quote:
zmprov gds user@domain.com
zmprov mds user@domain.com [external IMAP/POP account data source name] zimbraDataSourcePollingInterval 45m
Previously zimbraDataSourcePollingInterval could be set on account/COS and contrary to Bug 33151 - data polling interval inheritance issue actually did inherit, but just didn't show it in zmprov provisioning output.

As of 6.0.0 per Bug 34104 - Cleanup data source polling interval attributes we switched to separate attributes zimbraDataSource[Protocol]PollingInterval (where 'protocol' equals imap/pop3/rss/live/caldav/yab) on account/COS and zimbraDataSourcePollingInterval on the datasource only:

Quote:
Deprecated zimbraDataSourcePollingInterval on account/cos since 6.0.0. Values of zimbraDataSourcePollingInterval on account/cos are migrated to protocol specific zimbraDataSource{proto}PollingInterval.
Rules:
1. If zimbraDataSourcePollingInterval is set on data source, use it.
2. Otherwise use the zimbraDataSource{Proto}PollingInterval on account/cos
3. If zimbraDataSource{Proto}PollingInterval is not set on account/cos, use 0, which means no automated polling.
So to avoid having to tediously set it on each datasource, you want something like:
Quote:
zmprov mc COSname zimbraDataSourcePop3PollingInterval 45m
Or the more specific per user:
Quote:
zmprov ma user@domain.com zimbraDataSourcePop3PollingInterval 45m
While we now do it automatically for calendars Bug 12390 - automatically reload remote calendars & rss Bug 6491 - Allow automatic / scheduled reloading of feeds we didn't expose end users settings for mail polling because of performance Bug 22114 -Expose external account polling interval in UI however you can vote for Bug 21199 - add ability to set autopolling in admin console

Last edited by mmorse; 11-27-2009 at 11:50 PM..
Reply With Quote