Closed
Bug 23147
Opened 25 years ago
Closed 25 years ago
[DOGFOOD][BLOCKER] unable to view messages for IMAP & POP
Categories
(SeaMonkey :: MailNews: Message Display, defect, P3)
SeaMonkey
MailNews: Message Display
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: sspitzer, Assigned: mscott)
References
Details
on today's build (1-5-2000) on all three platforms, we are unable to load
messages into the message pane. (news, local, and I believe imap.)
Comment 1•25 years ago
|
||
how are you able to get passed the password problem? using the workaround pmock
posted in that bug?
Reporter | ||
Comment 2•25 years ago
|
||
I'm able to get passed the password problem because my password is saved in my
prefs.js file.
Reporter | ||
Comment 3•25 years ago
|
||
adding mscott, jefft, and bienvenu to the cc list.
Comment 4•25 years ago
|
||
I'm not having any trouble reading messages, but I'm running with mscott's
patches.
Comment 5•25 years ago
|
||
I am seeing this in the console:
DocLoaderFactory: Unable to create ContentViewer for command=view,
content-type=text/xul
probably the reason we are not seeing output.
- rhp
Reporter | ||
Comment 6•25 years ago
|
||
if you are running with mscott's "super-fast" message display patches, then your
vote doesn't count.
this seems to affecting the nightly build and the tip builds.
Comment 7•25 years ago
|
||
anyone have any ideas on this? linux build 2000-01-05-12-M13 just finished and
fixes the mail pw problem, so now I'm seeing this one.
Comment 8•25 years ago
|
||
That's strange, I still cannot see the IMAP messages display on the message
body.
I used 2000-01-05-12-M13 Linux commercial build.
Comment 9•25 years ago
|
||
I was referring to 23132, this bug is still live. I've talked to don and he's
trying to track someone down for this since this is the only blocker keeping the
tree closed (that I'm aware of).
Comment 10•25 years ago
|
||
This problem is not specific for IMAP.
It occurred on POP for Linux 2000-01-05-12-M13 commercial build, too.
Updated•25 years ago
|
Summary: [BLOCKER] unable to view messages → [DOGFOOD][BLOCKER] unable to view messages for IMAP & POP
Comment 11•25 years ago
|
||
Updating summary for adding IMAP & POP. Nominating [DOGFOOD].
Comment 12•25 years ago
|
||
For imap messages we failed with the following stack:
nsImapMockChannel::GetOwner() returns NS_ERROR_NOT_IMPLEMENTED. mscott, any
ideas?
nsImapMockChannel::GetOwner(nsImapMockChannel * const 0x037896c0, nsISupports *
* 0x0012f8a8) line 6410
nsXULDocument::PrepareToLoad(nsISupports * 0x03051ad0, const char * 0x03791a50,
nsIChannel * 0x037896c0, nsILoadGroup * 0x03054d10, nsIParser * * 0x0012f914)
line 4023 + 36 bytes
nsXULDocument::StartDocumentLoad(nsXULDocument * const 0x03791220, const char *
0x03791a50, nsIChannel * 0x037896c0, nsILoadGroup * 0x03054d10, nsISupports *
0x03051ad0, nsIStreamListener * * 0x0012fd30) line 722 + 48 bytes
nsLayoutDLF::CreateRDFDocument(const char * 0x03791a50, nsIChannel * 0x037896c0,
nsILoadGroup * 0x03054d10, const char * 0x0012fcf0, nsISupports * 0x03051ad0,
nsISupports * 0x00000000, nsIStreamListener * * 0x0012fd30, nsIContentViewer * *
0x0012fc10) line 455 + 43 bytes
nsLayoutDLF::CreateInstance(nsLayoutDLF * const 0x037918c0, const char *
0x03791a50, nsIChannel * 0x037896c0, nsILoadGroup * 0x03054d10, const char *
0x0012fcf0, nsISupports * 0x03051ad0, nsISupports * 0x00000000,
nsIStreamListener * * 0x0012fd30, nsIContentViewer * * 0x0012fc10) line 269 + 40
bytes
nsWebShell::CreateViewer(nsIChannel * 0x037896c0, const char * 0x0012fcf0, const
char * 0x03791a50, nsIStreamListener * * 0x0012fd30) line 1782 + 95 bytes
nsWebShell::DoContent(nsWebShell * const 0x03051aec, const char * 0x0012fcf0,
int 0, const char * 0x100782d0 gCommonEmptyBuffer, nsIChannel * 0x037896c0,
nsIStreamListener * * 0x0012fd30, int * 0x0012fcd4) line 1735 + 36 bytes
nsDocumentOpenInfo::DispatchContent(nsIChannel * 0x037896c0, nsISupports *
0x00000000) line 335 + 109 bytes
nsDocumentOpenInfo::OnStartRequest(nsDocumentOpenInfo * const 0x0378f870,
nsIChannel * 0x037896c0, nsISupports * 0x00000000) line 219 + 16 bytes
nsOnStartRequestEvent::HandleEvent(nsOnStartRequestEvent * const 0x03795d10)
line 199
nsStreamListenerEvent::HandlePLEvent(PLEvent * 0x03794400) line 93 + 12 bytes
PL_HandleEvent(PLEvent * 0x03794400) line 522 + 10 bytes
PL_ProcessPendingEvents(PLEventQueue * 0x0108ae70) line 483 + 9 bytes
_md_EventReceiverProc(HWND__ * 0x00240690, unsigned int 49445, unsigned int 0,
long 17346160) line 951 + 9 bytes
USER32! 77e7124c()
0108ae70()
Assignee | ||
Updated•25 years ago
|
Assignee: phil → mscott
Assignee | ||
Comment 13•25 years ago
|
||
yeah waterson and I just checked in the fixes.
repull nsImapProtocol.cpp and nsMsgProtocol.cpp
Assignee | ||
Comment 14•25 years ago
|
||
*** Bug 23176 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 15•25 years ago
|
||
my seamonkey build won't let me mark this bug as fixed! Can someone please do
that for me? =)
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 16•25 years ago
|
||
marking fixed for scott.
Comment 17•25 years ago
|
||
Does it fix on POP and News as well since problem also happened on those
servers.
Assignee | ||
Comment 18•25 years ago
|
||
Yes it does.
Comment 19•25 years ago
|
||
OK. Great!!
Comment 20•25 years ago
|
||
this appears to be fixed in the latest linux builds. respinning mac and windows
now.
Comment 21•25 years ago
|
||
Linux Redhat 6.0 (2000-01-05-15 M13)
I try it on this build, I can view message both in POP and IMAP now.
Waiting for Mac and Win_nt builds to come out.
Comment 22•25 years ago
|
||
Verified as fixed on win, mac, and linux using the following builds:
ftp://sweetlou/products/client/seamonkey/windows/32bit/x86/2000-01-05-16-M13/sea
monkey32e.exe
ftp://sweetlou/products/client/seamonkey/unix/linux_glibc/2.2/x86/2000-01-05-15-
M13/netscape-i686-pc-linux-gnu.tar.gz
ftp://sweetlou/products/client/seamonkey/macos/8.x/ppc/2000-01-05-15-M13/NSMacIn
staller-M13.sea.bin
I can view messages under pop, imap, and news. Great work Mscott. :)
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•