All users were logged out of Bugzilla on October 13th, 2018

Program errors and closes.



14 years ago
13 years ago


(Reporter: ccorleyjd, Assigned: mscott)


Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Build Identifier: Thunde~1.exe Ver 1.02.0

Nearly every time I attempt to reply to e-mail in Thunderbird using Windows XP
professional, it errors and closes.  The details of the error show the version,
thunde~1.exe 1.02.0, and this Modname: ndpwsspr.dll ModVersion: Offset

It might happen when I send any e-mail but mostly when I reply and it happens
almost every time if not every time.  I then have to re-start Thunderbird.

Reproducible: Always

Steps to Reproduce:
1.  Open Thunderbird.
2.  Select an in-mail.
3.  Hit reply.
4.  Write a reply.
5.  Attempt to send

Actual Results:  
Error, program closes.

Expected Results:  
Sent e-mail, stayed open.

See above.
PLease provide a talkback ID from that crash.

Comment 2

14 years ago
What is a talkback ID???
Talkback is the crash reporter.

Comment 4

14 years ago
The only crash report that I get is from Windows, and what it says is what I put
in the original bug report.

 Can you help me or not?  I am frustrated with Thunderbird; it errors nearly
every time I try to send an e-mail now, and it is very frustrating.  I need
help.  I told you what the error message says.  That's the only information that
I have or know how to find.

Comment 5

14 years ago
ndpwsspr.dll is described here: - you're
crashing in a non-mozilla dll. You could try disabling this software. I don't
know anything about it.

Comment 6

14 years ago
This is EXCELLENT information. I will disabled MailDefense and see if the
problem continues to occur.  THANK YOU.
ccorley: did that fix your problem ?
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.