= Сообщение: 1579 из 12549 ====================================== ENET.SYSOP = От : Björn Felten 2:203/2 29 Nov 14 01:40:42 Кому : Benny Pedersen 29 Nov 14 01:40:42 Тема : qico -b -i 2:203/0 fails FGHI : area://ENET.SYSOP?msgid=2:203/2+54791608 На : area://ENET.SYSOP?msgid=2:230/0+54791755 = Кодировка сообщения определена как: CP437 ================================== Ответ: area://ENET.SYSOP?msgid=2:230/0+54793d4f ============================================================================== BF>> Sigh! Are you really that dense or are you just trolling?
BP> or trying to understand you ?
OK, so that means alternative A).
Let me write this very slowly then:
You can connect to my system without problems because I run binkd in client mode only. It never answers *incoming* calls, just sends everything out. Radius answers all incoming calls here.
Binkd, that handles all *outgoing* calls, has detected a security violation when it tries to send mail to your qico. Neither Radius nor Argus can detect that security violation, so when I move the pending mail from the binkd out directory to the Radius ditto it gets sent.
Now do you understand?
And of course, I've never seen this security violation with any other of 20 or so systems that I send mail *to* regularly -- ergo: I make the conclusion that there's something rotten in the state of your mailer.
I suggest that we take this discussion to netmail. I just thought that some sysops would be interested in knowing exactly how the setup at 203/0 looks like ATM. As soon as I get Argus IPv6 aware, it'll all go back to what it was some two months ago (when I changed from Argus to Radius).
I might also add that I plan to call my totally rewritten version Tedious. RFC. :)
--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125 * Origin: news://felten.yi.org (2:203/2)
