Throttling Session Concurrency with SBS / Exchange 2003

I have really slacked off when it comes to my Technical Articles but I have to say that last two weeks of direct involvement with ExchangeDefender and fighting spammers has really reinvigorated my passion for helping people deal with this scum. So, what’s the problem?

Having any email troubles as of late? Email messages delayed? Coming in out of sequence or with a large delay? How about peers asking you why you haven’t responded to an email they sent you (and you explaining that you’ve just never seen it?)

If that sounds familiar, you have been a victim of a latest botnet, which whether intentionally or inconsequently, launched a large scale DDoS attack against many mail servers on the Internet.

This post shows you how to throttle down session concurrency with SBS / Exchange 2003.

I would like to thank my good friend Karl Palachuk for being a true leader and writing a series of blog posts on managed services that really encouraged me to start sharing my technical expertise with my audience. I hope you guys enjoy it.

Note: I wrote the post completely and totally drunk. I hope that is enough to excuse any typographic errors.

1 comment on “Throttling Session Concurrency with SBS / Exchange 2003 ”

  1. Joris says:

    Hi Vlad,

    yes, I do enjoy you sharing your technical experience. and i was delighted to read this problem description, as it's exactly what we are experiencing here.
    but: the solution guidelines don't seem to explain what's happening here. when looking at the current SMTP-sessions, i get the message that no items can be displayed. are there other reasons why mail is delayed than the one you described?

    Joris

1 historical pingbacks and trackbacks
  • Vlad Mazek - Vladville Blog » Blog Archive » Exchange 2003 Mailbombs slowing you down? pingback

    [...] other day I wrote an article on why you should consider limiting the session concurrency to RFC established standards if you don’t have decent perimeter security. Your really should [...]

Historical discussion. New comments are closed for this post.