> Do the full sources of the entire broken messages contain MIME that is
> broken in the same exact way? How do they compare, viewed as ASCII
> source, to plain-text messages received after the restart?
When I check the .mbx file on the IMail server, the emails before and
after restart are just your standard, run-of-the-mill plain text email
messages (no multipart attachments). I don't know how to get ASCII source
out of Outlook, but the mail headers of plain text emails before and after
reboot are IDENTICAL (except for message IDs and time stamps)...
Which is strange since we should expect different Content-Type. Shouldn't
we?
Content-Type: multipart/mixed;
boundary="----_=_NextPart_000_01C1DCC2.B9128790"
vs.
Content-Type: text/plain;
charset="us-ascii"
It seems that Outlook viewer "decided" to attach the message to itself?
> ... For Outlook to display a message is
> multipart, one hopes it has actually changed (mistakenly) the source
> to reflect that. If they look like text/plain, and (for instance)
> display as such in other MUAs and other Outlooks, but are displayed
> otherwise in this installation of Outlook, it's hosed.
Other users were fine during the 5 hour period this user was experiencing
this problem. In fact, this user leaves his mail on the IMail server for
web-based messaging. The same messages viewed on the web client DON'T
have the attachment problem! I guess that would be obvious if the .mbx
files don't show the attachment problem.
One other interesting tidbit: In an attempt to view the Outlook .pst file
for this user to get the source, I noticed that the file size was about
394MB.
All the latest W2K and MS Office patches were installed prior to this
weirdness.
User has not archived email in at least the last year.
> it's hosed.
Yeppers. Decided to rebuild user's machine just in case it's got something
nasty... something about ounce of prevention. :)
> It's a symptom of "Why Outlook sucks."
In reference to another thread "Is your email watching you?", I installed
Norton Firewall on our client machines last month even though we have a
corp-wide Cisco525 for our network. I've manually set each client's
Norton Firewall settings to detect their email address in outgoing traffic
(for example, "[EMAIL PROTECTED]"). Apparently, just viewing the spam in the
Outlook preview window SENDS OUT your email address to the spammers for
address verification. Norton Firewall detects this and asks you if you want
to block it. Our $50K Cisco FW lets this traffic through as normal
HTTP/port
80 traffic.
Don't you just love this job.
-Norm
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
An Archive of this list is available at:
http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
Please visit the Knowledge Base for answers to frequently asked
questions: http://www.ipswitch.com/support/IMail/
