Exchange 2003 rejecting SMTP from internal network servers

I just configured IMF on Exchange 2003. After doing so, other servers within the LAN are receiveing NDR's when trying to send SMTP traffic to the Exchange box. I've added our internal LAN subnet to the Global Sender ID and Connection Filter Configuration settings. Is there any thing else I'm missing.
PolymerManAsked:
Who is Participating?
 
Alan HardistyConnect With a Mentor Co-OwnerCommented:
Are you happy with this now or do you need further assistance?  Appreciate that it is not 100% perfect.
0
 
Alan HardistyCo-OwnerCommented:
Have you added the IP addresses of your internal servers to the Perimeter IP List and Internal IP Range Configuration?  (General Tab of Message Delivery Propertie)
0
 
Alan HardistyCo-OwnerCommented:
Have you also added these IP to the default SMTP Virtual Server - Access Tab, Relay Restrictions?
0
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

 
PolymerManAuthor Commented:
Thank you for your response. Yes I have added single IP and network range the entries in the global configuration.

0
 
PolymerManAuthor Commented:
I have also added the IP range to the virtual server relay configuration
0
 
Alan HardistyCo-OwnerCommented:
Have you tried telnetting from the problem servers to port 25 on the Exchange server?
What result / response do you get?
Can you try to send a message and post the results please.
http://support.microsoft.com/kb/153119 
0
 
PolymerManAuthor Commented:
Yes I have added our internal servers to the perimeter IP List and Internal IP Range configuration
0
 
Alan HardistyCo-OwnerCommented:
Did you see my Telnet suggestion?
0
 
PolymerManAuthor Commented:
I get 550.5.7.1 NDR

ready at  Wed, 15 Jul 2009 14:26:51 -0700

Data
354 Start mail input; end with <CRLF>.<CRLF>
Subject: Test message
Test.
.
550 5.7.1 Requested action not taken: message refused


Connection to host lost.
0
 
Alan HardistyCo-OwnerCommented:
Have you got the Intelligent Message Filtering Action set to Reject or No Action?
If the former, please change it to No Action and test again.
0
 
PolymerManAuthor Commented:
IMF was set to reject, so I change the setting to No Action and performed the Telnet session. With the setting set to No Action, the message was sent and I received it in my Junk E-Mail. Is it possible to have the setting at Reject but allow from internal servers.
0
 
Alan HardistyCo-OwnerCommented:
Did you restatr the Simple Mail Transfer Protocol (SMTP) service after setting up the filtering?
If not, please restart it and then change the No Action setting back to Reject.
Please test again.
Do you have any spam filtering softweare on the server?
0
 
PolymerManAuthor Commented:
I set IMF to Reject and restarted Simple Mail Transfer Protocol (SMTP). My Telnet test rejected the message once again.
Yes I do have AntiSpam software loaded on the Exchange server. It is Symantec Mail Security for Microsoft Exchange Version 6.0.8.262
0
 
Alan HardistyCo-OwnerCommented:
Did you enable Sender ID Filtering on the SMTP Virtual Server?  Are all the items checked?  If not - please check them all and restart the SMTP service again, then test again.
With the SMSMSE installed, you should be able to leave the IMF set to No Action and let SMSMSE deal with the spam, but it is another useful layer of filtering.
0
 
PolymerManAuthor Commented:
Yes all options were already checked.
0
 
Alan HardistyCo-OwnerCommented:
Well it's not exactly working as it should do but you do have a workaround.
Have you downloaded all Windows Updates for the Exchange Server? - go back several times if you have any updates to download until none left.
0
 
PolymerManAuthor Commented:
Thanks
0
 
PolymerManAuthor Commented:
The solution was a work around which lead to lowering the SPAM settings.
0
All Courses

From novice to tech pro — start learning today.