Exactly, hence a rule saying only traffic from port 25 on the mail server gets through the firewall out...and in.
On Fri, Dec 19, 2008 at 6:00 PM, Martin Blackstone <[email protected]>wrote: > Honestly, if a client machine is compromised into a spambot, it's not > going to use your Exchange server. > > It's going to send direct from its own newly installed SMTP server. > > > > *From:* Don Andrews [mailto:[email protected]] > *Sent:* Friday, December 19, 2008 2:02 PM > *To:* MS-Exchange Admin Issues > *Subject:* RE: Hourly sending limit in Exchange 2007? > > > > How 'bout scanning for spam in outbound messages? > > > ------------------------------ > > *From:* Kretche, Peter [mailto:[email protected]] > *Sent:* Friday, December 19, 2008 12:59 PM > *To:* MS-Exchange Admin Issues > *Subject:* Hourly sending limit in Exchange 2007? > > > > Anyone know of a transport agent/3rd party application for Exchange 2007 > that will allow to put a per user hourly sending limit to throttle spam if > an account would be compromised or a malicious behavior on the part of a > user? > > > > ------------------------------------------------- > Thank you, > Pete Kretche > MCP, A+, HP APS > Senior Network/Systems Administrator > > E-mail Administrator > UW - Green Bay > Voice: 920.465.5014 > Fax: 920.465.2864 > [email protected] > > > > No trees were harmed in the sending of this message, but a large number of > electrons were terribly inconvenienced. Please don't print this email > unless it is absolutely critical. > > > > > > > > > > > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
