Issue is solved.
I got a new node for fidonet. my NC told me by accident an aka that was
already busy with another bbs. so i had 2 different systems with the same aka.
to prevent issues like that it would be very nice if mystic could dupecheck
AKAs in the config. A prompt "This AKA is already set up" or something like
that.
I don't know how many nodes a avg. mystic board is serving. in case of the
blackice bbs the list is very long. the boards servers many nodes and points
from many networks and processes this year 1mio mails.
that means i have not all AKAs in a view and a prompt will help other sysops
dealing with similar problems in the future.
(:. BlackICE BBS <-> BlackICE.BBSIndex.com:23 <-> BlackICEbbs.de.vu .
-----------------------------------------------------------------------------
twitter.com/BlackICEbbs - bbsfse.de.vu - bbs-list-europe.de.vu
--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: BlackICE BBS (BlackICE.BBSindex.com:23) (2:240/8001)
|
Mystic BBS 
