PDF attachments being detected as Application/Octet-Stream instead of application/pdf

[Leythos]

We have a customer that sends PDF's from their copiers and from
workstations that are created using Adobe Acrobat.

When they send to people using WatchGuard Firebox X series units, using
Exchange 2003 Std, Outlook 2003 or Outlook 2007, and have converted the
document to PDF using Adobe, the firewall at the site they send to
detects it as Application/Octet-Stream.

If the send the PDF converted via their copier it properly shows as
Application/PDF.

From all of my other customers, and they all use WatchGuard firewalls
also, we don't see this problem. I don't see it from my own office when
I send PDF's to the same customer that detects that AOS from the other
customer.

Is there some conversion setting for attachments that could cause this?

--

Leythos
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
spam9...@rrohio.com (remove 999 for proper email address)

[John Fullbright]

The encoding is set on the sending side. The problem is one on the
customer's end. If the sender is using Exchange, then they likely are
missing a mime mapping setting.

"Leythos" <vo...@nowhere.lan> wrote in message
news:MPG.220122a8f...@Adfree.usenet.com...

[Leythos]

In article <umfsl#fXIHA...@TK2MSFTNGP04.phx.gbl>,
fjohn@donotspamnetappdotcom says...

> The encoding is set on the sending side. The problem is one on the
> customer's end. If the sender is using Exchange, then they likely are
> missing a mime mapping setting.

Any idea where I would look for this?

This is not my area of expertise, so any clues or pushes in the right
direction are appreciated.

[John Fullbright]

You're on the receiving end, you wouldn't.

"Leythos" <vo...@nowhere.lan> wrote in message

news:MPG.2201792dc...@Adfree.usenet.com...

[Leythos]

In article <ujpSSrgX...@TK2MSFTNGP04.phx.gbl>,
fjohn@donotspamnetappdotcom says...

> You're on the receiving end, you wouldn't.

But I know their IT manager and if I can find the area on my Exchange
server, which is not having the problem, I might be able to help them
with theirs by seeing what is missing.

[John Fullbright]

http://support.microsoft.com/kb/313730/en-us

"Leythos" <vo...@nowhere.lan> wrote in message

news:MPG.22019705c...@Adfree.usenet.com...

[John Fullbright]

http://support.microsoft.com/kb/313730/en-us

You want to associate application /pdf with pdf.

If the mime mapping is missing, it gets encoded the default;
application/octet-stream.

"Leythos" <vo...@nowhere.lan> wrote in message

news:MPG.22019705c...@Adfree.usenet.com...

[Leythos]

In article <#Ft0rNkX...@TK2MSFTNGP04.phx.gbl>,
fjohn@donotspamnetappdotcom says...

> http://support.microsoft.com/kb/313730/en-us
>
> You want to associate application /pdf with pdf.
>
> If the mime mapping is missing, it gets encoded the default;
> application/octet-stream.

Thanks - We will look at it today and let you know.

[Leythos]

In article <MPG.22026ab9e...@Adfree.usenet.com>,
vo...@nowhere.lan says...

> In article <#Ft0rNkX...@TK2MSFTNGP04.phx.gbl>,
> fjohn@donotspamnetappdotcom says...
> > http://support.microsoft.com/kb/313730/en-us
> >
> > You want to associate application /pdf with pdf.
> >
> > If the mime mapping is missing, it gets encoded the default;
> > application/octet-stream.
>
> Thanks - We will look at it today and let you know.

They found, as was suggested, that the PDF definition was missing and
added it.

We've actually started to see a number of people using exchange that
have this broken, interesting, but it seems to have come from people
that were running Exchange 2000 previously and upgraded to 2003.