MSGID: 2:280/464.27 234e6704
CHRS: IBMPC 2
TZUTC: 0000
REPLY: 2:240/1120.29 20090802
Hello Tim!

*** Sunday 16.01.22 at 13:27:45, Tim Schattkowsky wrote to Martin Foster:

 MF>> I'm now in a position to test this out, here's how I've set things up:

 TS> You should probably test against the upcoming release as I found an issue
 TS> in the dupe checker (which is already fixed now) that breaks the whole
 TS> thing.

Tested against v394 and I now see how it works .....

 MF>> - Uplink_A
 MF>> Primary uplink
 MF>> Linked into WINPOINT

 MF>> - Uplink_B
 MF>> Secondary uplink
 MF>> Linked into WINPOINT

 MF>> Then did this .....
 MF>> - Posted a message in WINPOINT via Uplink_A
 MF>> - Changed the properties of WINPOINT so that Uplink_B is now the Primary
 MF>> uplink.
 MF>> - Waited a while, polled Uplink_B and picked up my own message which I'd
 MF>> posted via Uplink_A

 MF>> This is what happened next .....
 MF>> - Message was tossed into my existing WINPOINT area

 TS> Good point, I didnt consider the case that one receives a message created
 TS> on the same system. In this case, the dupe checker actually currently
 TS> never sees the message. Will change that.

..... messages are now tossed into the "Doppelte Nachrichten" (Dupes) folder.
So, it's now just a simple matter of switching uplinks on/off in the
Properties for each area. This is fine for just a few areas but it would be
very laborious and time consuming for lots of areas. Just thought I'd throw
that one into the pot :-)

Regards,
Martin
--- WinPoint 394.0
 * Origin: WinPoint Test Rig - UK - (2:280/464.27)
SEEN-BY: 15/0 30/0 106/201 124/5016 129/330 153/757 7715 203/0 221/0
SEEN-BY: 221/1 6 229/110 317 426 428 664 700 240/1120 266/512 280/464
SEEN-BY: 280/5003 282/464 1038 292/854 8125 301/0 1 101 113 310/31
SEEN-BY: 317/3 320/219 335/364 341/66 234 396/45 460/58 712/848 920/1
SEEN-BY: 2452/250 5020/1042 5058/104
PATH: 280/464 301/1 229/426