I have several users in my office with BB's, but I have ye to set up a BES server (We just moved from Exchange to GroupWise, so I'm still fighting that fire). As a result, all my users have a GroupWise rule set to forward a copy of emails received to their office email address to their Blackberry.
Not all users are on the same carrier - I have Bell, Telus and Rogers users.
However, all of them are having the following problem:
Periodically, ( At this point I haven't been able to establish a pattern) the forwarded message will get bounced by the respective BB server with a 554 message. As such, the user does not get the original message to the blackberry, but ironically, the undeliverable message then gets forwarded to the blackberry by the GroupWise rule just fine. Here's the 554 message I get:
The attached file had the following undeliverable recipient(s):
Transcript of session follows:
Response: 554 mx01.bis.na.blackberry.com
The attached file looks something like this:
Received: from DOM-MGA-MTA by minerva.can.globalstar.com
with Novell_GroupWise; Tue, 29 Aug 2006 03:02:56 -0400
Received: from dino.corp.globalstar.com ([***.***.***.***])
by hermes.corp.globalstar.com with ESMTP; Tue, 29 Aug 2006 00:01:42 -0700
Received: from mercury.ss.airtouch.com (mercury.ss.airtouch.com [184.108.40.206])
by dino.corp.globalstar.com (8.12.10+Sun/8.12.10) with ESMTP id k7T71gZS002741
for <email@example.com>; Tue, 29 Aug 2006 00:01:42 -0700 (PDT)
Received: (from root@localhost)
by mercury.ss.airtouch.com (8.8.8p2+Sun/8.8.8) id HAA10022;
Tue, 29 Aug 2006 07:01:51 GMT
Date: Tue, 29 Aug 2006 07:01:51 GMT
From: "ARSystem" <ARSystem@globalstarusa.com>
Subject: ATSS00000059352 has been unassigned for over 24 hours
Content-Type: multipart/mixed;boundary="---------- =_52656D656479426F.756E646172792E"
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
A 554 error is a very generic 'F* You' from the recipient mail server, so there's no way of knowing the specific issue.
Has anyone encountered this before?
Christopher C. West