Is it legal to publish email that someone sent to me?
<p><em>I'm not asking whether it is ethical - that would be a totally different question.</em></p>

<p><strong>I'm asking whether it is legal?</strong></p>

<p>In my book - in my way how I interpret consensual reality - once I press <code>SEND</code> button it is transmitted via email client, via email server, via internet, to a destination email server....  On the way there are so many entities that can intercept the traffic that I effectively consider all my communication public.</p>

<p>Event when using GPG / PGP:</p>

<ul>
<li>I don't trust myself <em>(I'm yet to learn reliable way of generating private key)</em></li>
<li>I don't trust my device <em>(see what they did to <a href="https://media.ccc.de/browse/conferences/camp2015/camp2015-6799-how_to_destroy_a_laptop_with_top_secrets.html#video" rel="noreferrer">Snowden's laptop</a>)</em></li>
<li>I don't trust the recipient <em>(they can publish it online)</em></li>
</ul>

<p>I'm thinking about implementing a <strong>buffer system</strong>:</p>

<ul>
<li>email is received</li>
<li>automated reply: <em>"we consider your email public, 7 days to opt-out"</em></li>
<li>sender has an option to opt-out, ignore, or edit the email <em>(to remove non-public bits of information)</em></li>
<li>after 7 days with no action it defaults to be public</li>
</ul>

<p><strong>Would that system make it any more legal?</strong></p>

<hr>

<p>UPDATE: I'm still thinking about designing email system. Maybe best of two worlds:</p>

<ul>
<li>one public that goes directly to email group</li>
<li>one private, that strongly suggest all messages to be encrypted</li>
<li><em>(general philosophy - full transparency, everything in public - without infringing anyone's right and playing by the cultural norms accepted by society)</em></li>
<li><strong>THINK:</strong> email password resets are not compatible with public email inbox?</li>
</ul>

<p>Generally speaking, if a person sends you an email you can publish it. Like if they call you a bunch of nasty names, or threaten you in some way, that information is yours and you can publish it. </p>

<p>However, I'll give you three scenarios where you should not publish an email sent to you (and I'll edit to add more if they come up). </p>

<p><strong>Private facts. There is a tort called publication of private facts.</strong></p>

<blockquote>
  <p>A plaintiff must establish four elements to hold someone liable for
  publication of private facts:</p>
  
  <ol>
  <li>Public Disclosure: The disclosure of facts must be public. Another way of saying this is that the defendant must "give publicity" to the
  fact or facts in question.  </li>
  <li>Private Fact: The fact or facts disclosed must be private, and not generally known.  </li>
  <li>Offensive to a Reasonable Person: Publication of the private facts in question must be offensive to a reasonable person of ordinary
  sensibilities.  </li>
  <li>Not Newsworthy: The facts disclosed must not be newsworthy. Stated differently, the facts disclosed must not be a matter of legitimate
  public concern. </li>
  </ol>
</blockquote>

<p>From <a href="http://www.dmlp.org/legal-guide/publication-private-facts" rel="noreferrer">Digital Media Law Project</a></p>

<p>Note one thing - the offensive fact does not need to have been completely private for you to be liable, it must not have been <em>generally known</em>.  In other words, someone like you who has a really low "public" bar needs to be careful. </p>

<p>Also note that your buffer system might not help if the facts you publish are about someone other than the email sender; you are the one who published them. </p>

<p><strong>Stolen Information</strong> </p>

<p>If someone sends you some intellectual property of a third party it is not yours to publish. Trade secrets, copyrighted works, prototype photos, etc.  The sender might be breaking the law by sending the stuff to you but you're the one who published it so you can join as co-defendants.</p>

<p><a href="http://www.wired.com/2012/12/fbi-charges-barrett-brown/" rel="noreferrer">Barrett Brown was indicted for sharing a link to some stolen information</a>. A link! He's in prison on other charges.</p>

<p><strong>Copyright held by the original sender (ht to @Dave_D)</strong></p>

<p>If the sender is the original author of the email, then the sender holds the copyright to the body of the email. Publishing the email violates the copyright. However, you could account for this in your buffer. Maybe. I am not sure is that is explicit enough.</p>

<p><strong>No, it may not be legal.</strong></p>

<p>Most original material is subject to the <strong><em>copyright</em></strong> laws.  If one authors a poem, and sends it to a recipient by email, the poem is still copyrighted, and the author could still sue the recipient if the recipient uses the poem in ways which were not implicitly or explicitly authorised.</p>

<p>There are various <em>fair use</em> exceptions to the copyright law, as well as common knowledge like the fact that posting to public mailing lists, especially without the <code>X-No-Archive: yes</code> headers or some such, would result in the correspondence being picked up by various archival systems.  Same goes for emails to public officials, which would be a matter of public record.  (In fact, Jeb Bush (the 2016 presidential nominee) infamously released his whole mailbox (from his time as a Florida governor) a few months ago, which erroneously wasn't scrubbed to ensure that private information like social security numbers were excluded; but his whole mailbox was already available for anyone to inspect even prior to this event, should they have filed one of those public information requests with the state.)</p>

<p>If you want to publish all emails sent to a private email address of you as an individual, you are not a public official, and people emailing you would not otherwise know that you publish all your emails, then you might have to implement an opt-in system instead.  For example, you could use one of those please-confirm-your-email type of systems that were originally designed to protect against spam, to inform the senders that you would only accept their email if they give you permission to publish it, and that all further emails would be automatically published without any further confirmations.  You could also modify such a system to potentially automatically publish and/or discard emails depending on the <code>X-Archive</code> and <code>X-No-Archive</code> headers.</p>

copyright internet privacy hacking security