Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

exchange 2003 / delayed emails to specific domains

Posted on 2013-01-17
13
650 Views
Last Modified: 2013-06-24
Hey guys,

Running Exchange 2003 SP2

The only change I made on my client's network was switching over from Verizon DSL to Verizon FiOS. Yes, the IP addresses are different. I spoke with Verizon and had a reverse DNS entry created for the mail servers IP. I am having an issue with a few domains we are trying to email since the switch, and also weird items in the event logs as such:

This is an SMTP protocol warning log for virtual server ID 1, connection #3. The remote host "xxx.xxx.xxx.xxx", responded to the SMTP command "rcpt" with "421 4.7.1 <user@user.com>: Recipient address rejected: Can't accept mail while inactive.  ". The full command sent was "RCPT TO:<user@user.com>  ".  This may cause the connection to fail.

The items are sitting in the queue continuously retrying. Eventually they'll bounce back (though I haven't read one of the bounce back messages yet).

I am not on any blacklists whatsoever.

Any ideas? Can you help point me in the right direction?
0
Comment
Question by:tamaneri
  • 8
  • 4
13 Comments
 
LVL 42

Accepted Solution

by:
Amit earned 125 total points
ID: 38788393
DNS changes can take upto 3days to replicate globally. Leave it for few days and then check again.
0
 
LVL 10

Assisted Solution

by:rscottvan
rscottvan earned 375 total points
ID: 38788443
The mail is being rejected by the recipient's mailserver.  This usually means they believe the sender is a spammer.  Have a look here for a good explanation.
http://group-mail.com/email-error-codes/server-says-421-4-7-1-sender-address-rejected-account-disabled/

See if different internal senders can send to the recipient.  If other internal senders are successful, verify the client configuration (things like "from" and "reply to" addresses match.)

See if you can send from a gmail or yahoo or other third party account to the recipient.

Once you know if any of these senders works, you may need to contact the recipient domain mail admin to get removed from their internal blacklist.
0
 
LVL 3

Author Comment

by:tamaneri
ID: 38806628
@amitkulshrestha -- it's been well over a week and the issue still persists.

@rscottvan -- This is only one particular domain that shows up in the event logs with this error. There are a few other domains where the messages are being delayed before actually being sent. The issue is still occurring.

Any ideas?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
LVL 10

Assisted Solution

by:rscottvan
rscottvan earned 375 total points
ID: 38806693
Did you try sending from different local email addresses?  You need to pin this down to determine if it's only mail from an individual, or mail from any sender.

I think you'll need to contact the mail administrator at the far end and have them whitelist your domain or sender.
0
 
LVL 3

Author Comment

by:tamaneri
ID: 38806703
I've had no issues sending to these domains until we did an ISP switch (and our IP address changed as a result). So I would assume the issue would be on my end.

I did try sending from multiple inside addresses, the result(s) are the same :(
0
 
LVL 10

Assisted Solution

by:rscottvan
rscottvan earned 375 total points
ID: 38806764
The specific error you're receiving usually indicates you're blocked by the receiving mail server.  It's possible your mailserver's new IP is on an old internal blacklist of the receiving mailserver.

Does your domain have an SPF record?  If you post your domain name, I'll have a look at the DNS records to be sure they're configured correctly.
0
 
LVL 3

Author Comment

by:tamaneri
ID: 38806766
I was looking again through the event logs and noticed this:

This is an SMTP protocol error log for virtual server ID 1, connection #300. The remote host "12.102.252.75", responded to the SMTP command "mail" with "521-xx.xx.xx.xx blocked by sbc:blacklist.mailrelay.att.net.  521 DNSRBL: Blocked for abuse. See http://att.net/blocks  ". The full command sent was "MAIL FROM:<email@mail.com> SIZE=26626  ".  This will probably cause the connection to fail.

These weren't in the logs last week, but nonetheless this could be causing a lot of the issues. No idea why changing my mail servers IP address would cause this... but hey.

Confirmed I'm not a relay, i'm on no other blacklists (according to mxtoolbox) and my mail server is on a different public IP than anything else on the network. checked e-mail queues on exchange and they are clean.



Submitted to AT&T to have me removed, hopefully this works.
0
 
LVL 3

Author Comment

by:tamaneri
ID: 38806773
@rscottvan -- domain name is applause-tickets.com

I use mail.applause-tickets.com for the mail server. Thanks so much!
0
 
LVL 10

Expert Comment

by:rscottvan
ID: 38806875
OK, I think the problem is that the recipient server is doing SPF validation and your SPF record is wrong.  Here is your record:

applause-tickets.com.   2920    IN      TXT     "v=spf1 ip4:66.96.128.0/18 ?all"

The ip4 address range in the record needs to include your mailserver IP Address.  This would do in place of the current record, so long as all your outbound mail comes from a single IP:

applause-tickets.com.   2920    IN      TXT     "v=spf1 ip4:96.250.68.43/32 ?all"


SPF Overview
0
 
LVL 3

Author Comment

by:tamaneri
ID: 38806914
@rscottvan thanks again, I really appreciate it. I just modified the record, hopefully this puts the issue to bed! I'll report back.
0
 
LVL 3

Author Comment

by:tamaneri
ID: 38828246
Okay, so the record as been created and propagated. Also, according to AT&T, we've been removed from their blacklist.

Still having issues sending to a few domains though. Any other ideas? They'll stay in the queue continuously retrying. They will finally send though after about 2 days.
0
 
LVL 3

Author Comment

by:tamaneri
ID: 38867786
Anyone?
0
 
LVL 3

Author Comment

by:tamaneri
ID: 39272962
We switched off Exchange 2003 and went with Hosted Exchange by M$... no more issues.
0

Featured Post

Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

While rebooting windows server 2003 server , it's showing "active directory rebuilding indices please wait" at startup. It took a little while for this process to complete and once we logged on not all the services were started so another reboot is …
This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question