Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    BINKD    |    Support for the Internet BinKD mailer    |    8,958 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 6,574 of 8,958    |
|    Alexey Fayans to mark lewis    |
|    binkd connecting to own AKA    |
|    13 Jan 20 20:59:59    |
      MSGID: 2:5030/1997@fidonet 5e1cb40a       REPLY: 483.fido-binkd@1:3634/12 2281d749       CHRS: CP866 2       TZUTC: 0300       TID: FastEcho 1.46.1 43272       Hello mark!              On Mon, 13 Jan 2020 at 11:48 -0500, you wrote to me:               ml> in the specific case i'm looking at, the problem is a netmail from a        ml> node's point to the node but the node forwarded it here... apparently        ml> there is no automatic routing in place with the software i'm using        ml> that routes netmails from points to their boss node... in this        ml> instance, there was a routing problem on the boss node which resulted        ml> in the point netmail being sent here... that's been fixed but my        ml> system was following its routing table and sending all mail for that        ml> boss' points to the NC for forwarding to the node... since i'm also        ml> the NC for that net (and a few others) binkd was calling itself which        ml> just seems weird...              This is indeed a routing problem and should be fixed instead of trying to stop       binkd from doing its work.               ml> so far, i've fixed this case by deleting the ?ut file and adjusting my        ml> routing to specifically routes this node's point netmails to the node        ml> but to have to specifically set routes for all nets' nodes' points to        ml> avoid this if i'm also the NC of that net is painful to say the least        ml> :/              Routing should handle every case and never pack anything to your own AKA. This       is easily achieved with RNtrack, for example. My system will always resolve       final destination properly before packing anything (or discard mail that can't       be routed and send notification to sender).               ml> it just seems that a mailer should recognize mail destined to itself        ml> and refuse to make the attempt with an appropraite log notice...              I do not agree. Mailer reads outbound and delivers what can be delivered.               ml> i can imagine what a single node system on POTS would do trying to        ml> call itself...              It would do exactly the same. Single line node would receive BUSY all the time       though.                     ... Music Station BBS | https://bbs.bsrealm.net | telnet://bbs.bsrealm.net       --- GoldED+/W32-MSVC 1.1.5-b20180707        * Origin: Music Station | https://ms.bsrealm.net (2:5030/1997)       SEEN-BY: 1/123 50/109 90/1 103/705 154/10 203/0 221/0 1 6 242 360       SEEN-BY: 227/114 229/101 200 426 1014 230/0 240/5832 249/307 317 280/464       SEEN-BY: 280/5003 5555 292/854 310/31 342/200 396/45 423/81 120 451/30       SEEN-BY: 452/166 463/68 469/122 712/848 770/1 2452/250 5000/111 5001/100       SEEN-BY: 5005/49 5015/255 5019/42 5020/290 329 715 806 828 846 848       SEEN-BY: 5020/921 1042 1519 2047 2140 4441 12000 5022/128 5023/12       SEEN-BY: 5023/24 5030/1081 1900 1997 5034/13 5053/54 57 5054/8 5057/19       SEEN-BY: 5060/900 5064/56 5080/68 102 5083/444       PATH: 5030/1997 5023/24 5020/715 4441 1042 221/6 1 280/464 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca