migration

The main differences between Christoph Haas' setup and Mailfix module is that the latter uses an additional Postfix patch in order to provide quota support. This feature is not mandatory for this module to work, meaning that if you're not interested in quota management, then there is no need to install such patch, and no need for Postfix related directives (virtual_mailbox_limit_maps, virtual_mailbox_limit_override, virtual_maildir_limit_message and virtual_overquota_bounce).

The Postfix integration relies on database and file system settings.

For the database part, Mailfix uses standard Drupal user settings to provide mailboxes. For instance, Haas' configuration files point to mailserver database, whether Postfix under Mailfix module control points to Drupal database (let's call it drupal). In other words, if you already have some mapping in place between Drupal users and Postfix users (according to Haas' tutorial), the Mailfix module will create the appropriate database records for every registered mail domain and related users (the reason being that Mailfix uses Drupal's email field to configure them).

In case you don't have such mapping in place, meaning that your mail users don't match your Drupal users, then you will need to import your existing mail users into Drupal. There is a 5.x module at http://drupal.org/project/user_import, and probably others for 6.x.

Now, if you have aliasing in place, the Mailfix module provides "forward" support (same thing, just different names). But you will have to migrate these by hand. For instance, in Haas' database design the virtual_aliases table stores this information, one record per mapping. In Mailfix module this information is stored in mailfix_users table, specifically in forward field, which stores those mappings as comma separated values.

For the file system settings, which are mostly users and permissions issues, both configurations are very much alike, and there should be no need for changes.

HTH,

A. Saavedra

No additional info was provided nor requested. Thus we close this ticket.