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
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
automationstation
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.
ASKER
I have no user/pass for my connection, which is 3 bonded T1's. Where in Exchange would you configure the SMTP authentication?
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
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.
ASKER
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.