Startbootstrap-scrolling-nav

This project is maintained by ironsummitmedia

Revert Instructions for Solaris: 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: The instructions that follow will guide you through the reversion process. In summary you will be: - restoring the exectuable of the prior version from your backups or with packadd, - restoring configuration and account information from your prior version’s backups - 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. If Post.Office is running please shut it down by typing: </opt>/Post.Office shutdown
  2. Copy the existing, half-upgraded versions of the directories and files listed above to another location before attempting restoration.
  3. Restore the following sub-directory and all its file on top of your 3.0 versions from your prior version backups. This directory contains your account and configuration information:
  4. 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.)
  5. 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. Remove the 3.0 executables with pkgrm: pkgrm SCOM-MTA
  3. Download the version of Post.Office for Solaris that you were running prior to the upgrade (1.9.3 or 2.0) from our web site to a temporary directory.
  4. <packagename>.tar.Z
  5. 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 <packgename>.tar
  6. From the location in which you stored it, install the package by typing: pkgadd -d . SCOM-MTA Caution: The upgrade program will ask if you wish to change configuration information. You should answer "no".
  7. If you are currently using Program Delivery you may need to re-enable that feature by typing: chmod u+s /opt/post.office/local/Program-Deliver rm /opt/post.office/trusted/NO-PROGRAM-DELIVERIES
  8. Run the Post.Office configuration program:
For 1.9.3: /opt/post.office/Install For 2.0: /opt/post.office/Setup This will revert your account information and upgrade your executables back to your prior version of Post.Office. Revert Instructions for SunOS/Irix: The easiest way to restore is if you have made a total backup of your Post.Office including: Assuming you took that precaution (as instructed in the README.TXT and RELNOTES.TXT files), please:
  1. If Post.Office is running shut it down by typing: </usr>/local/Post.Office shutdown
  2. Copy the existing, half-upgraded versions of the directories and files listed above to another location before attempting restoration.
  3. Restore the following sub-directory and all its file on top of your 3.0 versions from your prior version backups. This directory contains your account and configuration information:
  4. 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.)
  5. Restore the file system directories containing your prior version’s Post.Office Executables on top of the 3.0 executables.
  6. 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.
Note: You might run into permission problems if you didn’t backup or restore with the original permissions. The standard permissions for UNIX are listed elsewhere in this FAQ for your review. Once you are restored and your permissions are properly set, start the Post.Office server (i.e. </usr/local/>Post.Office/Post.Office startup). 1.9.3 and 2.0 Only - NT Only - My system crashed. How do I restore Post.Office from my standard, full system backup files?
  1. Once you have re-installed NT, you must re-install Post.Office on the machine by: - Running Setup - Accessing Post.Office as "Postmaster" to complete the Installation Wrap-up Form
  2. After Post.Office has been re-installed, stop the Post.Office service.
  3. Using REGEDT32 take ownership of the MTA-Accounts key again and restore the key from disk.
  4. Assign your post.office user with Full Control Rights over the MTA-Accounts directory and remove the Everyone Group. Make this change recursive by selecting "Replace Permissions on Existing Subkeys"!
  5. Copy the PostOfficeDir directory from backup over the new PostOfficeDir directory. Assign "Full Control" Rights to your post.office-user, "Read" Rights to Administrators, and remove Everyone recursively down all directories and files! <\winnt35\system32>\spool\post.office\ Post.Office-user Full Control Administrator Read <\winnt35\system32>\spool\post.office \config\ <Same> (configuration files such as auto-replies and finger information) <\winnt35\system32>\spool\post.office \config\<subdirectories> <Same> <\winnt35\system32>\spool\post.office\control\ <Same> (control files of queued messages) <\winnt35\system32>\spool\post.office\deferred\ <Same> (control files of messages deferred or in error) <\winnt35\system32>\spool\post.office\messages\ <Same> (body and header files for messages that are queued or deferred)
  6. Assign "Change" Rights to Administrators in the PostOfficeDir/log directory recursively down all directories and files! <\winnt35\system32>\spool\post.office\log\ Post.Office-user Full Control (log files) Administrator Change
  7. Copy the mailbox directory from backup over the new MailboxDir directory. Assign your post.office-user with Full Control Rights and remove Everyone recursively down all directories and files! For example: <\winnt35\system32>\spool\post.office\mailbox\ Post.Office-user Full Control <\winnt35\system32>\spool\post.office\mailbox\Users_Real_Name_1\ <Same> <\winnt35\system32>\spool\post.office\mailbox\Users_Real_Name_1\In <Same> 199609241202…@postofficehostname.domainname.1
  8. Re-start the Post.Office service.