[quote user="radhx"]I will try and check out what I can do with Comodo Firewalls' setup, though I have already defined winpm-32.exe as safe/trusted application. Are there any other PMail EXE's / DLL's which I should indicate to my firewall, which could be raising the hackles of Comodo?[/quote]

I don't think this will help since it appears to inject its modules into any running application, so only removing it completely might solve your issues, I'm afraid - unless there's a way of exempting Pegasus Mail completely from being "firewalled" (software firewalls are useless anyway, BTW, it's enough to have Windows' own firewall running).

Hi,

I had reported this PMail crash on close some time back. Thought it was due to xclose plugin causing the error as crashes stopped for a while after removing xclose files.

http://community.pmail.com/forums/thread/30893.aspx (at the end)

But crashes are occurring again at the time of closing PMail though not regularly (where as it was every time when xclose was present).

I have already sent the crash dump to support.

Thanks & Regards,

Rad.

[quote user="radhx"]But crashes are occurring again at the time of closing PMail though not regularly (where as it was every time when xclose was present).

I have already sent the crash dump to support.[/quote]

Rad, the only crash dump there was related to S/MIME handling according to your own additional information, and it actually happens in TER. Do you use the latest version of the S/MIME extension?

Hi Michael,

Sorry, I forgot to check the queued mail, crash dump sent now.

My S/MIME plugin is version 1.1.3.4 dt. 2011-01-04, 23:11:32,  916.8KB within the PMSMEn.zip, I hope that is the latest one.

(when I try to update S/MIME plugin using s/mime-frontend->About->Update option, I get error "Can not read internet data".)

Today I downloaded PMSMEn.zip again from link in your mail, but that exe is dt. 2010-12-11 19:23:58 916.7KB.

So I have not changed my S/MIME plugin, please advice if otherwise.

I tried signed mail without "decrypt on download", and the status bar is displaying the signature details correctly.

But still the colouring rule is not being applied to that mail with signature. The only difference being previously there was only this rule, and now as I have stopped using Auto-filtering, there are other mail-to-folders rules along with this signature colouring one.

Thanks & Regards,

Rad.

[quote user="radhx"]Sorry, I forgot to check the queued mail, crash dump sent now.[/quote]

Raj, please open a new thread about S/MIME if you want to share this issue on the forums (the encryption forum might be the proper place), here's what your dump reveals about the supposed "on close" crash: Once again there appears to be a safeguard/firewall/anti-malware application involved, according to your dump the crash happend within modules of your Comodo firewall. Guess it's time to issue a more general warning here: This is the third kind of such an application causing trouble, the first one (also causing crashes) was the Spybot tool, and I encountered problems

myself

(hangs when clicking links after wakeup from stand-by mode)

with the Threatfire software - so much about system "protection" ...

ok... I am moving the S/MIME part to encryption forum.

I will try and check out what I can do with Comodo Firewalls' setup, though I have already defined winpm-32.exe as safe/trusted application. Are there any other PMail EXE's / DLL's which I should indicate to my firewall, which could be raising the hackles of Comodo?

Thanks & Regards,

Rad.