H
Hannah Swain
Good morning,
One of our customers regularly attached 44 contact lists from her contacts
to an email and sent these to one of her clients, monthly. The client would
receive the email and be able to pull the contact lists directly to her own
contacts.
Our client had Office 2003, her client has had Office 2007 for a while now.
A week ago, our client upgraded to Office 2007. Since then, the problems have
started.
Now, when our client attaches those distribution lists and sends them on to
her client, the receiving end doesn't see a card icon but sees an envelope.
When you open the envelope (double click on attachment) you're basically
looking at an empty email. When you try and pull the attachment to the
contacts, it opens a contact screen with the current user's information. The
same thing happened when my client sent the same email to me, I'm also using
Office 2007.
I assumed that there was probably a virus scanner or something filtering
incorrectly. As my client needed to get these files to her client asap, I
helped her zip the necessary distribution lists by creating a folder called
"address" on the desktop, dragging the distribution lists to the folder,
zipping the folder and sending it. I sent it to myself first: when I unzipped
the file and looked at the I saw the correct icon. When I double clicked on
the file, I got the correct view of the distribution list.
However, when my client sent this file to her client, she complained that
the files all looked like envelopes again. You could open the envelopes and
get the contents of the mailing list, but it still wasn't a solution.
It turned out that I was unzipping the file and then looking at the
contents. She was just double clicking on the zipped file and looking at the
zipped contents. When I had my client resend the zipped file and she had her
client unzip it first, then everything worked well. Just for general
information, I used Winrar, but when testing with my client, we used the
Windows zip utility.
What I noticed is that whatever is exported from Outlook, it seems to always
get the extension .msg - even if it's a distrubtion list. I'm thinking that
Microsoft has built the intelligence into Outlook 2007 to recognize the type
of file based on its contents and not on its extension. When one client still
had Office 2003, the extensions were different and Outlook was forced to
recognize the file as a mailing list and not as a message. Apparently the
default type for the msg extension is still email message. Somewhere in the
way Windows deals with looking into the zip file and the way Outlook deals
with its extensions, something is going wrong.
To sum it up, we have two problems:
1. When sending a distribution list as an attachment in Office 2007 and when
it is received by Office 2007, it is recognized as an email message.
2. When just clicking into a zip file which has distribution lists, the
lists are recognized as messages until it is unzipped manually.
What can we do to make this work?
Thanks very much for any light anyone can shed on this.
Kind regards,
Hannah Swain
2Eenheid Automatisering
One of our customers regularly attached 44 contact lists from her contacts
to an email and sent these to one of her clients, monthly. The client would
receive the email and be able to pull the contact lists directly to her own
contacts.
Our client had Office 2003, her client has had Office 2007 for a while now.
A week ago, our client upgraded to Office 2007. Since then, the problems have
started.
Now, when our client attaches those distribution lists and sends them on to
her client, the receiving end doesn't see a card icon but sees an envelope.
When you open the envelope (double click on attachment) you're basically
looking at an empty email. When you try and pull the attachment to the
contacts, it opens a contact screen with the current user's information. The
same thing happened when my client sent the same email to me, I'm also using
Office 2007.
I assumed that there was probably a virus scanner or something filtering
incorrectly. As my client needed to get these files to her client asap, I
helped her zip the necessary distribution lists by creating a folder called
"address" on the desktop, dragging the distribution lists to the folder,
zipping the folder and sending it. I sent it to myself first: when I unzipped
the file and looked at the I saw the correct icon. When I double clicked on
the file, I got the correct view of the distribution list.
However, when my client sent this file to her client, she complained that
the files all looked like envelopes again. You could open the envelopes and
get the contents of the mailing list, but it still wasn't a solution.
It turned out that I was unzipping the file and then looking at the
contents. She was just double clicking on the zipped file and looking at the
zipped contents. When I had my client resend the zipped file and she had her
client unzip it first, then everything worked well. Just for general
information, I used Winrar, but when testing with my client, we used the
Windows zip utility.
What I noticed is that whatever is exported from Outlook, it seems to always
get the extension .msg - even if it's a distrubtion list. I'm thinking that
Microsoft has built the intelligence into Outlook 2007 to recognize the type
of file based on its contents and not on its extension. When one client still
had Office 2003, the extensions were different and Outlook was forced to
recognize the file as a mailing list and not as a message. Apparently the
default type for the msg extension is still email message. Somewhere in the
way Windows deals with looking into the zip file and the way Outlook deals
with its extensions, something is going wrong.
To sum it up, we have two problems:
1. When sending a distribution list as an attachment in Office 2007 and when
it is received by Office 2007, it is recognized as an email message.
2. When just clicking into a zip file which has distribution lists, the
lists are recognized as messages until it is unzipped manually.
What can we do to make this work?
Thanks very much for any light anyone can shed on this.
Kind regards,
Hannah Swain
2Eenheid Automatisering