opening the new mail folder crashes PM (Windows 7)

Michael

posted Jul 12 '10 at 1:34 am

[quote user="djweber"]Yes, I followed the link and read Paul Stephanson's message. He suggested

(1) setting a limit on how many bytes of any file to have scanned (to 8000) and

(2) moving all the CNM files to another folder and then bringing them back one at a time until finding the offending file.

Like the case Paul was responding to, I suspected it would be a large file. To my surprise, after adding all other files, the offender turned out to be the one and only 0-byte file, absolutely empty![/quote]

The message I linked to provides two links, the first one pointing to the zero byte file issue, the second one to what you describe above. The zero byte file issue can be fixed permanently by updating Spamhalter like described in the first post linked to.

[quote user="djweber"]On the other hand, it would be nice to have a tidy list of all valid extensions, and what they correspond to.[/quote]

Goto Han's page.

[quote user="djweber"]Yes, I followed the link and read Paul Stephanson's message. He suggested(1) setting a limit on how many bytes of any file to have scanned (to 8000) and(2) moving all the CNM files to another folder and then bringing them back one at a time until finding the offending file.Like the case Paul was responding to, I suspected it would be a large file. To my surprise, after adding all other files, the offender turned out to be the one and only 0-byte file, absolutely empty![/quote]The message I linked to provides two links, the first one pointing to the zero byte file issue, the second one to what you describe above. The zero byte file issue can be fixed permanently by updating Spamhalter like described in the first post linked to. [quote user="djweber"]On the other hand, it would be nice to have a tidy list of all valid extensions, and what they correspond to.[/quote]Goto <a href="http://www.vandenbogaerde.net/pegasusmail/pf_pmfiles.html" target="_blank" mce_href="http://www.vandenbogaerde.net/pegasusmail/pf_pmfiles.html">Han's page</a>.

			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

djweber

posted Jul 10 '10 at 10:21 pm

Friends,

I recently got a new laptop with Windows 7 Ultimate (w/ 32 bit). I ported my mail folder over, loaded the most current version of PM, and all has been proceeding well. I did notice some infelicities when returning from a state of hibernation, but nothing serious. Now however,...

Any demand on the New Mail folder, whether trying to open the folder or attempting to download files, provokes a program failure. The error-message details:

Problem Event Name:   BEX
Application Name:   winpm-32.exe
Application Version:   4.5.2.0
Application Timestamp:   4b543cb5
Fault Module Name:   winpm-32.exe
Fault Module Version:   4.5.2.0
Fault Module Timestamp:   4b543cb5
Exception Offset:   0018b976
Exception Code:   c0000417
Exception Data:   00000000
OS Version:   6.1.7600.2.0.0.256.1
Locale ID:   1033
Additional Information 1:   33ea
Additional Information 2:   33eae82957ecd0537fe531be3014db14
Additional Information 3:   8eb7
Additional Information 4:   8eb7f7b2e539e98aa015fb4c3ac518b0

The curious thing is that I can open the program and do other things, like sending mail, opening other (real) folders, and such, but making any demand on the New Mail folder brings Pegasus to its knees. I've used Pegasus for long time (ever since the days of DOS!) and coped with various problems, but nothing so baffling as this.

HELP!! --David

P.S. For what it's worth, here's the details of how I'm set up:

WinPMail version: Version 4.52 (Win32), Jan 13 2010
Language resources: Standard UK English resource set
Extension Manager version: 1.13
Operating mode: Standalone
User name and ID: Single-user mode, 0
Windows version: 6.1
Windows flag word: 0
WINPMAIL.EXE directory: C:\PMAIL\Programs
Home mailbox location: E:\DJW\DJWEBER
New mailbox location: E:\DJW\DJWEBER
TMP environment variable: C:\Users\djweber\AppData\Local\Temp
TEMP environment variable: C:\Users\djweber\AppData\Local\Temp
LAN-based SMTP support: N, N, N
NetWare MHS support: N, N, N
Built-in TCP/IP support: Enabled
- WINSOCK version: (Not loaded)
- WINSOCK path: C:\Windows\system32\WSOCK32.DLL
Commandline: -A

Friends,I recently got a new laptop with Windows 7 Ultimate (w/ 32 bit). I ported my mail folder over, loaded the most current version of PM, and all has been proceeding well.&nbsp; I did notice some infelicities when returning from a state of hibernation, but nothing serious.&nbsp; Now however,...Any demand on the New Mail folder, whether trying to open the folder or attempting to download files, provokes a program failure.&nbsp; The error-message details:&nbsp;Problem Event Name:&nbsp;&nbsp; &nbsp;BEX &nbsp; Application Name:&nbsp;&nbsp; &nbsp;winpm-32.exe &nbsp; Application Version:&nbsp;&nbsp; &nbsp;4.5.2.0 &nbsp; Application Timestamp:&nbsp;&nbsp; &nbsp;4b543cb5 &nbsp; Fault Module Name:&nbsp;&nbsp; &nbsp;winpm-32.exe &nbsp; Fault Module Version:&nbsp;&nbsp; &nbsp;4.5.2.0 &nbsp; Fault Module Timestamp:&nbsp;&nbsp; &nbsp;4b543cb5 &nbsp; Exception Offset:&nbsp;&nbsp; &nbsp;0018b976 &nbsp; Exception Code:&nbsp;&nbsp; &nbsp;c0000417 &nbsp; Exception Data:&nbsp;&nbsp; &nbsp;00000000 &nbsp; OS Version:&nbsp;&nbsp; &nbsp;6.1.7600.2.0.0.256.1 &nbsp; Locale ID:&nbsp;&nbsp; &nbsp;1033 &nbsp; Additional Information 1:&nbsp;&nbsp; &nbsp;33ea &nbsp; Additional Information 2:&nbsp;&nbsp; &nbsp;33eae82957ecd0537fe531be3014db14 &nbsp; Additional Information 3:&nbsp;&nbsp; &nbsp;8eb7 &nbsp; Additional Information 4:&nbsp;&nbsp; &nbsp;8eb7f7b2e539e98aa015fb4c3ac518b0 The curious thing is that I can open the program and do other things, like sending mail, opening other (real) folders, and such, but making any demand on the New Mail folder brings Pegasus to its knees.&nbsp;&nbsp; I've used Pegasus for long time (ever since the days of DOS!)&nbsp; and coped with various problems, but nothing so baffling as this.HELP!!&nbsp; --David &nbsp;P.S. For what it's worth, here's the details of how I'm set up: WinPMail version: Version 4.52 (Win32), Jan 13 2010 Language resources: Standard UK English resource set Extension Manager version: 1.13 Operating mode: Standalone User name and ID: Single-user mode, 0 Windows version: 6.1 Windows flag word: 0 WINPMAIL.EXE directory: C:\PMAIL\Programs Home mailbox location: E:\DJW\DJWEBER New mailbox location: E:\DJW\DJWEBER TMP environment variable: C:\Users\djweber\AppData\Local\Temp TEMP environment variable: C:\Users\djweber\AppData\Local\Temp LAN-based SMTP support: N, N, N NetWare MHS support: N, N, N Built-in TCP/IP support: Enabled &nbsp; - WINSOCK version: (Not loaded) &nbsp; - WINSOCK path: C:\Windows\system32\WSOCK32.DLL Commandline: -A

Michael

posted Jul 10 '10 at 10:50 pm

[quote user="djweber"]Any demand on the New Mail folder, whether trying to open the folder or attempting to download files, provokes a program failure. [/quote]

Please check whether any of the links in this post helps.

[quote user="djweber"]Any demand on the New Mail folder, whether trying to open the folder or attempting to download files, provokes a program failure. [/quote]Please check whether any of the links in <a href="/forums/post/24050.aspx" target="_blank" mce_href="/forums/post/24050.aspx">this post</a> helps.

			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

djweber

posted Jul 12 '10 at 12:27 am

Yes, I followed the link and read Paul Stephanson's message. He suggested

(1) setting a limit on how many bytes of any file to have scanned (to 8000) and

(2) moving all the CNM files to another folder and then bringing them back one at a time until finding the offending file.

Like the case Paul was responding to, I suspected it would be a large file. To my surprise, after adding all other files, the offender turned out to be the one and only 0-byte file, absolutely empty!

My guess is that anyone could replicate the problem I had by creating an empty file X.CNM and putting it into the folder where CNM files go.

By the way, I used PM for a LONG time and must admit that until yesterday I did NOT know that the new message files were those with the extension CNM. I take that as an indication of how good PM is!

On the other hand, it would be nice to have a tidy list of all valid extensions, and what they correspond to.

And it would be nice to have an external utility that would say what files are irrelevant. Having carried PM forward for more than a decade, I suspect that there's some crud in that I ought to remove.

Well, thanks again for your help.

Best, --David

Yes, I followed the link and read Paul Stephanson's message. He suggested(1) setting a limit on how many bytes of any file to have scanned (to 8000) and(2) moving all the CNM files to another folder and then bringing them back one at a time until finding the offending file.Like the case Paul was responding to, I suspected it would be a large file. To my surprise, after adding all other files, the offender turned out to be the one and only 0-byte file, absolutely empty!My guess is that anyone could replicate the problem I had by creating an empty file X.CNM and putting it into the folder where CNM files go.By the way, I used PM for a LONG time and must admit that until yesterday I did NOT know that the new message files were those with the extension CNM. I take that as an indication of how good PM is!On the other hand, it would be nice to have a tidy list of all valid extensions, and what they correspond to.And it would be nice to have an external utility that would say what files are irrelevant.&nbsp; Having carried PM forward for more than a decade, I suspect that there's some crud in that I ought to remove.Well, thanks again for your help.Best, --David &nbsp;

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history