> I wonder if you have considered adding support for a CRAM-MD5 handshake
> in the binkp mailer? I think that would be a goodthing(TM).

Hashed passwords are always ReallyGoodThing(tm). I have to read latest
BinkP specs and I'll see then...

> I have also noticed that when a file is received by the mailer and there is
> already a file with that name in the inbound the original file is overwritten
> by the new one. That is not a goodthing(TM). Would it be possible to rename a
> file when received if a file by that name already exists in the inbound?

Yes, that's true. Usually you process incoming files immediately so the
attack vector is quite short lived. This is especially important for
incoming mail, as file names could be predictable. Rename would be a good
thing, as long as partially received files are deleted if connection is
lost.

For the reference, my scripts/gotmail.bz is:

int main()
{
        char flag_name;
        int f;

        flag_name = sprintf("%sgotmail.flg", bg_tempdir);
        f = fopen(flag_name, "wb");
        if (f !=- 1)
                fclose(f);
}

And I run following from my crontab:

#!/bin/sh

# incoming fido
if [ -f work/gotmail.flg ]; then
    rm -f work/gotmail.flg
    ./bbbs bogus w > /dev/null 2>&1
    ./bbbs btick > /dev/null 2>&1
    touch work/rescan.2
fi

# outgoing fido
if [ -f work/usermail.flg ]; then
    rm -f work/usermail.flg
    ./bbbs bogus a > /dev/null 2>&1
    touch work/rescan.2
fi

--- BBBS/Li6 v4.10 Toy-4