Community Discussions and Support

The perfect forum for discussions or technical questions about Pegasus Mail.

0
-1
closed
ullic posted Jun 29 '17 at 2:51 pm

[quote user="Brian Fluet"]There is one known condition where drag and drop doesn't work (with attached mailboxes); there may be others.  Loss of data is not a known subsequence of this failure though.[/quote]

Copy and Delete is the method now and it works (or at least kind of, sometimes it stops, some mails can't apparently be copied for whatever reason).

Anyway just expected that, if Drag&Drop is implemented, it wil work.....

Thank you anyway

 - Ulli -

 

0
-1
closed
Brian Fluet posted Jun 27 '17 at 7:35 pm

Glad it's fixed.  Don't be surprised if you have to do it again following a future Win10 update.  Hopefully just a resetting of the default apps and protocols will do the trick.

 

0
-1
closed
Brian Fluet posted Jun 29 '17 at 4:10 pm

I'm clueless.  I never see a "From:" prefix and only see the "To:" on copies of sent messages. When you look at the raw headers does the From: header contain a second "From:" (eg: From: From: Pablo)? 

This would explain the appearance of "From:" but wouldn't explain the "To:" when moved to a different folder.

When you move a message to a folder do you use a procedure other than drag and drop or the Move button?

 

0
-1
closed
rocket posted Aug 19 '17 at 4:14 am

[quote user="Brian Fluet"]

You forget, or are not aware, that filing trays are virtual, not physical, so to Pegasus Mail, a duplicate folder name is a duplicate folder name, regardless whether it appears in the root of the folder list or in a tray.  Avoid duplicate folder names throughout the folder tree.[/quote]

True, I was not aware of filing trays being virtual as this has never been involved in any issues for me before. And I agree to avoid mail folder names that are the same name due to this bug.

[quote]I agree that there should be a warning when a duplicate occurs but there isn't.  Adding prefixes (as Greenman suggested) or suffixes (my preference) to folder names in trays can be beneficial in helping prevent duplicates.  It can also be beneficial in rebuilding the tray structure should it ever be lost due to a corrupted HIERARCH.PM file.[/quote]

I've gone through the manual and under filing tray manipulation, including creating, nothing is mentioned in the manual or is there any warning against using duplicate mail folder names. And yes, I have applied a workaround at this stage. It's not ideal, but it is working now, but looking a bit untidy.

If you are going to provide filing trays, there will always be the possibility of duplicate mail folder names. It appears this has been an issue since filing trays were introduced to Pegasus. I would have thought there would have been a mention in the manual or a fix applied by now.

Anyhow, luckily Google saved my day and brought me to this thread. All is good for now as I've been able to find my "missing", copy to self, emails.

Thank you all. 

0
-1
closed
Greenman posted Jun 20 '17 at 5:20 pm

[quote user="Shades"]

The window that comes up IS "Search folders for text" but it is opened by Edit|Find Text or Ctrl F (with no message(s) open)

 Either way it still does not work

 [/quote]

Help us with this. When you say it is not working are you seeing an error message? Or, does the dialog crash etc.?

Tell us, step-by-step how you are searching for the string, making sure to include the exact search string you enter, and the search options you select. If you are not seeing errors or a crash, you may simply need to change your search criteria. 

0
-1
closed
Brian Fluet posted Jun 18 '17 at 9:05 pm

I received the posts Martin references in my email so the distribution part of it seems to be working as well. 

 

0
-1
closed
Brian Fluet posted Jun 9 '17 at 2:52 am

Restart Pegasus Mail if you haven't.

If it doesn't show, consider whether you might have inadvertently dragged and dropped it into an adjacent folder.

If that is ruled out, close Pegasus Mail then use a text editor to open HIERARCH.PM file located in the home mailbox directory.  Do a search for "junk".  The entry for the default junk mail folder will look something like this:

0,0,"1827B06E:2300:JUNK","3C514713:My mailbox","Junk or suspicious mail"

Yours may look very different or may not exist at all.  The goal is to see if there is an entry for the junk mail folder. 

In a HIERARCH.PM entry, the content between the set of quotes at the end of the entry is the Pegasus Mail folder name and the content between the colon and the second quote is the filename of the folder file.  So in the above example, the Pegasus Mail folder name is "Junk or suspicious mail" and its filename is JUNK.PM.  Your filename may be something like "FOL?????.PM".  Post back and let us know...

1. What the entry in HIERARCH.PM is, if one exits

2.  If one does exist, look to see if the folder file also exists.  If it does, do you want to try to repair it or trash it and create a new one?

 

0
-1
closed
Brian Fluet posted Jun 8 '17 at 2:38 am

A corrupted new message file could be causing a problem during the processing of new messages that Pegasus Mail does during startup.  To check this, use a file explorer and navigate to that users new mail directory and move out of that directory all files with the .CNM extension that have a date stamp newer than the last time that user successfully started Pegasus Mail.  If that user can now start Pegasus Mail then you know its a bad new message file.  Note: A .CNM file of zero size is probably the problem file so remove it and test a startup.

There isn't an easy way identify a bad message file if it's not of zero size.  All you can do is to move a few message files at a time back into the mailbox directory testing after each move until you identify the bad file.

If you don't know where that users new message directory is you can first check the default location of C:\PMAIL\MAIL\username.  If they're not in the default location you can start Pegasus Mail as one of the other users and click the 'Info" button in Help > About Pegasus Mail.  The resulting display will contain the path to the mailbox directories.

BTW, be sure you've allowed Pegasus Mail to sit in the "not responding" state for several minutes before assuming it has crashed.  That "not responding" state displays much too quickly, not recognizing that Pegasus Mail is busy with some background task.  Processing a large number of new messages and/or new mail filtering could result in the display of "not responding" until the processing is complete.

 

0
-1
closed
Michael posted May 31 '17 at 12:52 am

[quote user="Tom Barkas"]Trouble is I can only figure it out by trying it. I've no idea what a Unix Mailbox Format is or an MBOX and what email programmes use them and am only vaguely aware what IMAP is and don't have access to an external mail server as far as I know, but I expect I'll muddle through when the time comes!.[/quote]

See below for what Pegasus Mail's own help provides to answer your questions:

0
-1
closed
David Harris posted May 23 '17 at 6:06 am

[quote user="cogx"]

http://www.securityfocus.com/archive/1/540601

"v4.72 build 572
Vendor supposedly fixed: January 21, 2016

May 19, 2017 : Public Disclosure"

So,  that post says the flaw is still working in 4.72 build 572, but it was supposed to have been fixed in January 21, 2016 which should mean it was fixed in 4.72 build 572 (Feb 19, 2016)?

[/quote]

I think it's just a typo - the actual bug was fixed in January, in both Mercury and Pegasus Mail. I haven't as yet done a release because, frankly, this is a very minor security issue.

What the vulnerability entails is a common issue where an application allows Windows to search along the path for DLLs when loading them. In theory, this means that someone could place a DLL in a directory in the path earlier than the real version, and Windows would load the bogus one when the load call was made. In practice, this is really hardly an issue: Mercury is typically used as a service, so it's nearly impossible to inject a bogus DLL into the path before it starts up, and while it could possibly be exploited in Pegasus Mail, it's hard to see what benefit it would provide.

In both cases, the solution was easy (it's actually a problem in the TER editor I use, not in Pegasus Mail itself), and I'll have maintenance releases out shortly that address it.

Cheers!

-- David --

0
-1
closed
Art Layton posted May 21 '17 at 10:20 pm

Thanks for your response. I guess I should change my password for my comcast.net account?

the good news! I can send and receive email again. If I didn't have thousands of messages and hundreds of addresses in Pegasus, I would have switched to Gmail.

0
-1
closed
Brian Fluet posted May 18 '17 at 10:14 pm

An internet session log should help identify the sending problem.

One thing to check right off the bat...

In the Security tab of you SMTP host configuration is a setting called "Only use SSLv3...".  It should be unticked unless you are in the very rare circumstance of needing to use an old implementation of SSL.

 

0
-1
closed
Brian Fluet posted May 16 '17 at 6:55 pm

[quote user="breezes"] 1) Why are the moved emails not deleted from the "copies to self" folder?   [/quote]

I don't have an explanation as to why you aren't seeing them deleted.  I would restart Pegasus Mail then test using both the Move button and drag and drop.  Both methods should work.

[quote user="breezes"] 2)  Why is Pegasus willing to make two copies of the email in John Doe's folder, same datestamp and content, rather tan saying "Look here dummy, you already have that email in this folder"?[/quote]

Messages stored in folders are not stored as individual files but appended to a single file.  Pegasus Mail does not check the content of the folder file for duplicate content when you add a message to it. 

 

0
-1

Just some comments:

  • Pegasus Mail runs fine from the root of C: under Win10.  I haven't encountered any need to change permissions.  FWIW, each PC user needs full control over their mailbox directory.
  • The splash screen flash without Pegasus Mail opening is an indication that it can't find the mailbox directories.
  • You can specify the username in the command line using the -I option (eg: C:\PMAIL\Programs\winpm-32.exe -A -ms -I AA)
  • Migrating from machine to machine via copy/paste works fine as long as the paths are identical.  Best approach is to do the copy, run it once to create the registry that records the run-from location, then run the installer over top of it.  The installer creates the shortcuts (you'll need to tweak) and the registry entries needed for full functionality.
  • If you are routinely bouncing between two PC's and don't need Pegasus Mail as the default mail program consider running it from a flash drive.  I do this with the Pegasus Mail install I use for following the support list and the activity on this community forum.  It goes with me to work and when I travel. 


5.86k
32.91k
22
Actions
Hide topic messages
Enable infinite scrolling
Previous
Next
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft