Workaround for Postmaster web log on problems

I am very sorry for all of the inconvenience you've experienced.

We have duplicated the problem and we are looking into this. Here is a work around that you can try:

First, log in to Post.Office with the e-mail address of:

Postmaster@xxxxxxxxxxxxxxxxxxxxxxx

Second, modify the Postmaster account. Go to the account data form for the Postmaster and check the box:

POP3/IMAP4 Delivery:
Add a POP3 User name in the  POP3/IMAP4 Login Name: field.

Remove the entry from the Required Delivery Information:

Enter Forwarding Addresses for Designated Postmasters Below:

box.

Hit the submit button.

Go back to the Postmaster's Account Data Form (List of Accounts/Administrative Accounts) and modify the email address of the Postmaster to the proper address.

Postmaster@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Hit the submit button.

Sue

On Friday, November 22, 2002, at 09:51 AM, Charles Ying wrote:

Help! this has seemed to be getting worse.
I'm running 714 and I haven't had this problem before this version.  I'm not
able to log on to the web interface as postmaster.  It logs me on as a
general user, not with the postmaster privileges.
By Trial and Error, after doing it 10 different times. This is what I figured out. The manual tells you that if you want myself@xxxxxxxxxx to be "postmaster", all you have to do is to put that email address (and any others) into the "Enter forwarding Address for Designated Postmaster below" box in the Postmaster Account form. That works. But there is a catch!

Say you have changed the default root@xxxxxxxxxxxxxxx to me@xxxxxxxxxxx Post.Office will work fine UNTIL you re-install PO. When you do that, even if you are re-installing the same version of PO, the installer screws up your Postmaster settings. YOU MUST RUN THE POST.OFFICE APP again. When you do, you will see some screwy entry in the Postmaster field. It would be something like me@xxxxxxxxxxxxxx@mail.domain.comanyoneelse@xxxxxxxxxx (if you have anyoneelse@xxxxxxxxxx also assigned as a Postmaster). If you don't reset this field in the Post.Office app AND reboot. Then you will see the symptoms you describe.

Also, installation of Post.Office resets the Port # if you had changed it from its default (say to port 80) as well as the "Address Completion Domain" in the Mail Routing Form. If you had change that to "domain.com" instead of the default "mail.domain.com", re-installation will reset that back to mail.domain.com. This will throw you off if when you connect to administer PO, you are used to just entering your name in front of the @ and your password to connect. Postmaster account ignores any alias settings. So if PO thinks Postmaster is me@xxxxxxxxxx, I cannot try to log in as me@xxxxxxxxxxxxxxxx

Again, feel free to play with this and figure out the strange mind of the programmer who wrote this code. It must have been very late in the evening and he or she was really tired. Very sloppy stuff. Makes it tough for upgrades particularly since Tenon doesn't include any detail instructions for upgrades. When I bug Sue for such instructions, she did send me a recipe which I tried to follow to the letter and it did not work. So it is up to each of us to do our own trial and error to figure out the best recipe for upgrading a Post.Office with our own settings. Asking Tenon will only get you more confused.

Finding the original programmer at Software.com to explain what he or she was thinking would be great. I think I will try to track down someone at openwave (they bought software.com) and find the programmer responsible for all of our miseries.

Charles Ying