Ajcody-Server-Misc-Topics: Difference between revisions
m (→DAV Related) |
|||
Line 661: | Line 661: | ||
* [http://www.bitkinex.com/download.php# BitKinex 3.1.1 for Windows (freeware)] | * [http://www.bitkinex.com/download.php# BitKinex 3.1.1 for Windows (freeware)] | ||
* [http://www.webdrive.com/products/webdrive/index.html Webdrive - A Universal File Access Client that maps drive letters to FTP, WebDAV, SFTP and S3 Servers ($$)] | * [http://www.webdrive.com/products/webdrive/index.html Webdrive - A Universal File Access Client that maps drive letters to FTP, WebDAV, SFTP and S3 Servers ($$)] | ||
* [http://www.enginsite.com/Download.htm#Freeware EngInSite DataFreeway - SSH (SSH1, SSH2, SFTP), FTP WebDAV client for Windows. | |||
** [Listed as Freeware but will prompt about license upon first launch, trial version] | |||
====Notable Bugs And RFE's==== | ====Notable Bugs And RFE's==== |
Revision as of 20:18, 2 March 2010
- This article is NOT official Zimbra documentation. It is a user contribution and may include unsupported customizations, references, suggestions, or information. |
Miscellaneous Server Topics
Actual Miscellaneous Server Topics Homepage
Please see Ajcody-Server-Misc-Topics
Setting A Default Domain For User Login
In the admin web console goto:
Configuration > Global Settings
On the General Information tab to the right you'll see a variable called "Default domain". This will be the assumed domain for user logins as well [as well as other functionality].
If you have multiple domains and want to allow users avoid having to type in their domainname with their login credentials you should look at Virtual Hosting.
For Multi-Domains, please see:
Virtual [vhost] Hosting
References
- Multiple_SSL_Virtual_Hosts_5.0
- "Configuring for Virtual Hosting"
- I think the below link is probably superseded now by the other options explored below. When we are talking about vhosting multiple domains on Zimbra and allowing users to login with only their username rather than user@domain.
Non-Proxy [NGINX] Virtual Hosting
- You can configure multiple virtual hostnames to host more than one domain name on a server. When you create a virtual host, users can log in without have to specify the domain name as part of their user name. Virtual hosts are configured from the administration console Domains>Virtual Hosts tab. The virtual host requires a valid DNS configuration with an A record. When users log in, they enter the virtual host name in the browser. For example, https://mail.example.com. When the Zimbra logon screen displays, users enter only their user name and password. The authentication request searches for a domain with that virtual host name. When the virtual host is found, the authentication is completed against that domain.
- Example, you have a single ZCS setup and your going to host multiple domains. [This is only true with a single ZCS mailbox setup. ] You want your users of those domains to use the "domainname" throughout all client configurations and interactions with the mailserver. So the pop/imap/http url's use the mail domain they are in, rather than the physical hostname+domainname of the ZCS server.
- You would configure in the /etc/hosts and/or DNS to resolve the domainname targets that the user will be using to point to the physical ip address of the ZCS server.
- You would then in the admin web console of ZCS, setup the domains under the "Domain Virtual Hosts" section. And confirm the "default domain login" is properly setup for the users/domain users.
- Example, you have a single ZCS setup and your going to host multiple domains. [This is only true with a single ZCS mailbox setup. ] You want your users of those domains to use the "domainname" throughout all client configurations and interactions with the mailserver. So the pop/imap/http url's use the mail domain they are in, rather than the physical hostname+domainname of the ZCS server.
Proxy [NGINX] Virtual Hosting
General Description:
- You can configure multiple virtual hostnames to host more than one domain name on a server. When you create a virtual host, users can log in without have to specify the domain name as part of their user name. Virtual hosts are configured from the administration console Domains>Virtual Hosts tab. The virtual host requires a valid DNS configuration with an A record. When users log in, they enter the virtual host name in the browser. For example, https://mail.example.com. When the Zimbra logon screen displays, users enter only their user name and password. The authentication request searches for a domain with that virtual host name. When the virtual host is found, the authentication is completed against that domain.
- Exception. It would be possible to do the functions of Virtual Hosting without installing the zimbra proxy package. Using jetty directly for example. Our recommendation is to use the zimbra proxy package to achieve this though.
- Example, you have a single ZCS setup and your going to host multiple domains. [This is only true with a single ZCS mailbox setup. ] You want your users of those domains to use the "domainname" throughout all client configurations and interactions with the mailserver. So the pop/imap/http url's use the mail domain they are in, rather than the physical hostname+domainname of the ZCS server.
- You would configure in the /etc/hosts and/or DNS to resolve the domainname targets that the user will be using to point to the physical ip address of the ZCS server.
- You would then in the admin web console of ZCS, setup the domains under the "Domain Virtual Hosts" section. And confirm the "default domain login" is properly setup for the users/domain users.
- Example, you have a single ZCS setup and your going to host multiple domains. [This is only true with a single ZCS mailbox setup. ] You want your users of those domains to use the "domainname" throughout all client configurations and interactions with the mailserver. So the pop/imap/http url's use the mail domain they are in, rather than the physical hostname+domainname of the ZCS server.
- Exception. It would be possible to do the functions of Virtual Hosting without installing the zimbra proxy package. Using jetty directly for example. Our recommendation is to use the zimbra proxy package to achieve this though.
References:
Domain And User "Status" Changes
If you need to manually modify the status of a domain, for example - migration.
Checking Status - Mode Of Domain
If the domain is in "active" mode, the CLI output will show this.
zmprov gd domainname zimbraDomainStatus zimbraDomainStatus: active
The variables are all lowercase by the way.
Setting A Domain To Maintenance Status - Modes
To set a domain to "maintenance" mode, you would do the following.
zmprov md domainname zimbraDomainStatus maintenance
Setting A Domain To Active Status - Modes
To set a domain to "maintenance" mode, you would do the following.
zmprov md domainname zimbraDomainStatus active
Descriptions Of Status - Modes
Here's the descriptions for each of the "status" or "modes":
- Active. Active is the normal status for a mailbox account. Mail is delivered and users can log into the client interface.
- Maintenance. When a mailbox status is set to maintenance, login is disabled, and mail addressed to the account is queued at the MTA. An account can be set to maintenance mode for backing up, importing or restoring the mailbox.
- Locked. When a mailbox status is locked, the user cannot log in, but mail is still delivered to the account. The locked status can be set, if you suspect that a mail account has been hacked or is being used in an unauthorized manner.
- Closed. When a mailbox status is closed, the login is disabled, and messages are bounced. This status is used to soft-delete an account before deleting the account from the server. A closed account does not change the account license.
- LockOut. Users who try to log in and do not enter their correct password are locked out of their account after a specified number of consecutive failed login attempts. An account’s status is automatically changed to Lockout. How long the account is locked out is set by COS or Account configuration, but you can change the lockout status at any time.
Cross Mailbox Searches and Tracing
The crossmailbox search tool from the Admin web console requires the Archiving & Discovery package to be installed. The zmmboxsearch (CLI) doesn't require this.
Searches And Timeout Variables - ZCS 6+
httpclient_soaphttptransport_so_timeout is set by default to 60 - in seconds. If you are using the -m "*" variable, to search for everyone, you might need to set this to 0 [no timeout] on the mailstore your doing the search from.
zmlocalconfig -e httpclient_soaphttptransport_so_timeout=0
Cross Mailbox Search
Events/errors will show in /opt/zimbra/log/mailbox.log
Search From the CLI
From the CLI, see zmmboxsearch help page
Here's an example use of the zmmboxsearch command:
su - zimbra mkdir /tmp/testing zmmboxsearch -m user1@mail3.internal.homeunix.com,user2@mail3.internal.homeunix.com -q "in:inbox" -d /tmp/testing/
Try using the formats I've written about here - Ajcody-Notes#Web_Client_Search - for the query string.
Search From the CLI - A&D Accounts - Even If Primary Account Was Deleted
Here's an example use of the zmmboxsearch command when you have all your archive accounts using the domain name of zimbra.homeunix.com.archive:
su - zimbra mkdir /tmp/testing zmmboxsearch -m `zmprov gaa | grep zimbra.homeunix.com.archive` -q "in:inbox" -d /tmp/testing/
Single A&D account search is this simple, for example. Primary account was user1@mail3.internal.homeunix.com with archive account being user1-20081211@mail3.internal.homeunix.com.archive. This will work even if the primary account, user1@mail3.internal.homeunix.com, was deleted.
su - zimbra mkdir /tmp/testing zmmboxsearch -m user1-20081211@mail3.internal.homeunix.com.archive -q "in:inbox" -d /tmp/testing/
If this isn't working, make sure the archive accounts still exist. Example uses my "archive" domain:
zmprov gaa | grep mail3.internal.homeunix.com.archive
Searches From Admin Web Console - Deleted Primary Account But A&D Account Still Exists
Please see the following:
- http://bugzilla.zimbra.com/show_bug.cgi?id=37921
- "archives should be searchable independent of their original mailboxes"
Message Tracing
Please see the command help page for zmmsgtrace .
Deferred Emails - Error Of Connection Refused
Your having emails deferred and you check the /opt/log/zimbra.log file and see something like:
Sep 2 05:17:56 mail postfix/qmgr[12229]: 56A793151483: to=<USER@DOMAIN.net>, relay=none, delay=29404, delays=29404/0.08/0/0, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]: Connection refused)
Things to do to help trouble shoot the issue:
- Please confirm that iptables and selinux aren't running or are configured properly.
service iptables status
sestatus
- Can you telnet to the different ports for example? port 25?
- What's your /etc/hosts look like and is the format correct - confirm localhost entry is right?
cat /etc/hosts
- Check for hostname issues:
hostname YOUR_FQDN
hostname -t MX YOUR_DOMAINNAME
cat /etc/resolv.conf
- Give the output of the following as well - replace YOUR_SERVER_NAME:
zmprov gs YOUR_SERVER_NAME | grep -i mta
- Have you tried to disable DNS lookups? [zimbraMtaDnsLookupsEnabled]
zmprov ms YOUR_SERVER_NAME zimbraMtaDnsLookupsEnabled FALSE
- What's the current status of zimbra services?
zmcontrol status
- If you can restart zimbra - while starting zimbra get logging events that might be related to issue or other errors/warnings:
zmcontrol stop
tail -f /opt/zimbra/log/mailbox.log & /opt/zimbra/log/zmmailboxd.out & /var/log/zimbra.log
zmcontrol start
- Have you tried to disable antivirus and antispam to see if queue flushes?
- Amavis
zmamavisdctl status
zmamavisdctl stop
zmamavisdctl start
- Clam
zmclamdctl stop
zmclamdctl start
- Amavis
- Give the following output - as root:
netstat -lntp
lsof | grep TCP
- Checking postfix for deferred and command to flush:
postqueue -p
postqueue -f
What's my time and timezone?
I wrote up the steps to make sure the ZCS server is using the correct time and timezone here:
http://wiki.zimbra.com/index.php?title=Time_Zones_in_ZCS#The_server_OS
Volumes & zmvolume
Basic Concepts
- From Mike's forum post. Modified a little.
Each Zimbra mailbox server is configured with one index & message volume (NE can add secondary HSM volumes).
A volume will state it's condition as "current" as either true or false.
When a new message is delivered or created, the message is saved in the current message volume. Additional message volumes can be created, but only one is configured as the current volume where new messages are stored. If the volume is in danger of becoming full, you can configure a new current message volume. The new current message volume would then receive all the new messages. New messages are never stored in the previous volume once it's current value is set to false. A current volume cannot be deleted - via zmvolume. If there are accounts with messages referencing the older volume it should not be deleted until you point the volume path to wherever you've now moved the items.
Each mailbox is assigned to a permanent index directory on the current index volume. When an account is created, the current index volume is automatically defined for the account. You cannot change which index volume the account is assigned. As volumes become full, you can create a new current index volume for new accounts. When a new index volume is added as current, the older index volume is no longer assigned new accounts. Index volumes not marked current are still actively in use as the index volumes for accounts assigned to them - unlike the message volumes. Any index volume that is referenced by a mailbox as it's index volume cannot be deleted.
The Network Edition has the HSM (Hierarchical Storage Management) feature which involves moving data to other storage locations automatically after x amount of time. Messages and attachments are moved from a primary volume to the current secondary volume based on the age of the message; completely transparent to the user.
(Also a handy tidbit of info: collapsing message volumes - first tip is good for HSM > back to store, Klug's also points out that you can essentially use the same concept of Adam's wiki page [see below]; making it a subdirectory of the new filesystem location keeps it simple.)
The admin console > server > volumes tab is straight forward, make sure you have permission to write to the target location - see also: CLI_zmvolume (-l and -dc arguments display your volumes)
If you're curious how to view that in the DB:
su - zimbra mysql select * from zimbra.volume;
How To Go About Changing Volume Paths
List your current volume details
zmvolume -l
Make your directories to the "new" volume path. For example:
mkdir /san/mount/index /san/mount/store chown zimbra:zimbra /san/mount/index /san/mount/store
Shutdown zimbra so we can move the data.
zmcontrol stop
Now move all the old data and then make symbolic links from old to new.
mv /opt/zimbra/index/* /san/mount/index/ mv /opt/zimbra/store/* /san/mount/store/ rmdir /opt/zimbra/store /opt/zimbra/index ln -s /san/mount/index /opt/zimbra/index ln -s /san/mount/store /opt/zimbra/store
Start zimbra back up.
zmcontrol start
- Goto the admin web console , Configuration > Servers > server-name > Volumes Tab.
- Select index volume
- Click edit
- Modify the path to the new path
- Click edit
- Select store volume
- Click edit
- Modify the path to the new path
- Click edit
- Select index volume
- Click on Save in the upper left hand section.
To Modify Volume From CLI After Data Move
See what the details are of your volumes:
zmvolume -l /opt/zimbra/index and zmvolume -l /opt/zimbra/store Volume id: 2 name: index1 type: index path: /opt/zimbra/index compressed: false current: true Volume id: 1 name: message1 type: primaryMessage path: /opt/zimbra/store compressed: false current: true
Let's say your sym links are the ones shown above:
/opt/zimbra/index /opt/zimbra/store
And your new directory paths are:
/mnt/nas/index /mnt/nas/store
You would run the following to modify the volumes to use the real directory paths rather than the sym links.
zmvolume -e -id 2 -p /mnt/nas/index zmvolume -e -id 1 -p /mnt/nas/store
Convertd
From release notes:
An alternative implementation of the convertd daemon used for text extraction and conversion to HTML is now available as beta in 5.0.7. The new implementation is Apache multi-process based, as opposed to the original implementation which was multi-threaded. When libraries used to handle attachments fail or crash, the multi-process implementation allows for better availability. Since the new implementation is still in beta, the older multi- threaded implementation continues to be the default. If you are experiencing a high number of 400 (try again) error codes during LMTP delivery, or if you are seeing too many kvoop processes consuming memory, you can try the new Apache-based convertd.
- See Bug 2161 for more details.
Note - ALL mailstores must be running the same version of convertd. Multi-mailstore environments must plan upgrades/switch simultaneously.
- You must install the new zimbra-convertd package for it to be available.
- This is that reference during the installer about convertd. The basic convertd (v1) package is apart of zimbra-core.
- kvoop is when your running version 1 of convertd.
ps auxwww | grep -i kvoop
- Run the script you want. For 5.0.7+ , this script will now shutdown and restart necessary service components.
- Run /opt/zimbra/convertd/bin/upgrade_v2 to upgrade.
- Run /opt/zimbra/convertd/bin/downgrade_v1 to downgrade.
- Pre 5.0.7, you'll need to manually stop / start service components.
- Restart zimbra or one might be able to get away with just restarting convertd and mailstore.
zmcontrol stop
zmcontrol start
- Restart zimbra or one might be able to get away with just restarting convertd and mailstore.
Domain Rename Issues
We have a command to rename a "domain" and the resources within it - unfortunately it doesn't handle ALL of the different components for various reasons. Specifically Documents and Calendars [more down below].
Review this RFE that was done when they implemented the renameDomain command.
http://bugzilla.zimbra.com/show_bug.cgi?id=7655
Note comment 21 & 22 (confirming what QA'd). The syntax is
zmprov -l rd testold.com testnew.com
Problem With Documents
Problems that arise with Documents are explained here, comment #1 has workaround.
http://bugzilla.zimbra.com/show_bug.cgi?id=25873
Problem With Calendar & Appointments
Now, the very unfortunate part about calendars with a domainname change/move.
- "Ability to change a username globally on all appointments"
- "Cant edit calendar entries after renameDomain"
- "Ability to assign ownership (ie change organizer) of meetings based on search criteria"
The root issue here's seems to be more about the calendar standards and practices with the use of the "Organizer" field and notifications. You'll see 3 "work arounds" in comment 2 of bug 26736.
Export/Importing of the calendar data is shown here:
http://wiki.zimbra.com/index.php?title=User_Migration
This part specifically :
http://wiki.zimbra.com/index.php?title=User_Migration#Copy_Calendar_From_One_Zimbra_User_to_Another
Changing Default Port 80 - No Proxy In Use And Single Server Example
Review the zmtlsctl wiki page to determine the http/https use.
* CLI_zmtlsctl_to_set_Web_Server_Mode
This example changes 80 to 60081 and 443 to 60443.
Confirm current port use/access and that no iptables/firewall are in use:
**as root** lsof -P -n -i :80 -i :443 iptable -L **Policy As Accepted & None Blocked** cat /etc/selinux/config **SELINUX=disable**
Make sure your not running the zimbra proxy service:
**as zimbra** zmprov gs `zmhostname` | grep ServiceEnabled
Resolve any issues above before continuing.
Now, make any changes to the Web Server Mode you need in regards to http and https.
For example, I'll change mine to "mixed"
**as zimbra** zmtlsctl mixed
Now let's change the ports in use [zimbraMtaAuthHost is a valid mailbox server hostname if your a multi-server ZCS environment]:
zmprov ms mail.yourdomain.com zimbraMailPort 60081 zmprov ms mail.yourdomain.com zimbraMailSSLPort 60443 zmprov ms mail.yourdomain.com zimbraMtaAuthHost mail.yourdomain.com zmcontrol stop zmcontrol start
And now confirm the changes:
**as root** lsof -P -n -i :60081 -i :60443
Themes, Branding, Logos, And Other UI Customizations
Main Wiki Page: Skins
Please see:
- For ZCS 5.x+
- For ZCS 4.5.x
Finding Skins Variable From CLI
What skins are available [zimbraInstalledSkin]:
[zimbra@mail3 ~]$ zmprov gacf | grep -i skin zimbraInstalledSkin: bones zimbraInstalledSkin: sky zimbraInstalledSkin: lemongrass zimbraInstalledSkin: lavender zimbraInstalledSkin: yahoo zimbraInstalledSkin: waves zimbraInstalledSkin: bare zimbraInstalledSkin: sand zimbraInstalledSkin: steel zimbraInstalledSkin: hotrod zimbraInstalledSkin: beach
Can Users Change Their Skin? This depends on their COS and the COS Value [zimbraFeatureSkinChangeEnabled]:
[[zimbra@mail3 ~]$ zmprov gac default [zimbra@mail3 ~]$ zmprov gc default | grep -i skin zimbraFeatureSkinChangeEnabled: TRUE [zimbra@mail3 ~]$ zmprov gac default [zimbra@mail3 ~]$ zmprov gc default | grep -i skinchange zimbraFeatureSkinChangeEnabled: TRUE
What is the default skin for the cos [zimbraPrefSkin]:
[zimbra@mail3 ~]$ zmprov gc default | grep -i prefskin zimbraPrefSkin: beach
To Modify the default skin for a cos:
zmprov mc [cos name] zimbraPrefSkin Name_Of_Skin
Sending Email From The CLI (Command line) On Zimbra Server
Make a txt file:
vi /tmp/email.txt
Put in something like:
Date: Thu Nov 19 08:41:54 2008 To: extech@taxinfo.hrblock.com Subject: Test message From: admin@tax.hrblock.com
Body of message goes here
And then using the zimbra/postfix command for this, it would be:
/opt/zimbra/postfix/sbin/sendmail -t < /tmp/email.txt
or this, if that didn't work:
/opt/zimbra/postfix/sbin/sendmail -Am -t < /tmp/email.txt
I see the -Am referenced in the /opt/zimbra/conf/swatchrc.in file, but the man page for sendmail (zimbra/postfix) doesn't give clarity on this option.
Role Based Administration - Expansion Of Permission & Function Model For Admin Roles
Please see the following:
- "server side infrastructure for role based delegated administration"
- "role based delegate administration"
Spammers
Disconnect Web Session Spammer Hijacked
These might be related:
- "Manually Expire Web Sessions"
- http://bugzilla.zimbra.com/show_bug.cgi?id=34054
- probably related
- "Webclient timed logout setting appears to bind at login time"
- probably related
- http://bugzilla.zimbra.com/show_bug.cgi?id=34054
- Not sure about this one...
- "EndSessionRequest does not return"
Looks like they need some Votes/Comments
Mass Importing / Exporting Of Things (Tasks, Notes, Documents, Briefcase, etc.)
Notes
Please see, Ajcody-Client-Topics#Import_.26_Export_Notes_.26_Journal
Documents And Briefcase
Please see, Bulk Upload To Briefcase
Inter-Domain (Company To Company) Item Access [Sharing?] Via Rest
From /opt/zimbra/doc/rest.txt :
2. Inter-domain To access items across domains that span Zimbra installations, use the exact same naming convention. For example, if companyA installs Zimbra, and companyB installs Zimbra, someone at companyA should be able to reference an item from companyB using the same syntax: /home/john.smith@companyB.com/shared/contacts this can be accomplished with DNS SRV records. For example, companyB.com could publish a SRV record for _zimbra._tcp: _zimbra._tcp.companyB.com. SRV 10 5 80 zimbra.companyB.com The Zimbra proxy at companyA can then detect that companyB.com is not a local Zimbra domain, and do a DNS lookup for: _zimbra._tcp.companyB.com And get back "zimbra.companyB.com" as the name of the Zimbra sever to direct the request to. It would then do the equivalent of: http://zimbra.companyB.com/home/john.smith@companyB.com/shared/contacts
Rest Url's And Spaces , White Spaces, %20
From /opt/zimbra/doc/rest.txt :
ISSUES/NOTES 2. user-friendly item "ids"? It would be nice to have user-friendly names for items inside of a folder, such as (+ is url-encoded form of a space): /home/roland/calendar/Staff+Meeting /home/roland/contacts/Roland+Schemers /home/roland/inbox/Important+Meeting Exchange allows this type of naming, need to determine how/if we'd want to do this, and how to deal with collisions like it does. Might need to come up with a per-item query-param string, or use search: /home/roland/contacts/?query="Roland Schemers"
Faster Way To Get Directory Size On Filesytem - find vs du
Instead of using:
du -sh .
Try this instead:
find . -printf %k"\n" | awk '{ sum += $1 } END { print sum }'
Free Busy, FreeBusy, FB, F/B Topics
References
Current references for server topics for FB are:
- On your zimbra server:
- /opt/zimbra/doc/freebusy-interop.txt
- Free Busy Interop for Exchange 2003, 2007, and Non-Exchange Systems [similiar to above]:
- Setting Up Free Busy Interop with Exchange 2007:
- FB Interoperability setup & configuration - section "Zimbra Free/Busy Interoperability":
- Troubleshooting Exchange FB Interop:
Client Configuration topics for FB are:
- User sharing their FB with someone via email:
- Outlook and FB:
Free Busy Support Requirement Clarifications
Please see the following:
- "ZCS to ZCS free/busy interop"
- http://bugzilla.zimbra.com/show_bug.cgi?id=26398
- [marked as dup of above] "Free Busy documentation & configuration should include Zimbra to Zimbra"
- "Clarity on FB / Free Busy configuations we support"
- Similar, but not identical to above
- "Allow access to external users' internet free-busy, similar to Outlook"
- "ability to subscribe to externally published calendars"
- http://bugzilla.zimbra.com/show_bug.cgi?id=26398
Miscellaneous Bugs And Related RFEs
Please see:
- "Support checking free/busy from an external source for a zimbra account"
- "Interop: don't hard code cn=RECIPIENTS"
- "RFE: Extend Exchange Free/Busy interop to support multiple AD organizations"
WebDAV & Davfs2 - Briefcase - Documents - Notebook
At this time, I can not find anything in our documentation that states that Zimbra via WebDAV can replace a file server 100% and that it is a supported and promised feature & function of Zimbra. What is supported, seems to be the narrow action of "reading" objects from WebDAV. But the full functionality to grant complex permissions and shares, write files remotely, and expansive support for the various OS's and WebDAV clients is beyond official support at this time. If you believe differently, please share the source on this wiki page "Discussion" section.
Resources
Non-OS Based Webdav Clients
- Anyclient - The Free No-Install FTP, FTPS, SFTP and WebDAV Client
- BitKinex 3.1.1 for Windows (freeware)
- Webdrive - A Universal File Access Client that maps drive letters to FTP, WebDAV, SFTP and S3 Servers ($$)
- [http://www.enginsite.com/Download.htm#Freeware EngInSite DataFreeway - SSH (SSH1, SSH2, SFTP), FTP WebDAV client for Windows.
- [Listed as Freeware but will prompt about license upon first launch, trial version]
Notable Bugs And RFE's
From Release Notes 6.0.3
- Briefcase Spreadsheet and Presentation functions are beta for 6.0.0
DAV Related
- "server side webdav repository for zimbra users"
- "NPE in DAV on DF"
- http://bugzilla.zimbra.com/show_bug.cgi?id=19984
- dup of above "WebDAV generates an error"
- http://bugzilla.zimbra.com/show_bug.cgi?id=19984
- "files uploaded with webdav client and with spaces in the name become unusable"
- "davfs2 can't create/copy files via Zimbra WebDav"
- http://bugzilla.zimbra.com/show_bug.cgi?id=24178
- Release Notes description, "Linux users can now access documents in Briefcase as if they are accessing files on a network drive."
- http://bugzilla.zimbra.com/show_bug.cgi?id=24178
- "Webdav URL for a shared briefcase"
- "WebDav access doesn't work with Vista"
- "WebDAV not compatible with Windows 7"
- http://bugzilla.zimbra.com/show_bug.cgi?id=40067
- Something wrong with Windows 7 and webdav. My testing came to the same results as this article states.
- http://bugzilla.zimbra.com/show_bug.cgi?id=40067
- " Hide/delete resource forks created by Mac OS X on WebDAV access to Briefcase "
- "Editing and Saving a file via WebDAV (Mac OS X)"
- "Edit and Save As a new file name via WebDAV (Mac OS X)"
Document Sorting
- "Ability to sort items in the briefcase alphabetically, by date, type, size, owner, etc." [Helix target]
- http://bugzilla.zimbra.com/show_bug.cgi?id=25220
- Below will most likely become dup of above
- "Sort documents by date"
- Below will most likely become dup of above
- http://bugzilla.zimbra.com/show_bug.cgi?id=25220
- "Sorting should be available on ALL columns"
Unsorted
- "Invalid request while attempting to access sub folder of shared briefcase"
- "Briefcase for HTML lite client"
- "Documents for Html client"
- "Rename File in Briefcase"
- "Documents stored in browsing history creates document syncing issues"
- "Documents cannot be closed after closing history"
- "Table of contents not shown after clicking close on document history"
- "History/Edit links are not available half the time"
- "Briefcase - share expiration & share ability to file rather than just folder"
- "preview documents in briefcase "
- "Unable to import files into Documents Notebook"
- "Set a default file extension" [files are html files]
- "Convert (import/export) from popular document formats to edit via Zimbra AJAX editors"
- "Concurrent editing of Briefcase requires locking or notification"
- "Briefcase can show only 250 items - should do virtual paging"
- "Briefcase cleanup"
Max File Upload Size
Check the following variable:
zmprov gacf zimbraFileUploadMaxSize
To edit:
zmprov mcf zimbraFileUploadMaxSize 100000000
Also, with ZCS 6+ :
zmprov gacf zimbraMailContentMaxSize
To edit:
zmprov mcf zimbraMailContentMaxSize 100000000
Apple - Mac
On a Mac, I've confirmed this process works for read. It appears to write files but in the end it will not do it correctly. My test had left a file saved incorrectly and also left a dot [.*] file that could be seen in ZWC.
- Open Finder
- Go > Connect To Server
KDE3 - Konqueror3 - Linux
This works for read access, but not write. Though it does seems to allow you to create a "New Folder" when you right-click on the page and do Select New > Folder. The other options - Text File, etc. - fail as well as drop and drag.
- Open Konquerer
- Put in the appropriate url and authenticate when popup shows
- webdav/s://SERVERNAME/dav/USERNAME/Briefcase
KDE4 - Konqueror4 - Linux
This doesn't seem to work with reads or writes.
- Open Konquerer
- Put in the appropriate url and authenticate when popup shows
- webdav/s://SERVERNAME/dav/USERNAME/Briefcase
- webdav/s://SERVERNAME/service/dav/USERNAME/Briefcase
- http/s://SERVERNAME/dav/USERNAME/Briefcase
- http/s://SERVERNAME/service/dav/USERNAME/Briefcase
The http will output the properties of the destination but doesn't actually give a file listing.
Internet Explorer - IE
These various syntax tests either gives an error about access, page not found, or does output an xml type page listing details about the briefcase/notebook contents. It does not however, give it in a usable format - page indexing - where one could download the file so one could view it.
http/s ://$MAILSERVER/service/dav/$USERNAME http/s ://$MAILSERVER/service/dav/$USERNAME@$DOMAIN http/s ://$MAILSERVER/service/dav/$USERNAME%40$DOMAIN http/s ://$MAILSERVER/dav/$USERNAME/Briefcase/ http/s ://$MAILSERVER/dav/$USERNAME/Notebook/ webdav/s ://$MAILSERVER/dav/$USERNAME/Briefcase/ webdav/s ://$MAILSERVER/dav/$USERNAME/Notebook/
Firefox
These various syntax tests either gives an error about access, page not found, or does output an xml type page listing details about the briefcase/notebook contents. It does not however, give it in a usable format - page indexing - where one could download the file so one could view it.
http/s ://$MAILSERVER/service/dav/$USERNAME http/s ://$MAILSERVER/service/dav/$USERNAME@$DOMAIN http/s ://$MAILSERVER/service/dav/$USERNAME%40$DOMAIN http/s ://$MAILSERVER/dav/$USERNAME/Briefcase/ http/s ://$MAILSERVER/dav/$USERNAME/Notebook/ webdav/s ://$MAILSERVER/dav/$USERNAME/Briefcase/ webdav/s ://$MAILSERVER/dav/$USERNAME/Notebook/
RSS
Notable Bugs And RFE's
- "Expand documentation in admin guide/wiki for RSS topics"