'undefined' in webmail body
one of our users went away (using laptop/internet explorer/wireless) said several messages in uwc show up with 'undefined' in the body.
i believe this coincides with my application of t patch -60 to the messaging server.
Sun Java(tm) System Messaging Server 6.2-8.01 (built Nov 27 2006)
uwc - 118540-42
we did not apply new config yet, as it's taking me sometime to know how to fix those .new files ...
could he be seeing undefined because the new config is not yet applied?
haven't had any other complaints - though most (if not all) people use firefox.
the old patch - i think -52 did not seem to have these issues (so you would think running with the old config and the new -60 bits -if any are installed w/o installnewconfig- would be fine).
any clues on how to figure out these diff conflicts in the .new files?
am i generally supposed to delete
the indicator of the .new file <<<<<<< (keeping the .new file's code)
delete the separator indicator ==== and what's between it (old file's code) and the
>>>>>>> indicating end of old file's code ?
any other reason my user might see 'undefined' in the body using msie - my first guess was a slow internet connection and the complex uwc pages, but i have also seen this problem referenced in earlier patch levels.
thanks,
s7
[1426 byte] By [
starman7a] at [2007-11-26 18:12:18]
# 1
First, what do you see when you use a standard mail client, and IMAP?
What browser do you use, when you see the error. Is the error the same with other browsers?
The README that comes with the patch should include complete instructions for how to apply the patch. If you're having difficulty with a step, why don't you let us know where the problem is?
# 2
so far the only complaint was from a uwc user using msie.
no other complaints from uwc users (they use firefox) - i use pop and uwc from firefox (without error) - other users use other imap clients too and have not reported an error.
i think i know how to deal with the .new files (did what i describe make any sense?) - i am just wondering if not applying the newconfig yet could be behind this error - even though it never appeared to be present in the earlier patch level.
# 3
> so far the only complaint was from a uwc user using
> msie.
> no other complaints from uwc users (they use firefox)
> - i use pop and uwc from firefox (without error) -
> other users use other imap clients too and have not
> reported an error.
Knowing the version of IE might help. There're new versions of IE out, that we have not tested for compatibility. IE7, specifically isn't supported.
>
> i think i know how to deal with the .new files (did
> what i describe make any sense?) - i am just
> wondering if not applying the newconfig yet could be
> behind this error - even though it never appeared to
> be present in the earlier patch level.
We really don't know what the error is, yet. That makes it too early to know.
# 4
> Knowing the version of IE might help. There're new
> versions of IE out, that we have not tested for
> compatibility. IE7, specifically isn't supported.
>
> We really don't know what the error is, yet. That
> makes it too early to know.
the error is the 'undefined' in the body of the message (when using msie)
the user is non-technical - thinks it could have been a newer version of ie. said it looked a little unfamiliar - though he was using a PC and usually is on the mac.
