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

outgoing email not going out

We just changed our ISP and I am getting the following error sending email:

The following recipient(s) could not be reached:

  user@xxxxx.com on 4/28/2009 9:11 PM
  You do not have permission to send to this recipient. For assistance, contact your system administrator.
  <server01.xxxxx.local #5.7.1 smtp;554 5.7.1 <userl@xxxx.com>: Recipient address rejected: invalid sender (3)>

Where do I need to look to fix this?

TIA
0
MTCNS
Asked:
MTCNS
1 Solution
 
automationstationCommented:
Your new ISP probably requires SMTP authentication to send mail... make sure you are pointed to your ISP's SMTP server and that you configure authentication using a username and password for the internet connection.
0
 
MTCNSAuthor Commented:
I have no user/pass for my connection, which is 3 bonded T1's. Where in Exchange would you configure the SMTP authentication?
0
 
automationstationCommented:
So are you using an Active Directory Server running DNS? You would then need to make sure that the DNS is configured correctly on the server. Ideally, you would have the server pointing to itself for DNS and configure DNS forwarders... Right click your DNS Server name in the DNS MMC, select the forwarders tab... make sure you have your ISP's DNS1 and DNS2 listed in the forwarders. Remove any of the old entries. See if that doesn't do the trick.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
MSWarriorCommented:
We had a similar issue, and the cause we found for this was the reverse DNS PTR record etup for your new exchange IP address. If you haven't set this up yet, then contact your ISP and ask them to setup a reverse DNS PTR record for you. For more info, check this:
http://www.tech-faq.com/reverse-dns.shtml
0
 
MesthaCommented:
If you don't have a smart host set on the server then what you ISP needs doesn't matter.

Reverse DNS is the most likely, but the FQDN on the server is also invalid. host.domain.local isn't going to be accepted by the internet, it needs to be changed to host.example.com

Simon.
0
 
MTCNSAuthor Commented:
I figured it out just before you posted this. I just had to think it through. Thanks for your help, you were the only one to answer correctly. Thanks for the help.
0

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

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