Before the April 2006 KB911567 security patch for Outlook Express, I could
create "Template Emails" and store them in a folder named TEMPLATES in My
Documents. These are email messages with a subject but with no recipient name
in the TO field. The idea is that I can send this same email to many
different recipients at different times as the need arises. After creating
the email, I use FILE\SAVE AS to store it in my TEMPLATES folder. I keep a
menu toolbar for that folder on my Taskbar so that all I have to do is click
on the appropriate TEMPLATE email message and Outlook Express will launch a
composition window with my message ready to go. All I have to do is fill in
the TO field and click SEND. I can even add a special note to the body of the
text to personalize the message for any particular recipient.

After installing Cumulative Security Update for Internet Explorer for
Windows XP (KB912812), these emails now appear in the same sort of window
that you see when you look at an opened and read email message that you store
in your email inbox. Inotherwords, there is no TO field or SUBJECT field or
CC or BCC field because it is a completely different window. I cannot simply
click on my template email and enter a name in the TO field and SEND it off.
I would have to send it as an attachment. This may have something to do with
making Outlook Express a tad more secure, but it compromises a valuable
function that was formerly available. I know that it is KB91156 because I
uninstalled it from ADD-REMOVE PROGRAMS and my TEMPLATE EMAIL functionality
immediately returned. I'd like the patch for the obvious reason but consider
the functionality very important.

Incidentally, I also tried to locate a setting that would change the email
windows back to the composition window but had no success. Furthermore, I
attempted to recreate some of the original emails in the hopes that doing
them over by hand would cause them "to take" in the way they did before
KB91156, but again no success.

KB91156 is definitely the culprit. TO DUPLICATE MY EXPERIMENT: 1. UNINSTALL
KB91156 - 2. CREATE AN EMAIL MESSAGE, DO NOT PUT ANYTHING IN THE "TO" FIELD -
3. USE FILE\SAVE AS IN THE EMAIL WINDOW TO SAVE A COPY OF THE MESSAGE TO YOUR
DESKTOP - 4. CLOSE THE ORIGINAL MESSAGE - 5. DOUBLE-CLICK THE EMAIL MESSAGE
ICON ON YOUR DESKTOP TO OPEN IT - 6. FILL IN THE "TO" FIELD AND CLICK "SEND."
(You should be able to do this repeatedly as often as you wish without
compromising the original file on the desktop) - 7. REINSTALL KB91156 AND
ATTEMPT TO REPEAT STEPS 1-6. Any ideas?
--
Keith Halonen

Numerous posts have been received since 4/11 about this.

Your problem may be caused by the update KB911567 introduced on 4/11/06. Try
removing it as per this link and see if the problem persists:
http://www.oehelp.com/OETips.aspx#14

If that resolves it, for now, you may want to configure Automatic Updates to
either "Notify Only" or "Download but do not install". You can also choose
not to download or install 911567 and check: Do not tell me about it again.

How to configure and use Automatic Updates in Windows XP:
http://support.microsoft.com/?kbid=306525
--
Bruce Hagen
MS MVP - Outlook Express
~IB-CA~

"Keith Halonen" wrote in message
...
Before the April 2006 KB911567 security patch for Outlook Express, I could
create "Template Emails" and store them in a folder named TEMPLATES in My
Documents. These are email messages with a subject but with no recipient
name
in the TO field. The idea is that I can send this same email to many
different recipients at different times as the need arises. After creating
the email, I use FILE\SAVE AS to store it in my TEMPLATES folder. I keep a
menu toolbar for that folder on my Taskbar so that all I have to do is
click
on the appropriate TEMPLATE email message and Outlook Express will launch
a
composition window with my message ready to go. All I have to do is fill
in
the TO field and click SEND. I can even add a special note to the body of
the
text to personalize the message for any particular recipient.

After installing Cumulative Security Update for Internet Explorer for
Windows XP (KB912812), these emails now appear in the same sort of window
that you see when you look at an opened and read email message that you
store
in your email inbox. Inotherwords, there is no TO field or SUBJECT field
or
CC or BCC field because it is a completely different window. I cannot
simply
click on my template email and enter a name in the TO field and SEND it
off.
I would have to send it as an attachment. This may have something to do
with
making Outlook Express a tad more secure, but it compromises a valuable
function that was formerly available. I know that it is KB91156 because I
uninstalled it from ADD-REMOVE PROGRAMS and my TEMPLATE EMAIL
functionality
immediately returned. I'd like the patch for the obvious reason but
consider
the functionality very important.

Incidentally, I also tried to locate a setting that would change the email
windows back to the composition window but had no success. Furthermore, I
attempted to recreate some of the original emails in the hopes that doing
them over by hand would cause them "to take" in the way they did before
KB91156, but again no success.

KB91156 is definitely the culprit. TO DUPLICATE MY EXPERIMENT: 1.
UNINSTALL
KB91156 - 2. CREATE AN EMAIL MESSAGE, DO NOT PUT ANYTHING IN THE "TO"
FIELD -
3. USE FILE\SAVE AS IN THE EMAIL WINDOW TO SAVE A COPY OF THE MESSAGE TO
YOUR
DESKTOP - 4. CLOSE THE ORIGINAL MESSAGE - 5. DOUBLE-CLICK THE EMAIL
MESSAGE
ICON ON YOUR DESKTOP TO OPEN IT - 6. FILL IN THE "TO" FIELD AND CLICK
"SEND."
(You should be able to do this repeatedly as often as you wish without
compromising the original file on the desktop) - 7. REINSTALL KB91156 AND
ATTEMPT TO REPEAT STEPS 1-6. Any ideas?
--
Keith Halonen

Thanks, Bruce. Your first sentence - "Numerous posts have been received since
4/11 about this." - tells me a great deal. I'm not an übergeek but I've had
PCs since 1983 and even made some part-time income manually extracting
viruses and consulting. I had already removed the KB911567 update before
posting here. It was part of a batch of downloads released on that date and
its description made me suspect that it must be the culprit that was cramping
my style. Full functionality was restored immediately and I did tuck that
upgrade out of sight. I can always go back and get it again if I figure out
how to make it work without compromising my TEMPLATE email composition
windows. As for the upgrade-fetching configurations, automated settings are
disabled in all my security applications because I prefer to do all my
upgrading "manually" at least once a week.

I guess I'm mostly looking for someone with the selfsame problem who was
clever enough to find a workaround, which I have not yet been able to do for
myself.

--
Keith Halonen

I had the same problem (for 100 users). My solution was to remove the update
and then hide it at the Windows Update site, so it wouldn't appear again.
Not exactly a workaround, I know, but it'll do until MS fixes what they
broke.

The problem is caused by OE ignoring the mail header line "x-unsent:1",
which exists in your templates. If this line was read correctly, the email
templates would have editable address lines.

Since this security update was supposed to fix an addressbook vulnerability,
I really don't know what they are doing. By the way, you can workaround the
vulnerability by removing the *.wab file association in the registry. There
was an unchecked buffer that became a potential problem if people clicked on
a unknown Wab file.

--

Best regards,
Gerry

"Keith Halonen" wrote in message
...
Thanks, Bruce. Your first sentence - "Numerous posts have been received
since
4/11 about this." - tells me a great deal. I'm not an übergeek but I've
had
PCs since 1983 and even made some part-time income manually extracting
viruses and consulting. I had already removed the KB911567 update before
posting here. It was part of a batch of downloads released on that date
and
its description made me suspect that it must be the culprit that was
cramping
my style. Full functionality was restored immediately and I did tuck that
upgrade out of sight. I can always go back and get it again if I figure
out
how to make it work without compromising my TEMPLATE email composition
windows. As for the upgrade-fetching configurations, automated settings
are
disabled in all my security applications because I prefer to do all my
upgrading "manually" at least once a week.

I guess I'm mostly looking for someone with the selfsame problem who was
clever enough to find a workaround, which I have not yet been able to do
for
myself.

--
Keith Halonen

There isn't any workaround that I can find. You can't even drag unsent
messages into the Drafts folder and have them remain unsent.

They really screwed things up.

steve

"Keith Halonen" wrote in message
...
Thanks, Bruce. Your first sentence - "Numerous posts have been received
since
4/11 about this." - tells me a great deal. I'm not an übergeek but I've
had
PCs since 1983 and even made some part-time income manually extracting
viruses and consulting. I had already removed the KB911567 update before
posting here. It was part of a batch of downloads released on that date
and
its description made me suspect that it must be the culprit that was
cramping
my style. Full functionality was restored immediately and I did tuck that
upgrade out of sight. I can always go back and get it again if I figure
out
how to make it work without compromising my TEMPLATE email composition
windows. As for the upgrade-fetching configurations, automated settings
are
disabled in all my security applications because I prefer to do all my
upgrading "manually" at least once a week.

I guess I'm mostly looking for someone with the selfsame problem who was
clever enough to find a workaround, which I have not yet been able to do
for
myself.

--
Keith Halonen

"Steve Cochran" wrote in message
There isn't any workaround that I can find. You can't even drag unsent
messages into the Drafts folder and have them remain unsent.

Did you test my HTA?
(Only for text-format, no encoding, without attachment.)

In Japanese, I can use eml file by this HTA as before.

--
Miyahn (Masataka Miya****a) JPN
Microsoft MVP for Microsoft Office - Excel(Jan 2006 - Dec 2006)

Miyahn: While your idea is nice, one can just copy and paste the info by
opening the saved eml file in Notepad (right click, selecting Open With) and
then copy and paste it into a new message. Much quicker and easier than
dealing with an hta file. But the programming is a nice feat.
--
Jim Pickering, MVP, Outlook Express
https://mvp.support.microsoft.com/pr...8-1171988A62D6
Please deliver feedback to the newsgroup, so that others can be helped.

Customers in the U.S. and Canada can receive technical support from
Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for
support calls that are associated with security updates



"Miyahn" wrote in message
...
"Steve Cochran" wrote in message

There isn't any workaround that I can find. You can't even drag unsent
messages into the Drafts folder and have them remain unsent.

Did you test my HTA?
(Only for text-format, no encoding, without attachment.)

In Japanese, I can use eml file by this HTA as before.

--
Miyahn (Masataka Miya****a) JPN
Microsoft MVP for Microsoft Office - Excel(Jan 2006 - Dec 2006)

If it is just plain text, then I can use Edit | Select All and then copy
from the opened unsendable message and then paste that into a new message.
So I don't really need an HTA file.

Except maybe it would fill in the subject, etc.

My big issue is that the unsent eml files are often with embedded images and
sounds and html, so that's what I meant when I said there was no way around
it.

cheers,

steve

"Miyahn" wrote in message
...
"Steve Cochran" wrote in message

There isn't any workaround that I can find. You can't even drag unsent
messages into the Drafts folder and have them remain unsent.

Did you test my HTA?
(Only for text-format, no encoding, without attachment.)

In Japanese, I can use eml file by this HTA as before.

--
Miyahn (Masataka Miya****a) JPN
Microsoft MVP for Microsoft Office - Excel(Jan 2006 - Dec 2006)