Discussion Locked

Where is the mail stopped??

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
My Exchange server is connected to my ISP with a 256K pipe.My Exchange server is the "ultimate" destination (receiver-smtp)and my ISP acts as a intermediate destination (sender-smtp).Lets say I have mail restrictions setup on my exchange server and filtering by 3rd party software that filter's attachements,.jpg ect.When mail is sent to my exchange server is the "whole" mail (Data included)sent down my 256K pipe and then rejected based on restictions and filtering at my exchange server? Or, is the ip info about the message(Size,Intended recipient, originating sender)sent up and down the pipe and based on this info rejected? Now, what I would like to determine is, is my 256K connection to my ISP being consumed by mail that is rejected by my exchange+3rd party software or is the (data) never entering my 256k line, and actually stopped at the "intermediate" destination based on the Ip header info? I hope this all makes sense???

1 reply

by dynamo2003

To my understanding if you have a content filtering software on your exchange server the content do not get checked until the message reaches your server. Bearing in mind that the software is installed on your exchange server the content checker checks the header of the message to source out what sort of attachment you have in the message if any.

Also depending on the policy set in your content checker the sender will receive a message from your server stating the reason why the message is rejected. If no return policy is in place the content checker keeps the message quarantined for you to determine what to do with it.

As far as the connection between yourself and you ISP is concerned bandwidth becomes an issue if your Exchange server is being hit by a lot of messages with rejected attachment and the sender has to be notified.

Once you content checker is installed it is ideal to do a bit of baselining so that you can determine throughput to and fro your server.

This discussion is closed to new replies.