MD> I handle the loop messages differently. If a message comes to me not for MD> the first time, it is moved to the special area. Once a day messages are MD> released from the area. This is done in a hope that the routing may be MD> fixed during this delay. After the message comes for the 7th time, it is MD> clear that the routing has not been fixed during the week and the message MD> is bounced back to the sender (if he is in the nodelist). And the last but MD> not the least: when the message comes for the second time and a loop is MD> detected, I receive a message from my robot about it. So I can take some MD> actions to help with fixing the routing.
I do not know how my tosser handles loops, but in this case it was not routing failure. Du to some unfortunate handling the messages contained twoo INTL kludge lines. The first twoo systems in the loop processed the first line, causing the message to be delivered to the intended system. There and at the following system the second INTL line was processed, causing the message to be returned to the sender.
Nobody cared to make his software safe, to messages structures, that should not exist.
Kees
--- GoldED+/LNX 1.1.5--b20180707 * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
