Subj : binkd connecting to own AKA
To   : Tommi Koivula
From : mark lewis
Date : Mon Jan 13 2020 11:54 am

  Re: binkd connecting to own AKA
  By: Tommi Koivula to mark lewis on Mon Jan 13 2020 18:27:24


 ml>> how do you prevent binkd from connecting to one of its own AKAs?

 ml>> i see this from time to time and it results in a loop of the traffic
 ml>> being attempted to be sent...

 TK> "node 1:3634/12 do.not.poll."

 TK> It may try, but it wont connect. ;)

HA! that's funny but it would work i guess LUL

it was actually calling one of my administrative AKAs for HOST routing... i'm 
still looking at options...

FWIW: i did, at one time, have to put in a routing statement for my system to 
route to itself because it was sending the netmail to one of my upstream links 
which was sending it right back... that was a similar loop problem... i'll get 
it figured out somehow... i just don't really recall other mailers being able 
to connect to themselves over POTS or, as in this case, TCP/IP... it just seems 
proper that the mailer would recognize the destination as one of its own 
addresses and simply refuse to make the attempt at all... maybe with a 
configurable option? i dunno...


)\/(ark
--- SBBSecho 3.10-Linux
 * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

.