Closed Bug 252697 Opened 20 years ago Closed 20 years ago

blocked email and incorrect alert: "Unable to write the email to the mailbox. Make sure the file system allows you write privileges, and you have enough disk space to copy the mailbox."

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 166111

People

(Reporter: joshua, Assigned: mscott)

Details

Attachments

(2 files)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040614 Firefox/0.9
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040614 Firefox/0.9

Used TB for two weeks then get this alert, and can no longer view messages
already delivered.  Can read messages downloaded to other folders, and can
download from other accounts.  Message is inappropriate there is not permissions
or space problem.  Once encountered it will occur ever time TB is run.  Some
other bug caused my inbox file to be deleted, once this occurred downloads were
allowed again, it only took two days before the block occurred again.  Bug
report 166111 is similar but this is apparently a new and different bug.  I am
using TB v0.7.2 (20040707).

Can not create any logs, TB crashes immediately if using a logging batch file to
start.


Reproducible: Always
Steps to Reproduce:
Once the bug occurs it will happen every time on launch.  However, I can not
intentionally create the bug, from a blank TB install.
Do you have any anti-virus software running which could block access a mail file
because it has detected a virus in it?
I am receiving the same error message, "Unable to write the email to the
mailbox. Make sure the file system allows you write privileges, and you have
enough disk space to copy the mailbox." This happens upon checking the POP
server for new messages. 

This started yesterday when I upgraded to version 0.8 (filename
ThunderbirdSetup-0.8.exe). I downloaded the latest nightly build this morning
(20041005) but the problem persists. 

I've isolated the error to specific incoming e-mail messages. If they are
removed from the incoming directory on my mail server, other messages download
without a problem. I have four of them, but all are basically the same -- an
error message received from MAILER-DAEMON@yahoo.com informing me of a delivery
problem. I have just sent an attachment of one of them.
I am getting this error in my default account on one of my 5 email accounts. I
tried deleting messages through the web email to see if it was a specific email
and it was not. I setup a new additional profile and was able to download the
email in the new profile. I am still unable to in the default profile.
I just got this with TB1.0 also. But was a specific message though,
unfortunately, I cannot attach the exact message, as I had quite a few spam
messages and I deleted them all in a single batch, on the webmail...
Today this bug happened for the second time for me, but this time I deleted the
messages (with webmail) one at a time, so I identified this one as the one with
problems.
Just happened again to me.
And, again, mail was from MAILDER-DAEMON@yahoo.*

I guess they got some nasty malformation in that email, ok... but Mozilla
shouldn't say "permission error" anyway ;-)
Joshua Kolden(reporter), Ruth Rogers, Jeff and Lapo Luchini, please note that
saying "me too" only is not so effective for problem analysis.

To all of you, answer to question of comment #1 by ostgote first.

Anti-virus software is one of the most suspectable criminal on your situations.
And it is much more suspectable, because "MAILER-DAEMON@<popular-mail-domain>"
is frequently used sender name pattern by many spamers or virus mail senders,
and it has relation to at least one case of this bug.
See Bug 116443 for similar situation(mail folder file is deleted in this case).

What is your anti-virus software setting?
See setting for "*.msf"(control file of mail folder file) and "file with no
extention"(Unix Mbox format mail data file) and directry for mail folder("Local
Directry" setting of "Server Settings" of the account).
 
If problem occurs again, check files for the mail folder, <folder_name> file and
<folder_name>.msf file, about file size, timestamp of file, contents of file.
Then check anti-virus software's log.
(In reply to comment #8)
> Joshua Kolden(reporter), Ruth Rogers, Jeff and Lapo Luchini, please note that
> saying "me too" only is not so effective for problem analysis.

Excuse me??? 

I didn't say anything remotely resembling "me too". Over two months ago I gave
complete information on when and how I got the error AND spent a great deal of
time isolating the messages that caused it so I could upload one for you to look
at. I also mentioned that I had three more that were the same, if one wasn't
sufficient. 

Which part of that is just saying "me too"? For crying out loud, I'm a nursing
student, not a programmer. Do you do your own x-rays before going to the doctor? 

-Ruth Rogers
(In reply to comment #9)
> I didn't say anything remotely resembling "me too".
Thanks for your effort and sorry if you feel bad by my "mee too".
My "mee too" meant "saying 'this problem occurs on my environment too'" and has
 not bad meaning.
This is usueful and important sometimes because it makes "problem occurs" more
certain.
And you added mail sample and it is far more above my "me too".
This sample mail is also useful when the mail itself is the cause of problem.
This is true when mail display corrupton problem.
But mail data itself can not be the cause of the unexpected alert message
written in summary.

In additon, there was comment #1 already.
"Asking more detailed information" is usually done by more matured person in
programing area, because here is bugzilla.mozilla.org for developing software
instead of forum.
He thinks "problem occurs" is cetain and suspects a software, then asked about 
   "environment problem occured".
So information of "this problem occurs too" became not so effective for problem
analysis already, then I asked his question again to all of you.

Sorry again if you feel too bad by my "mee too".

*** This bug has been marked as a duplicate of 166111 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: