Thread: forwarding, can it loop?
View Single Post
Old 02-07-2004, 10:07   #5
gazzae
Inactive
 
gazzae's Avatar
 
Join Date: Jun 2003
Location: Belfast
Age: 45
Posts: 4,594
gazzae is cast in bronzegazzae is cast in bronzegazzae is cast in bronzegazzae is cast in bronze
gazzae is cast in bronzegazzae is cast in bronzegazzae is cast in bronzegazzae is cast in bronzegazzae is cast in bronzegazzae is cast in bronzegazzae is cast in bronzegazzae is cast in bronzegazzae is cast in bronzegazzae is cast in bronzegazzae is cast in bronzegazzae is cast in bronzegazzae is cast in bronzegazzae is cast in bronzegazzae is cast in bronzegazzae is cast in bronzegazzae is cast in bronzegazzae is cast in bronzegazzae is cast in bronze
Re: forwarding, can it loop?
http://www.microsoft.com/technet/pro.../frtfytr2.mspx

Quote:
Looping messages occur when a message moves back and forth between your server and some other (usually external) SMTP server. Sometimes a loop forms when an Exchange user sets up a rule to forward to another account, which has a rule to forward back to the Exchange user. Exchange can usually prevent this type of mail loop by examining the number of Received from stamps in a message's header. When that number reaches the limit you've defined in the SMTP virtual server's Maximum hop count property (on the Delivery tab of the virtual server's Properties dialog box), Exchange refuses to forward the message. (The hop-count default is 15.) Some systems' SMTP gateways, however, keep Exchange from detecting this type of loop because they strip the Received from information out of a message or they generate the forwards such that Exchange sees each one as a new message.

More often, though, message loops occur when an Exchange user sets up a rule to autoforward mail to an external account. The message encounters some external problem (e.g., the external account has exceeded its quota) and generates a nondelivery report (NDR). Because the Exchange account is configured to autoforward new messages, it automatically autoforwards the NDR, which the external account rejects and which causes another NDRââ‚ ¬ÃƒÂ¢Ã¢â€šÂ¬Ã‚thus forming a loop. Each time the message makes a round-trip, it grows in size as the systems add new message headers and new NDRs.

External email can also be a culprit of mail loops. For example, an external sender on the way out of the office configures an Out-of-Office ruleââ‚ ¬Ã¢â‚¬Âand sets the rule to request delivery confirmation. Before the user leaves, he or she sends a message to a user in your organizationâ↡¬â€but mistypes the address. Your system returns an NDR, but the Out-of-Office rule automatically replies right back and requests another delivery confirmation. The Out-of-Office functionality might not keep track of replies-per-sender, so it returns a message no matter how many times that message arrives from the same senderÃƒÂ¢Ã¢â€šà ¬Ã¢â‚¬Âthus forming another loop.
gazzae is offline   Reply With Quote