Thanks for all the feedback and bug reports received which makes up this minor point release.

As usual, a full change log is available here and the packaged release can be downloaded directly here.

Just over a week ago, we released V2 of ViMbAdmin which was a complete UI refresh.

Thanks for all the feedback and bug reports since then.

Today, we’re pleased to announce the immediate availability of 2.0.6 which has a number of incremental fixes and improvements including:

• Domain is now ‘sticky’ when moving between mailboxes, aliases and logs making it much easier to browse a single domain;
• A cookie is now used to remember the page length for individual users;
• We now use grouped icons with tooltips rather than labelled buttons throughout;
• The horrible your IP address has changed message is gone.

As usual, a full change log is available here and the packaged release can be downloaded directly here.

And here’s the new improved look:

We’ve also closed a lot of bugs, improved the functionality and navigation and added a couple of small features.

Let us know what you think!

0.3.4   2011-09-06
 - fix: https://github.com/opensolutions/ViMbAdmin/issues/3
 - add: Support new mailbox password hashes: crypt, sha1 and 
        salted sha1 and md5. Issue 9 from Google Code:

http://code.google.com/p/vimbadmin/issues/detail?id=9

 - fix: Changes in 0.3.2 prevented wildcard aliases
 - add: MD5-CRYPT hashing used by, for example, Dovecot.
        This addresses:

http://code.google.com/p/vimbadmin/issues/detail?id=6

0.3.3   2011-09-02
 - fix: Critical regression introduced in 0.3.2 preventing the
        editing of aliases

0.3.2   2011-09-01
 - fix: https://github.com/opensolutions/ViMbAdmin/issues/1
 - add: optional parameter in application.ini (skipVersionCheck) 
        to tell ViMbAdmin to skip the version check on login
        See: https://github.com/opensolutions/ViMbAdmin/issues/2
 - fix: we now check for duplicate mailboxes (and aliases) 
        rather than letting Doctrine throw exceptions for 
        uniqueness constraints. Thanks maysara for the report.
 - fix: validate new aliases and mailboxes which was not being 
        done previously

0.3.1 was released on August 23rd and it’s the sixth release since our last announcement.

Changes include:

• Various changes required for the migration to GitHub.
• A major fix of a bug preventing users to edit aliases.
• New favicon based on logo from Limeworks Australia – http://www.limeworks.com.au
• New autocomplete functionality (used on the Edit / Add Alias page)
• New logo thanks to Limeworks Australia – http://www.limeworks.com.au
• New login screen designFix a critical bug fix preventing email being sent during first use set up

As always, the full change log is available at:

https://github.com/opensolutions/ViMbAdmin/blob/master/CHANGELOG

As such I have converted my co-workers and we have migrated ViMbAdmin to GitHub. We feel that the project is in an early enough stage to not cause too much annoyance with the current user base. We do sincerely apologise for all and any inconvenience caused.

Do you want to continue with your SVN installation?

Feel free to svn switch your base from Google Code to the following which tracks our master (i.e. stable / production / release) branch:

http://svn.github.com/opensolutions/ViMbAdmin.git

Migrating to Git

Just follow the instructions at:

https://github.com/opensolutions/ViMbAdmin/wiki/Install-using-git

and skip the database setup. Just copy over your application/configs/application.ini file to the new Git clone.

Using Official Packaged Releases?

No problem – you’ll now find new versions at:

https://github.com/opensolutions/ViMbAdmin/archives/master

24 hours later, we proudly present the new face of ViMbAdmin:

With a cool new logo, we decided we needed to overhaul the login page. You can see the new face of ViMbAdmin at our updated live public demonstration page: http://www.opensolutions.ie/vimbadmin/. This has also been incorporated in a new release version, 0.2.4, which can be downloaded from here.

A sincere thanks to Robert Bell and his team Limeworks Australia for the logo.

• you can now conveniently add a new email alias in the “Aliases of [emailaddress]” popup window;
• when adding a new mailbox or alias, the domain is pre-selected when available;
• you can now set the number of rows to display in the configuration file;
• we’ve added a link to the login page to the mailbox password change page;
• you can now conveniently add domains to admins through the Administrators -> Domains screen;
• the system will now check and alert super admins if a new version is available as well as display the version in the footer;
• many bug fixes.

A full list of changes can be found in the change log and updating instructions can be found here.

In this first of a serious of articles where we delve into some of the hidden treasures in our ViMbAdmin application, we look at how to integrate Doctrine ORM with Zend – and specifically Zend_Application and Zend_Controller.

The first assumption (and requirement) we are going to make is that you are using Zend_Application. If you want to see a working application set up and configured for this, please checkout or browse our ViMbAdmin source code – which we’ll reference throughout this document.

Zend Application has a resource framework which allows us to bootstrap various resources on demand. We have created a Doctrine resource for this very purpose which you can download from here (and you may need to edit the class name and change the plugin path in the config code below to match your setup). Our implementation does many things:

• instantiates the Doctrine object;
• sets up an autoloader for Doctrine models;
• instantiates the Doctrine manager;
• opens the connection to the database;
• sets all collations and character sets to UTF8 (this is hard coded but can easily be changed);
• sets various hard coded Doctrine attributes which can also be changed.

We the add various configuration parameters to the application.ini file:

pluginPaths.ViMbAdmin_Resource = APPLICATION_PATH "/../library/ViMbAdmin/Resource"

resources.doctrine.connection_string = "phptype://username:password@host/database"
resources.doctrine.data_fixtures_path = APPLICATION_PATH "/../doctrine/data/fixtures"
resources.doctrine.models_path = APPLICATION_PATH "/models"
resources.doctrine.migrations_path = APPLICATION_PATH "/../doctrine/migrations"
resources.doctrine.sql_path = APPLICATION_PATH "/../doctrine/data/sql"
resources.doctrine.yaml_schema_path = APPLICATION_PATH "/../doctrine/schema"
resources.doctrine.generate_models_options.generateTableClasses = true
resources.doctrine.extensions_path = APPLICATION_PATH "/../library/DoctrineExtensions"

Or the following where $application is the instance of Zend_Application:

$application->getBootstrap()->bootstrap( 'doctrine' );

From that, you can use Doctrine to your hearts content!

We also have a Doctrine CLI script which works from the same resource. See:

http://code.google.com/p/vimbadmin/source/browse/trunk/bin/doctrine-cli.php

Open Solutions are pleased to announce the immediate availability of our latest free and open source web application, ViMbAdmin (vim-be-admin). ViMbAdmin is a web based interface which will allow you to manage mailboxes, virtual domains and aliases.

ViMbAdmin is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License version 3, or (at your option) any later version.

ViMbAdmin was entirely funded by Open Solutions and developed by our staff. If you find this application of value, please consider making a donation to our chosen charity.

Do you want to see it in action? We have a live demo which you can access here. You can also browse screenshots by clicking the image on this page.

ViMbAdmin was written in PHP using our own web application framework which includes the Zend Framework, the Doctrine ORM and the Smarty templating system with JQuery on the frontend.

ViMbAdmin is hosted on its own Google Code project page where you can find documentation, browse the source code and access our Subversion repository. We have set up a Google Groups discussion group and you can read our ViMbAdmin blog posts.

ViMbAdmin can work as a slot in replacement for Postfix Admin with a few MySQL ALTER statements.

Features

• Super admin(s) user level with full access;
• Admin(s) user level with access only to assigned domains and their mailboxes and aliases;
• Super admins can create and modify super admins and admins;
• JQuery Datatable throughout for quick in browser searching and pagination;
• Create, modify and purge domains including limited the number of mailboxes and aliases a non-super admin can create per-domain;
• Activate / deactivate admins, domains, mailboxes and aliases at the click of a button;
• Full logging;
• Facility for users (mailbox owners) to change their password;
• Forgotten Password / Password Reset function for admins;
• Very configurable including:
  • set default values for quotas, number of mailboxes and aliases for domain creation;
  • templated welcome and settings email for users;
  • either plain or MD5 mailbox password support;