Startbootstrap-sb-admin-2

This project is maintained by ironsummitmedia

Restoration Instructions for SunOS/Irix:
  1. Shutdown Post.Office </usr>/local/Post.Office shutdown
  2. 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.
  3. -r /usr/local/post.office /tmp/POexecBad3.0
  4. -r /var/spool/mailbox /tmp/POmailboxBad3.0
  5. -r /var/spool/post.office /tmp/POspoolBad3.0
  6. Remove the 3.0 executables: cd /usr/local rm -r Post.Office
  7. Copy the half upgraded versions of your account files. 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 to restore the "first" backup made so that you restore the working prior version of your MTA-Accounts database file: cd </var/spool/>Post.Office/config cp MTA-Accounts MTA-Accounts.bad3.0 cp BTAccounts.i BTAccounts.i.bad3.0 cp BTAccounts.a BTAccounts.a.bad3.0 cp MTA-Accounts.backup.yymmddhhmm MTA-Accounts 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. (The standard permissions for UNIX are listed elsewhere in this FAQ for your review.)
  8. Copy the half upgraded versions of your configuration files. 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 </var/spool/>Post.Office/config For each *.backup file with today’s date and time: cp <ServerModuleName> <ServerModuleName>.bad3.0 cp <ServerModuleName>.backup <ServerModuleName> 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. (The standard permissions for UNIX are listed elsewhere in this FAQ for your review.)
  9. We have written a perl script to help convert your mailbox directories from the new 3.0 structure to the old structure. (Note: You can download perl from the ftp site ntperl.hip.com.) Download from our ftp site a utility called unbucket.pl and run it using the following instructions:
  1. The bucketed mailboxes will be copied back up to the unbucketed structure.
  2. Download your prior version of Post.Office for Solaris (1.9.3 or 2.0) from our web site to a temporary directory.
  3. Uncompress the file you downloaded and expand the resulting archive file to create the Post.Office package (SCOM-MTA) by typing: cd /var/tmp/PO<version> uncompress <packagename>.tar.Z tar xvpf <packagename>.tar
  1. Run the Post.Office installation program: For 1.9.3: /usr/local/Install
For 2.0: /usr/local/InstallPO
  1. 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".
  1. If you are currently using Program Delivery you may need to re-enable that feature by typing:
  2. u+s /usr/local/post.office/local/Program-Deliver
  3. /usr/local/post.office/trusted/NO-PROGRAM-DELIVERIES
Your account information and executables have now been restored to your prior version of Post.Office. After your system is restored and working, please contact. We will evaluate your problem and then assist you with the 3.0 upgrade. 1.9.3, 2.0, 3.0 Only - NT Only - I was able to upgrade successfully to version 3.0, but I want to revert back to my previous version. How can I revert back to the prior version of Post.Office using my last standard, full system backup files from that version? If you made a total backup of your Post.Office system before upgrading (as instructed in the upgrade procedure) you should have copies of the following items: Registry information File system information The instructions that follow will guide you through the reversion process. In summary you will be: - restoring the exectuable of the prior version from our your backups, - restoring configuration and account information from your prior version’s backup - and running a script that will restructure your mailbox directory to the prior version’s structure. These instructions will mean that you will lose any account and configuration changes done in 3.0, but no mail will be lost. Any account and configuration changes that you have done in 3.0 will have to be re-entered after the reversion process is completed. These instructions assume that you named the backup files as suggested. If you selected other names or locations for those files you will need to adjust the instructions accordingly.
  1. Make sure that you are logged in as the Local Administrator of your host. Logging in as the Domain Administrator is not sufficient unless the machine you are using is a Primary Domain Controller.
  2. Shutdown the Post.Office Service:
  3. Panel -> Services -> Post.Office MTA -> Stop
  4. Set permissions to the default permissions for your Post.Office-User using the poperms utility delivered with Post.Office version 3.0:
  1. Back up the 3.0 version of the Post.Office Registry key:
  1. Restore your prior version of the Post.Office Registry key from backup:
  1. Back up the 3.0 Post.Office executables you have now.
  1. Move the Post.Office.dll out of the system directory (WINNT/system32) and rename it (suggested name: 30postoffice.save).
  2. Restore your saved Post.Office executables (the prior version).
  1. Back up the current Post.Office 3.0 configuration information.
  1. Back up the Post.Office 3.0 mailboxes you have now.
  1. We have written a perl script to help convert your mailbox directories from the new 3.0 structure to the old structure. (Note: You can download perl from the ftp site ntperl.hip.com.) Download from our ftp site a utility called unbucket.pl and run it using the following instructions:
  1. If you are restoring to Post.Office version 2.0, you will need to locate the 2.0 version of our poperms utility on our ftp site (ftp ftp.software.com). It can be found by following the path through the 2.0 version/operating system/platform/utilities directories. Run the poperms tool to set permissions back to the default settings. Return to the DOS command line (within the Post.Office executables directory) and type: poperms -a -u
  2. If you are restoring to Post.Office version 1.9.3, you will need to manually verify that your Registry and file system permissions are correct. Please refer to the section of this FAQ titled Permissions and Directory Locations which identifies the proper permission settings for Post.Office v1.9.3.
  3. Startup the Post.Office Service:
  4. Panel -> Services -> Post.Office MTA -> Stop
1.9.3, 2.0, 3.0 Only - UNIX Only - I was able to upgrade successfully to version 3.0 but I want to revert back to my previous version. How can I revert back to the prior version of Post.Office using my last standard, full system backup files from that version?