In your PMAIL folder is a program called pconfig.exe, run this.
This, among other things tells Pmail where to find it's data files (asking for your username is a symptom of not finding PMAIL.USR where it expects to).
Change any entries that start with c:\.... to d:\.... keeping all other data the same (assuming you kept it in the same folder(s) relative to the root of the drive)
There is probably more complete answers on the forum if you search for "PMAIL.USR" or "move drive"
> We have two or three email accounts some of which are accessed ban > internet mail program, and some of which are accessed via Pegasus. My > wife tried to log onto an account using Pegasus last week, but it just > opened the "new mail" window and then hung before fully opening it. The > PC "revved up" (fan speed wnet up to high speed, and we got "not > responding message". It's an old PC running XPhome . > > We had recenlty updated to latest Pegasus , but that doesn't seem to be > the problem. A data file corrupt, perhaps? I've on idea, and am not a > computer buff. I've re-indexed things in Pegasus in the past and > followed various hints and tips successfully, but can't find anythnig > on this particular issue > > > Any ideas very welcome . TIA
Move all of the *.CNM files out of the new mail directory and try again. It should now open normally. You can then put the messages back one at a time until you find the problem message.
It's probably going to be a really large message. If you are using content control then I'd recommend that you set a limit on the message size so you are not scanning these large files with encoded attachments.
1. Use Tools | Spam and content controls | Content control...
2. Select and edit the control definition
3. Select the "Message tests" tab.
4. Enter 8000 in "Check at most this many bytes in each message"
> > Sorry: should have said it starts up with the "in use by another > process window" so I said "carry on regardless"
No big deal, you crashed out of the program so is was unable to delete the lock file.
This can be done by manually moving the folders to another directory and then do an "Add mailbox to list" to access the old folders. This would require doing a complete rebuild of the hierarch.pm. It's the method I use and I move them to a separate user directory in my multiple user setup. I can then either run as the user or use "Add mailbox to list" to mount the other user mailbox. The hierarch.pm & state.pmj do need rebuilding to remove all of the moved folders.
You can do the "Add mailbox to list" and point at a different directory and then create new folders and move the mail from one mailbox to the other. You then delete the original folder. Now you are showing two different mailboxes in the same structure. Since the state.pmj and hierarch.pm are being updated with this process it's a lot cleaner albeit slower if there are a lot of folders involved.
Create an identity for the IMAP folders and attach it to the folders. Then become that IMAP identity and set the copy self folder to point at a IMAP folder in the account. Make sure you use a unique name for the folder. The copy self function works on the folder name and uses the first one that it finds with a matching name.
The symtoms are, A new mail comes in but does not display in the inbox,
only the 'New Mail' folder is highlighted and the number of new mail at
the bottom of the screen show there is an unread message. Once you
navigate back to the 'New Mail' folder the message is displayed. This
might suggest an indexing problem with the New Mail folder. However,
Pegasus is also crashing, sometimes when clicking on this new message
and somtimes when just moving messages from one folder to another or
just simply navigating from one folder to another.
Number 1 thing to do is to ensure that your Sophos anti-virus software is not doing an auto-protect on any of the Pegasus Mail files. If you want to check for viruses in the incoming mail then use something like the extension VirScan to call the anti-virus program prior to opening an attachment..
Name of Program: VIRSCAN: Virus Scanning Extension for Pegasus Mail
I am in the process of migrating users from an old Novell Netware 5.1 server to a new Novell Netware 5.1 server. Each server is in a different NDS tree and users are logging\attaching to both servers. How can I tell Pegasus 4.11 and 4.41 to use the e-mail\home directory on the new Netware 5.1 server and NDS tree when users are still logging into the old Netware 5.1 server and NDS tree. I need users to log into both servers until the mirgration is complete and I have serveral users that use different PCs throughtout the day. I know I can get round this problem if I tell the PC to log into the new Netware 5.1 server and NDS tree, but what about the users that log into the old server 1st.
No: I was not until yesterday, when a friend spotted my error. I wish I had seen your post long before this but I regret to say I have not logged onto this site recently.
Many thanks for the trouble you and others have taken to help me. I am embarrassed at people's time I have wasted through not reading instructions carefully enough.
This means that you are then either downloading it 3 times or you may have a broken filter forwarding the message to you. Go to File | Network configuration | General and turn on "Create Internet session logs (advanced diagnostic use only)"
Checking this control tells Pegasus Mail to create special log files that show the entire exchange of information between it and the servers it connects to. Each session will be created in a file called TCPxxxx.WPM in your home mailbox directory (the "xxxx" is replaced by four digits). Creating session logs will slow down the performance of your system somewhat, and you should be aware that any username and password information exchanged between Pegasus Mail and the server will be shown in the log, *even* if you use SSL to secure the connection. Session logs are primarily useful if you need to debug a problem between Pegasus Mail and one of the servers it connects to - you should enable the option only on instructions from a system administrator or from Pegasus Mail technical support. [ Technical note: this control has the same effect as using a "-Z 32" commandline switch when you run Pegasus Mail ]
You can now try again to receive the mail and then look at the resulting TCP/IP debug file. Review of this file will tell you exactly what is going on between WinPMail and the server. If you only see the message downloaded once then it's something you are doing after it is downloaded.
I've just copied across my whole PC PMAIL folder (while tempoarily renaming the one on my laptop).
And on my laptop I am no longer being asked for my pop3 password on entry - so guess it must be a 'feature' of the new vesion.
I can see the point if each pop3 has a different user/password authorisation but it would be nice to have a 'one password fits all' flag at some point in the future.
In the meantime I'll try to revert the version on my laptop to the one on my PC.
Thomas, the unnecessarily strict parsing of date headers in Pegasus has been a point of contention for some time. I do not know of any other email client that is so restrictive.
Why not just bite the bullet and support having this changed? Pegasus chokes on just about any minor inconsistency in this header, including the completely innocuous redundancy of containing both the time offset xxxx code and the 3-character timezone identifier (GMT), for example. The absence of a leading "+" sign should also not corrupt the parsing -- the logical contents of the header are not changed by these "imperfection" in adhering to the strict standard.
Yes, email engines do not always encode Date headers precisely according to the "rules", but an email client should be able to deal constructively with these where the content is non-contradictory.
2. Instead of sending all messages at once, try opening the outbound queue, highlighting each message one at a time, and sending them individually. Once you discover the problem message, open it. It's possible your antivirus decided it didn't like the outbound message and deleted part of it.
We actully decided a while back to use Windows server directory permissions to force all internal mail to be sent to the users extenal address (delivered by Mercury) so that when people here were corresponding with people outside any reply all done by people outside worked to all the addresses here because they were not shoprt internal addresses but full internet ones. To do this each users mailbox needs setting such that only they and the account Mercury runs on can access their mailbox.
Having said that we do have some departments where all users can access each other's mail because they need to work that way.
Is "Enable display of clickable hyperlinks" is checked in Tools -> Options -> Hyperlinks? Is "Find browser automatically" checked on that page or did you have the path to the browser hard-coded to match your old computer?
If there is an html version of the message, Bearhtml will display/print it correctly. Use the "V" button to change view from plain text to html formatting.
[quote user="WWD"]Went into pconfig.exe and checked... it was all set to Y's. Weird. I've done many installations of Pegasus on different machines and never had this happen before. No idea why it would default to Y's this time? Anyway, thanks for your suggestion. I appreciate your reply. [/quote]
The exact problem has just occurred to me (but a day after installing Pegasus on a new machine--a day during which I ran it with no problems that I can recall); and the same setting to all Y's *also* happened to me. But, now that I have reset those all to N, I still get the same error message, presumably because I have not deleted the temporary directory. Where *IS* the temporary directory? So far my search for it has proved unfruitful.