AKA addresses and domains

Your AKAs are the FidoNet-style addresses your board uses. Edit them in Network > Network AKA Addresses in PBConfig.

Figure 1. The AKA page, with one address on each of several networks.

The page lists one row for each address, with the columns Zone, Net, Node, Point, Domain and the full five-part Address (5D). The toolbar has Save, Insert, Edit, Delete, Copy and Paste. For example:

The same system can have more than one address, even on the same network. Use Copy and Paste to make a similar one quickly.

The AKA file itself (AKA.PRO) has no field for the network, so the domains are kept in a small text file beside it, Configs\AKADOMAIN.CFG, one line per AKA in the same order. ; lines are comments, and a blank line means no domain. Every other program reads AKA.PRO exactly as before.

• Domain is a drop-down that you can also type in. It lists the well-known networks (fidonet, fsxnet, micronet, fu-net, amiganet, tqwnet, agoranet, dovenet), the domains your other AKAs already use, and the domains found in PBTOSS.CFG.
• Typing a known network's domain fills its usual zone while Zone is still 0. If Zone is already set to something the network does not normally use, OK asks before keeping it. Any other domain name is accepted as typed.
• A domain is lower-case letters, digits, ., _ and -, up to 32 characters.

• PBToss. Each AKA takes its domain from AKADOMAIN.CFG. An AKA with no entry keeps PBTOSS.CFG's global domain, so nothing changes until you fill in domains. When every link of an echo is in one network and the area's AKA is in a different zone, PBToss sends as your AKA in that network and logs the choice.
• PBConfig. The AKA drop-down on each message area shows the five-part text.
• PBMailer. PBMailer keeps its own address lines in PBMAILER.CFG. In PBConfig's PBMailer settings, Use AKA list fills the local AKAs from this page, domain included. OK warns if a local AKA matches an address here but uses a different domain.