We are having problems sending to a domain that uses greylisting, where the GWIA will return an undeliverable instead of deferring the message and trying again later. Here is what the GWIA log shows (actual names changed):

11:05:23 720 MSG 3713743 Sender: dprill@ourdomain.edu
11:05:23 720 MSG 3713743 Building message: sc2b24f3.556
11:05:23 720 MSG 3713743 Recipient: user@anotherdomain.com
11:05:23 112 DMN: MSG 3713743 Connected to [216.240.189.1] (mail.anotherdomain.com)
11:05:24 112 DMN: MSG 3713743 Send Failure: 451 temporary failure (#4.3.0)
11:05:24 112 DMN: MSG 3713743 SMTP session ended: [216.240.189.1] (mail.anotherdomain.com)
11:05:33 568 MSG 3713743 Analyzing result file: /media/nss/MAIL/nhsu/wpgate/gwia/result/rc2b24f3.556
11:05:33 568 MSG 3713743 Detected error on SMTP command
11:05:33 568 MSG 3713743 Command: RCPT TO:
11:05:33 568 MSG 3713743 Response: 451 temporary failure (#4.3.0)
11:05:33 568 MSG 3713743 Detected error on SMTP command
11:05:33 568 MSG 3713743 Command: DATA
11:05:33 568 MSG 3713743 Response:
11:05:33 568 Building undeliverable message

The other admin says that their error response is correct and that our GWIA must not be reading the failure correctly and is executing the DATA command, resulting in the undeliverable.

I sent him a log showing our GWIA responding properly to another 451 temporary failure, but it was a 4.7.1 error, not a 4.3.0 like theirs.

Does this sound plausible? Is there some configuration change I could make on the GWIA to change the way it responds to 451 errors? We are on 8.0.1 HP1.

Dan