Mailing List SIMS@mail.stalker.com Message #6558
From: Richard Johnson <rdump@river.com>
Subject: Re: feature request
Date: Thu, 20 Jul 2000 09:08:45 -0600
To: SIMS Discussions <SIMS@mail.stalker.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

At 08:15 -0600 on 7/20/00, Franck Horlaville wrote:

> This is great. What would be even greater would be to add for which
> account it was received for :
>
> Received from xxx by yyyy with id zzzzz; date; for account@domain.com


SIMS does this.  Here's an example:

Received: from mail.customer.example.com ([10.35.111.93] verified) by
colorado.river.com (Stalker SMTP Server 1.8b8) with ESMTP id S.0000054145 for
<employee at river com>; Thu, 20 Jul 2000 08:01:22 -0700

Now, think for a moment about whether you're Bcc:ing my boss, boss at river
com, on a message telling me to get my ass in gear and provide the deliverable
or you're going to have to take your business elsewhere.  Both my and boss'
account are handled by the same server, but you said to Bcc: boss, meaning you
don't want me to know the message was also sent to him.

Of course, in an SMTP transaction, there is no way for SIMS to know which of
the envelope recipients was Bcc:ed, and which were To: or Cc:ed.  And after
the SMTP transaction there is nothing to prevent me from looking at the
Received headers.  If you were an MTA, what would you do in such a situation?

SIMS, as all other well-bred MTAs, doesn't show a "for <address@example.com>"
clause in Received headers when there is more than one destination address in
the envelope, to protect Bcc:s.


Richard

-----BEGIN PGP SIGNATURE-----
Version: PGP Personal Privacy 6.5.2
Comment: www.europarl.eu.int/dg4/stoa/en/publi/166499/execsum.htm

iQA/AwUBOXcV9WKSuJuuNAZUEQJ9SACfW/eF4OS1L01kocNpuYkBQz6WFNwAoKpi
gUSKLRn3fa8kepfRgBfp2/XK
=lqFK
-----END PGP SIGNATURE-----


Subscribe (FEED) Subscribe (DIGEST) Subscribe (INDEX) Unsubscribe Mail to Listmaster