====== FidoNet mail: PBMailer, PBToss and PBTic ======
Four programs move FidoNet-style mail and files.
^ Program ^ Job ^
| **PBMailer** | Talks to other systems. It answers calls and dials out using **BinkP** (with CRAM-MD5 authentication) or **EMSI** with Zmodem, and keeps the outbound queue in the standard BSO layout. |
| **PBToss** | Sorts incoming echomail and netmail packets into your message areas (JAM, Squish and Hudson), and scans your areas for new messages to pack for your links. It supports AreaFix and nodelists and has built-in unpackers. |
| **PBTic** | Processes file echoes (TIC files) into your file areas. |
| **PBUtil** | The netmail utility, ported from the original ProBoard tools. |
PBDispatch owns the BinkP port and starts a PBMailer for each call. It can also poll your links on a schedule.
Everything is configured in PBConfig: **Network > PBMailer Configuration**, **PBToss Configuration** and **PBTic Configuration**, plus the **Network AKA Addresses** screen. If you already run FastEcho or Internet Rex, import your settings with PBMigrate first (see [[v4:install:migrate_fidonet|Importing FastEcho and Internet Rex settings]]).
===== PBMailer =====
The settings live in ''Configs\PBMAILER.CFG'', one keyword per line, with ''#'' for comments. If the file does not exist, mailer integration is skipped. PBDispatch reads it once at start-up, so restart PBDispatch after changing it. PBMailer itself reads it fresh each time it runs. To check a file without any network activity:
PBMailer -cfg PBMAILER.CFG -test
**Global settings**
^ Setting ^ Meaning ^
| ''port'' | The TCP port PBDispatch listens on for inbound BinkP. 24554 is the conventional port. |
| ''maxsessions'' | The total number of mailer sessions, inbound and outbound together. |
| ''emsiprompt'' | A real EMSI caller waits for the answering mailer to speak first. PBMailer sends the EMSI request itself when a caller sends nothing recognisable for this many seconds. A BinkP caller is recognised at once. 0 means never speak first. Default 3. |
| ''outbound'', ''inbound'', ''temp'' | The three folders, all required. Use folders the account running PBMailer can read and write. |
| ''logfile'' | The shared session log. PBDispatch shows it live in the Mailer Monitor. |
| ''address'' | Your own address (one line per AKA). At least one is required. The first is your primary. |
**Each remote system** is a block:
node 1:267/1
address 1:267/1
inet uplink.example.com
port 24554
password secret123
poll 60
crashonly no
protocol binkp
endnode
^ Setting ^ Meaning ^
| ''node '' | A label, normally the system's address. It is what you give to ''-poll'' by hand. |
| ''address'' | The system's address. An inbound call is accepted only if its address matches a node. |
| ''inet'', ''port'' | Where PBMailer dials for an outbound poll. Not needed for a node that only calls you. |
| ''password'' | The session password. |
| ''poll'' | Minutes between automatic polls by PBDispatch. PBConfig now marks this setting **deprecated** and leaves it at 0. Poll from **Mailer / Tosser > Poll Uplinks** in PBDispatch, or by hand with ''PBMailer -poll ''. |
| ''protocol'' | ''binkp'' (the default) or ''emsi'' for systems without BinkP, such as FrontDoor or Binkley. It only affects calls you make. Inbound calls are recognised automatically. |
| ''present'' | Which of your AKAs to announce when PBMailer dials this node, one line each. Leave out to announce them all. Use it when the remote system has a password for only some of your addresses. It does not apply when the node calls you. |
| ''crashonly'' | Parsed and stored; not yet acted on. |
===== The PBMailer Configuration screen =====
You do not have to edit ''PBMAILER.CFG'' by hand. **Network > PBMailer Configuration** in PBConfig lists your links and edits them.
{{ :v4:images:config-pbmailer-node.png?900 |The PBMailer Configuration screen with the Edit Node window}}
//Figure 1. The list of links and the Edit Node window. Names and the session password have been blurred.//
The list has one row for each remote system, with **Name**, **Addresses**, **Host / Inet**, **Port** and **Active**. The toolbar has **Save**, **Settings...**, **Insert**, **Edit**, **Delete**, **Copy** and **Paste**. **Settings...** is where the global settings go.
**Insert** or **Edit** opens **Edit Node**:
^ Field ^ What it is ^
| **Node Name** | A label for the link, normally its address and the sysop's name. |
| **Addresses (one per line)** | The system's addresses. An inbound call is accepted only if its address is listed. A domain can follow the address, as in ''1:266/512@fidonet''. |
| **Host / Inet** | The host name or IP address PBMailer dials. |
| **Port** | The TCP port, normally 24554. |
| **Password** | The session password you agreed with the sysop. Keep it private. |
| **Present AKAs (blank = all)** | Which of your own addresses to announce to this system, separated by spaces. Leave it blank to announce all of them. |
| **Protocol (when we call them)** | **BinkP**, or EMSI for systems without BinkP. |
| **Poll (minutes, DEPRECATED)** | Leave at 0. See the table above. |
| **Crash Only (deliver immediately, ignore schedule)** | Marks the link as crash-only. |
| **Active (uncheck to switch this system off without deleting it)** | Turns the link off and keeps its settings. |
===== Watching it work =====
PBDispatch's **Mailer Monitor** shows one row per mail line with a live progress bar, the log of the selected line, a history of finished calls and the outbound queue. Open it from **View > Mailer Monitor Window**.
{{ :v4:images:dispatch-mailer-monitor.png?900 |The Mailer Monitor}}
//Figure 1. The Mailer Monitor.//
PBDispatch's Tools menu also has entries to poll a link on demand, a queue viewer for PBToss, and an events viewer.
===== PBToss =====
PBToss reads ''Configs\PBTOSS.CFG'', which holds your **links** (the systems you exchange echoes with: address, packet password, AreaFix password, flavor) and, for each echo, an **area** block that names the message area and the links that carry it.
* An echo area in PBToss must already exist as a message area in PBConfig. Create the areas first, then the PBToss entries.
* The area's **Active** switch turns an echo on or off without deleting it. An inactive area is hidden from callers.
* Each area is sent under an AKA of yours. 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 (see [[v4:mail:aka_domains|AKA addresses and domains]]).
* ''pbtoss -test'' sends a test packet.
* Messages typed at the board, and messages posted through the news server, are picked up by the next scan. PBNntp touches ''TOSS.SEM'' to trigger one.
//A full PBToss and PBTic reference is being written.//
===== Bringing in echoes you already have =====
If you are moving from FastEcho, use **Import from FastEcho...** on the **Message Areas** toolbar in PBConfig. See [[v4:install:migrate_fidonet|Importing FastEcho and Internet Rex settings]].