Hi g00r00,

On 2017-06-26 15:34:15, you wrote to me:

 Wv>> Binkd only knows the binkp protocol. The "blocked"
message is outside
 Wv>> that protocol, so just garbage to it, which is ignored. (I suspect)

 gr> Yep I am well aware of that.  But I thought you asked about changing it so
 gr> a meaningful message appears in the BINKD log.  I am not a binkd developer,
 gr> so I can't change the way it logs anything! :)

 gr> If your IP is blocked the connection is dropped when you try to connect.

The tcp/ip connection is first made, then dropped. A "normal"
firewall just wouldn't allow the connection to be made. That's were the
confusion in the binkd log starts.

 gr> The way that binkd logs that is not up to me; I'm not sure there is
 gr> anything I could do other than to not block it when its blocked.

What Mark said: Talk to the mailer a bit. There probably is a message in
the protocol that can tell the mailer on the otherside it isn't allowed to
connect. Like mystic does when it tells the otherside that unsecure
sessions are not allowed.

Bye, Wilfred.

--- FMail-lnx64 2.1.0.12-B20170618