Problem with Pegasus 4.41 on Home Network

posted Aug 22 '08 at 9:18 pm

What email address do you send the reply to?

None, I copy and paste the text into a 'quick reply' here.

<blockquote>What email address do you send the reply to? </blockquote>None, I copy and paste the text into a 'quick reply' here.&nbsp;

StanH

posted Aug 15 '08 at 8:04 am

(I also posted this problem on the Newsgroup:
comp.mail.pegasus-mail.ms-windows)

I updated Pegasus 4.21b to v4.41 on a Windows 98 PC. No problem.

The problem is running Pegasus from another PC over my home network. Recent emails are missing. Nothing from 2008. Here are the counts of new mail in the toolbar at the bottom of screen. (But all folders are affected similarly.)

#1 PC with Pegasus v4.41 installed: 967 new, Windows 98SE.
#2 PC connected to #1 by ethernet: 919 new, Windows XP Pro.
#3 PC connected to #1 by wireless: 1191 new, Windows XP Home.

Pegasus is installed on #1 PC in D:\Program Files\Pmail\winpm-32.exe

Mailbox is installed on #1 PC in E:\Mail\Pmail\

On Pegasus's first startup over the network it displayed this
message-box:

"Pegasus Mail has detected that you have previously used an older
versin on this mail box"
[x] Show me what's new [continue]

On #1 PC with the V4.41 I downloaded 38 emails from POP3 and moved them to a newly-created folder. Everything seems normal on #1, but
over on #2 PC & #3 PC I can't see the folder at all -- much less the 38 files.

What is my problem and how can I fix it. I will appreciate any advice.
Stan Hilliard

(I also posted this problem on the Newsgroup: &nbsp;comp.mail.pegasus-mail.ms-windows) I updated Pegasus 4.21b to v4.41 on a Windows 98 PC. No problem. The problem is running Pegasus from another PC over my home network. Recent emails are missing. Nothing from 2008. Here are the counts of new mail in the toolbar at the bottom of screen. (But all folders are affected similarly.) #1 PC with Pegasus v4.41 installed: 967 new, Windows 98SE. #2 PC connected to #1 by ethernet: 919 new, Windows XP Pro. #3 PC connected to #1 by wireless: 1191 new, Windows XP Home. Pegasus is installed on #1 PC in D:\Program Files\Pmail\winpm-32.exe Mailbox is installed on #1 PC in E:\Mail\Pmail\ On Pegasus's first startup over the network it displayed this message-box: "Pegasus Mail has detected that you have previously used an older versin on this mail box" [x] Show me what's new&nbsp; [continue] On #1 PC with the V4.41 I downloaded 38 emails from POP3 and moved them to a newly-created folder. Everything seems normal on #1, but over on #2 PC &amp; #3 PC I can't see the folder at all -- much less the 38 files. What is my problem and how can I fix it. I will appreciate any advice. Stan Hilliard

PaulW

posted Aug 15 '08 at 9:35 am

How are you mapping those drive letters?

PC1 has drives D: and E: which are probably in the configuration files. When you run from other PCs those drives won't exist (or point elsewhere).

It's easier on a network to use network mapping in the form '\\server\sharename'. If you run pconfig.exe and change the paths, then the folders should be found.

How are you mapping those drive letters? PC1 has drives D: and E: which are probably in the configuration files.&nbsp; When you run&nbsp;from other PCs those drives won't exist (or point elsewhere). It's&nbsp;easier on a network to use network mapping in the form '\\server\sharename'.&nbsp; If you run pconfig.exe and change the paths, then the folders should be found.

StanH

posted Aug 15 '08 at 7:02 pm

[quote user="PaulW"]... use network mapping in the form '\\server\sharename'. If you run pconfig.exe and change the paths, then the folders should be found.[/quote]

I think I already have that. The links to Pegasus from #2 PC and #3 PC are:

"\\Tower\D\Program Files\PMAIL\winpm-32.exe"

On #1 PC the Share Name of D: (where the program is) = "D"

On #1 PC the share name of E: (where the mailbox is) = "E"

On #1 PC both partitions have access type = Full

What else can I do that might make all the mail in the mailbox visible to #2 PC and #3 PC?

Should I install Pegasus on each PC and try addressing only the mailbox on #1 PC?

[quote user="PaulW"]... use network mapping in the form '\\server\sharename'.&nbsp; If you run pconfig.exe and change the paths, then the folders should be found.[/quote]I think I already have that. The links to Pegasus from #2 PC and #3 PC are:"\\Tower\D\Program Files\PMAIL\winpm-32.exe"&nbsp; On #1 PC the Share Name of D: (where the program is) = "D"On #1 PC the share name of E: (where the mailbox is) = "E"On #1 PC both partitions have access type = Full&nbsp;What else can I do that might make all the mail in the mailbox visible to #2 PC and #3 PC?&nbsp;Should I install Pegasus on each PC and try addressing only the mailbox on #1 PC?

Thomas R. Stephenson

posted Aug 15 '08 at 7:44 pm

What else can I do that might make all the mail in the mailbox visible to #2 PC and #3 PC?

Run pconfig.exe in ..\ Program Files\PMAIL\ and reset the Standalone HOME and NEW mail directory spec to the UNC format as well. Probably something like \\Tower\E\PMail\Mail\~8 if the mailbox is e:\pmail\mail.

<blockquote>What else can I do that might make all the mail in the mailbox visible to #2 PC and #3 PC? </blockquote>Run pconfig.exe in ..\ Program Files\PMAIL\ and reset the Standalone HOME and NEW mail directory spec to the UNC format as well.&nbsp; Probably something like \\Tower\E\PMail\Mail\~8 if the mailbox is e:\pmail\mail.&nbsp;&nbsp;

StanH

posted Aug 15 '08 at 10:43 pm

[quote user="Thomas R. Stephenson"]Run pconfig.exe in ..\ Program Files\PMAIL\ and reset the Standalone HOME and NEW mail directory spec to the UNC format as well. Probably something like \\Tower\E\PMail\Mail\~8 if the mailbox is e:\pmail\mail. [/quote]

I did that. Then on startup of Pegasus it asked me for my username. I have never used a username with Pegasus before.

What should I do?

[quote user="Thomas R. Stephenson"]Run pconfig.exe in ..\ Program Files\PMAIL\ and reset the Standalone HOME and NEW mail directory spec to the UNC format as well.&nbsp; Probably something like \\Tower\E\PMail\Mail\~8 if the mailbox is e:\pmail\mail. [/quote]I did that. Then on startup of Pegasus it asked me for my username. I have never used a username with Pegasus before.&nbsp;What should I do?&nbsp;&nbsp;

Thomas R. Stephenson

posted Aug 15 '08 at 11:35 pm

Generally speaking if you only have one user and it asks for the username then the path to the new mail directory is incorrect. Verify the path you entered in pconfig.

Generally speaking if you only have one user and it asks for the username then the path to the new mail directory is incorrect.&nbsp; Verify the path you entered in pconfig. &nbsp;

StanH

posted Aug 16 '08 at 12:20 am

[quote user="Thomas R. Stephenson"]... if you only have one user ,,,[/quote]

I did have a spelling error in the path to the new mail directory. Fixing that did not change anything -- still wants username. So I removed the "~8" from the end of the paths (since I didn't understand it.) Now I can see all the mail from #2 PC. So the problem appears to be solved. What is the explanation of this?

Since the issue came up, please define a "username". I am the only real person using these PCs at this time but I might want to give my wife access later. Does the following complicate the matter? I have several email addresses on the POP3 server of my main Internet provider. I also use three providers, two of which I have Pegasus pointing to them -- they being associated with different identities. So the identities determine both the Internet provider and the mailbox within provider.

In this situation, what is a "username"?

Is there a better way that I should be configuring Pegasus?

[quote user="Thomas R. Stephenson"]... if you only have one user ,,,[/quote]I did have a spelling error in the path to the new mail directory. Fixing that did not change anything -- still wants username. So I removed the "~8" from the end of the paths (since I didn't understand it.) Now I can see all the mail from #2 PC. So the problem appears to be solved. What is the explanation of this? Since the issue came up, please define a "username". I am the only real person using these PCs at this time but I might want to give my wife access later. Does the following complicate the matter? I have several email addresses on the POP3 server of my main Internet provider. I also use three providers, two of which I have Pegasus pointing to them -- they being associated with different identities. So the identities determine both the Internet provider and the mailbox within provider. &nbsp; In this situation, what is a "username"?Is there a better way that I should be configuring Pegasus?&nbsp;

Thomas R. Stephenson

posted Aug 16 '08 at 12:41 am

I did have a spelling error in the path to new mail. Fixing that did
not change anything -- still wants username. So I removed the "~8" from
the end of the paths (since I didn't understand it.) Now I can see all
the mail from #2 PC. So the problem appears to be solved. What is the
explanation of this?

You have a really old single-user installation that has the mail in c:\pmail\mail instead of c:\pmail\mail\admin.

Since the issue came up, please define a "username". I am the only
real person using these PCs at this time but I might want to give my
wife access later. Does the following complicate the matter? I have
several email addresses on the POP3 server of my main Internet
provider. I also use three providers, two of which I have Pegasus
pointing to them -- they being associated with different identities. So
the identities determine both the Internet provider and the mailbox
within provider.

In this situation, what is a "username"?

A little background structure. The older Pegasus Mail single-user setups had the program in ..\pmail and the mail in ..\pmail\mail. To add multiple users you had to jump through hoops to convert to the multiuser mode. Here's a glossary entry I had for converting from single-user to multi-user:

----------------------------------------------------------------------------------------------------- multi --------------------------------------------------------------------------------------

These are the procedures for converting from single user to multiuser. This process assumes that you used the default settings when installing WinPmail in single user mode, therefore the basic directory is c:\pmail and the mail directory is c:\pmail\mail.

1: Go to the MSDOS prompt and create a directory for your current mail files and username. I assume you are using a username of THOMAS.

MD c:\pmail\mail\THOMAS

2: Move your current mail files from the c:\pmail\mail directory to the c:\pmail\mail\THOMAS directory.

MOVE c:\pmail\mail\*.* c:\pmail\mail\THOMAS

3: Edit your pmail.ini file and change all instances of c:\pmail\mail to c:\pmail\mail\THOMAS. If you have saved your username in win.ini, edit the win.ini file and remove the username line.

4: Delete the file c:\pmail\pmail.cfg. This will remove your current configuration and force WinPmail to go the install process.

5: Double click on the WinPmail icon. Since the pmail.cfg is missing, this will cause WinPmail to go through the install process. Select the multiuser option.

6: You will be asked to about the users. Add the username THOMAS and any other users you wish. Make sure you give administrator privileges to at least one username so you will be able to administer to users. Select close.

7: You will be asked to select a username, use THOMAS. This should now open WinPmail using you old mail information. You will now have an additional menu item under Address that will allow you to administer your users from WinPmail.

8: You now can create an icon for each user with the -i <username> commandline option to enable starting WinPmail without having to enter the username each time.

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

This was a pain in the rear so in v4.x the basic installer installed always in the multi-user mode and if there was more than one user it queried for the username. In the structure the program went into ..\pmail\programs, the pmail.usr file went into the ..\pmail\mail directories and the users mail directory went into ..\pmail\mail\<username> with admin the default single-user username. The difference shows up in the pmail.cfg by adding the ~8 (~n) to the end of the path structure to tell the program to query the user for the username that will replace the ~8.

<blockquote>I did have a spelling error in the path to new mail. Fixing that did not change anything -- still wants username. So I removed the "~8" from the end of the paths (since I didn't understand it.) Now I can see all the mail from #2 PC. So the problem appears to be solved. What is the explanation of this?</blockquote>You have a really old single-user installation that has the mail in c:\pmail\mail instead of c:\pmail\mail\admin.<blockquote>Since the issue came up, please define a "username". I am the only real person using these PCs at this time but I might want to give my wife access later. Does the following complicate the matter? I have several email addresses on the POP3 server of my main Internet provider. I also use three providers, two of which I have Pegasus pointing to them -- they being associated with different identities. So the identities determine both the Internet provider and the mailbox within provider. </blockquote><blockquote>In this situation, what is a "username"?</blockquote>&nbsp;A little background structure.&nbsp; The older Pegasus Mail single-user setups had the program in&nbsp; ..\pmail and the mail in ..\pmail\mail.&nbsp; To add multiple users you had to jump through hoops to convert to the multiuser mode. Here's a glossary entry I had for converting from single-user to multi-user:----------------------------------------------------------------------------------------------------- multi -------------------------------------------------------------------------------------- &nbsp;These are the procedures for converting from single user to multiuser.&nbsp; This process assumes that you used the default settings when installing WinPmail in single user mode, therefore the basic directory is c:\pmail and the mail directory is c:\pmail\mail. &nbsp; 1:&nbsp; Go to the MSDOS prompt and create a directory for your current mail files and username.&nbsp; I assume you are using a username of THOMAS.&nbsp; &nbsp; &nbsp;&nbsp;&nbsp; MD c:\pmail\mail\THOMAS 2:&nbsp; Move your current mail files from the c:\pmail\mail directory to the c:\pmail\mail\THOMAS directory.&nbsp; &nbsp; &nbsp;&nbsp;&nbsp; MOVE c:\pmail\mail\*.* c:\pmail\mail\THOMAS 3:&nbsp; Edit your pmail.ini file and change all instances of c:\pmail\mail to c:\pmail\mail\THOMAS.&nbsp; If you have saved your username in win.ini, edit the win.ini file and remove the username line. &nbsp; 4:&nbsp; Delete the file c:\pmail\pmail.cfg.&nbsp; This will remove your current configuration and force WinPmail to go the install process. &nbsp; 5:&nbsp; Double click on the WinPmail icon.&nbsp; Since the pmail.cfg is missing, this will cause WinPmail to go through the install process.&nbsp; Select the multiuser option.&nbsp; &nbsp; 6:&nbsp; You will be asked to about the users.&nbsp; Add the username THOMAS and any other users you wish.&nbsp; Make sure you give administrator privileges to at least one username so you will be able to administer to users.&nbsp; Select close. &nbsp; 7:&nbsp; You will be asked to select a username, use THOMAS.&nbsp; This should now open WinPmail using you old mail information.&nbsp; You will now have an additional menu item under Address that will allow you to administer your users from WinPmail. &nbsp; 8:&nbsp; You now can create an icon for each user with the -i &lt;username&gt; commandline option to enable starting WinPmail without having to enter the username each time. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- This was a pain in the rear so in v4.x the basic installer installed always in the multi-user mode and if there was more than one user it queried for the username.&nbsp; In the structure the program went into ..\pmail\programs, the pmail.usr file went into the ..\pmail\mail directories and the users mail directory went into ..\pmail\mail\&lt;username&gt; with admin the default single-user username.&nbsp; The difference shows up in the pmail.cfg by adding the ~8 (~n) to the end of the path structure to tell the program to query the user for the username that will replace the ~8.&nbsp;&nbsp;

StanH

posted Aug 16 '08 at 7:52 am

[quote user="StanH"]Now I can see all the mail from #2 PC. So the problem appears to be solved. [/quote]

I spoke too soon.

All of the files in the new mail folder are displayed on #2 PC, but the files dated later than mid April 2007 are not displayed in any other folder.

[quote user="StanH"]Now I can see all the mail from #2 PC. So the problem appears to be solved. [/quote] I spoke too soon. All of the files in the new mail folder are displayed on #2 PC, but the files dated later than mid April 2007 are not displayed in any other folder.

Thomas R. Stephenson

posted Aug 16 '08 at 5:45 pm

Use Help | About Pegasus Mail | Info to verify that all systems are using the same HOME and NEW mail directory spec as specified in the pconfig. The HOME mail directory is specified in the pmail.ini and it may still be looking at old mail.

FWIW, it really sounds like you have duplicates of your mail directories.

Use Help | About Pegasus Mail | Info to verify that all systems are using the same HOME and NEW mail directory spec as specified in the pconfig.&nbsp; The HOME mail directory is specified in the pmail.ini and it may still be looking at old mail.FWIW, it really sounds like you have duplicates of your mail directories.&nbsp;

StanH

posted Aug 16 '08 at 9:34 pm

[quote user="Thomas R. Stephenson"]Use Help | About Pegasus Mail | Info to verify that all systems are using the same HOME and NEW mail directory spec as specified in the pconfig. The HOME mail directory is specified in the pmail.ini and it may still be looking at old mail.[/quote]
Tom, thanks for explaining the Pegasus' mechanism for handling single/multi users.

With [help] I found that the new mail directory was correct but the mail directory was/is still or the old form "E:\" and not "\\tower\E\".

I found PMAIL.INI in the new mail directory dated today. There was also a PMAILINI.OLD dated two days ago. There is what pmail.ini contains:

SECTION: [Pegasus Mail for Windows - built-in TCP/IP Mail]
Directory to place incoming POP3 mail     = E:Mail\Pmail\NewMail
Search mask to locate outgoing messages   = E:\MAIL\PMAIL\*.PMX

SECTION: [General]
Home mailbox location                     = E:\MAIL\PMAIL

SECTION: [Pegasus Mail for Windows - Run Info]
Working home mailbox location    = E:\MAIL\PMAIL
New mailbox location             = \\tower\E\Mail\Pmail\NewMail

SECTION: [WinPMail Identity - sales]
Home mailbox location                     = E:\MAIL\PMAIL
Directory to place incoming POP3 mail     = E:Mail\Pmail\NewMail
Search mask to locate outgoing messages   = E:\MAIL\PMAIL\*.PMX

SECTION: [WinPMail Identity - shilliard]
Home mailbox location                     = E:\MAIL\PMAIL
Directory to place incoming POP3 mail     = E:Mail\Pmail\NewMail
Search mask to locate outgoing messages   = E:\MAIL\PMAIL\*.PMX

... There are seven identities total. I am wondering why pconfig.exe only would have changed one of the many instances of "E:\mail\pmail\newmail" in pmail.ini?

The path that pconfig.exe displays to the mail folder is in network syntax (\\tower\E\mail\pmail) even though it did not make any of those conversions. Does this imply there is something else that should be changed to make pconfig.exe work properly?

Sincerely, Stan Hilliard

[quote user="Thomas R. Stephenson"]Use Help | About Pegasus Mail | Info to verify that all systems are using the same HOME and NEW mail directory spec as specified in the pconfig. The HOME mail directory is specified in the pmail.ini and it may still be looking at old mail.[/quote] Tom, thanks for explaining the Pegasus' mechanism for handling single/multi users. With [help] I found that the new mail directory was correct but the mail directory was/is still or the old form "E:\" and not "\\tower\E\". I found PMAIL.INI in the new mail directory dated today. There was also a PMAILINI.OLD dated two days ago. There is what pmail.ini contains: SECTION: [Pegasus Mail for Windows - built-in TCP/IP Mail] Directory to place incoming POP3 mail&nbsp;&nbsp;&nbsp;&nbsp; = E:Mail\Pmail\NewMail Search mask to locate outgoing messages&nbsp;&nbsp; = E:\MAIL\PMAIL\*.PMX SECTION: [General] Home mailbox location&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = E:\MAIL\PMAIL SECTION: [Pegasus Mail for Windows - Run Info] Working home mailbox location&nbsp;&nbsp;&nbsp; = E:\MAIL\PMAIL New mailbox location&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = \\tower\E\Mail\Pmail\NewMail SECTION: [WinPMail Identity - sales] Home mailbox location&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = E:\MAIL\PMAIL Directory to place incoming POP3 mail&nbsp;&nbsp;&nbsp;&nbsp; = E:Mail\Pmail\NewMail Search mask to locate outgoing messages&nbsp;&nbsp; = E:\MAIL\PMAIL\*.PMX SECTION: [WinPMail Identity - shilliard] Home mailbox location&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = E:\MAIL\PMAIL Directory to place incoming POP3 mail&nbsp;&nbsp;&nbsp;&nbsp; = E:Mail\Pmail\NewMail Search mask to locate outgoing messages&nbsp;&nbsp; = E:\MAIL\PMAIL\*.PMX ... There are seven identities total. I am wondering why pconfig.exe only would have changed one of the many instances of "E:\mail\pmail\newmail" in pmail.ini? The path that pconfig.exe displays to the mail folder is in network syntax (\\tower\E\mail\pmail) even though it did not make any of those conversions. Does this imply there is something else that should be changed to make pconfig.exe work properly? Sincerely, Stan Hilliard

StanH

posted Aug 16 '08 at 9:50 pm

[quote user="Thomas R. Stephenson"]FWIW, it really sounds like you have duplicates of your mail directories. [/quote]

The PMAIL program directory on Partition D of #1 PC contains a MAIL folder that does not contain any emails. It contains ADMIN and DEFAULTS directories. They both contain only files dated 2003.

#1 PC also contains two partitions (F and Q) that each contain backups of the mail folders from earlier dates.

Stan Hilliard

[quote user="Thomas R. Stephenson"]FWIW, it really sounds like you have duplicates of your mail directories. [/quote]The PMAIL program directory on Partition D of #1 PC contains a MAIL folder that does not contain any emails. It contains&nbsp; ADMIN and DEFAULTS&nbsp; directories. They both contain only files dated 2003.&nbsp;#1 PC also contains two partitions (F and Q) that each contain backups of the mail folders from earlier dates.&nbsp;Stan Hilliard&nbsp;

Thomas R. Stephenson

posted Aug 17 '08 at 6:26 am

The pconfig.exe changes nothing in the pmail.ini file, you have you make those changes manually to the file.

The pconfig.exe changes nothing in the pmail.ini file, you have you make those changes manually to the file.&nbsp;

StanH

posted Aug 19 '08 at 4:18 am

[quote user="Thomas R. Stephenson"]... you have you make those changes manually to the file. [/quote]

I made the changes and Pegasus the directories are accessible over the network. Thanks for the help.

[quote user="Thomas R. Stephenson"]The pconfig.exe changes nothing in the pmail.ini file,[/quote]

After my original running of pconfig.exe I ran Pagesus and then looked in pmail.ini. The path in pmail.ini to newmail was in network syntax. Am I correct in assuming that pconfig changed winpm-32.exe which in turn changed pmail.ini the nest time I ran Pegasus?

Is there a simple explanation for when I changed the format of the path to the main mailbox from within Pegasus that setting did not persist?

Stan Hilliard

[quote user="Thomas R. Stephenson"]... you have you make those changes manually to the file. [/quote]I made the changes and Pegasus the directories are accessible over the network. Thanks for the help. [quote user="Thomas R. Stephenson"]The pconfig.exe changes nothing in the pmail.ini file,[/quote]After my original running of pconfig.exe I ran Pagesus and then looked in pmail.ini. The path in pmail.ini to newmail was in network syntax. Am I correct in assuming that pconfig changed winpm-32.exe which in turn changed pmail.ini the nest time I ran Pegasus?Is there a simple explanation for when I changed the format of the path to the main mailbox from within Pegasus that setting did not persist?Stan Hilliard&nbsp;

Thomas R. Stephenson

posted Aug 19 '08 at 6:01 am

After my original running of pconfig.exe I ran Pagesus and then looked
in pmail.ini. The path in pmail.ini to newmail was in network syntax.
Am I correct in assuming that pconfig changed winpm-32.exe which in
turn changed pmail.ini the nest time I ran Pegasus?

Pconfig.exe changes the pmail.cfg file telling Pegasus mail where to find the new mail directory of the user and the pmail.ini file. The pmail.ini file is read to get the HOME mail directory. If there is a mailbox there when you close the program the new mail directory is saved as the directory you started with but the home mail directory as what was shown in the pmail.ini If there is not mailbox located where specified in the npmail in the the new mail directory is used to find the mailbox.

Is there a simple explanation for when I changed the format of the path
to the main mailbox from within Pegasus that setting did not persist?

All these data are held in memory until the program closes and re-writes the pmail.ini file.

<blockquote>After my original running of pconfig.exe I ran Pagesus and then looked in pmail.ini. The path in pmail.ini to newmail was in network syntax. Am I correct in assuming that pconfig changed winpm-32.exe which in turn changed pmail.ini the nest time I ran Pegasus?</blockquote>Pconfig.exe changes the pmail.cfg file telling Pegasus mail where to find the new mail directory of the user and the pmail.ini file.&nbsp; The pmail.ini file is read to get the HOME mail directory.&nbsp; If there is a mailbox there when you close the program the new mail directory is saved as the directory you started with but the home mail directory as what was shown in the pmail.ini If there is not mailbox located where specified in the npmail in the the new mail directory is used to find the mailbox.<blockquote>&nbsp;Is there a simple explanation for when I changed the format of the path to the main mailbox from within Pegasus that setting did not persist?</blockquote>All these data are held in memory until the program closes and re-writes the pmail.ini file.&nbsp;

StanH

posted Aug 21 '08 at 6:25 am

I thought my network addressing problem was solved but the saved mail has the same problem as the mail folders had before. I can access all saved mail from #1 PC, but from #2 PC over the network all the emails after April 2007 have no bodies. They are listed and can be opened and have subjects and outgoing addresses, but no body text.

How can I access saved mail from the networked #2 PC?

Stan Hilliard

I thought my network addressing problem was solved but the saved mail has the same problem as the mail folders had before. I can access all saved mail from #1 PC, but from #2 PC over the network all the emails after April 2007 have no bodies. They are listed and can be opened and have subjects and outgoing addresses, but&nbsp; no body&nbsp; text. How can I access saved mail from the networked #2 PC?&nbsp;Stan Hilliard&nbsp;

Thomas R. Stephenson

posted Aug 21 '08 at 7:06 pm

The 2nd PC is not pointing at the same HOME mail directory directory as the 1st PC. You also must have an old mailbox available since if it were not looking at a mailbox you would see nothing but the new mail.

Again, check the setting for the HOME and NEW mail directory and verify you are using a UNC format instead of a drive letter type path so you can be sure that different drive mappings are not causing the problem.

The 2nd PC is not pointing at the same HOME mail directory directory as the 1st PC.&nbsp; You also must have an old mailbox available since if it were not looking at a mailbox you would see nothing but the new mail.&nbsp; Again, check the setting for the HOME and NEW mail directory and verify you are using a UNC format instead of a drive letter type path so you can be sure that different drive mappings are not causing the problem.&nbsp;&nbsp;

StanH

posted Aug 22 '08 at 12:01 am

[quote user="Thomas R. Stephenson"]The 2nd PC is not pointing at the same HOME mail directory directory as the 1st PC. You also must have an old mailbox available since if it were not looking at a mailbox you would see nothing but the new mail.

Again, check the setting for the HOME and NEW mail directory and verify you are using a UNC format instead of a drive letter type path so you can be sure that different drive mappings are not causing the problem.[/quote]
You are right. Here are my total settings and related paths and directories for #1 PC and #2 PC:

==== On #1 PC: ====
In pegasus [tools][general settengs][mailbox location]
\\TOWER\E\MAIL\PMAIL

Runing D:\PMAIL\pconfig.exe
\\tower\E\Mail\Pmail
\\tower\E\Mail\Pmail\NewMail

In file D:\PMAIL\PMAIL.CFG
\\tower\E\Mail\Pmail\NewMail (+45 spaces) \\tower\E\Mail\Pmail

In file E:\Mail\Pmail\NewMail\PMAIL.INI
No references to "E:" or \\tower (other than \E\)
No references to "homebuilt", which is the name of #2PC.

==== On #2 PC: ====
I found the other mailbox. On #2 PC. I am using E:\mail\pmail\

and E:\mail\pmail\newmail as a backup that I created April 25 2007. I

guess that is the mailbox that has been confusing Pegasus.

E:\mail\pmail\ contains about 45 files starting 8/14/2008 to present -- the period that I have been networking Pegasus. Mostly FOL*.PPM but also
NEWCACHE.PM
CACHE.PM
STATE.PMJ
HIERARCH.PM
FOLSTATE.PN
DESKTOP.PM0
virscan.log
virscan.bck

E:\mail\pmail\newmail\ contains 2 recent files:
PMAIL.INI
PMAIL.OLD

Could it be that Pegasus is hard coded to look on the local PC first regardless of other settings?
Stan Hilliard

[quote user="Thomas R. Stephenson"]The 2nd PC is not pointing at the same HOME mail directory directory as the 1st PC.&nbsp; You also must have an old mailbox available since if it were not looking at a mailbox you would see nothing but the new mail. Again, check the setting for the HOME and NEW mail directory and verify you are using a UNC format instead of a drive letter type path so you can be sure that different drive mappings are not causing the problem.[/quote] You are right. Here are my total settings and related paths and directories for #1 PC and #2 PC: ==== On #1 PC: ==== In pegasus [tools][general settengs][mailbox location] \\TOWER\E\MAIL\PMAIL Runing D:\PMAIL\pconfig.exe \\tower\E\Mail\Pmail \\tower\E\Mail\Pmail\NewMail In file D:\PMAIL\PMAIL.CFG \\tower\E\Mail\Pmail\NewMail&nbsp;&nbsp; (+45 spaces)&nbsp; \\tower\E\Mail\Pmail In file E:\Mail\Pmail\NewMail\PMAIL.INI No references to "E:" or \\tower (other than \E\) No references to "homebuilt", which is the name of #2PC. ==== On #2 PC: ==== I found the other mailbox. On #2 PC. I am using E:\mail\pmail\ and E:\mail\pmail\newmail as a backup that I created April 25 2007. I guess that is the mailbox that has been confusing Pegasus. E:\mail\pmail\ contains about 45 files starting 8/14/2008 to present -- the period that I have been networking Pegasus. Mostly FOL*.PPM but also NEWCACHE.PM CACHE.PM STATE.PMJ HIERARCH.PM FOLSTATE.PN DESKTOP.PM0 virscan.log virscan.bck E:\mail\pmail\newmail\ contains 2 recent files: PMAIL.INI PMAIL.OLD Could it be that Pegasus is hard coded to look on the local PC first regardless of other settings? Stan Hilliard&nbsp;

Thomas R. Stephenson

posted Aug 22 '08 at 12:55 am

On 21 Aug 2008 23:03 Pegasus Mail & Mercury - Automated Email <Thomas R. Stephenson> wrote:

> > Thomas R. Stephenson:
> >
> > The 2nd PC is not pointing at the same HOME mail directory directory as
> > the 1st PC. You also must have an old mailbox available since if it were
> > not looking at a mailbox you would see nothing but the new mail.
> >
> > Again, check the setting for the HOME and NEW mail directory and
> > verify you are using a UNC format instead of a drive letter type
> > path so you can be sure that different drive mappings are not
> > causing the problem.
>
>
> You are right. Here are my total settings and related paths and
> directories for #1 PC and #2 PC:
>
> On #1 PC:
> In pegasus [tools][general settengs][mailbox location]
> \\TOWER\E\MAIL\PMAIL

You should try Help | About Pegasus Mail | Info to see the mail directory locations, there a snippet of mine. Note that I am running separate HOME and NEW mail directories on the same remote server.

Pegasus Mail for Microsoft Windows
Copyright (C) 1992-2008, David Harris, all rights reserved
Electronic mail to support@pmail.gen.nz.

WinPMail version: Version 4.50 VC19 (Win32), Aug 13 2008
Language resources: Standard UK English resource set
Extension Manager version: 1.13
Operating mode: Standalone
User name and ID: support, 0
Windows version: 5.1
Windows flag word: 0
WINPMAIL.EXE directory: C:\pmail
Home mailbox location: \\tstephenson\c_drive\pmail\mail\thomas
New mailbox location: \\tstephenson\c_drive\PMAIL\MAIL\support

>
> Runing D:\PMAIL\pconfig.exe
> \\tower\E\Mail\Pmail
> \\tower\E\Mail\Pmail\NewMail

You should really use pconfig.exe to read these data. It's easy to cur and paste.

Home mailbox : [\\tstephenson\c_drive\PMAIL\MAIL\~n ]
New mailbox : \\tstephenson\c_drive\PMAIL\MAIL\~n
Asynch gateway? : N

>
> In file D:\PMAIL\PMAIL.CFG
> \\tower\E\Mail\Pmail\NewMail (+45 spaces) \\tower\E\Mail\Pmail
>
> In file E:\Mail\Pmail\NewMail\PMAIL.INI
> No references to "E:" or \\tower (other than \E\)
> No references to "homebuilt", which is the name of #2PC.
>
> I found the other mailbox. On #2 PC I am using E:\mail\pmail\ and
> E:\mail\pmail\newmail as a backup that I created April 25 2007. I
> guess that is the mailbox that has been confusing Pegasus.

Could be but in this case the HOME mail directory in the pmail.ini file should be pointing to this directory.

>
> On #2 PC.
> E:\mail\pmail\ contains about 45 files starting 8/14/2008 to present
> -- the period that I have been networking Pegasus. Mostly FOL*.PPM
> but also
> NEWCACHE.PM
> CACHE.PM
> STATE.PMJ
> HIERARCH.PM
> FOLSTATE.PN
> DESKTOP.PM0
> virscan.log
> virscan.bck
>
> E:\mail\pmail\newmail\ contains 2 recent files:
> PMAIL.INI
> PMAIL.OLD
>
> Could it be that Pegasus is hard coded to look on the local PC first
> regardless of other settings?

Only if you are using the -ROAM commandline option.

-ROAM This option tells Pegasus Mail that it should ignore the configured drive letter when locating user mailboxes and mail files, and should instead use the drive letter of the drive from which WINPM-32.EXE was run. If Pegasus Mail and your mailbox directories are located on the same physical drive, you should always use this option. -ROAM greatly simplifies running the program on Peer-to-Peer and non-NetWare networks, because it allows the same copy of the program to be run no matter what drive letter mappings exist on the particular workstation where it runs. This switch also allows you to install a complete, working copy of Pegasus Mail, complete with mailboxes, onto a memory stick, and to use that memory stick in any computer where it is subsequently plugged. You must not use this switch if Pegasus Mail and your mailbox directories cannot be accessed using the same drive letter. This switch is ignored and has no effect in either Novell NetWare operating mode.

> Stan Hilliard

On 21 Aug 2008 23:03 Pegasus Mail &amp; Mercury - Automated Email &lt;Thomas R. Stephenson&gt; wrote: &gt; &gt;&nbsp; Thomas R. Stephenson: &gt; &gt; &gt; &gt; The 2nd PC is not pointing at the same HOME mail directory directory as &gt; &gt; the 1st PC.&nbsp; You also must have an old mailbox available since if it were &gt; &gt; not looking at a mailbox you would see nothing but the new mail. &gt; &gt; &gt; &gt; Again, check the setting for the HOME and NEW mail directory and &gt; &gt; verify you are using a UNC format instead of a drive letter type &gt; &gt; path so you can be sure that different drive mappings are not &gt; &gt; causing the problem. &gt; &gt; &gt; You are right. Here are my total settings and related paths and &gt; directories for #1 PC and #2 PC: &gt; &gt; On #1 PC: &gt; In pegasus [tools][general settengs][mailbox location] &gt; \\TOWER\E\MAIL\PMAIL You should try Help | About Pegasus Mail | Info to see the mail directory locations, there a snippet of mine.&nbsp; Note that I am running separate HOME and NEW mail directories on the same remote server. Pegasus Mail for Microsoft Windows Copyright (C) 1992-2008, David Harris, all rights reserved Electronic mail to support@pmail.gen.nz. WinPMail version: Version 4.50 VC19 (Win32), Aug 13 2008 Language resources: Standard UK English resource set Extension Manager version: 1.13 Operating mode: Standalone User name and ID: support, 0 Windows version: 5.1 Windows flag word: 0 WINPMAIL.EXE directory: C:\pmail Home mailbox location: \\tstephenson\c_drive\pmail\mail\thomas New mailbox location: \\tstephenson\c_drive\PMAIL\MAIL\support &gt; &gt; Runing D:\PMAIL\pconfig.exe &gt; \\tower\E\Mail\Pmail &gt; \\tower\E\Mail\Pmail\NewMail You should really use pconfig.exe to read these data.&nbsp; It's easy to cur and paste. Home mailbox :&nbsp;&nbsp;&nbsp; [\\tstephenson\c_drive\PMAIL\MAIL\~n&nbsp; ] New mailbox&nbsp; :&nbsp;&nbsp;&nbsp;&nbsp; \\tstephenson\c_drive\PMAIL\MAIL\~n Asynch gateway? :&nbsp; N &gt; &gt; In file D:\PMAIL\PMAIL.CFG &gt; \\tower\E\Mail\Pmail\NewMail&nbsp;&nbsp; (+45 spaces)&nbsp; \\tower\E\Mail\Pmail &gt; &gt; In file E:\Mail\Pmail\NewMail\PMAIL.INI &gt; No references to "E:" or \\tower (other than \E\) &gt; No references to "homebuilt", which is the name of #2PC. &gt; &gt; I found the other mailbox. On #2 PC I am using E:\mail\pmail\ and &gt; E:\mail\pmail\newmail as a backup that I created April 25 2007. I &gt; guess that is the mailbox that has been confusing Pegasus. Could be but in this case the HOME mail directory in the pmail.ini file should be pointing to this directory. &gt; &gt; On #2 PC. &gt; E:\mail\pmail\ contains about 45 files starting 8/14/2008 to present &gt; -- the period that I have been networking Pegasus. Mostly FOL*.PPM &gt; but also &gt; NEWCACHE.PM &gt; CACHE.PM &gt; STATE.PMJ &gt; HIERARCH.PM &gt; FOLSTATE.PN &gt; DESKTOP.PM0 &gt; virscan.log &gt; virscan.bck &gt; &gt; E:\mail\pmail\newmail\ contains 2 recent files: &gt; PMAIL.INI &gt; PMAIL.OLD &gt; &gt; Could it be that Pegasus is hard coded to look on the local PC first &gt; regardless of other settings? Only if you are using the -ROAM commandline option. -ROAM&nbsp; This option tells Pegasus Mail that it should ignore the configured drive letter when locating user mailboxes and mail files, and should instead use the drive letter of the drive from which WINPM-32.EXE was run. If Pegasus Mail and your mailbox directories are located on the same physical drive, you should always use this option. -ROAM greatly simplifies running the program on Peer-to-Peer and non-NetWare networks, because it allows the same copy of the program to be run no matter what drive letter mappings exist on the particular workstation where it runs. This switch also allows you to install a complete, working copy of Pegasus Mail, complete with mailboxes, onto a memory stick, and to use that memory stick in any computer where it is subsequently plugged. You must not use this switch if Pegasus Mail and your mailbox directories cannot be accessed using the same drive letter. This switch is ignored and has no effect in either Novell NetWare operating mode. &gt; Stan Hilliard

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history