[quote user="janco admin"]Hi Everyone! Just to give a little detail on how i have things set up first. I am running mercury 4.72 on a windows server running 2003 R2. From there it drops the email into seperate folders. I have pegasus setup on the client workstations so when they log in there reading the mail from the server. Ok heres my issue. I have an account on the server named "neault" now when that user signs into pegasus it just crashes. Now if i try to open that same folder from any other workstation it also crashes. I then tried previous versions of pegasus and 4.41 will allow that account to open up and work flawlessly. I know that was the last version that was written in borlen c. I have serveral other accounts that were created before that one and they work just fine. If anyone has an idea that would be a big help.[/quote]
Is Pegasus Mail installed on each workstation or is it installed on a server.
If you can run Pegasus Mail as other users but not as "neault" then there is something in the configuration files of the "neault" mailbox folder that is causing the crash. I always first check the PMAIL.INI. (Point of note: PMAIL.INI holds much of the configuration for that mailbox (Pegasus user) and gets updated with each run of Pegasus. Accessing the mailbox with different versions of Pegasus Mail without having a dedicated PMAIL.INI file for each version can cause problems. Refer to the help topic "Command line options" -Y switch for info on how to do this.)
To check the PMAIL.INi file make sure Pegasus Mail is not running anywhere as the "neault" user which in your case sounds like a non issue. Make a copy of the neault
mailbox folder for backup (insurance) purposes. Rename the PMAIL.INI
file in the neault mailbox folder to something like PMAIL_INI.RENAMED. When
you start Pegasus Mail as user neault a new PMAIL.INI file will be
created. Note that most configuration settings will be gone but that's
ok because the purpose of this test is just to see if Pegasus Mail will start up with the new PMAIL.INI file. IIRC, on restart you will
be prompted to provide some configuration settings. Skip these if you
can as your goal is to simply get Pegasus Mail fully opened.
If it opens without the crash you know the
problem was with the old PMAIL.INI file. My suggestion is to not try to
identify the problem in the pmail.ini file but to reconfigure the "neault" user from scratch. You can use a
text editor to view/print the original PMAIL.INI file which you can use
for reference.
If it Pegasus Mail still crashes, delete
the new PMAIL.INI file (if one ever got created) then rename the PMAIL_INI.RENAMED file back
to PMAIL.INI. This will bring you back to where you were before the
test. Report back here and we'll try to figure out the next step.
<p>[quote user="janco admin"]Hi Everyone! Just to give a little detail on how i have things set up first. I am running mercury 4.72 on a windows server running 2003 R2. From there it drops the email into seperate folders. I have pegasus setup on the client workstations so when they log in there reading the mail from the server. Ok heres my issue. I have an account on the server named "neault" now when that user signs into pegasus it just crashes. Now if i try to open that same folder from any other workstation it also crashes. I then tried previous versions of pegasus and 4.41 will allow that account to open up and work flawlessly. I know that was the last version that was written in borlen c. I have serveral other accounts that were created before that one and they work just fine. If anyone has an idea that would be a big help.[/quote]</p><p>Is Pegasus Mail installed on each workstation or is it installed on a server.</p><p>If you can run Pegasus Mail as other users but not as "neault" then there is something in the configuration files of the "neault" mailbox folder that is causing the crash.&nbsp; I always first check the PMAIL.INI.&nbsp; (Point of note:&nbsp; PMAIL.INI holds much of the configuration for that mailbox (Pegasus user) and gets updated with each run of Pegasus.&nbsp; Accessing the mailbox with different versions of Pegasus Mail without having a dedicated PMAIL.INI file for each version can cause problems.&nbsp; Refer to the help topic "Command line options" -Y switch for info on how to do this.)
</p><p>&nbsp;To check the PMAIL.INi file make sure Pegasus Mail is not running anywhere as the "neault" user which in your case sounds like a non issue. &nbsp; Make a copy of the neault
mailbox folder for backup (insurance) purposes.&nbsp; Rename the PMAIL.INI
file in the neault mailbox folder to something like PMAIL_INI.RENAMED.&nbsp; When
you start Pegasus Mail as user neault a new PMAIL.INI file will be
created.&nbsp; Note that most configuration settings will be gone but that's
ok because the purpose of this test is just to see if Pegasus Mail will start up with the new PMAIL.INI file.&nbsp; IIRC, on restart you will
be prompted to provide some configuration settings.&nbsp; Skip these if you
can as your goal is to simply get Pegasus Mail fully opened.&nbsp;</p><p>If it opens without the crash you know the
problem was with the old PMAIL.INI file.&nbsp; My suggestion is to not try to
identify the problem in the pmail.ini file but to reconfigure the "neault" user from scratch.&nbsp; You can use a
text editor to view/print the original PMAIL.INI file which you can use
for reference.
</p><p>If it Pegasus Mail still crashes, delete
the new PMAIL.INI file (if one ever got created) then rename the PMAIL_INI.RENAMED file back
to PMAIL.INI.&nbsp; This will bring you back to where you were before the
test.&nbsp; Report back here and we'll try to figure out the next step.</p><p>
</p>