I have some people in the office that are not able to access attachments on
emails. However, when they forward the email to some other people in the
office, the attachments are there and accesible. Where would i find the cause
of this?

does outlook say its blocking these attachments ???

if so this may help

http://support.microsoft.com/default.aspx/kb/829982



"Jay Scheponik" wrote:

> I have some people in the office that are not able to access attachments on
> emails. However, when they forward the email to some other people in the
> office, the attachments are there and accesible. Where would i find the cause
> of this?

"Jay Scheponik" <Jay (E-Mail Removed)> wrote in
message news:A98482E2-31BA-43AC-9542-(E-Mail Removed)...
> I have some people in the office that are not able to access
> attachments on
> emails. However, when they forward the email to some other people in
> the
> office, the attachments are there and accesible. Where would i find
> the cause
> of this?


The problem could be the attachment is still in the received copy of
your forwarded e-mail but the recipient can't see it. Have them check
the size of the mail item they receive from you to see how big it is.
Perhaps you are incorrectly using Rich-Text Format (RTF) when sending
e-mails. RTF should only be used between Outlook users sending to
each other within the same Exchange organization. That is, unless you
are using Exchange (to prevent mangling of RTF mails) and unless you
can guarantee the recipient also uses Outlook, you should not be using
RTF. Normally you should only send in plain-text for HTML formats.
The recipient might have a Winmail.dat attachment which contains your
RTF message but they might not have a means of opening it because
their e-mail client doesn't support Microsoft's proprietary RTF
document standard. See:

http://www.quarella.co.uk/email/attachments.html
http://support.microsoft.com/kb/278061/en-us
http://support.microsoft.com/kb/830302/en-us

I suppose I should lay it out like this:

Exchange Server 2007
all users running Outlook 2003

UserA recieves an email that sender (external) says has an attachment. UserA
sees no attachment. UserA forwards this message to UserB (internal). UserB
sees and can access the attachments. UserA does not always experience this
issue but when they do, UserB can always see and access the attachments.

"Jay Scheponik" wrote in message
news:C7AE18EB-AE37-48FC-A876-(E-Mail Removed)...
>I suppose I should lay it out like this:
>
> Exchange Server 2007
> all users running Outlook 2003
>
> UserA recieves an email that sender (external) says has an
> attachment. UserA
> sees no attachment. UserA forwards this message to UserB (internal).
> UserB
> sees and can access the attachments. UserA does not always
> experience this
> issue but when they do, UserB can always see and access the
> attachments.


Unfortunately Outlook bastardizes the e-mail when it saves it into
their database file (PST). You don't get to see the real e-mail
(i.e., its raw format). You can't use Outlook Outlook Express to
receive a test e-mail with the attachment and then look at the raw
e-mail (Ctrl+F3) to see if the MIME parts exist in the e-mail to
delineate the parts where the attachment is encoded - because OE won't
connect to Exchange. Even right-clicking in the e-mail body and
selecting View Source won't show the CID used within the e-mail to
point at where Outlook saved the object (attached file). You can use
an add-in, like PocketKnife Peek to see that there is an attachment
(but not get at it).

As a test, receive an e-mail with an attachment. Then start to
forward it but do not send it. In the new-mail window that appears
(the embedded editor in Outlook, not when using Word as the e-mail
editor), the attached file should show up in the list. See if you can
open or save it from there.

Are you using a Windows Rights Server to regulate who can look at the
content of internal e-mails?

I had asked if RTF was used to format the e-mail to which the file got
attached. Outlook displays a paperclip icon for disposition=attached
content (attached files). RTF embeds the attachment
(disposition=inline) so the recipient that uses an RTF-capable e-mail
client (Outlook) won't see a paperclip icon because the attachment is
inline in the body. It might be possible that the icon shown in an
RTF-formatted e-mail that the RTF-enabled recipient sees normally in
the body is hidden by other content. I only use the embedded editor
in Outlook. I don't use Word as the e-mail editor. Which one are the
problematic users using? If they use Word to view e-mails, see what
happens when they disable using Word.