Re: Unpacking TNEF/winmail.dat files at mail server

--=-HIflCSHvbjOmGI0qHyTA
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Thu, 2004-10-21 at 08:50, Kevin Fries wrote:

>=20
> I have one subcontractor that is just killing me. She is using Outlook,
> which in and of itself is a virus factory, but also has Rich Text turned
> on, which now sends us important attachments encapsulated in a file
> called winmail.dat. Our users are using either Mozilla or Outlook
> Express (for those that refuse to listen to me). The OE users are not
> seeing the winmail.dat file at all, but the Mozilla users are.
>=20
It occurs to me that the party causing the problem ought to be the one
who fixes it. I assume this subcontractor makes money from their
dealings with you. Are you in a position to
(ask|plead|suggest|tell|demand) that mail sent to your company be plain
text? Granted, since she is a Windows user, she may know nothing about
changing the settings for Outlook, so you might have to explain how it
is done.
> What I would like to do (short of strangling the vendor) is to use
> something like the tnefclean perl script on every message that comes in
> to fix the damage done by Microsoft and return a message with normal
> attachments. Then let Postfix and Kaspersky do their things.
>=20
> Is this possible? Is there a magic keyword I should be googling on?
> Better yet a How-To?
>=20
We use amavisd-new to quarantine anything with a TNEF attachment, so I
am not familiar with the script you refer to. I do have one question,
though. Can't Kaspersky scan TNEF?
--=20
Robin Lynn Frank - Director of Operations
Paradigm-Omega, LLC - http://paradigm-omega.com
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D
SpamTrap: pf@null-route.merseine.nu
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D
We support boycotting overseas outsourcers.

--=-HIflCSHvbjOmGI0qHyTA
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Sed quis custodiet ipsos custodes?

iD8DBQBBd+K2o0pgX8xyW4YRAn4RAKDP59k+MyiKEXCwVhblpN/IPeoORgCfQ8nJ
8jNqrg+2nBMMZICMqCI2hys=
=rPEN
-----END PGP SIGNATURE-----

--=-HIflCSHvbjOmGI0qHyTA--