Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    MYSTIC    |    Mystic support echo    |    16,010 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 13,289 of 16,010    |
|    g00r00 to buanzo    |
|    Re: Use passwords only if needed?    |
|    05 Apr 21 23:47:29    |
      TID: Mystic BBS 1.12 A47       MSGID: 1:129/215 0fe88ac8       REPLY: 4:900/107 a5b4d458       TZUTC: -0400        bu> So, my hub sends me .PKT without passwords. I made the mistake of        bu> configuring the node to use a .PKT password, so of course mutil sees        bu> them as Invalid PKT.               bu> I was wondering, is there any reason why Mystic attempts to use a        bu> password on a .PKT when it is not needed, at least to detect the        bu> situation and log a more appropriate message?              I may not be understanding your question but I'll give it a shot and if I am       misunderstanding let me know.              In the first quote it sounds to me like Mystic is requiring a password for the       PKT because you've configured require a password for the PKT.              I am assuming in the second quote you are talking about unsecure echomail.        The PKT defines if it requires a password to process it, so if Mystic receives       an unsecure echomail packet that says it requires a password, Mystic will not       process it. Mystic should never process a password-secured echomail packet if       it doesn't know the password.              The resulting error message in the latest version looks like:               + Importing ABCD.PKT (from 1:1/1 to 1:2/1)        ! Password found but no configuration for node 1:1/1              In older versions it used to only say "! Bad password" but that was changed to       add the "no configuration for node |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca