1.  Setup a distribution list called RepliedTo (in Pegasus Mail press F6) . Add the email address of any and all mailing services like newsletters/blogs/listservs etc) This will prevent them from getting out-of-office messages.

2.  Setup a New Mail rule set that checks if current sender is already in the repliedTo distribution list (see Scan list rule trigger). If so just quit rule set

3. If sender not in list, then add an action to add sender to RepliedTo list

4. Send Out-of-office message to sender. ONLY DO THIS WHEN YOU ARE AT THE MACHINE, SO YOU CAN STOP PEGASUS MAIL IF THINGS SEEM TO BE REPEATING. 

As a precaution do not implement point 4. until the rest of your ruleset is working correctly.   Testing can be done quite easily by sending yourself a message from another email address, ie home email 

You have been warned... :-)

Martin 

I discovered, while using my crash-on-close Pegasus, that Pegasus was crashing when I selected the deleted mail folder.  While I couldn't delete the folder by selecting it first, I found that re-indexing with right-click, while not resulting in a successful re-index, did leave that folder highlighted as selected.  I was then able to delete it and re-create it with a message deletion.  There seem at the moment to be no further crashes on exit.

I believe Jerry is on to something.  Here is a sample User Defined Gateway.

             Gateway name :  MERCURY
           *New mail path :
   Is ? a program to run? :  N
    *New mail search mask :
      *Outgoing mail path :  \\machinename\path\MERCURY\QUEUE
   *Run for outgoing mail :
         *Filename format :  ~d~d.101
  Run to validate address :
    *Reply address format : ["~o" <~r>                   ]
  Accepts SMTP addresses? :  Y
  Simple message headers? :  'Glue' headers
    UUEncode attachments? :  Y
          Burst messages? :  N    Gateway processes BCC? : N
      Strip gateway name? :  Y
  Force all mail through? :  Y

Hi Guys,

I have moved my installation of Pegasus and Mercury to a new server as we had a flood at the weekend.

Everything seems to be working fine apart from the sending of emails, receiving emails is fine. I have tried my best to track down the issue which I think I have found.

 Pegasus is creating the .101 files in the correct queue for Mercury but I have compared it to an old .101 file and it is missing this from the top.

 $$ "Name" <sent@from.address>
T to@this.address

 I have tried editing one of the new .101 files and adding this manually and then Mercury will sent it. Does anyone have any ideas for getting this back?

Kind Regards

Dave

In addtion to Brian Fluet's comments you'll need to
enable IMAP access via GMails web interface.

Login to Gmail go to Settings > Forwarding and POP/IMAP
Enable IMAP
Auto-Expunge off
Move the message to the Trash
Do not limit the number of messages in an IMAP folder

Also at GMail - Settings > Labels
Select/deselect which folder you desire to Show in IMAP

Hello Jerry,

Something I found that may be helpful for others regarding my question about Pegasus being slow to launch.

I began having strange occurances with spam mail not being directed to the Junk mail folder and began looking at Spamhalter.  The database had grown very large so I deleted about half of it, but still the problem went on.  I decided to just delete all the Spamhalter database and rebuild it to a current status, ridding my disk of all the old files.

 I then disabled Spamhalter and the following day when I returned to work, opened Pegasus and it opened instantly.

I've conclude that the extremely large Spamhalter database was causing the launch problem and probably was also the reason it was taking mail so long to download.

 Hope that helps.. regards and thanks

[quote user="HB_wup"]So I will delete those emails in case you don't have another brilliant idea to save them.

But again: My pmail is working again so you saved my day! ;-))

 [/quote]

 I am happy winpm-32 is working well again with current and received messages.

Save those old moved message files until you can at least use Notepad to check and view them and at least determine who the messages were from. Even if messages are encoded the header portion and any plain text content will be readable in Notepad. It is  possible you may even be able to determine why all the messages failed to open properly.

Are any of the suspect messages actually blank, no contents, or any of them indicating that they all binary content with noting readable in Notepad? Those can be indications of what might be the cause of their failure and whether some other step in mail delivery chain may have converted the to binary or some Anti Virus software might have altered the raw messages or header  portion.

On occasion when marking several messages, 10-20, either for "Train messages as SPAM" or "Train messages as Not-SPAM" the SPAM Halter box that comes up will remain there for a minute - 4 minutes, or longer, which during that time period the entire PMail window will turn 'GREYED' out and show as Not responding or maybe just the small box for SPAM doing it's job will be 'Not responding'.  There have been times when Windows will come up with their window with the multiple choices, Check the web for a solution, Stop the application, or wait for it to finish.  Usually choose wait for app to finish and 15 minutes later Ctrl+Alt+Delete, Task Manager, Kill Process the only way to clear the hang.  Have not noted any common issues that could be causing this. 

Will be a little more observant as to when this happens and what is being done.

http://idw-doc.homepage.t-online.de/PMUtils/MiniDumpAndSources.zip

Is same as download button in Community downloads section. After install be sure to read the readme file also.

This could be within the software that runs the Microsoft Mouse, because; that is what caused my Wireless Keyboard and mouse to stop working about three weeks ago.  Could not find anyone that had an idea as to what was causing both the laptop keyboard and Microsoft Wireless Laser Keyboard and Mouse 6000 v2.0 to stop working.  Even Microsoft's Tech support told me it was the radio transmitter had died and go purchase a new one.  Well I did some investigating and discovered it was some software they had put upon my system for the Microsoft Keyboard & Mouse that had corrupted my registry file, tried to correct the problem areas and was not allowed to access or change any key, "Access Denied", so had to restore to an earlier time and that caused other issues that demanded more research and work.  Well just now getting back to some normal operation, not fully back yet.  So this problem just may be part of that left over screwed-up mess caused by Microsoft's Automatic Updates.  I have now set to 'inform and allow me to decide what and when to download/install.' 

 I am a troubleshooter and analyst not just a deleter and restorer without knowing WHY or what caused the problem.

Back to topic, seems a bit strange to me that my mouse wheel works just fine here on the forum for scrolling a page yet in Pegasus Mail in Text only or even the list of messages panel will not scroll using any mouse that is wheel capable.  Do have a generic wireless mouse with a wheel and it works just fine.  Just remembered JGSoft's EditPad Light v7.x is used by me instead of NotePad and the scroll works just fine in those text files.

Edited by NTxLS: adding more information

Hi Jerry,

 Thanks, I understand that the installer defaults to either c:\pmail, or the path of the last install.

My concern is that the installer offers you the opportunity to change the default, but does not check the validity of the path entered. (In this case I used the "Browse" button rather than type in a path directly). The installer then enters as much of the path as it can, then silently truncates the entry without complaint.

When you then invoke PMail after installing, it simply grinds to a halt, also without offering an error message to help you fix the problem.

 Cheers,

 Garry

Martin forwarded your problem message to me and I did some testing with IERenderer: It turns out that it takes extremely long in rendering this message, and trying to display it in IE itself shows the same delay (as well as Opera, Firefox doesn't do so). The culprit is the broken kind of image URLs used in this message (starting with a double slash) which needs to be fixed by whoever creates these messages in the first place. I've implemented a workaround (still failing to display the images, though) for now but this shouldn't be the final solution since we can only make guesses about what the originator wanted to code, and I'm not willing to double-guess for security reasons ...

"bfluet,"

 I have read that about -roam and understand it quite well, just @ 72.8 years of age the mind is not with me most of the time, what I am saying is when copying the "PMail.cfg" file over to the 'Micro SD' card "I" had neglected to edit that file and change to DRIVE letter from my USB to the card.  I went back through the operation that was supposed to have been done and thought I had done, WRONG!, it has been done now though.  Yes, I had all entries correct in the Icon (link) file to run Pegasus because my mail finally came down because of another ERROR I had made in setting up the connection to the server.  When that was discovered and my mail made a showing caused me think, "then this other problem could be very simple," "retrace your steps, DUMMY!!!"  Which I had just done before coming here to check on this DUMB mistaken request for an explanation.

 Yes, when I make an error or mistake I admit my error or mistake.  I take the blame for some things that go wrong and credit for those that do work well, the later one is the smallest list.  I am proud but very honest and will admit when needed.

 A very large Thank YOU!! for this HELP that is very well put and do not shy away from using the HELP file that came with Pegasus it is well written.  Just I have a problem in locating the exact point for the problem I am facing.  I read over some other parts and FORGET what I was originally looking for, side tracked, and then spend maybe 1 or 2 days before getting back to my original trouble.  So your quoting of the HELP File is good for me and maybe another out here that is has the same experience.

Thanks for the info.....I think I'll follow your advice!

I should have worded that a bit differently, with all my other problems that have driven me nuts my mind is just racing in many different directions.  Should have said, "which has priority for check mail?"  That would be the one measured in 'seconds', most often the other would be not very much traffic less often.

Not thinking very clearly yet, need to get back into the swing of things.

[quote user="sjmullock"]Are you saying it would be better to send all this information to "beta-reports..." rather than post here? Having asked the question here, should I also send the email off to "beta-reports.."? I didn't think to do this largely because I didn't think I was using a beta version.[/quote]

This account is just for any test results that might be helpful in further development of Pegasus Mail, but it's not a support account in general.

Under Tools go to Internet Options to setup for receive and send servers.

At the bottom of the General page click on the Pegasus Setup Wizard for easy setup.

Thanks for your patience, Jerry.  I added -ms to the end of both of the target lines, and now it works!

Jerry,

Your method is the best of course will fix it no matter what. The method I suggested comes in handy as a first step that is non destructive, can be done within the application.

Glad it was able to help. 

Jerry

Its exactly what I needed - Thanks

Reuven