Increase functionality of iManager on your FreeBSD v2 Virtual Server with iManagerPro.

• Server Admin user can give a "privileged" user the ability to maintain the email accounts for (only) his domain. Currently, this is done through the /etc/domainmaps file.
• Server Admin user can assign a "privileged" user's max pop accounts.
• Server Admin user can assign a "privileged" user's max forward accounts.
• Server Admin user can assign a "privileged" user's max mail quota. Unless activated, the mail quota is unlimited.
• Server Admin user can assign a "privileged" user's optional login prefix. Activating this feature automatically creates a unique and consistent POP login id for each new POP account created by the privileged user. The script takes the login prefix, and appends an incremented number to it each time a new POP account is activated.
• Server Admin user can assign a "privileged" user's login group. Unless activated, the login group will be the same as the POP userid.
• Server Admin user can update /etc/domainmaps file through a link in iManager.
• Server Admin user can translate iManagerPro easily to any other languages by translating the strings/en/imanagerpro file.
• iManagerPro privileged user has link in iManager leading them to the iManagerPro 'Maintain E-mail Accounts' scripts.
• Privileged user can view, add, edit, and remove POP3 and Forwards based on the limits set by the Admin.
• Entries by the privileged user in the virtmap file are automatically grouped together. This means that all entries for a subhost will be grouped next to each other in the virtmaps file.
• Catchall is automatically created and defaulted to the "trash_mail" alias with first POP addition. Privileged user has ability to modify the catchall; but, cannot delete it. This ensures that mail for the privileged user's domain is not directed to another subhost on the server.
• Privileged user is prevented from deleting self.
  
  
New features in iManagerPro for iManager 2.12.1


• New for this release is the ability for a single domain admin (trying to use new CPX language here) to administer multiple domains. Just make separate entries using the same userid for each line. For example, to give 'mark' the ability to manage both serverpros.com and precisionpros.com, just add two entries in the /etc/domainmaps file like this:
  
  mark:serverpros.com,20,10,3,server_?,
  mark:precisionpros.com,20,10,3,precise_?,
  

  When mark logs into iManagerPro, he will now have the option to update the email accounts for either of the domains.
  
  

New features in iManagerPro for iManager 2.12


• In the /etc/domainmaps file, the loginPrefix can now include a '?' giving the privileged user the ability to append to the end of the loginPrefix when creating POP3 userids. For example,if I put imanager_? as the loginPrefix, then all userid's that the admin creates will start with imanager_ and end with whatever the admin enters for the userid (for example, imanager_mark, imanager_john, imanager_brad, etc.). You also retain the ability to define a loginPrefix without the ? which will cause userids to be created automatically by using the loginPrefix and an incremented number (for example, imanager1, imanager2, imanager3, etc.).
• FTP users can now manage htaccess style password protection on their web directories. FTP users can click on the 'file manager' link and traverse to the web directory they would like to password protect. They can enable/disable protection, and add/delete users.
• Disk usage is calculated and displayed when in 'view all' mode for POP3 users so that the admin (privileged user) can quickly and easily see usage for all POP users. Any user who is using more than 80% of their capacity is shown in bold red.
• Fixed bug that allowed privileged user to create more POP accounts than they should have.
• Fixed bug in how user profile was displayed in single user mode.

New features in iManagerPro for iManager 2.12.4

• Added 'vinstall' setup with complete copy of iManager 2.12.4. This will allow users to revert to latest stable version of iManagerPro - even with updates to iManager.
• Fixed bug that made the user_pref file owned by root.
• Fixed bug to make cgi scripts have proper ownership and privileges.

What does the above mean?

It means that you can now allow your client to add/modify/delete their own email accounts. As the Server Admin, you will define how many pop accounts and mail forwards that the client will be able to create (by making updates to the /etc/domainmaps file). You will also be able to optionally specify the maximum amount of disk space the POP accounts will be able to consume, and to create a unique login prefix for each privileged user. The client will only have update privileges for their domain, they will not have visibility to anyone else's email.

Assumptions Made by the iManager Add-on:

iManagerPro makes the assumption that you are using the most recent version of sendmail loaded (if the most recent version of sendmail is not loaded, vinstall sendmail).

iManagerPro makes the assumption that every domain will have a catch-all defined for it in the /etc/mail/virtusertable file. If you do not typically define catchalls, iManagerPro will set up a "trash_mail" catchall for you the first time the domain admin creates an email address. Undefined catchalls will be mapped to a trash_mail alias. Setup an alias to have trash_mail go to the trash:

trash_mail: /dev/null

iManagerPro will map unwanted catchall email to this default address (which will in turn, send it to the trash).

All new POP accounts will be mapped in the /etc/mail/virtusertable file.

Preparing Your Files:

If you are installing iManagerPro on a server that does not have mail accounts set-up, you must first initiate the virtusertable. You can do this by logging into imanager as the admin user, and creating a virtusertable entry (it can be a bogus one, or a valid one, it does not matter. The point is simply that there must be at least one entry before iManagerPro will work).

If you are installing iManagerPro on a server that already has email addresses defined, and you do not normally define POP accounts in virtusertable, you will first need to define your server's current POP accounts in the virtusertable file before granting update privileges to your client.

Installation Instructions for iManagerPro:

Installation is a very easy 3 step procedure - copy the imanagerproV2.zip file to your server, unzip the file and run 'vinstall imanagerpro'.

1. Logged on as root, Upload the imanagerproV2.zip file to the / directory on your server.

2. Unzip imanagerproV2.zip

There are 3 files that will be unzipped onto your server:

- imanagerproV2.tar - this is a complete copy of iManager 2.12.4 along with all iManagerPro files.
- imanagerpro.install - this is the imanagerpro vinstall program
- domainmaps - this is the domainmaps file (if you already have a domainmaps file - do NOT overwrite your old file)

3. run the vinstall program - 'vinstall imanagerpro'

This will untar iManager 2.12.4 along with all iManagerPro files and set proper permissions and ownership. iManagerPro modifies the following iManager files:

/usr/local/etc/htdocs/imanager/library/imanager.pl
This will cause a new menu item to appear for privileged users accessing the iManagerPro program.

/usr/local/etc/htdocs/imanager/library/passwd.pl
This will allow iManagerPro to compare the server's users with the domainmaps file.

/usr/local/etc/htdocs/imanager/library/init.pl
This will give iManagerPro permission to update virtusertable and passwd files

/usr/local/etc/htdocs/imanager/library/iroot.pl
This will allow iManagerPro to edit the /etc/domainmaps file.

/usr/local/etc/htdocs/imanager/library/fm_browse.pl
This will allow iManagerPro to password protect web directories.

/usr/local/etc/htdocs/imanager/library/fm_util.pl
This will allow iManagerPro to password protect web directories.

Unless you have edited any of the files above, it is safe to allow them to be overwritten. All other files being loaded are new files created specifically by iManagerPro

  usr/local/etc/httpd/htdocs/imanager/library/fm_protect.pl
  usr/local/etc/httpd/htdocs/imanager/library/Apache/Htpasswd.pm
  usr/local/etc/httpd/htdocs/imanager/library/forwards.pl
  usr/local/etc/httpd/htdocs/imanager/library/mapmanager.pl
  usr/local/etc/httpd/htdocs/imanager/library/ipro.pl
  usr/local/etc/httpd/htdocs/imanager/library/pop3.pl
  usr/local/etc/httpd/htdocs/imanager/wizards/fm_protect.cgi
  usr/local/etc/httpd/htdocs/imanager/wizards/forwards_add.cgi
  usr/local/etc/httpd/htdocs/imanager/wizards/forwards_edit.cgi
  usr/local/etc/httpd/htdocs/imanager/wizards/forwards_remove.cgi
  usr/local/etc/httpd/htdocs/imanager/wizards/forwards_view.cgi
  usr/local/etc/httpd/htdocs/imanager/wizards/ipro.cgi
  usr/local/etc/httpd/htdocs/imanager/wizards/mapmanager.cgi
  usr/local/etc/httpd/htdocs/imanager/wizards/pop3_add.cgi
  usr/local/etc/httpd/htdocs/imanager/wizards/pop3_edit.cgi
  usr/local/etc/httpd/htdocs/imanager/wizards/pop3_remove.cgi
  usr/local/etc/httpd/htdocs/imanager/wizards/pop3_view.cgi
  usr/local/etc/httpd/htdocs/imanager/strings/en/imanagerpro
  etc/domainmaps

Defining Privileged Users:

After unzipping imanagerproV2.zip, edit the new /etc/domainmaps file, so you can map a privileged user to a domain name, and assign quotas for the number of forwards and pops that the user will be able to maintain for their domain. You can edit the file directly through iManager, or through any text editor. The domainmaps file takes on the following format:

user:domain,maxForwards,maxPOPS,(optional)mailQuota,(optional)loginPrefix,(optional)loginGroup notice that user and domain are separated with a colon ":" A user can now be associated with multiple domains!

iManagerPro converted to other languages

iManagerPro can easily be converted to other languages by translating the /imanager/strings/en/imanagerpro file.

Currently, the following languages are supported by iManager (please let us know if you can convert iManagerPro to other languages).

• English
• Japanese (EUC) after installing iManagerPro, save this file as /imanager/strings/ja/imanagerpo (drop the .ja extension from the filename). Thanks to Manabu Onoue for the translation!

  Troubleshooting:

  • If you encounter problems or have questions about iManagerPro, please send an email to the VPS2 mailing list on ProviderTalk, or email support@precisionpros.com

   

Home | About Us | FAQ | Resources | Contact Us

---

© 2000 - 2002 ProviderTalk, a PrecisionPros Network site
6543 East Omega Street, Mesa, AZ 85215