Home Contact Us Search

[ Order a Server ] [ Server Support ]


[ Getting Started ] [ Server Help ] [ Add on Help ] [ Solution ] [ Trouble Shooting ]

PLEASE NOTE, THIS IS VERY OLD ARCHIVE INFORMATION AND MAY NOT FUNCTION ON NEW SERVERS

iManagerPRO

Increase functionality of iManager on your Virtual Server with iManagerPro.

You must first have iManager installed before upgrading to 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.

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

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.

 

If you have email accounts defined on your server, you will need to review and possibly modify your virtmaps file before granting Privileged 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.

Installation Instructions for iManagerPro:

Click to Download

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

% unzip imanagerpro.zip

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

The first 3 files will be replaced for the following reasons:

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

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

~/www/htdocs/imanager/strings/en/profile
This will allow iManagerPro to give POP3 users access to the vacation autoreply scripts.

The next 4 files are replaced simply to update the "about" information of iManagerPro:

~/usr/local/etc/httpd/htdocs/imanager/VERSION 
~/usr/local/etc/httpd/htdocs/imanager/strings/en/ABOUT 
~/usr/local/etc/httpd/htdocs/imanager/strings/en/main 
~/usr/local/etc/httpd/htdocs/imanager/library/info.pl 

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!

Troubleshooting:

There are no known issues with iManagerPro. Possible problems that may appear include:

  • If files do not have permissions set during installation:
    Use the following commands at a telnet prompt to set permissions on the files.
    cd ~/www/htdocs/imanager/wizards
    chmod 755 *.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 Privileged Users
    You must use a HARD RETURN (ENTER KEY) at the end of the last entry in the domainmaps file.
  

PLEASE NOTE, THIS IS OLD ARCHIVE INFORMATION AND MAY NOT FUNCTION ON NEW SERVERS