Arrrghh! A word of CAUTION to anyone trying this work-around:

The size of the original SPAMBUST.DAT is 25K, with my additions I got past the approx. 32K limit of Pegasus' internal file editor. Unfortunately, it silently trunkates the file. Editing is disabled, but saving is not.

Using an external editor works just fine, of course, but can't be invoked from within Pegasus.

Cheers,
Erik 

Thomas,

That sounds good!

I'd just like to stress that automatic whitelisting seems to work well for me - with the one exception that I don't want to be whitelisted myself...

Cheers,
Erik
 

It is possible to use an expression filtering rule to check the *X-UC-Weight* setting in the header of emails and automatically forward those with this header to the is_spam account on your system.  You can then use the same rule to file the messages wherever you want.

Thanks Thomas!

In your example, sure, that will throw the parser for a loop.  However, if one has to choose between an algorithm that is less than perfect and one that is just plain outright error-prone, if those are the only two choices, then doesn't it make logical sense to use the one that statistically will result in the least amount of errors (even if it isn't perfect)?

Finding a rogue "From ???@??? " in the body text of a message is going to be FAR less likely to occur than in messages with "from today" or "From everyone" or the other millions of other possible english phrases that now do result in a corrupted PMG index file being created, as my own experience showed me.

In any case, I know how to fix my own MBX files, to get my messages out and into a normal Pegasus Mail folder, so I'm going to do that and then never use the MBX format in Pegasus Mail again.   I just didn't realize Pegasus was not actually able to properly create a PGM index file from scanning a MBX file, like Thunderbird is able to create its index MSF file directly from a local folder (mbox file), until yesterday; it was like someone sucker punched me in the gut, having used Pegasus Mail since 1995 and never realizing this fact.

When starting Pmail for a particular user I get:

OLE error window.. no error number - OK

then

OLE Error - unable to access file - OK

I recreated a new mailbox and set it up and still get the error message.  This happens from more that one workstation.

Novell network, Windows Xp and Pmail ver 4.41 

Thanks,

Jerry Gunn

Metamora Township High School 

After having searched the web I can tell you that neither aol nor hotmail have a pop3 server, yahoo has one but you have to activate the option (I don't know how I don't use it).

For aol the only thing you can do if you want to use Pegasus Mail is to use IMAP (Tools/IMAP profiles), for hotmail you've 3 solutions, retrieve your mail via http (commonly called webmail) or to use outlook express or TB with an extension (webmail-hotmail).

Conclusion : you can use Pegasus Mail with your yahoo account only 

Thomas, believe it or not, it seems the upgrade did the trick. I upgraded and now I've had two test messages reaching addresses that did not get my mail this afternoon.

What's going on -- beats me. But thanks for your help. It's a great program and I suppose my next donation is overdue. I'll have to see to that.

Jaakko

 

[quote user="Greenman"]

Are there any diagnostics I can run or any logs Pegasus generates which may help identify the cause?

[/quote]

None that I can think of.  The only reason I know of that would cause a message not to be found in a folder is that it really is the folder but it's not displaying where you thing it should be displaying.  

You sir, are my hero.

Now i remember why i had left my local printer as default. It had accidentally gotten changed to the network printer.

makes perfect sense.

 thank you!
 

Thank you for the explanation.

I did go in to the authentication settings (Internet mail options>sending(smtp)>security and under SMTP Authentication I choise the 2nd option and put in my user name and password. When I tried to send mail I received this message:

[*] Connection established to 207.69.189.203
>> 0093 220-elasmtp-curtail.atl.sa.earthlink.net ESMTP Exim 4.67 #1 Mon, 21 Jan 2008 18:12:34 -0500
>> 0079 220-NO UCE.  EarthLink does not authorize the use of its computers or network
>> 0070 220 equipment to accept, transmit, or distribute unsolicited e-mail.
<< 0022 EHLO [192.168.1.101]
>> 0081 250-elasmtp-curtail.atl.sa.earthlink.net Hello [192.168.1.101] [24.136.136.144]
>> 0019 250-SIZE 14680064
>> 0016 250-PIPELINING
>> 0031 250-AUTH PLAIN LOGIN CRAM-MD5
>> 0014 250-STARTTLS
>> 0010 250 HELP
<< 0015 AUTH CRAM-MD5
>> 0082 334 PDI0ODA0LjEyMDA5NTcxNTVAZWxhc210cC1jdXJ0YWlsLmF0bC5zYS5lYXJ0aGxpbmsubmV0Pg==
<< 0058 bXVsZGVycyBjMjVhMzJiYmE1ZTU2MTcxN2QzMjgxYzQ1NjIyMDE5Ng==

Thomas,

Thanks, I have chosen the first option under authentication. Options 2 & 3 did not help, so I'll see how #1 functions. I have also enabled session logging and will post it when I encounter any more problems.

Sincerely,

Bob Mulder

Hooray, it worked!!! I am now sending as well as receiving!!! Thank you, thank you, thank you ---- and I will keep these instructions just in case!!

 Sue

Move them back one at a time.  i'd recommend that you move them off to another folder called "To Do" or something like that.  Leaving mail to lie around in the new mail folder for days, weeks, months is just asking for trouble.

Hi,

I'm using Pegasus Mail since many, many years without any serious problem till now. since 1 year I'm using Pmail 4.41 under Windows Vista 32bits Ultimate. I use Pmail under an admin account even if Vista UAC is active.

I use both POP3 and IMAP for accessing distinct mboxes with distinct identities.

Since some months it happens that Pmail, for unclear reasons, hangs while accessing IMAP mboxes (both remote inbox folder and other remote ones); mboxes that since minutes before it was correctly managing.

I was not able to identify what is the firing event of this behaviour. Sometimes affter disconnecting and reconnecting the remote IMAP mbox, PMail seems to solve the problem, sometimes I'm forced to clear the IMAP folder's caches, sometimes I'm forced to download the remote messages via POP3 in order to reduce the number of messages on the remote mbox (anyway always less than 100!).

I've also tried to remove an IMAP profile and recreate it from scratch, but it seems not able to solve the problem systematically.

If I try to log the TCP sessions, it seems PMail is not able to complete the remote folder fetch and close the TCP session (but I'm not sure this happens always!). At the UI level, when on a remote inbox/folder the number of contained messages is not longer displayed, that's the indication PMail is in this strange status. Then I'm forced to kill it and hope the problem is solved restarting PMail.

Any hints is appreciated. Thanks

   Dom
 

State.pmj under addressbooks IIRC, however I do not know this, it's simply that I do know that the system addressbooks data is stored at the user level.

[AddressBooks]
support.0.IGR7ZC2D.PMR=0,0,0,0,"0,0,0,0,0"
techsupp.0.PMAILSUP.PMR=0,0,0,0,"0,0,0,0,0"

[quote user="Thomas R. Stephenson"]

I've used the UTF-8 for a couple of years now and do not seem to have a problem.  That said, I can't be sure that the people receiving the mail with non-UTF mailer would complain either.

 [/quote]

Thanks Thomas.

I went with this one. I'm also under the impression it's more widely supported than the 8859 one, being more modern.

(can be wrong, of course!)

Best,

François

It's now working as I expected.

At the time of testing I already had a long standing address book entry for "Her" but no user named "Her".

After creating the user "Her" I then ran the tests sending mails to "Her" and "PM:Her" before opening and closing Pmail and ran into the previously described problem. Since then I have closed and opened Pmail and the same tests work OK.

I guess that Pmail needed to be closed to force something to be written to disc so that the function would work.

Bob

[quote user="aderoy"]

I am not the poster, but I use RAR compressed files due to much better compression ratios, and speed of compression. Also the available commandline does come in handy for scripting etc.

[/quote]

Not the point, the point is that ZIP is a very common format and supported directly by the Windows OS, RAR is not.  The receiver needs to have some sort of program on their end to receive this as an attachment.  When you send a RAR attachment you'll probably find a number of receivers will ask you to send a ZIP archive instead. 

Again, my question, do you select to send RAR instead of ZIP when sending email attachments?  Unless I were to receive this sort of archive on my home system I'd not be able to use it.