An FAQ post for future reference because, well, it’s a FAQ!
ViMbAdmin is primarily a database frontend for managing virtual mailboxes with mail services such as Postfix and Dovecot.
A frequently asked question is does it / can it support vacation / out of office auto-responders. The short answer is no.
The main way to handle OOO responders is via SIEVE (e.g. Dovecot’s version). To put a front end on this, you need a server configured for external SIEVE management and a client with SIEVE support (which ViMbAdmin does not have).
I’ve done it in three ways in the past:
- directly editing the .dovecot.sieve file. This is only really good for people with access to the server and some clue.
- Using a Thunderbird plugin allowing editing of SIEVE files. Again, clue required.
- For one customer, they can do it via the SoGO web interface we installed for them. This is a very nice interface for people migrating from Exchange.
We did look at fixing a Thunderbird Out of Office plugin but didn’t get very far.
What we all need here is for someone for write / sponsor a decent SIEVE based Thunderbird OOO plugin. Here’s some prior art: https://addons.mozilla.org/en-US/thunderbird/addon/sieve.
As part of pushing our new release of ViMbAdmin, I wrote up a mini how-to for setting up a virtual email system on Ubuntu where the components are:
- Postfix as the SMTP engine;
- Dovecot for IMAP. POP3, Sieve and LMTP;
- ViMbAdmin as the domain / mailbox / alias management system via web interface.
It supports a number of features including mailbox archival and deletion, quota support and display of mailbox sizes (as well as per domain totals).
Find the how-to at:
This post is much less of a detailed how-to but rather some useful links. We were tasked with the job of sync’ing about 1,000 MS Exchange mailboxes to a Dovecot server. This needed to be done via an administrator account on the Exchange end as individual user passwords were not available.
The tool of choice for this is imapsync. Unfortunately, there is not a single formula that will work for all as it can depend on the Exchange configuration and version as well as the use of domains on the Exchange and ActiveDirectory servers.
To help understand the various combinations of logins for Exchange, I found the following invaluable: Understanding login strings with POP3/IMAP.
Also invaluable is the imapsync FAQ – just search for mentions of Exchange.
In the end, the following worked for me (but your mileage will most definitely vary!):
./imapsync --host1 exchange-server
--user1 'domain/adminuser/user' --password1 'admin-password'
--host2 dovecot-server --user2 firstname.lastname@example.org
One key element here is that when logging into Exchange as an individual user I had to use
--authmech1 NTLM but if you use this auth method with the above user string, you will always end up logging into the admin’s mailbox, not the user’s. That, at least, was my experience.
In my career to date, I successfully managed to avoid all but the periphery engagement in OpenLDAP. Until recently that is – we had to build a Microsoft Exchange like environment with open source software in a way that was closely integrated and easily managed. But, more on that another time. For anyone else diving into OpenLDAP, here are some articles on my experiences that I have penned:
We’ve just pushed a new release of ViMbAdmin – version 2.1. The main highlights are:
- it’s now possible to restrict access to a mailbox via either IMAP, POP3 or both. See this page on the wiki for more information.
- it’s our first release requiring a database migration. But it’s really really easy – see this page for those instructions.
As always, a live demo is available at: http://www.opensolutions.ie/vimbadmin/.