Trick

Peter - Gary is correct, the MS first level recognized the issue resolution
as one that should be no cost & it was no cost to me. To get to the first
level in the auto response system though I had to be ready to pay - don't
know if I could get thru some other way as I don't use that system very much.

The reason I did use it is that the MS help process sends one to these
communities and I did read a lot of (but not all) discussion so I knew it
wasn't just me & without finding a root cause fix, I went to MS.

These boards are a bit clunky or I don't know how to use them optimally. MS
is aware of the discussion and as Gary says that helps them in priority.
There is no KB in the system yet; they apparently don't know what is causing
the "winmail.fol" system file to sometimes just disappear from the various
box folders. It is good idea to check any misbehaving system to see if it is
there or not.

MS agrees once that file somehow gets clobbered, the headers stick and can't
be deleted. The outbox stuck header or no "winmail.fol" causes sending
e-mail to not happen until regeneration of the outbox at the app Local Folder
level & I was getting no error message from sending unless I tried to delete
the stuck header.

Gary should find regeneration (replaces his missing "winmail.fol") works as
others have written here. It can't simply be copied in - MS & I tried that
w/o success. So far the glitch deleting the file has not returned for me -
but regeneration is the workaround until a KB. I have not taken any other
action to stop the glitch (e.g. McAfee is still on full strength.)