locked
Forward Rule Problem.... RRS feed

  • Question

  • Hi Folks,

    Yesterday we had a problem where an old user had a forward rule setup to an external account. For some reason the foward appeared to fail yesterday and we kept getting bounce backs into the account which in turn were trying to forward. This nearly killed our exchange server as the queue "messages awaiting directory lookup" seemed to fill up very rapidly.

    We managed to break into his account and delete the rule, we just wondered if there was anything we could set in system manager to prevent it processing all the duplicate bounce backs ?

    Running Exchange 2003, on Server 2003.

    Thanks in advance.


    • Edited by pss53 Friday, October 14, 2011 2:31 PM
    Friday, October 14, 2011 2:30 PM

Answers

  • Best thing is to not allow auto-replies or auto-forwarding to the Internet:

    http://support.microsoft.com/kb/266166

     

     

    • Marked as answer by emma.yoyo Friday, October 21, 2011 1:41 AM
    Friday, October 14, 2011 3:05 PM
  • On Fri, 14 Oct 2011 14:30:32 +0000, pss53 wrote:
     
    >
    >
    >Hi Folks,
    >
    >Yesterday we had a problem where an old user had a forward rule setup to an external account. For some reason the foward appeared to fail yesterday and we kept getting bounce backs into the account which in turn were trying to forward. This nearly killed our exchange server as the queue "messages awaiting directory lookup" seemed to fill up very rapidly.
    >
    >We managed to break into his account and delete the rule, we just wondered if there was anything we could set in system manager to prevent it processing all the duplicate bounce backs ?
    >
    >Running Exchange 2003, on Server 2003.
     
    Finding the problem is the first thing to do. After that you can block
    the IP address or sender address (assuming it wasn't "<>" and the loop
    was casued by NDRs or some other DSN) -- or shut down the SMTP
    service, find the message(s) in the queue folder, and then go dig out
    the queued messages in the database's MTA in/out folders with MFCMAPI.
     
    But if you know the reason for the loop and it's something as simple
    as removing a rule from a mailbox, then that's the most direct
    approach.
     
    Of course, not allowing the auto-forwarding of messages would be a
    good idea. You can prevent that for the "default" domain and then
    allow exceptions (if you must) for specific domains.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Marked as answer by emma.yoyo Friday, October 21, 2011 1:42 AM
    Friday, October 14, 2011 8:28 PM

All replies

  • Best thing is to not allow auto-replies or auto-forwarding to the Internet:

    http://support.microsoft.com/kb/266166

     

     

    • Marked as answer by emma.yoyo Friday, October 21, 2011 1:41 AM
    Friday, October 14, 2011 3:05 PM
  • Magic, i'll give that a go thanks!!! 
    Friday, October 14, 2011 3:17 PM
  • On Fri, 14 Oct 2011 14:30:32 +0000, pss53 wrote:
     
    >
    >
    >Hi Folks,
    >
    >Yesterday we had a problem where an old user had a forward rule setup to an external account. For some reason the foward appeared to fail yesterday and we kept getting bounce backs into the account which in turn were trying to forward. This nearly killed our exchange server as the queue "messages awaiting directory lookup" seemed to fill up very rapidly.
    >
    >We managed to break into his account and delete the rule, we just wondered if there was anything we could set in system manager to prevent it processing all the duplicate bounce backs ?
    >
    >Running Exchange 2003, on Server 2003.
     
    Finding the problem is the first thing to do. After that you can block
    the IP address or sender address (assuming it wasn't "<>" and the loop
    was casued by NDRs or some other DSN) -- or shut down the SMTP
    service, find the message(s) in the queue folder, and then go dig out
    the queued messages in the database's MTA in/out folders with MFCMAPI.
     
    But if you know the reason for the loop and it's something as simple
    as removing a rule from a mailbox, then that's the most direct
    approach.
     
    Of course, not allowing the auto-forwarding of messages would be a
    good idea. You can prevent that for the "default" domain and then
    allow exceptions (if you must) for specific domains.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Marked as answer by emma.yoyo Friday, October 21, 2011 1:42 AM
    Friday, October 14, 2011 8:28 PM
  • Hi pss53,

    Any updates?

    Frank Wang

    Forum Support

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

     

    Monday, October 17, 2011 6:01 AM
  • Hi pss53,

    Any updates?

    Frank Wang

     

    Wednesday, October 19, 2011 1:39 AM