JE> JH> I believe if you don't have a bink session password set the packet
JE> JH> JE> JH> JE> JH> JE> JH> fi
JE> JH> goes to unsecure which is really only for tossing netmail.
JE> Yes I believe you are correct on that. But thats not the issue. I have
JE> the setting in the .ini to process echomail mail from the unsecure
JE> folder. It does process the .PKT but skips tossing in to the msg base.
As Jay mentioned: At least one of the issues here is that echomail will never
be allowed from unsecure packets. If it was, then anyone could easily destroy
networks with spam posts and floods (and trust me there are spammers and others
childish people enough to do stuff like that unfortunately).
When processing unsecured PKTs is enabled, it will only process netmail and
skip over any echomail. That is what you see happening in your logs.
If you want to accept echomail from an incoming connection they have to be a
known connection. To do this they need to be setup in your echomail nodes,
they need to present the same address you've set them up for, and they need to
have an agreed password to authenticate.
If you do have them setup and its still going to unsecured, then the issue is
likely found in the mis.log which will detail the BINKP authentication. Most
likely in this case they are not presenting the same address to you that you
have configured for them.
... If you can't make it good, make it LOOK good. -Bill Gates.
--- Mystic BBS v1.12 A48 2022/02/03 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)
|
