Newbie - Outbound bounced immediatley

[rkee]

All outbound mail is immediatley bounced to the origionator.
I can't seem to find any oddities in IMS......

Your message did not reach some or all of the intended recipients.
Subject:meeting
Sent:1/24/01 4:05 PM

The following recipient(s) could not be reached:

XXXXX@medmail.com on 1/24/01 4:05 PM
The recipient name is not recognized
MSEXCH:MSExchangeMTA:ECHCO:JRC_SERVER

Any help or suggestions greatly appreciated
Randy

 

[rkee]

I should add we're running Exchange 5 w/ outlook clients. Only outbound internet mail affected we are able to receive OK, local internal send receive Lan is OK.
Thank You very much for any suggestions
Randy

 

[rkee]

I found my own answer at

http://www.msexchange.org/messageboards.htm

*********************************************************


hendro@bataindonesia.com
unregistered posted 08-31-2000 02:51 AM
--------------------------------------------------------------------------------
I'm using Exhange 5.5 SP3 on Win2000 Server.
We are able to receive email from outside but can't send email out - only to our internal organization address.

Nizar
Senior Exchange Member posted 08-31-2000 08:41 AM
--------------------------------------------------------------------------------
This is a very ambiguous question, you need to be more accurate in your troubleshooting. First thing you should do is turn diagnostic logging in the IMC to maximum, and then check what error messages are displayed in the application log of Windows 2000. This is the best place to start the troubleshooting process. BTW, are you using DNS to forward outgoing mail, or you are sending it to a specific mail server? In the former case, make sure that DNS is properly configured in Windows 2000. Check the mail queues, are the messages stuck in the outgoing queue?

hendro@bataindonesia.com
unregistered posted 08-31-2000 10:41 PM
--------------------------------------------------------------------------------
I've recheck the DNS. It is configured to point to our own mail server. I've check the outgoing queues and there are no unsent email. All email going to address other than @bataindonesia.com will bounce back and showing message that the recipient is unkown when it shouldn't.

salman12345
Junior Exchange Member posted 09-01-2000 09:54 AM
--------------------------------------------------------------------------------
Hey, You might want to check the SMTP settings in each users mailboxes. It is in the email tab. Put SMTP stiings as follows
SMTP abc.def.ghr.kli.com
Put the full domain name in SMTP and not the one you use with in your organization. I think this should fix it.


Russ
unregistered posted 09-03-2000 11:52 AM
--------------------------------------------------------------------------------
Hendro;
Are you saying that if you look in your DNS server addresses in Advanced TCP/IP settings, the DNS server listed here is this server (and that this is in fact a valid DNS server)? Or are you saying that if you look on the IMS properties, Connections tab, you have an entry for Forward to host pointing to this server? If it is the first, try using a different DNS server, get an address from your ISP. If it is the second, either switch to DNS (and use a valid DNS server), or use Forward to host to another SMTP server (check with your ISP to see if they have a relay server you can use). If you are doing Forward to host to yourself, you are never trying to send any mail beyond this server, so yes, the recipient will be unrecognized. Another thing to check: On Address Space tab of IMS, you should have either a blank or an asterisk for the address. You should not have your own domain name. This would allow you to send mail only to your own domain, and again would create an unknown recipient NDR. The NDR in this case would be generated by the MTA, which you should be able to see in the last line of the NDR.

AndrewL
Junior Exchange Member posted 09-04-2000 07:39 AM
--------------------------------------------------------------------------------
I've just had what would seem to be exactly the same problem, and it came down to permissions on the services account.
Check out TechNet articles:
Q152624
Q154298
Q247787

Hope that this helps.

Andy.