Outlook 2007 renames attachments

[jperry]

It seems that if you receive an attachment with the following format it will
rename it as indicated:

filename like com?.* renames to com_.*

Attachment Name Renamed
comm.jpg com_.jpg
coma.txt com_.txt
com7.sql com_.sql

If you save the file it will save it as com_.ext but if you forward the file
to a non-2007 client it will again show the proper name on the other client.
This was tested with several different deployments of Outlook 2007 in various
environments and though each had an Exchange 2003 server in use. Outlook
2003 clients as well as other remote mail such as gmail did not seem to have
this problem and when you attach the file in the Outlook 2007 client you will
not see the file renamed. Near as I can tell its only when you receive the
attached files.

Just in case something weird was happening I also checked the autocorrect
options in Outlook but nothing seems set to rename comm by default and none
of the Exchagne administrators (I am one here) have added any special rules
to try and manipulate messages in this fashion and it seems to only be a
client side problem anyway.

I do not know if this is a bug, something that is intended or some kind of
simple oversight on my part. I also am not sure how to bring this to the
attention of a MS representative to determine if it is a problem.

If you can suggest anything I can check please do so. If this is something
intentional can you point out where this is documented and if there are any
other file names I need to be aware of that will be modified in this manner.
I am aware of the blocking of unsafe attachments, but have never seen one or
any documentation that a file name (not the extension) should be modified.

Any help is greatly appreciated!

Cheers.
-jperry

 

[Diane Poremsky {MVP}]

It's not Outlook doing it. What antivirus are you using, both on the server
and local machine.

--
Diane Poremsky [MVP - Outlook]
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:
(e-mail address removed)

Exchange Messaging Outlook newsletter:
(e-mail address removed)




** Please include your Outlook version, Account type, and Windows Version
when requesting assistance **

 

[jperry]

On my machine it is Symantec Anti-Virus 8.1.0.825 Corporate, the Exchange
server has SAV Corp 10.1.6, the OLK 2003 client has 8.1 and the second
OLK2007 in my environment tested has 10.1.6.

The other deployment I asked someone to test is not using Symantec for
server or client security though I am not certain which AV product they are
using. I checked the logs for any events, noticies, tampering, and all
history for infected items and did not find a single entry in my local
machine and nothing relavent on the server.

Please note that if I forward a message that shows the attachment as
com_.txt to a OLK2003 client on the same server you can see and save the file
as the original name (comm.txt for instance). Same applies to files
forwarded to gmail or other clients.

As such this appears to be a problem localized with the client side only
(Outlook 2007).

It's not Outlook doing it. What antivirus are you using, both on the server
and local machine.

--
Diane Poremsky [MVP - Outlook]
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:
(e-mail address removed)

Exchange Messaging Outlook newsletter:
(e-mail address removed)




** Please include your Outlook version, Account type, and Windows Version
when requesting assistance **

It seems that if you receive an attachment with the following format it
will
rename it as indicated:

filename like com?.* renames to com_.*

Attachment Name Renamed
comm.jpg com_.jpg
coma.txt com_.txt
com7.sql com_.sql

If you save the file it will save it as com_.ext but if you forward the
file
to a non-2007 client it will again show the proper name on the other
client.
This was tested with several different deployments of Outlook 2007 in
various
environments and though each had an Exchange 2003 server in use. Outlook
2003 clients as well as other remote mail such as gmail did not seem to
have
this problem and when you attach the file in the Outlook 2007 client you
will
not see the file renamed. Near as I can tell its only when you receive
the
attached files.

Just in case something weird was happening I also checked the autocorrect
options in Outlook but nothing seems set to rename comm by default and
none
of the Exchagne administrators (I am one here) have added any special
rules
to try and manipulate messages in this fashion and it seems to only be a
client side problem anyway.

I do not know if this is a bug, something that is intended or some kind of
simple oversight on my part. I also am not sure how to bring this to the
attention of a MS representative to determine if it is a problem.

If you can suggest anything I can check please do so. If this is
something
intentional can you point out where this is documented and if there are
any
other file names I need to be aware of that will be modified in this
manner.
I am aware of the blocking of unsafe attachments, but have never seen one
or
any documentation that a file name (not the extension) should be modified.

Any help is greatly appreciated!

Cheers.
-jperry

 

[Diane Poremsky {MVP}]

Is Symantec on the local machine set to scan incoming email? What addins are
installed (tools, trust center, addins)

--
Diane Poremsky [MVP - Outlook]
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:
(e-mail address removed)

Exchange Messaging Outlook newsletter:
(e-mail address removed)




** Please include your Outlook version, Account type, and Windows Version
when requesting assistance **

On my machine it is Symantec Anti-Virus 8.1.0.825 Corporate, the Exchange
server has SAV Corp 10.1.6, the OLK 2003 client has 8.1 and the second
OLK2007 in my environment tested has 10.1.6.

The other deployment I asked someone to test is not using Symantec for
server or client security though I am not certain which AV product they
are
using. I checked the logs for any events, noticies, tampering, and all
history for infected items and did not find a single entry in my local
machine and nothing relavent on the server.

Please note that if I forward a message that shows the attachment as
com_.txt to a OLK2003 client on the same server you can see and save the
file
as the original name (comm.txt for instance). Same applies to files
forwarded to gmail or other clients.

As such this appears to be a problem localized with the client side only
(Outlook 2007).

It's not Outlook doing it. What antivirus are you using, both on the
server
and local machine.

--
Diane Poremsky [MVP - Outlook]
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:
(e-mail address removed)

Exchange Messaging Outlook newsletter:
(e-mail address removed)




** Please include your Outlook version, Account type, and Windows Version
when requesting assistance **

It seems that if you receive an attachment with the following format it
will
rename it as indicated:

filename like com?.* renames to com_.*

Attachment Name Renamed
comm.jpg com_.jpg
coma.txt com_.txt
com7.sql com_.sql

If you save the file it will save it as com_.ext but if you forward the
file
to a non-2007 client it will again show the proper name on the other
client.
This was tested with several different deployments of Outlook 2007 in
various
environments and though each had an Exchange 2003 server in use.
Outlook
2003 clients as well as other remote mail such as gmail did not seem to
have
this problem and when you attach the file in the Outlook 2007 client
you
will
not see the file renamed. Near as I can tell its only when you receive
the
attached files.

Just in case something weird was happening I also checked the
autocorrect
options in Outlook but nothing seems set to rename comm by default and
none
of the Exchagne administrators (I am one here) have added any special
rules
to try and manipulate messages in this fashion and it seems to only be
a
client side problem anyway.

I do not know if this is a bug, something that is intended or some kind
of
simple oversight on my part. I also am not sure how to bring this to
the
attention of a MS representative to determine if it is a problem.

If you can suggest anything I can check please do so. If this is
something
intentional can you point out where this is documented and if there are
any
other file names I need to be aware of that will be modified in this
manner.
I am aware of the blocking of unsafe attachments, but have never seen
one
or
any documentation that a file name (not the extension) should be
modified.

Any help is greatly appreciated!

Cheers.
-jperry

 

[jperry]

I'll install a clean VM with XP and Outlook 2007 and no other tools, AV, etc
and see if the problem still occurs and report back tomorrow. Thanks for the
help thus far.

Is Symantec on the local machine set to scan incoming email? What addins are
installed (tools, trust center, addins)

--
Diane Poremsky [MVP - Outlook]
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:
(e-mail address removed)

Exchange Messaging Outlook newsletter:
(e-mail address removed)




** Please include your Outlook version, Account type, and Windows Version
when requesting assistance **

On my machine it is Symantec Anti-Virus 8.1.0.825 Corporate, the Exchange
server has SAV Corp 10.1.6, the OLK 2003 client has 8.1 and the second
OLK2007 in my environment tested has 10.1.6.

The other deployment I asked someone to test is not using Symantec for
server or client security though I am not certain which AV product they
are
using. I checked the logs for any events, noticies, tampering, and all
history for infected items and did not find a single entry in my local
machine and nothing relavent on the server.

Please note that if I forward a message that shows the attachment as
com_.txt to a OLK2003 client on the same server you can see and save the
file
as the original name (comm.txt for instance). Same applies to files
forwarded to gmail or other clients.

As such this appears to be a problem localized with the client side only
(Outlook 2007).

It's not Outlook doing it. What antivirus are you using, both on the
server
and local machine.

--
Diane Poremsky [MVP - Outlook]
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:
(e-mail address removed)

Exchange Messaging Outlook newsletter:
(e-mail address removed)




** Please include your Outlook version, Account type, and Windows Version
when requesting assistance **


It seems that if you receive an attachment with the following format it
will
rename it as indicated:

filename like com?.* renames to com_.*

Attachment Name Renamed
comm.jpg com_.jpg
coma.txt com_.txt
com7.sql com_.sql

If you save the file it will save it as com_.ext but if you forward the
file
to a non-2007 client it will again show the proper name on the other
client.
This was tested with several different deployments of Outlook 2007 in
various
environments and though each had an Exchange 2003 server in use.
Outlook
2003 clients as well as other remote mail such as gmail did not seem to
have
this problem and when you attach the file in the Outlook 2007 client
you
will
not see the file renamed. Near as I can tell its only when you receive
the
attached files.

Just in case something weird was happening I also checked the
autocorrect
options in Outlook but nothing seems set to rename comm by default and
none
of the Exchagne administrators (I am one here) have added any special
rules
to try and manipulate messages in this fashion and it seems to only be
a
client side problem anyway.

I do not know if this is a bug, something that is intended or some kind
of
simple oversight on my part. I also am not sure how to bring this to
the
attention of a MS representative to determine if it is a problem.

If you can suggest anything I can check please do so. If this is
something
intentional can you point out where this is documented and if there are
any
other file names I need to be aware of that will be modified in this
manner.
I am aware of the blocking of unsafe attachments, but have never seen
one
or
any documentation that a file name (not the extension) should be
modified.

Any help is greatly appreciated!

Cheers.
-jperry