Hello,
I recieved a strange email from some company. The mail headers do not list me
as recipient so I do not know why I did recieve the mail at all. Also the top 'FROM '
header line (and the derieved return path) is a bit strange and I do not really know
what to make of it. I attached the email to this letter, so if any of You mail gurus
are listening perhaps You know why I get this mail and what to make of the header line.
Bye,
Robert S. {:).
--
Robert S"utterlin
eMail: [EMAIL PROTECTED]
office phone: +(49)89 / 3299 - 3545
office address: Giessenbachstrasse, POBox 1603, 85740 Garching, Germany
priv phone: (+49)89 / 54 76 31 83
address: Siglstr. 15, 80686 Muenchen, Germany.
This is an automated message from C & C's satellite E-Mail system.
Your E-Mail message has been delivered.
Your message contains attachments. Please send attachments only if
required for operations.
Thank you for your cooperation,
C & C's E-Mail Computer
The e-mail message follows:
-----------------------------------------------------------------
> Received: from buffy.tpgi.com.au([203.12.160.34]) (2198 bytes) by
>kraken.cctechnol.com
> via sendmail with P:esmtp/R:batch_it/T:batch_smtp
> (sender: <[EMAIL PROTECTED]>)
> id <[EMAIL PROTECTED]>
> for <[EMAIL PROTECTED]>; Wed, 29 Mar 2000 20:17:11 -0600 (CST)
> (Smail-3.2.0.111 2000-Feb-17 #2 built 2000-Mar-20)
> Received: (from smtpd@localhost)
> by buffy.tpgi.com.au (8.9.3/8.9.3) id MAA18448
> for <[EMAIL PROTECTED]>; Thu, 30 Mar 2000 12:17:00 +1000
> Received: from bri2-56k-098.tpgi.com.au(203.29.144.98), claiming to be "serra"
> via SMTP by buffy.tpgi.com.au, id smtpdKbkZme; Thu Mar 30 12:16:49 2000
> Received: by serra (sSMTP sendmail emulation); Thu, 30 Mar 2000 12:23:05 +1000
> Date: Thu, 30 Mar 2000 12:23:04 +1000
> From: Darrin Mison <[EMAIL PROTECTED]>
> To: Sam Alleman <[EMAIL PROTECTED]>
> Subject: Re: update encoding?
> Message-ID: <[EMAIL PROTECTED]>
> References: <[EMAIL PROTECTED]>
> Mime-Version: 1.0
> Content-Type: multipart/signed; micalg=pgp-md5;
> protocol="application/pgp-signature"; boundary="opJtzjQTFsWo+cga"
> X-Mailer: Mutt 1.0i
> In-Reply-To: <[EMAIL PROTECTED]>; from
>[EMAIL PROTECTED] on Wed, Mar 29, 2000 at 10:45:23PM +0900
> X-Operating-System: Linux serra 2.2.12-20
>
>
> --opJtzjQTFsWo+cga
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: quoted-printable
>
> guessing here, but you use pgp to sign a message which=20
> you have postponed and then you get this when you send=20
> it again. Don't know how to avoid it or if to.
>
>
> As Sam Alleman<[EMAIL PROTECTED]> once said:
> >=20
> > Hello again,
> >=20
> > Can anyone tell me what this message is all about:
> >=20
> > ~~/tmp/mutt-xena-22566-0 [#1] modified. Update encoding? ([y]/n):
> >=20
> > What does this mean, and is there any way to bypass this question?
> > Thanks.
> >=20
> > Sam
>
> --
> Darrin Mison
> --=20
> "Necessity is the mother of invention" is a silly proverb. "Necessity
> is the mother of futile dodges" is much nearer the truth.
> -- Alfred North Whitehead
>
> --opJtzjQTFsWo+cga
> Content-Type: application/pgp-signature
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.1 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
>
> iEYEAREBAAYFAjjiuogACgkQbJuZmIkY3S6B5ACeMgFDnAoSqSP099T75Tq0D+xm
> 7JAAn0LT5oLioplDYNnuZyM15xGI2UV2
> =//v7
> -----END PGP SIGNATURE-----
>
> --opJtzjQTFsWo+cga--
> .
