Re: I-D ACTION:draft-ietf-msgtrk-smtpext-01.txt

On Wed, 28 Mar 2001 16:33:27 -0800 Chris Newman <[email protected]> 
wrote:

> I think you need to distinguish between the different types of 
> forwarding. 
> One class is "public automated unconditional MTA-level forwarding" which is 
> always tracked.  Private manual conditional UA-level forwarding is likely 
> never tracked.  Then there's a bunch of gray areas (e.g., MTA-level Sieve 
> redirect) which may require a site-level or user-level choice.

I think that we should presume that sieve redirection is done during final
delivery and is directed by the user 100% of the time.   I'm sure that 
there are arguments for other uses which is fine, but I think that it 
intent that matters.   If it is a user rule, then it is final delivery and
that is in MUA land.   Final delivery through the sieve engine should 
terminate tracking (I think).

> Some discussion of the privacy issues with respect to tracking forwarded 
> messages is in order.  If the forwarding isn't public information, the 
> tracking system may need to suppress some of the results.  An example would 
> be a [email protected] address forwarded to an individual.  Perhaps the 
> site doesn't want that individual's name known to reduce headhunter calls.

Hmm ... so this would typically hit the aliasing engine in most MTA's.   
Unless I'm mistaken, we have recommended treating this exactly as DSN 
does, which I believe differentiates between final recipient and original 
recipient.   Does the DSN spec allow for site specification of whether or 
not they will report differences between orignal and final recipient?

In any case, the answer to the above question doesn't really matter.   We 
should just do as DSN does I think.

Cheers.

---
Steve Hole
Chief Technology Officer
ACI - MessagingDirect
<mailto:[email protected]>
Phone: 780-424-4922