Hello Roger,

On 28 May 16 06:03, Roger Nelson wrote to Mark Hofmann:

 RN> I don't blame you for doing that, but I'd like to know what happened.
 RN> I want to know if my mailer is doing that, but I don't think it is.
 RN> Joe and I tested this by removing the session password and so
 RN> everything began working again.  Once a session password in placed,
 RN> however, the problem begins anew.  I have never had a packet password
 RN> for him and many others, whom, I might add, do not have this problem.

It wouldn't be your mailer doing that. It would be the editor or tosser
stuffing the password into the echomail header. The mailer itself doesn't
modify the contents of echomail/netmail.

So I suppose if you want to find a possible real solution, see if there's a way
to edit binkd settings manually. You would have to add the session password
there, and not use the one in DB's Security section. If there is any way you
can edit the "node" line in binkd that DB creates, the session password goes in
there, for example:

node 1:154/10@fidonet -md bbs.pharcyde.org  c /usr/fido/1154100

    (my node number) (md5) (my address)    (session pw)
(crash/hold/direct/immediate/etc) (optional "filebox" - not necessary)

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20160322