Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 137  |
|  mark lewis to Vincent Coen  |
|  Test 2  |
|  17 Jan 22 15:26:38  |
 REPLY: 2:250/1@fidonet 61e5bfe7 MSGID: 1:3634/12.73 61e5d25a PID: GED+LNX 1.1.5-b20180707 CHRS: CP437 2 TZUTC: -0500 TID: hpt/lnx 1.9.0-cur 17-02-17 On 2022 Jan 17 19:11:36, you wrote to me: >> nodelist.010 >> ,1000,Shenks_Express,Virginia_Beach_VA,Carol_Shenkenberger,-Unpublishe >> d-,300,XX,CM,INA:24555,IBN:shenks.dyndns.org >> Node 1:275/1000@fidonet shenks.dyndns.org;24555 - >> OHHH! i see why now... damnit... override going back in place until i >> can figure out what's going on with the damned nodelists... fack... VC> You may have the same issue I have if you have set Carol up with two AKA's VC> in the same entry. If so your mailer may well not know which port to use. i have separate entries for her two systems... look closely at the nodelist line above and then the line from my binkd nodelist... see that ';'? that's because the binkd nodelist compiler sees the INA:24555 as one domain and the IBN:shenks.dyndns.org as a second domain... so it writes them both... since there is no domain known as 24555, a DNS lookup returns NXDOMAIN and binkd then tries the other domain which works BUT uses the 24554 port which then connects to 1:275/100 and binkd complains the node does not have 1:275/1000 in its address list which is correct :) if she will remove the INA and put the port on the IBN where it belongs, then it will work properly and use the correct port to connect to her /1000... )\/(ark "The soul of a small kitten in the body of a mighty dragon. Look on my majesty, ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!" ... Attack fur not leather; it's safer to harass old women than bikers. --- * Origin: (1:3634/12.73) SEEN-BY: 1/120 18/0 123/0 153/7715 229/426 250/1 275/100 1000 640/1321 SEEN-BY: 3634/0 12 PATH: 3634/12 153/7715 229/426 |
[ << oldest | < older | list | newer > | newest >> ]