Announcement

Collapse
No announcement yet.

Kill Large e-mails

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Kill Large e-mails

    I have an exchange server (2003) running about 150 users. Right now it's behind a DSL broadband line. I know that's not the right way, and we're moving soon to a data center, but right now someone just sent out a 7MB attachment to 1,000 (yes, one thousand) people, and our exchange server slowed to a crawl. People aren't getting their e-mails, and we can barely even log in remotely. We have someone there right now physically accessing the server, but we don't know how to kill all those e-mails, or in general how to kill a large e-mail that we don't want being sent out.

    Please help ASAP so we can get our server up and running.

    Thanks so much

    -Eli

  • #2
    Re: Kill Large e-mails

    First - go in to ESM and disable all outbound email. That will stop all email from going out and give you control over the server. It is in the queues section under servers.

    Next - configure an SMTP Connector. Set it to use DNS address space set to *, the cost to be 1. On the content restrictions tab configure the restriction on size to be 2500 (it is measured in k, so that is 2.5mb).

    Setup another connector with no restrictions, a slightly higher cost (2). On the delivery options set it to Never run.

    You can then enable outbound email. Everything caught in the queue that is less than 2.5mb will go out, everything higher will sit in the queue until you release it (or probably delete it).

    Simon.
    --
    Simon Butler
    Exchange MVP

    Blog: http://blog.sembee.co.uk/
    More Exchange Content: http://exchange.sembee.info/
    Exchange Resources List: http://exbpa.com/
    In the UK? Hire me: http://www.sembee.co.uk/

    Sembee is a registered trademark, used here with permission.

    Comment


    • #3
      Re: Kill Large e-mails

      I sent your suggestion to my guy at the exchange server and he responded:

      The problem here was two fold

      1. The server was inaccessible during this time. (not only the bandwidth, but the whole server)
      2. There were over 1000 different queues that have to be deleted one at a time. (There are similar methods to put all the queues into one large queue and then delete the whole thing. The problem with this is this would apply to all the legitimate mail trying to go out also.)

      What we did was similar:

      1. Disabled outgoing mail
      2. Froze all the queues
      3. Enabled outgoing mail
      4. Unfreezing the legitimate queues one or two at a time so as not to cause a clog-up again
      5. Painstakingly deleting those 1000 mails one at a time. If anyone has a suggestion in deleting all the messages together, or in larger than 1 at a time groups I would appreciate it. Each mail was to a different email domain, therefore in its own queue. You canít natively delete from more than one queue at a time. If the server gets rebooted, or the services restart before this deleting is finished it will start all over again and try to deliver the mails that I havenít deleted yet. I have about 450 to go.
      Any ideas?

      Comment


      • #4
        Re: Kill Large e-mails

        If you create the SMTP Connectors as I outlined, then all of the queues will be eventually stack up in to to a single queue. You can then delete them all in one hit.

        It is a very similar technique to my spam cleanup method which I have outlined here: http://www.amset.info/exchange/spam-cleanup.asp
        However I have tweaked it slightly so that the legitimate smaller mail goes out.

        Simon.
        --
        Simon Butler
        Exchange MVP

        Blog: http://blog.sembee.co.uk/
        More Exchange Content: http://exchange.sembee.info/
        Exchange Resources List: http://exbpa.com/
        In the UK? Hire me: http://www.sembee.co.uk/

        Sembee is a registered trademark, used here with permission.

        Comment


        • #5
          Re: Kill Large e-mails

          And to avoid this happening in the future, a public flogging of the offender will usually server as a lesson to all. However in case management a wimps, you can restrict either the maximum number of recipients that particular user can send to or you can make it a global setting.

          If individual, AD Users & Computers, the User's Properties, Exchange General, Delivery Options, Recipient Limits.

          If global, Exchange Management Console, Global Settings, Message Delivery, right click, Properties, Defaults, Recipient Limits.

          Damn, should have done a screenshot, would have saved typing.
          1 1 was a racehorse.
          2 2 was 1 2.
          1 1 1 1 race 1 day,
          2 2 1 1 2

          Comment


          • #6
            Re: Kill Large e-mails

            Thank you all for your suggestions. Yes, we actually did set a global limit on recipients.

            Sembee, I should have you know that your suggestion crashed our server. I don't know why, but it did. After it rebooted, since all the legitimate mail had been sent out already, he was able to run the aquadmcli utility (however you spell it) and delete all the messages in the queue.

            Thanks again for your help

            Comment


            • #7
              Re: Kill Large e-mails

              Never had it crash a server before. I have used that method to clear thousands of messages before (10,000+) without any problems.

              Simon.
              --
              Simon Butler
              Exchange MVP

              Blog: http://blog.sembee.co.uk/
              More Exchange Content: http://exchange.sembee.info/
              Exchange Resources List: http://exbpa.com/
              In the UK? Hire me: http://www.sembee.co.uk/

              Sembee is a registered trademark, used here with permission.

              Comment

              Working...
              X