Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

What's going on with this mail rejection, please:

Status
Not open for further replies.

jlockley

Technical User
Nov 28, 2001
1,522
US
I don't know if this is the right place to ask. Some mail is being rejected. My guess is that it has to do with the secondary DNS setting, but here's the message. Note that some mail gets through, the address given (me@mystupidserver.com) is correct. Routing through Squirrelmail works. Spamhouse filter on, but nothing apparently caught. (I hate spamhouse, but...). I suppose it's not important to say we are hosted on slicenet and that the mail interface is squirrel on dovecot, but there it is. Here the message

----- Transcript of session follows -----
... while talking to mystupidserver.us.com.:
>>> DATA
<<< 554 5.7.1 <imo-d21.mx.aol.com[205.188.144.207]>: Client host rejected:
Access denied
554 5.0.0 Service unavailable

<<< 554 5.5.1 Error: no valid recipients
Final-Recipient: RFC822; me@us.com
Action: failed
Status: 5.7.1
Remote-MTA: DNS; mystupidserver.us.com
Diagnostic-Code: SMTP; 554 5.7.1 <imo-d21.mx.aol.com[205.188.144.207]>: Client
host rejected: Access denied
Last-Attempt-Date: Fri, 21 Nov 2008 14:50:32 -0500 (EST)
Received: from Xxxxxx@aol.com
by imo-d21.mx.aol.com (mail_out_v39.1.) id m.c60.32af5baa (34899)
for <me@us.com>; Fri, 21 Nov 2008 14:50:19 -0500 (EST)
Return-Path: <xxxxxx@aol.com>
Received: from smtprly-ma01.mx.aol.com (smtprly-ma01.mx.aol.com [64.12.207.140])
by cia-da01.mx.aol.com (v121_r4.6) with ESMTP id MAILCIADA018-5c46492710f4a9;
Fri, 21 Nov 2008 14:50:19 -0500
Received: from MBLK-M24 (mblk-m24.mblk.aol.com [64.12.136.68]) by
smtprly-ma01.mx.aol.com (v121_r4.6) with ESMTP id MAILSMTPRLYMA014-5c46492710f4a9;
Fri, 21 Nov 2008 14:50:12 -0500
To: me@us.com
Subject: info
Date: Fri, 21 Nov 2008 14:50:12 -0500
X-MB-Message-Source: WebUI
X-AOL-IP: 24.5.24.23
X-MB-Message-Type: User
MIME-Version: 1.0
From: xxxxxx@aol.com
Content-Type: multipart/alternative;
boundary="--------MB_8CB1A29806CCEBD_1710_1BD_MBLK-M24.sysops.aol.com"
X-Mailer: AOL Webmail 39997-STANDARD
Received: from 24.5.24.23 by MBLK-M24.sysops.aol.com (64.12.136.68) with HTTP
(WebMailUI); Fri, 21 Nov 2008 14:50:12 -0500
Message-Id: <8CB1A29806A6C64-1710-DA@MBLK-M24.sysops.aol.com>
X-Spam-Flag:NO

 
Is your mail receiver service/application configured to use any blacklists at all?
 
Yes. Spam Assassin and Spamhouse (Spamhaus)?
I am not configuring them, and it appears that this is a security related error, but we find nothing in the spam program folders.
 
It's normal to find no message received after a connection is rejected.

I'm wondering here:
You seem to have 2 domains(?) -
us.com
and
mystupidserver.com

The receiving SMTP application will be aware of one of those domains as being its domain, and then it would be configured to reject relay attempts.
Unless you've enabled relay for your second domain, it will reject mail for that domain because it thinks those are relay attempts.

Just a thought.
 
I don't see that as a relaying attempt.

To me, it appears as if AOL is dropping the connection because of a security issue. Either you're blacklisted, or there is a configuration issue (or both). Verify reverse DNS records to start.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
 
Thanks. It is definitely security, but the question is what is causing it. We too have come to suspect a DNS issue. Reverse DNS gives some funny responses (that would do it.)

The PAM configuration in the records is all bumfiddled, so we may just take down the entire slice and rebuild.
 
Pat Richard,

It's Ubuntu, not Exchange. Squirrelmail, to be exact. We have routed around the issue for now by setting it u p on GMail, but that's not satisfactory for the long run.
Unfortunately, until we can get the PAM issues resolved, and I haven't a clue what they are, I can access neither the console nor PuTTy to check logs, etc.
This has been a rough week for us.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top