Restoration Instructions for SunOS/Irix:
- Shutdown Post.Office
/local/Post.Office shutdown - For safety’s sake please copy the existing, half upgraded versions of the mailbox directories and the executables directory to another location before attempting restoration.
- Remove the 2.0 executables:
cd /usr/local
rm -r Post.Office - Copy the original file and then replace the half upgraded version of your MTA-Accounts file with the backup of the file made during upgrade. If you attempted to run the upgrade more that once, make sure that you restore the “first” backup that was made so that you restore the working 1.9.3b version of your MTA-Accounts database file:
cd Post.Office/config
cp MTA-Accounts MTA-Accounts.bad2.0
cp MTA-Accounts.bak.yymmddhhmm MTA-AccountsNote: You might run into ownership or permission problems if you didn’t back up or restore with the original permissions. It’s possible that executing a chown on the copied files and assigning ownership to your post.office user (mta) will be enough. (The standard permissions for UNIX are listed elsewhere in this FAQ for your review.) - Copy the original file and then replace the half upgraded version of your configuration files with the backup of the files made during the upgrade. You might have old ones there that you DON”T want to use, so only use the *.backup files with today’s date:
cd Post.Office/configFor each *.backup file with today’s date:cp
.bad2.0
cp.backup Note: You might run into ownership or permission problems if you didn’t back up or restore with the original permissions. It’s possible that executing a chown on the copied files and assigning ownership to your post.office user (mta) will be enough. (Thestandard permissions for UNIX are listed elsewhere in this FAQ for your review.)
- Download the 1.9.3b version of Post.Office for Solaris from our web site into a temporary directory.
- Uncompress the file you downloaded, expand the resulting archive file, and then change to the newly created directory by typing:
cd /var/tmp/PO1.9.3b
uncompress post_office--v1_9_3b_tar.Z
tar xvpf post_office--v1_9_3b_tar
cd Post.Office - Upgrade Post.Office version 1.9.3b by typing.
- Run the Post.Office configuration program:
./Install
- the installation program is finished, it will re-start Post.Office for you.
Caution: The upgrade program will ask if you wish to change configuration information. You should answer “no”.
- If you are currently using Program Delivery you will need to re-enable that feature
by typing: - u+s /usr/local/post.office/local/Program-Deliver
- /usr/local/post.office/trusted/NO-PROGRAM-DELIVERIES
Caution: There are security issues associated with the use of Program Delivery. Please read Appendix G of the Post.Office manual to ensure you understand those issues before enabling this feature.
Your account information and executables have now been restored to the 1.9.3b version of Post.Office.
4.4 Locating Post.Office
NT only: Can I move Post.Office to a new machine and transfer all my accounts with it ?
In summary: You need to shutdown the Post.Office service on your old host; save the MTA-accounts registry key, the mailbox directory and post.office directories so they can be moved to the new machine; install Post.Office from scratch on the new machine; then restore the MTA-Accounts registry key, mailbox directory and post.office directory from your old host. You must understand how NT permissions work to perform these steps successfully.
These instructions will only work if you are moving between the same Post.Office versions (i.e. v1.9.3 to v1.9.3) on the same platform (i.e. NT-Intel to NT-Intel, NT-Mips to NT-Mips, etc.). If you want to upgrade, please do that either before or after you move Post.Office.
Please follow the steps below:
ON YOUR OLD HOST:
- Login as the Local NT Administrator of that host (i.e. Administrator).
- Stop/Shutdown your Post.Office Service. (Control Panel -> Services -> Post.Office MTA -> Stop)
- Change the permissions recursively and save the Registry Key MTA-Accounts
– Run regedt32 and open the window for HKEY_LOCAL_MACHINE
– Open software/software.com/post.office
– Highlight the MTA-Accounts Key
– Take ownership of the key (Security -> Owners)
– Change the permissions, add the special NT group “Everyone” with full control
permissions. Make this change recursive by selecting “(X)Replace P - ermissions on
Existing Sub-keys”.! (Security -> Permissions)Please Note: NT doesn’t let you take ownership recursively in the Registry Editor,
so you might have to take ownership of every sub-directory below Software.com,
before the system will let you change permissions recursively.– Save the Registry Key (Registry -> Save Key)
- Change permissions recursively and save your Post.Office directory. If you are using version 1.9.3, you can check your Post.Office icon in Control Panel to see what your PostOffice Directory is defined as, by default it is “\winnt35\system32\spool\post.office”.
– Run File Manager and highlight your post.office directory.
– Take ownership of the directory and answer “yes” when it asks you if you want to change sub-directories and files as well. (Security -> Owner)
– Change the permissions and add the special NT group “Everyone” with Full Control permissions. Specify that you want to (X)Replace permissions on all sub-directories, (X)Replace permissions on existing files, then click OK. (Security -> Permissions)
– Save this directory. - Change permissions recursively and save your Mailbox directory. If you are using version 1.9.3, you can check your Post.Office icon in Control Panel to see what your Mailbox Directory is defined as, by default it is “\winnt35\system32\spool\post.office\mailbox”.
– Run File Manager and highlight your Mailbox directory.
– Take ownership of the directory and answer “yes” when it asks you if you want to change sub-directories and files as well. (Security -> Owner)
– Change the permissions and add the special NT group “Everyone” with Full Control permissions. Specify that you want to (X)Replace permissions on all sub-directories, (X)Replace permissions on existing files, then click OK. (Security -> Permissions)
– Save this directory. - Start/Startup the Post.Office MTA Service (Control Panel -> Services -> Post.Office MTA -> Start)
ON YOUR NEW HOST:
- As a local Administrator of your NT host, (i.e. Administrator), complete a brand new installation of Post.Office on the new machine. Remember, this includes two steps;
-running Setup
-and then accessing Post.Office as “Postmaster” to complete the Installation Wrap-up Forms via your Web Browser. - Stop/Shutdown your Post.Office Service. (Control Panel -> Services -> Post.Office MTA -> Stop)
- Take ownership of the new MTA-Accounts key so you are allowed to restore the saved key.
– Run regedt32 and open the window for HKEY_LOCAL_MACHINE
– Open software/software.com/post.office
– Highlight the MTA-Accounts Key
– Take ownership of the key (Security -> Owners)
– Change the permissions, modify the Administrator user with Full Control permissions. Make this change recursive by selecting “(X)Replace Permissions on Existing Sub-keys”.! (Security -> Permissions)Please Note: NT doesn’t let you take ownership recursively in the Registry Editor, so you might have to take ownership of every sub-directory below Software.com, before the system will let you change permissions recursively.– Restore the saved key. (Registry – Restore)
Please Note: NT doesn’t let you take ownership recursively in the Registry Editor, so you might have to take ownership of every sub-directory below Software.com, before the system will let you change permissions recursively.
- Change the permissions recursively to restore permissions to the default values for the Registry Key:
– Change permissions, remove the special NT Group “Everyone”, add your Post.Office -user with Full Control rights, add Administrator user with Read permissions. Make this change recursive by selecting ” (X)Replace Permissions on Existing Sub-keys”! (Security -> Permissions) - Copy the PostOffice directory from backup over the new PostOffice directory. Fix permissions recursively back to the default values
– Run File Manager and highlight your post.office directory.
– Take ownership of the directory and answer “yes” when it asks you if you want to change sub-directories and files as well. (Security -> Owner)
– Change the permissions, modify the Administrator user with Full Control permissions. Specify that you want to (X)Replace permissions on all sub-directories, (X)Replace permissions on existing files, then click OK. (Security -> Permissions)
– Replace the current Post.Office directory with the saved directory.
– Change permissions, remove the special NT Group “Everyone”, add your
Post.Office-user with “Full Control” Rights, add Administrator with Read rights and make this change recursive by selecting “(X)Replace Permissions on Sub-Directories and (X) Replace Permissions on Existing Files”. (Security -> Permissions)When finished, the Post.Office user should have Full Control, and the Administrator should have Read Only permission over the following directory, its subdirectories and files: <\winnt35\system32>\spool\post.office\ - Assign “Change” Rights to Administrators in the PostOfficeDir/log directory and make this change recursive by selecting “(X)Replace Permissions on Sub-Directories and (X) Replace Permissions on Existing Files”. (Security -> Permissions)When finished, the Post.Office user should have Full Control, and the Administrator should have Change permission over the following directory, its subdirectories and files: <\winnt35\system32>\spool\post.office\log\
- Copy the mailbox directory from backup over the new MailboxDir directory. Assign your post.office-user with Full Control Rights and remove Everyone. Make this change recursive by selecting “(X)Replace Permissions on Sub-Directories and (X) Replace Permissions on Existing Files”. (Security -> Permissions)When finished, the Post.Office user should have Full Control over the following directory, its subdirectories and files: <\winnt35\system32>\spool\post.office\mailbox\
- Start the service.
Remember, because you have restored account information (including your [email protected] account) from your old host to your new host, you will have to sign on with your original “Postmaster” e-mail address and “original” Postmaster password. Then you will have to modify your restored account information to match the new configuration of your new host.
If your host name or domainname is different on your new host you will need to:
- edit the email address of your Postmaster account to refer to the newpostofficehostname.yourdomainname address.
- change the e-mail addresses for any user accounts that have the host name defined within them or who’s domainname is also changing. If you are implementing some form of “Host Name Hiding” you will probably not need to change all your users unless they are still referencing the host name in one of their email-addresses.
- check your Postmaster account and change any of your forwardee’s to have the corrected address
- check your Post.Office Address Completion Domain or your Local Domain fields, you may need to change your host name there as well.
- don’t forget you’ll also need to have your DNS revised to point your domain’s mail (MX record) to the new name hostname.domainname and you will need an Address Record (A record) for that host name as well.
- If your mail clients are connecting to Post.Office SMTP and POP3 servers via the server name hostname.domainname you will need to change your clients to point to newhostname.domainname.
If your TCP/IP address is different on your new host, you will need to:
- -change the Internet addresses for any accounts that have the tcp/ip address defined within them. Three of these accounts are special accounts. Display a list of all your user’s from the Post.Office configuration forms. At the end of the list are the Special Accounts. They list the Account Manager, Configuration Manager Error Handler. Modify the e-mail addresses on these accounts to reference your new TCP/IP address instead of the old.
- don’t forget you need to have your DNS revised to point your domain’s A record for that host. It now needs to point to the new tcp/ip address.