Closed
Bug 188717
Opened 22 years ago
Closed 22 years ago
If I attempt to send a mail, it cannot save the mail to my "sent" folder and sends a blank mail
Categories
(MailNews Core :: MIME, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: efaust93, Assigned: bugzilla)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130
When I send a mail, I recieve the message "The message was sent successfully,
but could not be copied to your sent folder. Unable to open the file
c:\DOCUME~1\EFAUST93\LOCALS~1\TEMP\nsmail.eml. Would you like to return to the
compose window?" Mozilla also sends a blank e-mail to the recipient. This
happens no matter who is logged into the workstation and no matter what profile
I use.
Reproducible: Always
Steps to Reproduce:
1. try to send a mail (happens every time)
2.
3.
Actual Results:
I receive the error message that I stated and only a blank e-mail is sent.
Expected Results:
It should have saved the mail in my "Sent" folder and sent the e-mail with the
message that I specified.
I have uninstalled Mozilla, rebooted, then reinstalled Mozilla (1.2.1). I
reverted down to a previous version of Mozilla (1.1) and received the same
results. I tried Mozilla 1.3a to see if this would resolve the issue and it did
not.
I deleted the Mozilla directory after I uninstalled Mozilla and this did not
help. I deleted the nsmail.eml file also and it created nsmail-1.eml and gave
me the same error.
I even went as far as to uninstall Mozilla, remove all of Mozilla's registry
entries, reboot, then reinstall Mozilla and create a new profile but I received
the same results - I can only send blank e-mails and it does not save the mail
in my sent folder.
Comment 1•22 years ago
|
||
Do you use Imap or SMTP ?
Reporter | ||
Comment 2•22 years ago
|
||
I am using SMTP
Comment 3•22 years ago
|
||
Please check Paths and account/server names in your prefs.js file.
Also check out bug 71618
Reporter | ||
Comment 4•22 years ago
|
||
I upgraded to Mozilla 1.3 and this problem went away.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•