RT sending mail as Apache - getting bounced

All -

I have an existing setup where we are starting to receive error messages on
our final SMTP server. We’re receiving the following messages when someone
sends an e-mail from RT - either through an incoming e-mail, or a new ticket
that was created in RT.

Here’s the error:

All -

I have an existing setup where we are starting to receive error messages on
our final SMTP server. We’re receiving the following messages when someone
sends an e-mail from RT - either through an incoming e-mail, or a new ticket
that was created in RT. This has been working fine for about 6 months.

Local server is Centos4, running postfix 2.2.5 and RT 3.4.4. Destination
mail server is FC1, running Exim 4.

Here’s the error we’re receiving from our server where the destination
e-mail accounts reside (running Exim 4):

Error on RT box:

Reporting-MTA: dns; netmon.pipelinewireless.us

X-Postfix-Queue-ID: 21BD63F4B79

X-Postfix-Sender: rfc822; apache@netmon.pipelinewireless.us

Arrival-Date: Sun, 5 Feb 2006 11:31:46 -0500 (EST)

Content-Type: text/plain

Final-Recipient: rfc822; clane@pipeline-wireless.com

Action: failed

Status: 5.0.0

Diagnostic-Code: X-Postfix; host 66.197.151.197[66.197.151.197] said: 550

Administrative prohibition (in reply to end of DATA command)

Final-Recipient: rfc822; chale@pipelinewireless.us

Action: failed

Status: 5.0.0

Diagnostic-Code: X-Postfix; host 66.197.151.197[66.197.151.197] said: 550

Administrative prohibition (in reply to end of DATA command)

Error on mail server:

2006-02-05 11:31:46 1F5mni-0007m1-5o H=netmon.pipelinewireless.us
[67.99.82.5] F=apache@netmon.pipelinewireless.us rejected after DATA:
there is no valid sender in any header line

It seems to be a sender verification issue, but I’m not sure why. I did
notice the maillogs are showing mail coming from
mailto:apache@netmon.pipelinewireless.us apache@netmon.pipelinewireless.us

  • could this be an issue? Apache is listed in the /etc/aliases and goes to
    root. I’ve tried to whitelist @netmon.pipelinewireless.us on the FC1 box.

I also wonder since we redirect all of our ops/support/abuse to
ops/support/abuse@support.pipelinewireless.us (the
netmon.pipelinewireless.us box is aliased or CNAME’d to
support.pipelinewireless.us), when RT sends an e-mail from a
ops-comment/support-comment/etc-comment, there is no valid e-mail address on
the mail server. It appears as though the reply is coming from
ops-comment@pipelinewireless.us:

Received: from localhost (localhost [127.0.0.1])

            by netmon.pipelinewireless.us (Postfix) with ESMTP id

21BD63F4B79;

            Sun,  5 Feb 2006 11:31:46 -0500 (EST)

Received: from netmon.pipelinewireless.us ([127.0.0.1])

by localhost (netmon.pipelinewireless.us [127.0.0.1]) (amavisd-new, port
10024)

with ESMTP id 19552-06; Sun, 5 Feb 2006 11:31:44 -0500 (EST)

Received: by netmon.pipelinewireless.us (Postfix, from userid 48)

            id E80663F4B96; Sun,  5 Feb 2006 11:31:44 -0500 (EST)Subject: [Comment] RE: [pipeline-wireless.com #10623] AutoReply: testing

again - delete me

From: "chale@pipeline-wireless.com via RT" ops-comment@pipelinewireless.us

Reply-To: ops-comment@pipelinewireless.us

In-Reply-To: 037501c62a71$e41af200$800101df@pipelinewireless.local

References: RT-Ticket-10623@pipeline-wireless.com
rt-3.4.4-32222-1139156802-215.10623-3-0@pipeline-wireless.com
037501c62a71$e41af200$800101df@pipelinewireless.local

Message-ID: rt-3.4.4-32222-1139157104-932.10623-8-0@pipeline-wireless.com

Precedence: bulk

X-RT-Loop-Prevention: pipeline-wireless.com

RT-Ticket: pipeline-wireless.com #10623

Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/)

RT-Originator: chale@pipeline-wireless.com

To: “AdminCc of pipeline-wireless.com Ticket #10623”: ;

MIME-Version: 1.0

X-RT-Original-Encoding: utf-8

Date: Sun, 5 Feb 2006 11:31:44 -0500 (EST)

X-Virus-Scanned: by amavisd-new at http://www.pipelinewireless.us - Contact
postmaster@pipelinewireless.us for additional

information.

Content-Type: text/plain; charset=utf-8

Content-Transfer-Encoding: quoted-printable

Still not sure why this is not working anymore. This has been working since
day 1. Ideas?

Chris