Closed Bug 108892 Opened 23 years ago Closed 23 years ago

Cannot send HTML mail

Categories

(MailNews Core :: Composition, defect)

Product:
MailNews Core
Component:
Composition
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 108912

People

(Reporter: joao, Assigned: bugzilla)

Details

(Keywords: smoketest) 

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.5+)
Gecko/20011105
BuildID:    2001110503

After composing a Email message in HTML with text formatted in some style (like
italic or bold, for example), I click on Send and the message is not sent, no
matter which of the 3 options I choose: HTML+Text, HTML only or Text only!

Reproducible: Always
Steps to Reproduce:
1. In "Mail & Newsgroups Account Settings" choose "Compose messages in HTML
format" and click OK.
2. Type Ctrl+M to open a new mail message window and fill the "To" and "Subject"
fields as you like.
4. In the body, just type the text "Hello" and format the text with a style like
italic or bold.
5. Now try to send the message, in "HTML only" first and then using the other
two options.

Actual Results:  The email message is not sent, even though Mozilla reports no
errors.

Expected Results:  A "Sending Messages" dialog box should appear and, seconds
after, the message should be sent.
seeing this on commercial trunk builds:

windows 2001-11-07-06-trunk
linux 2001-11-07-06-trunk
mac 2001-11-07-04-trunk

Error Message: regarding SMPT server not found or set up incorrectly.  

setting are fine.  same server setup with 4.x on these test machines works fine.
Severity: major → blocker
Keywords: smoketest
OS: Windows 2000 → All
Hardware: PC → All
Just download the latest build (2001110703) and noticed the bug didn't occur
anymore.
I downloaded commercial build from 2001-11-07-09 on win98.  This problem still 
exists.  I still get the SMTP error and Send failed.  
However, the same build on POP accounts work.  I was able to compose an html 
message on a default pop account it worked.
Default imap account sending is still failing on the respin build too.  
Confirming.
Status: UNCONFIRMED → NEW
Ever confirmed: true
tested respin for windows build 2001-11-07-09-trunk and still see this on both 
POP and IMAP accounts
Okay as I said if you have pop as your default account in a profile(first 
account) sending an html mail still worksforme on the build I mentioned.
If you have a profile with imap as your first account and pop as your second 
account then both fail to send html mail. 
any interesting JS errors coming up on the JS console when you send? Tasks /
Tools / Javascript Console.
Accepting.
Status: NEW → ASSIGNED
Using Build 2001110703 Win2K I am able to send html mail using my imap account.
I would suggest trying a different(new) profile to see if that works to narrow
down the test cases.
Using the same build as I mentioned if you create a new profile with 
2001-11-07-09 build sending html mail works and does not give me any sending 
error.  I would like to mention that I did not use any activation and I did not 
create any webmail account. This is my imap test account that I created in a new 
profile.  
Using this morning WIndows debug build, I can send HTML email without problem. I
have only one IMAP account setup.
SMoketester says not reproducable with new profile...should this be marked 
INVALID then?
Severity: blocker → critical
See also Bug 108912 which has better description of the error while sending. 
Varada wanted to know if a few old builds could be checked to see when this 
happened. 

Here is some information:
I have a profile which was migrated a while back. This just has one imap 
account.  I had used this profile to check this bug using 2001-11-07-09 build. 
Means I opened this profile using today's build and failed to send.
I opened the same profile and tried to send from the imap account from the 
following builds and still failed to send.  
2001-10-26-06, 2001-10-29-11, 2001-10-30-03, 2001-10-31-06.

I have another profile which is a migrated one a while back again which is an 
imap account. But this account uses SSL and I get prompted on the certificate 
dialog. I had not used this profile with today's build. I launched this profile 
with all the old builds mentioned above. Sending html mail worked fine.  I also 
used this profile which has worked for all the above mentioned old builds and 
launched this with today's build and it still was able to send html mail.

So the only thing I could think of is as soon as installing today's build which 
ever profile you used after the installation has some profile corruption.  This 
profile will fail to send html mail using any old builds.  
But if you use some other profile which was not used after installing today's 
build then you can send html mail with the old builds as well as today's build. 
Hope this helps!


Using Sheela's profile which fails to send (using the 11/7 build) we found a
workaround. Go into Account Settings, select the Identity panel, select the
Advanced button. It states that it is using the Default server. After changing
it to a specific server (i.e. nsmail-2) then she was able to send messages. This
problem appears to be an association problem.
The action that triggers the problem is opening the Account Settings dialog and
selecting the OK button.

Steps to reproduce:
1. Use a new or migrated profile configured for an IMAP account (although the
problem also occurs with POP)
2. Login to the account
3. Send a message, it should send successfully
4. Select Edit|Mail & Newsgroup Account Settings (just open the Account Settings
dialog don't switch to another panel)
5. Select the OK button
6. Send another message

Actual Results: It reports that it can't send.
Note: In step #5 if I select the Cancel button I am still able to send a message
so the problem occurs when the OK button is selected.

Additional Information:
- With a POP account I always had a problem sending because in a new profile I
always cancel the login and go into Account Settings to Leave Messages On Server. 
Marking this bug a dupe of bug# 108912 since it appears that Account Manager is
causing the problem.

*** This bug has been marked as a duplicate of 108912 ***
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
I do know that after using ns6.2 I had noticed that on creation of a new
newsgroup account [before it stopped working], the setting for prompting the
user fails to popup to ask the user via dialog menu what way the user would like
to choose to send messages.. this dialog never gets fired up.. and it has been
broken for a long time.
verified dupe
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.