Closed Bug 32551 Opened 24 years ago Closed 24 years ago

AOL IMAP: Reply an attached message didn't display the original attached web content

Categories

(SeaMonkey :: MailNews: Message Display, defect, P3)

Product:
SeaMonkey
Component:
MailNews: Message Display
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED INVALID

People

(Reporter: huang, Assigned: Bienvenu)

Details

AOL IMAP: Reply an attached message didn't display the original attached web 
content

Used 03-20-05-nb1b Mac build:
1) Login to AOL IMAP mail account
2) Compose new message/Send mail with "Attach web"
3) Actual Results: Reply this attached message will display as following:

Expected results: Should display the web content as same as sent.

(P.S. sometimes when just sending the web page is also displaying the same 
problem....but not everytime. Reply will display this problem everytime....)


krnhuang wrote: > attach2 > > > -------------------------------------------------
----------------------- > > <"http://www.mozilla.org/">> > Bugzilla > > Report A 
Bug <"http://www.mozilla.org/quality/help/bug-form.html"> - Use > the Bugzilla 
Helper. > View Bugs Already Reported Today > <"http://bugzilla.mozilla.org/
buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=
REOPENED&bug_status=RESOLVED&email1=&emailtype1=substring&emailassigned_to1=1&
email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&
changedin=1&votes=&chfield=%5BBug+creation%5D&chfieldfrom=&chfieldto=Now&
chfieldvalue=&product=Browser&product=MailNews&short_desc=&short_desc_type=
substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=
substring&status_whiteboard=&status_whiteboard_type=substring&keywords=&
keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&
newqueryname=&order=Reuse+same+sort+as+last+time"> > > --------------------------
---------------------------------------------- > Show Mozilla bug no. > ---------
--------------------------------------------------------------- > > * Query Page 
<"query.cgi"> (Search existing bug reports) > * Get summary reports <
"reports.cgi">> * Enter a new bug report <"enter_bug.cgi"> (Advanced) > > * Open 
a new Bugzilla account <"createaccount.cgi">> * Change your password or user 
preferences <"userprefs.cgi">> * Log out of Bugzilla <"relogin.cgi">> > What's 
all this, then? > > This is mozilla.org <"http://www.mozilla.org/">'s bug-
tracking system, > our database for recording bugs in Mozilla and other 
mozilla.org > projects. For more information about Bugzilla, see our bug page > <
"http://www.mozilla.org/bugs/">. > > *This is /not/ the place to report bugs 
about commercial Netscape > products.* For that, try Netscape's own bug reporting 
form > <"http://help.netscape.com/forms/bug-client.html"> instead. Netscape > 
bugs reported here will be ignored. (Netscape browsers usually have a > blue and 
black `N' logo in the top right of the window.) > > When reporting a bug > > * *
Read the Bugzilla fact sheet <"http://www.mozilla.org/bugs/">* > so you know what 
you're doing. > * *Open a Bugzilla account <"createaccount.cgi">* if you don't > 
have one already. > * *Make sure you can reproduce the bug*, and explain to 
others how > to reproduce it as well. If engineers can't reproduce your bug, > 
they won't be able to fix it. > * *Read the bug reporting guidelines > <"http://
www.mozilla.org/quality/bug-writing-guidelines.html">* to > learn how to write 
bug reports that get bugs fixed. > * *Make sure your bug hasn't already been 
reported*. Consult the > list of most frequently reported bugs > <"http://
www.mozilla.org/quality/most-frequent-bugs/">, and search > <"query.cgi"> for 
bugs matching the one you've found. > * *Use the Bugzilla Helper > <"http://
www.mozilla.org/quality/help/bug-form.html"> to report > bugs*. This form helps 
you write well written bug reports. > > Copyright 1998-2000, The Mozilla 
Organization > > bugzilla.mozilla.org.html > > Content-Type: > > text/html > 
Content-Encoding: > > 7bit > >
Phil found a way to weasel out of owning this bug.  Reassigning.
Assignee: phil → selmer
QA Contact: lchiang → huang
David, you seem to be the first point of contact on this.  If you think beta2
must have this, please mark it M16.  Thanks.
Assignee: selmer → bienvenu
Target Milestone: --- → M17
it's probably a server bug/feature anyway with the AOL gateway. If that's the 
case, of course, I can't do anything about it. AOL mail currently only allows 
one attachment as I understand it.
Status: NEW → ASSIGNED
Adding nsbeta2 on the keywords.
Keywords: nsbeta2
I think this is a server issue which is out of our control.  I don't know if 
we'll address for beta2.
Then, who can take care of the server's issue? We shouldn't release Netscape 6 
with this issue, isn't it? beta2 or post beta2?
Keywords: nsbeta3
Whiteboard: [nsbeta2-]
Putting on [nsbeta2-] radar. 

kmurray, need to know if this is a server side feature.  Can you find out 
for us please?  Thanks!  The PDT.

Putting on nsbeta3 keyword radar.
sent email to kmurray on this as he is not in the cc: list.
adding kevin to cc list. This bug is wasting away on my list - there's nothing I
can do about it, as far as I know.
Keywords: nsbeta2
Whiteboard: [nsbeta2-]
Sorry for not responding sooner. I would not pull this off the beta2 wire, but I 
believe it is essential for the final product. This falls under the 
"correctness" keyword. Adding.
Keywords: correctness
Problem is still occurring on some web pages. And sometimes I will get an 
error message display: " This message contains characters not found in the 
chosen character coding. The message maybe unreadable to the recipient. Sen 
it anyway or "Cancel" to choose a different character coding" when I replying 
for some message. I think it's good for display that error, but after users 
select Cancel, they have no direction WHERE to choose the different character 
coding. We probably need to think a way for solve the reply attachement problem 
for AOL or give direction for users when the error display.....
Better to release note for beta2 for this problem. Adding relnote2 for the 
keywords.
Keywords: relnote2
If there's really nothing we can do perhaps we should mark WONTFIX? Is this 
something the server team is likely to fix for us?
Is this really only the Mac?
Keywords: mail3
No. It's also occurring on other platforms.
Changing the platforms to all.
OS: Mac System 8.6 → All
Hardware: Macintosh → All
David, can you say with certainty that this is a server problem?  Can you make 
that determination and update the bug?  Thanks!  Steve
Whiteboard: [b3 need info]
How about giving an example web page that demonstrates the problem? I don't
understand the bugsplat thing, and it's not really a link. Karen, did you verify
that this isn't happening with other imap servers?
I still maintain that this is a server "feature". Try it with the netscape mail
server and the aol mail server. If you send the mail with a netscape smtp server
to an aol account, when you read it with aol, you'll get vastly different
message than if you use a netscape smtp server to send a message to a netscape
internal (not web-mail) account.  By using a netscape smtp server for both
tests, it becomes pretty obvious that the aol server is doing something special
to the message. 
David, I will check this bug later since I am focusing on nsbeta2 verification 
now...
I'm marking invalid - this is a server thing. The same thing would happen if you
sent the message from 4.x or Outlook express. If anyone disagrees, they can
re-open it.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
It seems that there is problem for AOL incoming message for today's build.
I couldn't retest this bug for today's build. I will try that tomorrow....
Hmm...interesting. After I use AOL client & M17 to access AOL account, then I 
can connect to AOL by using M18 now.

OK. By using 08-07-15-M18 commercial build:
* For 4.x: 
I did verify on 4.x for reply a messages with attached "www.yahoo.com" web page, 
it reply with the original web page.

* For Seamonkey:
After I send/reply with attached "www.yahoo.com", it will display a confirm 
dialog when trying to reply/sending: "This message contains characters not found 
in the chosen character coding. The message maybe unreadable to the recipient. 
Send it anyway or "Cancel" to choose a different character coding".
  - After select OK from this confirm dialog: you can go back to check the reply 
message which just with this page's text and link, not the original web page.
  - After select Cancel from this confirm dialog: users have no direction WHERE 
to choose the different character coding???....(probably need to improve this 
confirm dialog to ensure given the right information for users to follow...)

So, is this still AOL server issue? If this is still AOL server issue, how can 
we track and report this problem for the AOL server? Anybody knows? We shouldn't 
just let it go for this problem, isn't it?
Provided info already, clear status whiteboard.
Whiteboard: [b3 need info]
By using Seamonkey, this problem is not occurring on other IMAP servers (NMS 
4.15, MSE 5.5, UW 12.25,& Cyrus 1.5.2). Looks like this is specific AOL server 
problem, I am Marking as verified now. We probably need release notes for RTM.
Status: RESOLVED → VERIFIED
Keywords: relnoteRTM
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.