Re: SMTP RFC: "MUST NOT" change or delete Received header

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This isn't new for mail processing software developers. US EPCA. Product liability concerns. You will pay more in commercial insurance. Tamper with passthru, routing mail, you are at more risk, more so than others that don't. There were court precedence not only with tampering, but related to ownership and privacy issues. Google, yahoo, now facebook, etc, have all relied on the middle ware ownership legal concept to help get away with the privacy, tampering related borderline ethical issues. Congress has relaxed the laws to allow for "Good Samaritan" provisions, where you are allowed to do more, but don't go overboard. Of course, push come to shove, the devils would be the details.

Remember, its not just about protecting yourself, but protecting your customers are well.

On 3/29/2014 1:16 PM, John Levine wrote:
In article <CAPv4CP9nFmYfondSrqA7ETkhvCMe4YrqRjOdGZuPiLz2kZzXrw@xxxxxxxxxxxxxx> you write:
I think the privacy beach from exposing intermediate steps is small,

agreed

and in some cases knowledge of the routing may be required by law.

That seems unlikely.  Got any citations?

R's,
John




--
HLS






[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]