Unable to send messages BCC

What steps will reproduce the problem?
1. Send an email with only a Bcc recipient

What is the expected output? What do you see instead?
Mail should send along as normal, but instead it bounces back.

The problem is that the email being passed to gpg-mailgate doesn't contain Bcc 
information. Here's an example email that was sent Bcc to 
notmyrealemail@gmail.com:

Received: from [0.0.0.0] (localhost [127.0.0.1])
        by mydomain.foo (Postfix) with ESMTP id 4EA12512BB1
        for <notmyrealemail@gmail.com>; Wed,  7 Mar 2012 22:18:41 +0000 (UTC)
Message-ID: <4F57DED2.6050904@mydomain.foo>
Date: Wed, 07 Mar 2012 15:18:58 -0700
From: Me <me@mydomain.foo>
MIME-Version: 1.0
To: undisclosed-recipients:;
Subject: test bcc email
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

test bcc email

Ok, so maybe we could look at the Received header to determine the Bcc list? 
Wrong. Here's what happens when you have multiple Bcc recipients, you get 
multiple emails like this:

Received: from [0.0.0.0] (localhost [127.0.0.1])
        by mydomain.foo (Postfix) with ESMTP id 60D7D51A9E8;
        Wed,  7 Mar 2012 22:25:06 +0000 (UTC)
Message-ID: <4F57E065.6030903@mydomain.foo>
Date: Wed, 07 Mar 2012 15:25:41 -0700
From: Me <me@mydomain.foo>
MIME-Version: 1.0
To: undisclosed-recipients:;
Subject: bcc test2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

bcc test2

Now there is *no way* for gpg-mailgate to know the recipients of this email 
because it's not being passed at all. Without being sent a Final-Recipient or 
Original-Recipient header by Postfix, gpg-map can't handle Bcc emails. I don't 
have enough knowledge of Postfix to determine a solution.
Original issue reported on code.google.com by paul.bro...@gmail.com on 7 Mar 2012 at 10:30
ovpn-to / gpg-mailgate.py

Unable to send messages BCC #5
