**works with iManager 2.05b on VPSv1 servers!
Increase functionality of iManager on your FreeBSD v1 Virtual Server with 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.
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 email@example.com does not have a virtmap entry, and simply falls into the catchall, then, firstname.lastname@example.org will not work properly in the vacation autoreply).
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
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.
Installation Instructions for iManagerPro:
Installation is very easy. Upload the imanagerpro.zip file to the root directory on your server and unzip it:
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
The files will be replaced for the following reasons:
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:
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:
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).
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).