Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 20 Nov 2003 05:57:39 +0100
From:      Harald Schmalzbauer <h@schmalzbauer.de>
To:        "Minnesota Slinky" <mnslinky@yahoo.com>, "'Gregory Sutter'" <gsutter@zer0.org>, "'SWIT'" <mark@s-wit.net>
Cc:        chat@freebsd.org
Subject:   Re: SCO going after BSD???
Message-ID:  <200311200557.45071@harrymail>
In-Reply-To: <000c01c3af1e$b42e9fe0$6801a8c0@Nomad>
References:  <000c01c3af1e$b42e9fe0$6801a8c0@Nomad>

next in thread | previous in thread | raw e-mail | index | archive | help

--Boundary-02=_InEv/OqNLREpMwX
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

On Thursday 20 November 2003 05:28, Minnesota Slinky wrote:
>=20
> -----Original Message-----
> From: owner-freebsd-questions@freebsd.org
> [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of Gregory Sutter
> Sent: Wednesday, November 19, 2003 7:39 PM
> To: SWIT
> Cc: chat@FreeBSD.org; freebsd-questions@freebsd.org
> Subject: Re: SCO going after BSD???
>=20
> On 2003-11-19 20:11 -0500, SWIT <mark@s-wit.net> wrote:
> > is this a unix thing or what.
> >  many times i get messages from the list were the message is an
> attachment
> > and not in the email.
> > was curious as to why.
>=20
> The messages you see as attachments are messages that have been PGP
> signed to prove their authenticity.  The problem is with Outlook
> Express.  Not only does it fail to support PGP/MIME (many programs
> don't support PGP/MIME and still can display PGP signed email
> correctly), but it is actually broken.  Outlook Express ignores the
> following MIME headers in the message:
>=20
>   Content-Type: text/plain; charset=3Diso-8859-1
>   Content-Disposition: inline
>=20
> These headers show that the part is not an attachment but should be
> displayed inline, and that it contains pure text that doesn't need a
> special handler to be displayed.  Why Outlook Express fails to
> recognize this, and why Microsoft fails to issue a patch to fix the
> problem, is unknown.
>=20
> [
> Response paraphrased from:
> http://lists.gnupg.org/pipermail/gnupg-users/2003-September/020155.html
> ]
>=20
> Greg
> --=20
> Gregory S. Sutter                   Fighting ignorance since 1975!
> mailto:gsutter@zer0.org             (It's taking longer than I thought.)
> http://zer0.org/~gsutter/
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> freebsd-questions-unsubscribe@freebsd.org
>=20
>=20
> I talked to a couple of people who do beta testing for Microsoft and
> they said the issue came up a few years ago.  According to them (one
> being my father), it has to do with security and virus protection.

Yea, of course I undertand that they're concentrating on text/plain viruses=
=2E=20
=46irst they have to get this problem fixed, then they'll perhaps have a lo=
ok=20
at executables. And if they make bulbs, darkness will be standard...

SCNR

=2DHarry

P.S.: Please always answer above signatures. Good MUAs will strip them when=
=20
quoting so everybody has to change settings to be able to answer!


> Again, this is second-hand, so take it for what it's worth...
>=20
> Eric F Crist
> President
> AdTech Integrated Systems, Inc
> (952) 403-9000
>=20
>=20
>=20
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o=
rg"
>=20
>=20

--Boundary-02=_InEv/OqNLREpMwX
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQA/vEnIBylq0S4AzzwRAsPOAKCQOKElRg80HMAPKGc8PWFQ9scAEQCfQ/3N
MaIip9GAnKlXLBQ263V8q7E=
=Hb8d
-----END PGP SIGNATURE-----

--Boundary-02=_InEv/OqNLREpMwX--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200311200557.45071>