ProviderTalk RESOURCES - iManagerPro **works with iManager 2.05b on VPSv1 servers! **

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

  • ~/etc/domainmaps file allows server admin to map a user to a domain for email privileges
  • ~/etc/domainmaps file allows server admin to map max forwards and max pop accounts to a user
  • ~/etc/domainmaps file allows server admin to create a default max POP3 quota that will be used for all new users added
  • privileged users can maintain the POP, forwards, and catch-all for their domain by logging into iManager
  • ALL POP3 users can now maintain their own vacation autoreply program through iManagerPro

What does the above mean?

It means that you can now allow your client to add/modify/delete their own email accounts, and vacation autoreplies. 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 specify the maximum amount of disk space the POP accounts will be able to consume. 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 have the most recent version of iManager loaded (if iManager is not loaded, vinstall imanager2).

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

iManagerPro's vacation program makes the assumption that you have address mappings for the pop user.  Email addresses that are caught by the "catchall" will NOT work properly in the  vacation autoreply (if support@precisionpros.com does not have a virtmap entry, and simply falls into the catchall, then, support@precisionpros.com will not work properly in the vacation autoreply).

iManagerPro makes the assumption that every domain will have a catch-all defined for it in the virtmaps file. If you do not typically define catchalls, create an *alias* called trash_mail and map it to the
trash can.

trash_mail: /dev/null   Click to Open Click to Close

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/virtmaps file.

Preparing Your Files:

If you are installing iManagerPro on a server that does not have mail accounts set-up, no changes or preparation is necessary before installing.

If you do not define POP accounts in virtmaps, you will first need to define your server's current POP accounts in the virtmaps file before granting update privileges to your client.

 

  Click to Open Click to Close

If you have email accounts defined on your server, you will need to review and possibly modify your virtmaps file before granting Priviledged User status to your client. If there is more than one email address mapping going to the same POP mail account, iManagerPro will not be able to manage the mailbox. Mapping would need to be completed to allow for one address going to the mailbox and additional addresses routing to the original address.

  Click to Open Click to Close

Installation Instructions for iManagerPro:

Installation is very easy. Upload the imanagerpro.zip file to the root directory on your server and unzip it:

% unzip imanagerpro.zip   Click to Open Click to Close

The files will be extracted to their proper directories. There are 4 files that you will be prompted for permission to overwrite on your server for a first time installation.

The files will be replaced for the following reasons:

~/usr/local/etc/htdocs/imanager/library/imanager.pl
T
his 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/strings/en/main
This will allow iManagerPro to give POP3 users access to the vacation autoreply scripts.

~/usr/local/etc/htdocs/imanager/strings/en/iroot
This will allow iManagerPro to display the POP3, Forwards, and catchall menus scripts.

Unless you have edited any of the 4 files above, it is safe to reply "yes". All other files being unzipped are new files created specifically by iManagerPro. The following is a complete list:

~/etc/domainmaps
~/usr/bin/vacation
~/usr/local/etc/httpd/htdocs/imanager/library/catchall.pl
~/usr/local/etc/httpd/htdocs/imanager/library/forward.pl
~/usr/local/etc/httpd/htdocs/imanager/library/mapmanager.pl
~/usr/local/etc/httpd/htdocs/imanager/library/pop3.pl
~/usr/local/etc/httpd/htdocs/imanager/library/vacation.pl
~/usr/local/etc/httpd/htdocs/imanager/strings/en/forwards
~/usr/local/etc/httpd/htdocs/imanager/strings/en/pop3
~/usr/local/etc/httpd/htdocs/imanager/strings/en/vacation
~/usr/local/etc/httpd/htdocs/imanager/wizards/catchall_edit.cgi
~/usr/local/etc/httpd/htdocs/imanager/wizards/forward_add.cgi
~/usr/local/etc/httpd/htdocs/imanager/wizards/forward_edit.cgi
~/usr/local/etc/httpd/htdocs/imanager/wizards/forward_remove.cgi
~/usr/local/etc/httpd/htdocs/imanager/wizards/forward_view.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/wizards/vacation.cgi
~/usr/local/etc/httpd/htdocs/imanager/wizards/vacationoff.cgi
~/usr/local/etc/httpd/htdocs/imanager/wizards/vacationon.cgi

Unless you have edited either of these files, it is safe to reply "yes". All other files are new files used specifically by iManagerPro.

Defining Privileged Users:

After unzipping imanagerpro.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. The domainmaps file takes on the following format:

user:domain,maxforwards,maxpops,mail disk quota
notice that user and domain are separated with a colon ":"

A user can be associated only with a single domain!

  Click to Open Click to Close

iManagerPro converted to other languages

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

  • English
  • Japanese
    Inportant notice about these files are:
    
    1. Encoding is "EUC-JP" which is best handled by UNIX.
    
    2. Overwrites encoding.pl
    The following line is modified to handle japanese.
    
    Line85:    $g_default_content_type = "text/html; charset=EUC-JP";
    #iso-2022-jp";
    
    3. Overwrites init.pl
    The following lines are modified for Japanization.
    Line23:    $g_defaultlanguage = "jp";
    This is not required since it is not used yet, but just to make sure.
    Line62:    $g_default_content_type = "text/html\; charset=EUC-JP";
    
    4. Adds string files to imanager/strings/jp/
    
  • European Spanish
    1. follow normal imanagerpro installation
    2. unzip imanagerproes.zip file.  The init.pl file will be overwritten with your new default language preferences.
    Files will also be extracted to the ~/htdocs/imanager/strings/es directory.
    

Troubleshooting:

iManagerPro has a bug that doubles the number of blank lines in your ~/etc/virtmaps file each time the file is updated. Make sure that there are no blank lines in your ~/etc/virtmaps file. iManagerPro handles comment lines fine. So, for first time installations, change all blank lines to comment lines (put the pound sign character, #, as the first character on blank lines).
Other problems that may appear include:

  • If files do not have permissions set properly during installation:
    Use the following commands at a telnet prompt to set permissions on the files.
    chmod 755 ~/www/htdocs/imanager/wizards/*.cgi
    chmod 755 ~/usr/bin/vacation
  • If a privileged user is not able to add POP accounts because a message is displayed indicating there are only "root and serverlogin" users in the password file:
    Refer to the MORE HELP button under Defining Priviledged Users
    You must use a HARD RETURN (ENTER KEY) at the end of the last entry in the domainmaps file.
  • If you encounter problems or have questions about iManagerPro, please send an email to the iserver 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