Done. Thanks.

[quote user="sirob"]

I have been using Trend Micro Internet Security on 2 Win XP systems for many years with no problem.

I recently updated to Trend Micro Titanium and experienced severe problems with Pegasus. Trend Micro had no solution for me, so I was forced to uninstall and re-install Titanium, and re-install the previous version.

I am also running Titanium on a third system under Win 7. The only problem here is that when I delete a Pegasus message it takes about 4 seconds for the action to complete - is this normal?

[/quote]

AV programs have been know to cause problems with Pegasus Mail, some more than others.  Trend Micro Titanium may fall into the "more" category.  The rule of thumb is to exclude mailbox folders from active scanning because of conflicts that can occur when Pegasus Mail tries to access/process a file at the same time the AV scanner has a hold of it.  Deletes can cause a good bit of file activity in the mailbox folder so Trend Micro scanning could certainly be having an impact.     

[quote user="bfluet"]I hope so.  It's v2.4.4.2 which I downloaded and installed yesterday. [/quote]

So I have no idea, please provide a test message (via About dialog's contant link, a zipped CNM file would be best) and tell me which URLs I need to test.

[quote user="sirob"]BTW, should I also install this for my Win XP version? [/quote]

Check the IERenderer history at the download site for other issues having been solved or new features you might like to use since I fixed the IE 9 issues.

[quote user="pamela_downer"]Reporting back to say the problem fixed itself after about 10 days. Nothing changed except the passing of time.[/quote]

Most probably there are two issues to solve:

Set Tools => Options => Advanced settings => Load Windows Internet Services to Always (if it isn't already) and for working with IE 9 (I must have missed your original post for unknown reasons, sorry).

Thank you!  The first part went perfectly.  I will try the switching bit later, as it is not so immediate an issue.

I appreciate your very helpful guidance[:)]

Edit: double post due to slow internet connection, please disregard

 Moderator: This thread can be removed, I am unable to do this myself.

[quote user="Henrik Rosenø"]

Noone seems to answer. Should I create a new thread? Or seek help elsewhere?

[/quote]

OK. Now I am moving this to a new thread. The new thread is here: http://community.pmail.com/forums/31507/ShowThread.aspx#31507

[quote user="Sonnenberger"]Oder habe ich dich falsch verstanden? [/quote]

Das wäre halt die wahrscheinlichste Lösung gewesen, andere sind z.B. zu finden. Allerdings würde ich gerne wissen, welche Mail dafür verantwortlich ist: Wenn also eine CNM-Datei das Problem verursacht, dann bitte gezippt an "beta-reports [at] pmail.gen.nz" senden. Wenn das alles nicht hilft, dann bitte das MiniDump-Tool benutzen (ggf. noch mal nachfragen).

If you are installing using new 4.61 exe download it will install to c:\pmail by default and is where most should accept default offered. That may or may not be your current install but it is probably  where it is now also though path to winpm-32.exe might be just slightly different as new full clean install places the exe's in :c:\pmail\programs

The install archive exe does not contain configuration data at all and only default mail folders plus sample or introduction message only if a clean full install. *IF" old setup is detected then  installer will pick up and use old location, old settings, and old folders and messages and that can be very good or very bad. Very convenient and easy if you want to save everything "old" but very bad if you want a new clean installation. Good if all old settings were correct and very bad if there just one or more critical settings are not correct. That is why reinstall is hardly ever necessary and seldom fixes any user problems. To do that or get a clean install you must relocate Pegasus Mail files now on drive and preferable encase them within a compressed archive so installer can not find them during clean full install. Then later after up and running with new install you can copy back the messages and messages folders and address book information and such, keeping in mind that anything that had errors before will still have them after copy to new install also. What should never be copied back to new install is the old configuration and settings or  pmail.ini or related *.pnd files if there is any known defect you are trying to repair by new install. Only restore old settings and ini file if old setup or version was working correctly when  last used.

Hi people,

I'm new here.

I just installed 4.61 and was wondering if there's a way to automatically include a business card graphic in each sig of a new message?

I tried it like this in the sigs but it didn't work:

Author of The Planetary Bill of Rights Project
If you value your freedom, read it!
The Book is at Amazon.com: http://tinyurl.com/45wbn6v
<img src="http://www.planetarybillofrights.org/card.jpg">

Now works!!! Thanks!!!

I also had to check "Disable certificate validation"

[quote user="idw"][quote user="marius"]Ah, that is certainly a good way around it. Thank you very much for your swift reply![/quote]

If you update IERenderer to the the menu entries will be back.[/quote]

Sorry, it was supposed to fix this, but I had to fix it again, the next update will provide a working solution.

Hello.

Just started to configure Pegasus.

I made-up a few accounts I have.

But

in the left column there is none of the account names vsible.

When I want to write a message, 

- I see no possibility to select my snder-account. How do I select?

- the edit-form only displays TO, but no FROM. Where can I make visible the FROM line?

[quote user="David_himself"]Yes, this machine still has IE6.  (Maybe I should update to IE9 now.  I always resisted updating to IE7 because it was even worse than IE6 and ran the risk of messing up settings for QuickLaunch, default mailer and default browser.)[/quote]

IE 9 isn't available for XP, but I've been using IE 8 on my XP machine without any troubles - well, my default browser being Opera, of course ...

And: The "drop target" error is an IE 6 error returned by the different zoom handling it provides. BTW, here's ...:

This behavior is by design. The following OLECMDID values are not defined for use by the IWebBrowser2::ExecWB() method: [...]

Clearly something about drop targets, I guess ...

Every 4 years or so I join here to ask a Q or two. Have used Pegasus (4.52(WIn32) for 10 years+ and am a cyber-challenged old professor.

Recently I got error messages when I attempt to alphabetize Inbox and Pegasus closed, now when I Send and nothing mailed. Cannot Debug -- Pegasus closes .

Can I download Pegasus again and have all my folders saved? Or repair somehow.

Many thanks,

Neil Ross
Berkeley CA
USA

[quote user="Thomas R. Stephenson"]>And no, Pegasus Mail should not be looking in other fields for a Date: field data since in a RFC 2822 message it must be present.[/quote]

It must be.... yet it is not.  So in the interest of error checking, wouldn't it be better to take the date of the last "hop" shown in the header instead of some random date that it happens to show because some variable wasn't cleared from the last message in the list?  I've already asked the offending party (before I ever posted here) to clean up their headers because they are non-compliant.  That's the obvious part.  I was just hoping that PM could do a better job in the event of this error.  BTW, they (the company that was sending the emails with no date) never responded to my mail which is typical of dealing with big companies.

As to the header, here's the header.  Only thing really missing is "Date:".  I've blocked out some data to protect the innocent.  :)

Received: (qmail 30531 invoked from network); 11 Jun 2011 23:21:33 -0400
Received: from mail04.firstdatacorp.com (HELO firstdatacorp.com) (204.124.84.42)
  by hosting2.qishost.com with (DHE-RSA-AES256-SHA encrypted) SMTP; 11 Jun 2011 23:21:33 -0400
Received: from ([10.174.197.253])
    by mail04.firstdatacorp.com with ESMTP  id 5502511.10727113;
    Sat, 11 Jun 2011 22:22:08 -0500
From: Gateway <g*****@linkpt.net>
To: Me <****@****.com>
Message-ID: <338419280.159741307848907248.JavaMail.websrvr@10.174.196.29>
Subject: <order number here> processed
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-EsetId: D316EF209881C4378051
X-PM-PLACEHOLDER:                                          .

Message body here.

My PC just updated IE 9 yesterday, thanks for posting the fix so fast.  I suspect you will hear more and more of this problem as the days go by....

According to this post, "The method of identification for all attachments depends on the settings in two files: FILETYPE.PM & MIME-MAP.PM ... The default files have not been updated for some time."

http://community.pmail.com/forums/post/20740.aspx

Does anyone have a set of patches to these 2 files, or updated versions incorporating patches?

In particular, the various OpenDocument file types and extensions (.odt, .odp, .ods, etc.) used by Openoffice, LibreOffice, etc. are not given the proper mime-type headers by Pegasus.

These file types are described e.g. here:

http://en.wikipedia.org/wiki/OpenDocument

Hopefully these will be updated in the next Pegasus release, but patches might be easy for someone knowledgeable to provide in the meantime.

The problem appeared to be related to WINSOCK.DLL in the list could apparently have been due to the Service Pack 3 installation, nothing to do with PM operation.  It seems the "problem" is known from a Google search and a number of solutions were offered mainly for installations of SP2.

Can't connect to internet [Solved/Closed]
http://en.kioskea.net/forum/affich-9657-can-t-connect-to-internet
http://en.kioskea.net/s/Winsock.dll+problem+after+installing+win+xp+sp3

How to Troubleshoot and Fix Windows XP SP2
Limited or No Connectivity Error Message
http://www.pchell.com/support/limitedconnectivity.shtml

Repair Windows XP TCP Network Settings With WinSock XP Fix Utility
http://www.watchingthenet.com/repair-windows-xp-tcp-network-settings-with-winsock-xp-fix-utility.html

From reading the pages the fact that I re-booted the machine may have reset the TCP/IP stack.  There is even a MS patch (KB884020) quoted for one version of the problem with SP2.   It seems the glitch was an operating system fault.

 Rodney Fry