5.7.1 Requested action not taken: message refused



We run Exchange 2003 on a Server 2003 box, we never had this problem under
Exchange 5.5 and if you do a "google" of that error message, people ALL over
the internet are having the same exact issue, with no ryhme or reason why it
happening. Seems like a bug in 2003 to me, but anyway, getting this message
very randomly 99.9% of messages are being delivered to us with the occasional
one bouncing back to the sender. Yes we have 2MX records one for
ipcapitalgroup.com and one for ipcg.com, both point correctly to mailserver,
DNS reports all come back fine.

Any help would be wonderful, thank you.

Here is the header of the the e-mail with the error in it.

>Date: Mon, 4 Apr 2005 20:54:27 -0400
>From: Mail Delivery Subsystem <MAILER-DAEMON@xxxxxxx>
>To: <jak473@xxxxxxx>
>Subject: Returned mail: see transcript for details
>Auto-Submitted: auto-generated (failure)
>
>The original message was received at Mon, 4 Apr 2005 20:54:26 -0400
>from 68-234-216-170.stcgpa.adelphia.net [68.234.216.170]
>
> ----- The following addresses had permanent fatal errors -----
><rsimmons@xxxxxxxx>
> (reason: 550 5.7.1 Requested action not taken: message refused)
>
> ----- Transcript of session follows -----
>... while talking to mail.ipcg.com.:
> >>> DATA
><<< 550 5.7.1 Requested action not taken: message refused
>554 5.0.0 Service unavailable
>Reporting-MTA: dns; f05n15.cac.psu.edu
>Received-From-MTA: DNS; 68-234-216-170.stcgpa.adelphia.net
>Arrival-Date: Mon, 4 Apr 2005 20:54:26 -0400
>
>Final-Recipient: RFC822; rsimmons@xxxxxxxx
>Action: failed
>Status: 5.7.1
>Remote-MTA: DNS; mail.ipcg.com
>Diagnostic-Code: SMTP; 550 5.7.1 Requested action not taken: message refused
>Last-Attempt-Date: Mon, 4 Apr 2005 20:54:27 -0400
>Return-Path: <jak473@xxxxxxx>
>Received: from JKintzer.psu.edu (68-234-216-170.stcgpa.adelphia.net
>[68.234.216.170])
> by f05n15.cac.psu.edu (8.13.2/8.13.2) with ESMTP id j350sLaa026036
> for <rsimmons@xxxxxxxx>; Mon, 4 Apr 2005 20:54:26 -0400
>Message-Id: <5.2.0.9.2.20050404203230.019e3298@xxxxxxxxxxxxx>
>X-Sender: jak473@xxxxxxxxxxxxx
>X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
>Date: Mon, 04 Apr 2005 20:54:41 -0400
>To: rsimmons@xxxxxxxx
>From: "John A. Kintzer" <jak473@xxxxxxx>
>Subject: ipCapital/Waterbury
>Mime-Version: 1.0
>Content-Type: text/plain; charset="us-ascii"; format=flowed
>X-Virus-Scanned: by amavisd-new

.



Relevant Pages

  • Re: [PATCH 1/2] LogFS proper
    ... Do enums have a significant ... Reason enough to use it for the simple cases. ... why are function and line included in BUG() then? ... More than in other filesystems simply because LogFS is younger. ...
    (Linux-Kernel)
  • Re: Checking for A Blank String
    ... Yes and in this case you pointed out a bug. ... as I do with other programming languages. ... | screwdriver to screw in a nail although there is a hammer in the toolbox ... function, regardless of their actual reason, why would I want to prefer it ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Security researchers organization
    ... > The Sardonix.org security auditing web site was designed to ... Sardonix provides: ... prevent last year's Chunked Encoding bug? ... -> this provides a reason for individual team members to share their ...
    (NT-Bugtraq)
  • Re: 8.0 rc.d scripts less verbose?
    ... bug, but it's a bug that we've come to depend on. ... This late in the release cycle I'm comfortable adding a knob, ... pre-command routine or the command itself failed. ... whatever reason), it is nice to have an approximate idea which one ...
    (freebsd-stable)
  • Re: disable a memory block from swapping to hard disk
    ... That was the reason I am looking if it is possible to get a memory block ... Clearly this is a driver bug, so you should report it to the vendor along ... with the dump file generated at the time of BSOD. ...
    (microsoft.public.vc.language)