Your problem isn't with Pegasus Mail - it's something at a lower level. Error 276B is the code for "WSASYSNOTREADY". Here's the description from the WinSock error reference:

-------------------------------------- cut here --------------------------------

WSASYSNOTREADY (10091) Network

subsystem is unavailable

Berkeley description: No equivalent.

WinSock description: The WinSock implementation cannot

function at this time, because the underlying system it uses to provide

network services is currently unavailable.

User suggestions:

• Check that the WINSOCK.DLL file is in the current path

• Check that the WINSOCK.DLL file is from the same vendor as your

  underlying protocol stack. You cannot mix and match (WINSOCK DLLs must

  be supplied by the same vendor that provided your underlying protocol

  stack).

• You cannot use more than one WinSock implementation simultaneously.

  If you have more than one WINSOCK DLL on your system, be sure the first

  one in the path is appropriate for the network subsystem currently

  loaded.

• Check your WinSock implementation documentation to be sure all

  necessary components are currently installed and configured correctly.

-------------------------------------- cut here --------------------------------

I'm sorry I can't elaborate much on this, but all Pegasus Mail is doing is reporting an error occurring at a lower level - it's not actually causing the error itself.

About the only thing I can suggest you try is to go into Tools|Options, select the "Advanced" page, and in the group of controls labelled "Load Windows Internet Services (WSOCK32.DLL)", change the setting from "on demand" to "always" or vice-versa.

Cheers!

-- David --

Hi all !

Well, although I checked my filtering rules before posting on the forum, I decided to give it another try since there was little chance of any kind of corruption in the filtering features of my dear Pegasus Mail. Note that this was the first suggestion of David, and it proved that I indeed put a rule that was not properly written, and here it is for the next idiots like me who should think deeper before crying out to the wolf : it is an expression based rule and it was of this form "if the headers contains *[special offer]* then move to folder X". Of course the error is in the use of "[]". Also, it is plainly trivial now that my problem had nothing to do whatsoever with Vincent's plug-in, it just happened that I updated the plug-in and put the new rule in the same period ... bad luck I guess.

Bye !

Ginhead.
 

[quote user="chas"]

Hi Peter,

Thank you.

I can dowloand the messages using Netscape Messenger 4.8 and Thunderbird so the messages download. I've followed others instrcutiuons re: waht to input inot the POP3 Receving Mail and SMTP Outgoing Mail but it doesn't download the messages for soem reason. It says it's connecting the mail server but it never downloads.

I imagine it's the Settings but 2 Pegaus users said they were correct so I'm baffled.

I appreciaite your help and suggestions.

 

[/quote]

It's not the settings within Pegasus mail you have to work with.  It's never able to connect to the POP3 host.  You have to find out why your system is not allowing Pegasus Mail to connect to the outside world so it can connect to the POP3 host.

I have thought about doing this and I'm sure I could make this work, but it would just be double duty everytime I need to email a customer a system message ( IE I also use this for cc declined messages, auto renewal messages, etc, etc)....   I do that a lot during the course of a day ( I'd guess on average 25-30 times ).

It would be much simpler of course if Pegasus just did it.  David, I'd be willing to Donate to get this fixed, would that help?  I'm getting a bit desperate here, please help?

Hello,

    If the message you want to print is an html message, you can try to use Bearhtml to print it. First make sure you have Bearhtml's attention by keying in Shift + F1. If Bearhtml help appears, all is well, key in Shift + F1 again to return to the message.  Now try Shift + Ctrl + P to have Bearhtml print the message.

If that does not produce the right results, you might try:  Edit Bearhtml.ini to state PrintSetup=yes, save the file then restart Pegasus Mail. Re-open the message and key in Shift +_ Ctrl + P and this time a Print Setup dialog appears with a Print Propertys/Advanced button. Check the setup and advanced setup pages for alternative tray selections and set as required. Click Ok to actually print the message.
 

HTH

 Martin 

Can you provide any more information? Exactly at what point does the crash occur? Does the crash message say anything that might assist us?

Cheers!

-- David --

[quote user="qa007"]Hello!

Is it possible to find anywhere a step-by-step description how to set up a Gmail account in Pegasus Mail for MS-DOS v3.5 for DOS?

Thanks for your help!
[/quote]

 It can be done but the effort required is way too tough if you are starting from scratch using some old XT/AT machine that can't run WinPmail..  If you are already using PMail with a POP3 account though you can use SSL Tunnelling to make the connection to GMail using the proper connection setup.

(a) -POP3-

  Server host name: pop.gmail.com
  User name: <your_user_name>@gmail.com
  Password: <your_password>
  Server TCP/IP port: 995
 

(b) - SMTP via SSL -

  Server host name: smtp.gmail.com
  Server TCP/IP port: 465
 

Personally I use PMail with Mercury/32 handling all the mail to the internet, including GMail with little or no difficulty.  It uses the same pmail.cfg file as WinPMail.
 

[quote user="David Harris"]

Works fine for me...  I can only fix problems I know about, and increasingly, I can only fix problems I can reproduce.

If you can tell me how to duplicate this error, I'll be happy to look into it for you, but I've just spent about ten minutes deleting, moving, adding and otherwise shuffling things in and out of folders, and in all cases, the title bar updated correctly.

[/quote]

I've seen this in all Windows installations of  Pmail I had or have done for somebody. Perhaps it is what mr. Bogaerde wrote, although I do not use the WindowBar.

Here are few window-grabs of my Pmail window (got new mail, moving to junk, deleteing) -> my Pmail window-grabs

Perhaps it helps you recreate it ...

Bye, LesLes
 

I f you want to be really lazy, (don't we all)  then simply create a rule to automatically delete messages from your Spam folder when they are more than "n" days old.

Martin 

David -

You were on the right track, the issue IS with the NOS.  It could have been in the initial installation of Mercury and it's alias file or a migration from Bindery>NDS.  Either way, ConsoleOne revealed under a user object's Other attributes tab, a setting for EMail Address unilike the E-mail address attribute under the General tab, which is blank for all users in this eDir context.  The Other EMail attribute is not present for user objects created after the migration to NDS.  The Other attribute EMail setting had a 0SMTP:aliasname set, which was changed, the NLMs unloaded/loaded, and now the user's e-mail has the desired specification wrt Sender and Message-ID.  Best to tidy up by removing that Other EMail attribute from all user objects.

Thanks again.  Cheers!     -Robert

My, my.  What a compendium of mis-steps and disappointments!

 It seems as though the biggest problem you encountered was trying to download several thousand emails, and failing to set the all-important switch in Pegasus to "download only unread emails".  That is why it started to download all of them a second time.  A common error -- I even forget to set this occasionally when setting Pegasus up on a new system.

All in all, you really set yourself up for disappointment with *any* email client the way you went about it.  Your past attempts with others should have given you a clue that small steps are better than big ones when venturing into unfamiliar (to you) territory.  But you just dove into the pool without checking how deep the water was.

 Happy landings, wherever you email quest takes you.
 

Bingo, that's the solution. I have about 5 domains that the email server handles so just like you have above I link them together with 'ANDNOT'. So far this seems to be working. Thanks for your input on this!

Chris 

[quote user="James Plummer"]

I have been a user of Pegasus for  over 10 years.  Recently I have had this problem, that Pegasus just  crashes . Sometimes I am writing an email, and am in the program for some time and  VROOM  everything crashes and all the information is gone, and Pegasus crashes. I  now have to first write  my email in MSWord, and then copy and paste into Pegasus in case it crashes again. I  saw some reference regarding antivirus that may be causing it. I wrote to Pegasus sometime back, but my email was ignored.

Where did you write?  I can't think of any mail that is ever ignored.
 

Is there any method to fix this inconvenience. Changing from Pegause to another email would set me back years, so i am forced to stick with Pegasus, can anyone help me to solve this problem.

James

[/quote]

Strange, what version of WinPMail are you using?   In any case, what kind of crash are you getting?  Are there error messages saying the program has crashed (usually 3 of these) or does the program simply go away.  If you get the crash messages you then need to look at what is happening to Pegasus Mail; if the program simply goes away then you need to look at the system level to find the program/function  that crashed that caused the OS to shutdown WinPMail.  You mentioned the anti-virus program.  Which one are you using, some are worse than others.  Are you using an anti-virus proxy between WinPMail and the server?  Is the anti-virus program scanning the WinPMail directories?  Either of these could cause a crash if the anti-virus program grabs a file away from WinPMail for any reason.

[quote user="Peter Strömblad"]You can use the forum: "" here at the community.[/quote]

Thanks!  I managed to miss that one.

 - Vince 

Thanks Irelam. Finally got it sorted. Vista seems determined to make things twice as complex as they ought to be. Anyway, Virscan safely ensconced and working well. Thanks again.

[quote user="bfluet"]

I am curious whether the delay is there when doing a delete without the message going to the Deleted messages folder (hold the Ctrl key down when clicking Yes in response to the delete confirmation prompt).

[/quote]

This could be it.

Deleting messages also started going slow for me in the last few days.

After reading your post, I went to my Deleted Messages folder and deleted the first message which it did straight away. The second deletion took a bit longer. I then tagged all 1800 odd messages and Pegasus basically froze, although after killing Pegasus, when I fired it back up, there was only 150 odd messages left to delete, so it was just super busy deleting messages.

So after I fired Pegasus back up, I selected about 15 messages in my Deleted Messages folder at a time and deleted them, which it did slowly. After doing that a couple of times I chose the option to Recover Deleted Space on the Deleted Messages folder. This did the trick. All messages I deleted after that, deleted instantly.

So I'm thinking the first problem was the excessive number of messages in the Deleted Messages folder, and the second issue was a fragmented or maybe corrupted Deleted Messages file.

Hope this helps.

Cheers

I assume that you are correct, and as the folder was created as part of a corruption shutdown, I will delete it.

In passing, I would note that finding anything via the index is often very difficult. One would expect an entry under link, but none exists. I originally searched for icon, without success, and so on.

Is there anyway of logging suggested index entries and shortcomings?

Thank you for your help. 

Good thing I've already come up with an acceptable, even if not perfect, workaround: generate a "dry run" which processes 100% of the records in the file.  The only thing that will be incorrect is the precise time.  But being off by a few minutes (or maybe just 1 or 2 minutes in some cases) shouldn't cause too much concern.

Thanks for the quick response.
 

[quote user="dleigh"]

Would simply like to suggest that changing "text" URLs into hyper-links be added as an option. ...

[/quote]

This is already an option. The only thing is that it only converts what looks like URLs into hyperlinks only in plain text messages. In HTML messages, PMail is assuming if the writer wanted a clickable link, they'd have made it an <a ..> link to begin with. Maybe I'm already used to that, since my general-purpose editor does pretty much the same thing. It will hyperlink anything that looks like a URL--BUT IF AND ONLY IF the document is not already an HTML document. If it is an HTML document, it won't do any conversions, since most often, those conversions mess up the way the writer originally designed the HTML. Personally, I agree that trying to "second guess" HTML documents is more headache than it's worth; Not only does it increase the load on the CPU and slow down rendering the message, I've found it often makes HMTL line up all messed up and half the time unreadable until I read it as plain text!

Regards,

C. M. 

Current versions have limited import/export capabilities via the now ancient "PMIMPORT" DOS utility still provided with the program. V5 will support import/export in a variety of formats, including CSV, TSV and Vcard.

Cheers!

-- David --