Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Text does not send with message

  • 13 답장
  • 2 이 문제를 만남
  • 3 보기
  • 최종 답변자: Matt

more options

In addition to the usual problem: "There was a problem including the file file:///C:/DOCUME~1/Dave/LOCALS~1/Temp/nsemail.html in the message. Would you like to continue sending the message without this file"? Thunderbird says that mail was sent successfully. When I check the sent box whatever I typed in the text field is gone and my recipient says that the text field is empty. The subject line text goes through without a problem. any ideas? Thanks

In addition to the usual problem: "There was a problem including the file file:///C:/DOCUME~1/Dave/LOCALS~1/Temp/nsemail.html in the message. Would you like to continue sending the message without this file"? Thunderbird says that mail was sent successfully. When I check the sent box whatever I typed in the text field is gone and my recipient says that the text field is empty. The subject line text goes through without a problem. any ideas? Thanks

선택된 해결법

Matt; Thanks for getting back to me. The solutions sited in the link you sent me is for incoming mail, and sending and receiving linked to ssl cache respectively. Neither proved fruitful. But, they got me going in the right direction. This is what has so far worked for me. I added the the Avast certificate as directed in the Thunderbird certificates and deleted the entries entitled "Avast Mail Scanner" from the servers tab. https://www.avast.com/en-eu/faq.php?article=AVKB91#artTitle I ran through the posts in this thread: https://forum.avast.co/index.php?topic=78428.msg1245756#msg... then I asked this in the Avast form: https://forum.avast.com/?topic=182308.new;topicseen#new From the answers I was able to "solve" the problem. Open the Avast interface and open settings. In General settings scroll down to exclusions. Click on browse. In the window that opens open respective folders "C:\Documents and Settings\[user]\Local Settings\Temp". Check the box next to Temp to select the path. Click OK. Add "\nsemail.html"to the end of the path. Click Add and then click OK. Click OK to close Settings. This should work for Windows XP which is apparently the only affected OS.

문맥에 따라 이 답변을 읽어주세요 👍 0

모든 댓글 (13)

more options

lots of ideas. one two that might help. 1 kill your anti virus program. or See https://wiki.mozilla.org/Thunderbird:Testing:Antivirus_Related_Performance_Issues#AVAST for the workaround you have to insert in Avast to make it behave.

more options

선택된 해결법

Matt; Thanks for getting back to me. The solutions sited in the link you sent me is for incoming mail, and sending and receiving linked to ssl cache respectively. Neither proved fruitful. But, they got me going in the right direction. This is what has so far worked for me. I added the the Avast certificate as directed in the Thunderbird certificates and deleted the entries entitled "Avast Mail Scanner" from the servers tab. https://www.avast.com/en-eu/faq.php?article=AVKB91#artTitle I ran through the posts in this thread: https://forum.avast.co/index.php?topic=78428.msg1245756#msg... then I asked this in the Avast form: https://forum.avast.com/?topic=182308.new;topicseen#new From the answers I was able to "solve" the problem. Open the Avast interface and open settings. In General settings scroll down to exclusions. Click on browse. In the window that opens open respective folders "C:\Documents and Settings\[user]\Local Settings\Temp". Check the box next to Temp to select the path. Click OK. Add "\nsemail.html"to the end of the path. Click Add and then click OK. Click OK to close Settings. This should work for Windows XP which is apparently the only affected OS.

글쓴이 DavidSorge 수정일시

more options

To quote from the link I gave you Avast caused slowness and errors regarding nsemail.HTML

The release of Avast 10.3.2223 ( We think it is that version) has resulted in issues with avasts preventing Thunderbird from functioning correctly. The workaround appears to be to create an exception in avast for the file nsemail.html in your computers temp folder.

So your have gone the long way to get to exactly the same location. You created an exception in Avast.

more options

I have XP SP3, Avast and have the problem described.

"There was a problem including the file file:///C:/DOCUME~1/Dave/LOCALS~1/Temp/nsemail.html in the message

Adding the exclusion in avast to the file which could not be included solved the problem immediately "C:\Documents and Settings\[user]\Local Settings\Temp\nsemail.html"

more options

There was a problem including the file file:///C:/DOCUME~1/FABIAN~1/LOCALS~1/Temp/nsemail-3.html in the message. Would you like to continue sending the message without this file?

Tried the format advised in other help but the path (like mine says "-3") which differs, so based on my extract how would I input that exclusion in Avast ?

more options

Your really asking the wrong people. Ask Avast how to use their software.

Or you could just clean out your obviously "full of junk" temp folder to it does not have the 3.

I have no idea what operating system your using as you just jumped on the end of someone else's question with your question about avast. But there is generally a disk cleanup entry on the system tools menu in Accessories on the start menu. Use it.

more options

Matt

Appreciate the prompt response On XP Will do the disk clean up - not sure where I clean up the temp junk file - will search for it Thanks

more options

Back again, had to relocate. Matt, the instructions in the link you sent me to, were for me, a non power user, too vague. I found an article on setting the TB side that was very clear. It's in one of those links in the chosen solution. The Avast side not so much. So when I figured out how to add the exceptions in Avast I attempted to write out what I did clearly and precisely, hoping they would make there way to the article: "https://wiki.mozilla.org/Thunderbird:Testing:Antivirus_Related_Performance_Issues#AVAST" and hoping that they could help others. Mozilla encourages users to get involved, so I did. When Einstein was born he didn't know how to read or write but by the time he was 26 he proved that E = mc2. There must have been a time you didn't know anything about FF or TB, and there are many of us out here that still don't. To simply say E=mc2 may work for an expert, but then they wouldn't have had to ask in the first place, but it doesn't help neophytes.

more options

MurderMystery said

Matt Appreciate the prompt response On XP Will do the disk clean up - not sure where I clean up the temp junk file - will search for it Thanks

In the same place I told you it was. Start menu > accessories> system tools > disk cleanup. to phrase it another way.

more options

MurderMystery said

There was a problem including the file file:///C:/DOCUME~1/FABIAN~1/LOCALS~1/Temp/nsemail-3.html in the message. Would you like to continue sending the message without this file? Tried the format advised in other help but the path (like mine says "-3") which differs, so based on my extract how would I input that exclusion in Avast ?

You need to put the Avast exception in TB and the TB exception in Avast. I'm not sure by what you wrote exactly what you did. If the "-3", as Matt seems to indicate, has to do with junk, clearing it out is something you should do. If you are worried that the "Path" doesn't look exactly like mine then try it. Avast looked at the "package" and didn't like what it saw. It's what they call a false/positive. TB responds by suggesting that you just send the email without nsemail.html, or in your case nsemail-3.html, which as you know means that the body of your mail doesn't get sent. In any event the exception has to be the exact string that the Path is, or it will be ignored. Hopefully we can get a more defined answer as to what the -3 is all about as I'm very curious to know.

more options

DavidSorge said

Back again, had to relocate. Matt, the instructions in the link you sent me to, were for me, a non power user, too vague. I found an article on setting the TB side that was very clear. It's in one of those links in the chosen solution. The Avast side not so much. So when I figured out how to add the exceptions in Avast I attempted to write out what I did clearly and precisely, hoping they would make there way to the article: "https://wiki.mozilla.org/Thunderbird:Testing:Antivirus_Related_Performance_Issues#AVAST" and hoping that they could help others. Mozilla encourages users to get involved, so I did. When Einstein was born he didn't know how to read or write but by the time he was 26 he proved that E = mc2. There must have been a time you didn't know anything about FF or TB, and there are many of us out here that still don't. To simply say E=mc2 may work for an expert, but then they wouldn't have had to ask in the first place, but it doesn't help neophytes.

The link I provided was delibaratly vague on how to manage avast as it is with all the other anti virus products mentions. We do not have the resources to maintain a library of instruction for products that change daily. We can not even cope with our own updates. As far as the avast certificate goes, personally I consider being asked to compromise my security for such a stupid reason as justification to remove the software. I don't care how it scores in the various tests. If those writing the product think they should be in the chain of trust, let them spends the millions of dollars required to audit their business and software to get placed in there. Instead they ask individual users to place all their financial trust in them and most do. Those certificates protect your online banking. Manually adding to them is something not to be taken lightly.

more options

Thanks to all who responded

used this exact line :*\nsemail.html and touch wood it has worked on 5 test emails sent.

So hoping it is now resolved

more options

I little background on windows temp files and Thunderbird.

When a temp file is required, Thunderbird asks Windows to create a file. in this example nsmail.htm. Windows replies, already got that one. so Thunderbird adds a number and asks again. This cycle can go on through a hundred or more request reply sequences before an acceptable name is created.

Now these existing files are simply rubbish, left over from previous use and not deleted for a thousand and one reasons. The reality is Windows does an truly awful job of managing it's temp files and the folder fills with gunk. I have seen occasions where systems are crawling along and opening the temp folder takes an age to disclose more than 10,000 orphaned temp files. Clearing out these files makes the system respond faster, frees disk space and should really be done as a housekeeping task regularly.

Anyone who has used windows knows it gets slower the longer you use it (in months and years terms) clearing out the temp folder is one of the things that restores that just installed speed. If you use internet explorer there is an internet temp folder with similar gunk.

Now on a similar background. This time on Windows file systems.

Once upon a time (BEG) there was DOS and that was all there was to store files. this came with an inherent limitation of 8 characters to a file name followed by up to 3 characters as a file extension. It was in this era that we got things like PDF and DOC when Microsoft released windows 95 they also created a new naming convention where files could have names 264 characters long. to allow interoperability with the older system, the new system also stored an 8.3 file name. this is what is seen in a path that looks like C:/DOCUME~1/FABIAN~1/LOCALS~1/Temp/nsemail-3.htm The ~1 is a dead giveaway to this as it is used to make sure the 8.3 names contain no duplicates when the long name is truncated. For instance the .DOCUME~1 refers to C:\Documents and Settings.

Given that in the intervening years Microsoft have moved from FAT through the FAT32 to NTFS file systems. Why are anti virus programs still using the old 8.3 names? That I do not know. Perhaps they have simply never been updated in the last 20 years. Or perhaps there is a valid reason, like the long names are not available to the kernel.