• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 841
  • Last Modified:

Not receiving email from yahoo, gmail, aol, pacbell.net, hotmail, etc...

Recently we upgraded from a Frame-relay T1 to a AT&T MIS T3. Our DIA service  (IP Block) was moved to this new router and the same exact routing statements were setup there as well. The configurations are exactly the same between the old router and the new. The only thin I changed on my PIX 515E was the new IP address and static routes. Our email leaves out of a Charter Cable Modem and incoming email is coming through the T3. The MX records did not change. There are PTR records for the cable modem and T3. I can telnet to our spam device on port 25.  The problem that i am having is that i get email from dell, att, charter, but noting from gmail, yahoo, hotmail, pacbell.net, etc...
  • 4
  • 2
1 Solution
csltAuthor Commented:
Here is a header from a NDR:

Delivered-To: xxxxx@xxxxx.com
Received: by with SMTP id l19cs35581ybd;
        Tue, 6 Apr 2010 12:55:33 -0700 (PDT)
Received: by with SMTP id q14mr8409378ybf.140.1270583733323;
        Tue, 06 Apr 2010 12:55:33 -0700 (PDT)
MIME-Version: 1.0
Return-Path: <>
Received: by with SMTP id q14mr13579422ybf.140; Tue, 06 Apr 2010
      12:55:33 -0700 (PDT)
From: Mail Delivery Subsystem <mailer-daemon@googlemail.com>
To: xxxxx@xxxxx.com
Subject: Delivery Status Notification (Delay)
Message-ID: <000e0cd754c81506a6048396d401@google.com>
Date: Tue, 06 Apr 2010 19:55:33 +0000
Content-Type: text/plain; charset=ISO-8859-1

This is an automatically generated Delivery Status Notification



Delivery to the following recipient has been delayed:


Message will be retried for 2 more day(s)

Technical details of temporary failure:
The recipient server did not accept our requests to connect. Learn more at http://mail.google.com/support/bin/answer.py?answer=7720 
[xxxxx.cityxxxxx. (10): Connection timed out]

----- Original message -----

MIME-Version: 1.0
Received: by with HTTP; Mon, 5 Apr 2010 11:08:19 -0700 (PDT)
Date: Mon, 5 Apr 2010 11:08:19 -0700
Received: by with SMTP id q14mr6902190ybf.140.1270490899345;
      Mon, 05 Apr 2010 11:08:19 -0700 (PDT)
Message-ID: <i2s2b5ddf341004051108ia56929ecvdc76569f3307bc6@mail.gmail.com>
Subject: adas
From: aaaaa <xxxxx@xxxxx.com>
To: aaaaaa <yyyyyyy@yyyyy.com>
Content-Type: multipart/alternative; boundary=000e0cd754c8bef37b04838136a8

You say the IP block was moved, then you say "was the new IP address " 

The bottom line is, the IP address that you MX references - did this change? If so, you need to update your MX record.

I think you may have given your domain in the question there, and I tried to connect to your MX and could not. smtp.citxxxxxx

csltAuthor Commented:
a new static IP was given to us and we own a class C that is routed to our new router. the MX record resides in that class C. The only changed on teh network is the IP address of the internet connection from AT&T
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

You hav a Class C.

Ok, well xxxxx.cityxxxxx points to xx.xx.xx.11

That IP does not have port 25 open.

Either open port 25 on that IP or change to whatever IP you have configured for inbound mail.

Possibly create an allow rule or whitelist on the spam device to test with for gmail
csltAuthor Commented:
Cisco pin-pointed the problem. It is AT&T. there is a major routing issue for my circuit.
csltAuthor Commented:
I figured it out with AT&T SUpport
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now