Our team uses the Ruby gem hitch to manage pairing. You set it up with a group email address (e.g. [email protected]) and then tell it who is pairing:

$ hitch james tiffany

Hitch then sets your Git author configuration so that our commits look like

commit 629dbd4739eaa91a720dd432c7a8e6e1a511cb2d
Author: James and Tiffany <[email protected]>
Date:   Thu Oct 31 13:59:05 2013 -0700

Unfortunately, we've only been able to come up with two options:

1. [email protected] doesn't exist. The downside is that if Travis CI tries to notify us that we broke the build, we don't see it.
2. [email protected] does exist and forwards to all the developers. Now the downside is that everyone gets spammed with every broken build by every pair.

We have too many possible pair to do any of the following:

1. set up actual [email protected] email addresses or groups (n^2 email addresses)
2. set up forwarding rules for [email protected] (n^2 forwarding rules)
3. set up forwarding rules for [email protected] (n forwarding rules for each of n developers)

Does anyone have a system that works for them?