I've just got a bounce from sending an email to one of my redirects.
The header from the bounced messsage is below (with usernames/domains obscured).

The original message was sent from a gmail account to an address unconnected to Plus/Force9, and CCd to 2 redirects on my force9 hosted domain (obscured as "force9 hosted domain1"). Only one of the redirects seems to have bounced (so far - it took many hours for the bounce to appear). Just to complicate things, the sending gmail account is setting the From address to be a username on a different force9 hosted domain (obscured as "force9 hosted domain2").

The headers and bounce message don't seem to contain any useful info as to why it failed, as far as I can see. Only one of the redirects (obscured as "<redirect2>") seems to have bounced so far, though they are both redirecting to exactly the same external address.

This all worked OK before the changes.

Are redirects flakey? Is there something in the header that says why it failed? If not, then please add something.

-----------
From:   Mailer-Daemon@fhw-sunmxcore04.plus.net
Subject:
Date: 6 December 2008 15:04:13 GMT+09:00
To:   <username>@googlemail.com
This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  <redirect2>@<force9 hosted domain1>

------ This is a copy of the message, including all the headers. ------

Return-path: <username>@googlemail.com>
Received: from [212.159.7.38] (helo=mx.ptn-ipin03.plus.net)
     by fhw-sunmxcore04.plus.net with esmtp (PlusNet MXCore v2.00) id 1L8T0W-0003gy-8B
     for <redirect2>@<force9 hosted domain1>; Fri, 05 Dec 2008 05:13:40 +0000
Received-SPF: None identity=pra; client-ip=209.85.198.249;
  receiver=mx.ptn-ipin03.plus.net;
  envelope-from="<username>@googlemail.com";
  x-sender="<username>@googlemail.com";
  x-conformance=sidf_compatible
Received-SPF: Pass identity=mailfrom; client-ip=209.85.198.249;
  receiver=mx.ptn-ipin03.plus.net;
  envelope-from="<username>@googlemail.com";
  x-sender="<username>@googlemail.com";
  x-conformance=sidf_compatible
Received-SPF: None identity=helo; client-ip=209.85.198.249;
  receiver=mx.ptn-ipin03.plus.net;
  envelope-from="<username>@googlemail.com";
  x-sender="postmaster@rv-out-0708.google.com";
  x-conformance=sidf_compatible
Authentication-Results: mx.ptn-ipin03.plus.net; dkim=pass (signature verified [TEST]) header.i=@googlemail.com
X-SBRS: 5.2
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuIAAGlHOEnRVcb5mGdsb2JhbACTET4BAQEBAQgJDAcRr1spCItOAQSBegiDIg
X-IronPort-AV: E=McAfee;i="5300,2777,5454"; a="958567"
X-IronPort-AV: E=Sophos;i="4.33,718,1220223600";
   d="scan'208";a="958567"
Received: from rv-out-0708.google.com ([209.85.198.249])
  by mx.ptn-ipin03.plus.net with ESMTP; 05 Dec 2008 05:13:39 +0000
Received: by rv-out-0708.google.com with SMTP id c5so4400687rvf.24
        for <redirect2>@<force9 hosted domain1>; Thu, 04 Dec 2008 21:13:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlemail.com; s=gamma;
        h=domainkey-signature:received:received:in-reply-to:references
         :mime-version:content-type:message-id:content-transfer-encoding:cc
         :from:subject:date:to:x-mailer:sender;
        bh=r7Q6xa65Ra8CxPWbLB9wNwrPeEBPek+xTOU05uVoGzc=;
        b=DjInUbSbbNpGNDtI4fopLE5odkQnZlYYNuft52Y9xz0xbdiMtP6FXpE1YD7O3tzlQ1
         +vfkBsFfIYlqbCBWdZoo8m3Dmrj5BBvQRulw3jLo+0sKV8Gmw+dz/puDi+xqbCY2ZtAC
         F4ce2+2l8nSmNiOT87hIpmhljnjmGTW2YR/hU=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=in-reply-to:references:mime-version:content-type:message-id
         :content-transfer-encoding:cc:from:subject:date:to:x-mailer:sender;
        b=dbRbeE+VHPsn00b76WrhM1wlGJANo0kPbDN2RGXlJhND26cf++9L3//XCvEsDAgpxr
         lsGuwxBofEXpCymDp7PRKD+kiewgTVJHBfT4pQeJ3hQvmzRWt3j3xirfYfYzJePZzC+U
         8GRutPt8+1UnJyOC5AT0iACcaPfswuy8JvzNQ=
Received: by 10.140.157.4 with SMTP id f4mr7353031rve.84.1228454018250;
        Thu, 04 Dec 2008 21:13:38 -0800 (PST)
Received: from ?192.168.24.93? (y008212.ppp.asahi-net.or.jp [118.243.8.212])
        by mx.google.com with ESMTPS id l31sm17447365rvb.2.2008.12.04.21.13.36
        (version=TLSv1/SSLv3 cipher=RC4-MD5);
        Thu, 04 Dec 2008 21:13:37 -0800 (PST)
In-Reply-To: <3D4B3E3ABEA3BA44831E0C37E81E8D7504BAAEC3@RRAMEXC1.leggmason.com>
References: <3D4B3E3ABEA3BA44831E0C37E81E8D7504BAAEC3@RRAMEXC1.leggmason.com>
Mime-Version: 1.0 (Apple Message framework v624)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <e40a18c31df3da9adf36825660d5603f@<sender force9 hosted domain>
Content-Transfer-Encoding: 7bit
Cc: <redirect1>@<force9 hosted domain1>,
 <redirect2>@<force9 hosted domain1>
From: <username>@<force9 hosted domain2>
Subject: Re: X address isn't working
Date: Fri, 5 Dec 2008 14:13:34 +0900
To: "Name" <username>@LMUS.LeggMason.com>
X-Mailer: Apple Mail (2.624)
Sender: Woll Newall <username>@googlemail.com>
X-pn-pstn: Spam 0

I'm not aware of any problems affecting redirects. Are you able to PM me with the unsanitised headers and full body of the bounce message? I'll then make sure this gets looked into tomorrow. Is it just one of your redirects that's affected and is the problem intermittent or is no email getting through at all?