From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN: 
X-Spam-Status: No, score=-2.1 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00,
 URIBL_BLOCKED shortcircuit=no autolearn=unavailable version=3.3.2
X-Original-To: unicorn-public@bogomips.org
Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net
 (Postfix) with ESMTP id 6CA9C1F7D7; Sat,  4 Oct 2014 23:22:41 +0000 (UTC)
Date: Sat, 4 Oct 2014 23:22:41 +0000
From: Eric Wong <e@80x24.org>
To: unicorn-public@bogomips.org
Subject: [ANN] email submission port (587) enabled
Message-ID: <20141004232241.GA23908@dcvr.yhbt.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
List-Id: <unicorn-public@bogomips.org>

For those of you unfortunate enough to be stuck behind firewalls
or rely on crap webmail interfaces, you can pass the:

   --smtp-server-port=587 --smtp-server=bogomips.org

options to "git send-email" when sending patches/plain-text mail
to unicorn-public@bogomips.org

You'll still need a valid From: address to receive replies and
participate in the discussion if you're not subscribed to the
mailing list.

Note: "git send-email" can send regular plain-text emails with
valid Subject: and From: headers.  If you're not familiar with
email message headers, they're nearly identical to HTTP, and
you can use "git format-patch"-generated patches as a guide.

Caveats:

- This will expose your client IP address to the world
  (but many existing mail setups do that anyways)

- This will not work for Cc-ing others in replies directly,
  but works for all @bogomips.org email addresses,
  so you may want to add "--suppress-cc=all" or similar.

Patchbomb away! :D

ref: http://www.ietf.org/rfc/rfc4409.txt
  https://www.kernel.org/pub/software/scm/git/docs/git-send-email.html