The perfect forum for discussions or technical questions about Pegasus Mail.
Thanks for the kind word.
The addition of the folder entry to the current HIERARCH file was unnecessary. Pegasus Mail would have detected the new folder files and updated HIERARCH accordingly. It was harmless though.
I assumed the folder had been deleted from within Pegasus Mail but the process would have been the same if it had been deleted from within a file explorer.
I'm glad you got it back.
Please also forward it to irelam@telus.net as I would like to check if Bearhtml has the same problem
Thank you
Martin
Thank you Martin for your response. I have utilized your suggestions and entered into the tools/options phase. I've also copied your reply for future use since I haven't had any recent messages to see if working or not.
Since others may be waiting and I have your reply on solution, I will simply mark as solved and wait for future incoming emails to see if working.
As mentioned before, thank you AND all the others fo the help
Thanks for the replies. I know the installation was C:\\Pmail (at least that!)
I will be seeing them online again after the weekend and will check with them about if IERenderer or BearHtml are in place. I am a bit rusty on this, but will read your replies as I speak with them and sort it out. My father in law is a loose cannon on a computer (who always throws his hands up saying "I didn't touch anything!" so it's not always sure what has been clicked on to create issues such as this. When I spoke to them yesterday they said all was well, once again.
[quote user="Redgy"]Only one minor problem now: starting Pegasus NOT as administrator but as LVANXXXX leads to a screen where it is announced that minidump ended unsuccesfully.[/quote]
This doesn't sound like a familiar error message: Can you please quote the exact error message (or post a screen shot of the error dialog taken via Alt + Print, the Options tab of this forum's editor allows you to attach files up 46 KB in size)?
I'd like to mention that there aren't any attachments in the messages that I am moving. So all the emails are no more than 10k or so. My disks are running 50% or more, free space. My boot drive is SSD and the mirrored drives are Sata.
One thing that could be an issue is that my mailbox is on the mirrored drive.
However, as an example, I can move 100Gb of files to the mirrored drive in about 10 to 15 minutes. Pegasus takes much longer to move much less although it is moving messages within the mirrored drive.
Because I splitted mailbox directory and New Mail Directory too, here some additions on New Mail directory:
As you see the problem with splitting Pegasus Mailbox into those two directories is, that IMAP takes a complete different mailboxstructure - there is no access at the home mailbox directory by Pegasus.
It seems David at some point of developement of Pegasus and Mercury didn't remember the opportunity of splitting [:(]
Olaf
Fair point. I seldom need to migrate when anything in my configuration will be changing -- always on Drive D, away from the OS -- but when I do, I've been handling that manually as well.
Not for everyone to do it that way, though. - CKM
Thanks Brian, that appears to have worked perfectly. I am always shy of anything that involves the registry.
Ian.
8 Jan 17 ARGH!! Years of struggle... and it may simply have been an anti-malware issue. To use SSL/ port 995 POP with Pegasus and mail.yahoo.com (and other) with Norton Internet Security, create Firewall exception, and be sure to move to top of "rules" list, ABOVE the rules that lock down everything not unlocked by "Higher" rules. "Years" because Norton, if that's what it was, only blocked the connection SOMETIMES. Eset's WONDERFUL security package dealt with the needs of my POP without these hassles. https://www.eset.com/us/search-brand/eis
(First, turn your anti-malware off, try a POP access. Works? Didn't before? Maybe anti-malware!
Turn it back on!! NOW!
Second.... using SSL? Be advised that the SSL code in Pegasus was overhauled early in 2016. The problems below went back to before that, but you should probably update yourself. The Help/ About pop-up may say "v 4.7" in the icon, upper right. LOOK AT THE "fine print", lower left. I think it was at 4.71 that the new SSL code was introduced. At 8 Jan 17, 4.72 was the "current" version.. and it still said "4.7" in the icon, upper right. (Not complaining! All of the 4.7xxx variants ARE, 4.7 versions... just be aware, that for the SSL upgrade, you need go beyond 4.70... and don't assume that "4.7" is telling you WHICH 4.7xxx variant you have!)
For Norton...
Go to Settings/ Firewall
Traffic Rules Tab...
Add.
Now... you CAN set up a rule that says "let anyone do anything". Resist the temptation to provide "generous" permissions when not sure what's needed.
What I used, which SEEMS to help... still early days, and we know how fragile email is, anyway...
Add an "ALLOW" rule. Next page
Allow connections TO **and** FROM other computers. Next page
(Specify WHICH computer: ) Allow only.. listed below. (add) Individually: pop.mail.yahoo.co.uk was the one I needed. Next page
(Protocol) I'd like to try just TCP. For the moment, I broke my "narrow permissions" rule and allowed TCP and UDP. And allow on 995. I also added 110, probably unnecessarily. Next page
I didn't ask for Security Log history entries. You mt want to, but probably not "needed". I turned OFF "Apply rule for NAT traversal traffic. Next page
(What to call rule)... anything you like! I used "Allow pop.yahoo.co.uk 995 access". Next Page
"Finish"... but you AREN'T FINISHED!!!... you must move your rule up the list, above the "block (almost everything)" rules which are there already, to establish default behavior.
Apply. Close. And your "can't fetch email" woes should be over!!! (^_^)
Contact details at http://sheepdogsoftware.co.uk... interested to learn if this helps anyone, or if there are errors. I don't monitor this forum closely, as much as I love Pegasus... have used it for MANY years.
===
P.S. : Sad to say, above does not seem to be "100%" solution. Still, even post-excepetion-rule-creation, getting times when access denied... but... less often? Maybe it's the way the wind is blowing? Or wishful thinking. It DOES, in limited tests, seem that turning off my Norton to download mail MAY be helping. Only a "clue", maybe, NOT an answer! (of course, Sigh.)
Problem solved - sort of. Found the place to make change.
Fire it up and modify the configuration settings to your liking (Tools > Options) then close it. This will create the configuration files. Be careful not to overwrite any of these. HINT: A print out of the PMAIL.INI file from the Admin mailbox of the Win7 install can serve as a handy guide for matching many of the configuration settings. Don't copy it though.
If you only have one POP3 & SMTP hosts then I suggest creating those manually. It's possible to copy the files from the Win7 install but I believe new ones are the better way to go when so little effort is required to create them.
This users recurring Pegasus Mail crash issue has me at my wits end so I may have to resort to attempting a manual install of your MiniDump in the hopes of generating a dump report that will expose whatever I am missing.
Yahoo is not the only one. Gmail also has an "Allow less secure apps" option the needs to be enabled for Pegasus Mail to POP messages. At least at one time it did. I haven't tested Pegasus Mail v4.7x with that option disabled.
Happy to report copy/paste of PM! and PMR files worked!
THANK YOU SO MUCH!
Bob
Just to wrap things up, I want to clarify that the dictionary is not at fault, and cannot be edited without rebuilding it. The only recourse is to add the offending word(s) into the user dictionary. This is true for Microsoft Office and all other dictionaries. The problem is simply that the AFF file rules need to be edited in your case. The only real alternative is to either add the word to your user dictionary, or ignore (all) spelling prompts for the word. If that gets tedious then you can avoid the prompt for the apostrophy'd word and spell it out in full, ie it's becomes it is.
Cheers and Merry Christmas from one old-timer.......
Martin
I would have to research what the others are although you can do this yourself using Han's guide to Pegasus Mail filenames and extensions. Find it at: http://www.vandenbogaerde.net/pegasusmail/pf_pmfiles.html
Just a remark on this thread. There is a known problem with leaving an IMAP session running, if Windows Power Management invokes the Sleep or Hibernation to partially shutdown the system. There is presently no "Keep-alive" for IMAP. So if you are going to be away from your PC for an extended period (ie over-night) I would recommend shutting down Pegasus Mail before leaving the PC.
Martin
Many of us see the "Not responding" verbiage in Pegasus Mail window title bars while Pegasus Mail is working. My guess is that it is generated by the OS when Pegasus Mail is busy stops communicating with the OS for a period of time (a way too short period IMHO). This started with the introduction of v4.70 when some processes started taking longer than they had. This gives the appearance of a hang of Pegasus Mail and the associated display of the "Not responding" verbiage. It only affects some of us and, AFAIK, the cause has yet to be identified. If this sounds like what you are experiencing then there isn't a solution. Only patience. A "wonky" internet connection could exacerbate the issue.
Also, if the Win10 machine is an upgrade from Win7 do a reinstall of Pegasus Mail on top of the existing one (backup of the mailbox directory(ies) first). We are suspicious that the Win10 upgrade process and the recent upgrade to the Anniversary edition sometimes adversely affect a Pegasus Mail installation.
Great! Glad you got it sorted out :)
