Subj : WINT Expiratiration WARNing #2 To : Ward Dossche From : Vincent Coen Date : Mon Aug 30 2021 18:59:33 Hello Ward! Sunday August 29 2021 23:39, you wrote to me: VC>> RESCANNED 2:221/6 VC>> MSGID: 2:250/1@fidonet 475e2c8b VC>> PID: MBSE-FIDO 1.0.7.22 (GNU/Linux-x86_64) VC>> CHRS: UTF-8 4 VC>> TZUTC: 0100 VC>> TID: MBSE-FIDO 1.0.7.22 (GNU/Linux-x86_64) VC>> RESCANNED 2:221/6 VC>> MSGID: 2:250/1@fidonet 475e2c8c VC>> PID: MBSE-FIDO 1.0.7.22 (GNU/Linux-x86_64) VC>> CHRS: UTF-8 4 VC>> TZUTC: 0100 VC>> TID: MBSE-FIDO 1.0.7.22 (GNU/Linux-x86_64) VC>> RESCANNED 2:221/6 VC>> MSGID: 2:250/1@fidonet 475e2c8d VC>> PID: MBSE-FIDO 1.0.7.22 (GNU/Linux-x86_64) VC>> CHRS: UTF-8 4 VC>> TZUTC: 0100 VC>> TID: MBSE-FIDO 1.0.7.22 (GNU/Linux-x86_64) VC>> RESCANNED 2:221/6 VC>> MSGID: 2:250/1@fidonet 475e2c8e VC>> PID: MBSE-FIDO 1.0.7.22 (GNU/Linux-x86_64) VC>> CHRS: UTF-8 4 VC>> TZUTC: 0100 VC>> TID: MBSE-FIDO 1.0.7.22 (GNU/Linux-x86_64) VC>> RESCANNED 2:221/6 VC>> MSGID: 2:250/1@fidonet 475e2c8f VC>> PID: MBSE-FIDO 1.0.7.22 (GNU/Linux-x86_64) VC>> CHRS: UTF-8 4 VC>> TZUTC: 0100 VC>> TID: MBSE-FIDO 1.0.7.22 (GNU/Linux-x86_64) VC>> RESCANNED 2:221/6 VC>> MSGID: 2:250/1@fidonet 475e2c90 VC>> PID: MBSE-FIDO 1.0.7.22 (GNU/Linux-x86_64) VC>> CHRS: UTF-8 4 VC>> TZUTC: 0100 VC>> @TID: MBSE-FIDO 1.0.7.22 (GNU/Linux-x86_64) > This must be the world-record kludges in a single message ... That msg went to 1:106/201 and he is in the nodelist with the top red tape as @INTL 1:106/201 2:25/21 @MSGID: 2:25/21@fidonet 475e780c @PID: MBSE-FIDO 1.0.7.22 (GNU/Linux-x86_64) @CHRS: UTF-8 4 @TZUTC: 0100 To: Dale Barnes, 1:106/201 CC: dalebarnes42@majik.net The CC get ignored the tail only has : -!- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64) ! Origin: Elist-MaintBOT (2:25/21) So cannot see what or why as 2:221/6 should not be in the loop so do you have any path info ? It should have gone via 1:261/38 on or after 01 Aug 21 23:30.. Vincent --- Mageia Linux v8 X64/Mbse v1.0.7.22/GoldED+/LNX 1.1.5-b20180707 * Origin: The Elist Maintainer (2:250/1) .