<metaname="description"content="BSO Import / Export The scanner/tosser module ftn_bso provides Binkley Style Outbound (BSO) import/toss and scan/export of messages EchoMail and NetMail messages. Configuration is supplied in config.hjson under scannerTossers.ftn_bso."/>
<metaproperty="og:description"content="BSO Import / Export The scanner/tosser module ftn_bso provides Binkley Style Outbound (BSO) import/toss and scan/export of messages EchoMail and NetMail messages. Configuration is supplied in config.hjson under scannerTossers.ftn_bso."/>
{"publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"/enigma-bbs/assets/images/enigma-logo.png"}},"description":"BSO Import / Export The scanner/tosser module ftn_bso provides Binkley Style Outbound (BSO) import/toss and scan/export of messages EchoMail and NetMail messages. Configuration is supplied in config.hjson under scannerTossers.ftn_bso.","headline":"BSO Import / Export","url":"/enigma-bbs/messageareas/bso-import-export.html","dateModified":"2022-04-27T05:19:38+00:00","@type":"BlogPosting","datePublished":"2022-04-27T05:19:38+00:00","mainEntityOfPage":{"@type":"WebPage","@id":"/enigma-bbs/messageareas/bso-import-export.html"},"@context":"https://schema.org"}</script>
<p>The scanner/tosser module <codeclass="language-plaintext highlighter-rouge">ftn_bso</code> provides <strong>B</strong>inkley <strong>S</strong>tyle <strong>O</strong>utbound (BSO) import/toss and scan/export of messages EchoMail and NetMail messages. Configuration is supplied in <codeclass="language-plaintext highlighter-rouge">config.hjson</code> under <codeclass="language-plaintext highlighter-rouge">scannerTossers.ftn_bso</code>.</p>
<p><imgclass="emoji"title=":information_source:"alt=":information_source:"src="https://github.githubassets.com/images/icons/emoji/unicode/2139.png"height="20"width="20"> ENiGMA½’s <codeclass="language-plaintext highlighter-rouge">ftn_bso</code> module is not a mailer and <strong>makes no attempts to perform packet transport</strong>! An external <ahref="http://www.filegate.net/bbsmailers.htm">mailer</a> such as <ahref="https://github.com/pgul/binkd">Binkd</a> is required for this task!</p>
<h3id="configuration">Configuration</h3>
<p>Let’s look at some of the basic configuration:</p>
<td>Sets <codeclass="language-plaintext highlighter-rouge">import</code> and <codeclass="language-plaintext highlighter-rouge">export</code> schedules. <ahref="https://bunkat.github.io/later/parsers.html#text">Later style text parsing</a> supported. <codeclass="language-plaintext highlighter-rouge">import</code> also can utilize a <codeclass="language-plaintext highlighter-rouge">@watch:<path/to/file></code> syntax while <codeclass="language-plaintext highlighter-rouge">export</code> additionally supports <codeclass="language-plaintext highlighter-rouge">@immediate</code>.</td>
<td>Explicitly set default network (by tag found within <codeclass="language-plaintext highlighter-rouge">messageNetworks.ftn.networks</code>). If not set, the first found is used.</td>
<td>Per-node settings. Entries (keys) here support wildcards for a portion of the FTN-style address (e.g.: <codeclass="language-plaintext highlighter-rouge">21:1/*</code>). See <strong>Nodes</strong> below.</td>
<td>Overrides the system <em>target</em> ArcMail bundle size of 2048000 bytes (2M)</td>
</tr>
</tbody>
</table>
<h4id="nodes">Nodes</h4>
<p>The <codeclass="language-plaintext highlighter-rouge">nodes</code> section defines how to export messages for one or more uplinks.</p>
<p>A node entry starts with a <ahref="http://ftsc.org/docs/old/fsp-1028.001">FTN address</a> (up to 5D) <strong>as a key</strong> in <codeclass="language-plaintext highlighter-rouge">config.hjson</code>. This key may contain wildcard(s) for net/zone/node/point/domain.</p>
<codeclass="language-plaintext highlighter-rouge">2</code>, <codeclass="language-plaintext highlighter-rouge">2.2</code>, or <codeclass="language-plaintext highlighter-rouge">2+</code>. Defaults to <codeclass="language-plaintext highlighter-rouge">2+</code> for modern mailer compatibility.</td>
<td>Specifies the archive type (by extension or MIME type) for ArcMail bundles. This should be <codeclass="language-plaintext highlighter-rouge">zip</code> (or <codeclass="language-plaintext highlighter-rouge">application/zip</code>) for most setups. Other valid examples include <codeclass="language-plaintext highlighter-rouge">arc</code>, <codeclass="language-plaintext highlighter-rouge">arj</code>, <codeclass="language-plaintext highlighter-rouge">lhz</code>, <codeclass="language-plaintext highlighter-rouge">pak</code>, <codeclass="language-plaintext highlighter-rouge">sqz</code>, or <codeclass="language-plaintext highlighter-rouge">zoo</code>. See <ahref="/enigma-bbs/configuration/archivers.html">Archivers</a> for more information.</td>
</tr>
</tbody>
</table>
<p><strong>Example</strong>:</p>
<pre><codeclass="language-hjson">{
scannerTossers: {
ftn_bso: {
nodes: {
"21:*": { // wildcard address
packetType: 2+
packetPassword: D@TP4SS
encoding: cp437
archiveType: zip
}
}
}
}
}
</code></pre>
<h4id="paths">Paths</h4>
<p>Paths for packet files work out of the box and are relative to your install directory. If you want to configure <codeclass="language-plaintext highlighter-rouge">reject</code> or <codeclass="language-plaintext highlighter-rouge">retain</code> to keep rejected/imported packet files respectively, set those values. You may override defaults as well.</p>
<td>Path in which to write imported packet files. Useful for debugging or if you wish to archive the raw .pkt files.</td>
<td>No default</td>
</tr>
</tbody>
</table>
<h3id="scheduling">Scheduling</h3>
<p>Schedules can be defined for importing and exporting via <codeclass="language-plaintext highlighter-rouge">import</code> and <codeclass="language-plaintext highlighter-rouge">export</code> under <codeclass="language-plaintext highlighter-rouge">schedule</code>. Each entry is allowed a “free form” text and/or special indicators for immediate export or watch file triggers.</p>
<ul>
<li>
<codeclass="language-plaintext highlighter-rouge">@immediate</code>: A message will be immediately exported if this trigger is defined in a schedule. Only used for <codeclass="language-plaintext highlighter-rouge">export</code>.</li>
<li>
<codeclass="language-plaintext highlighter-rouge">@watch:/path/to/file</code>: This trigger watches the path specified for changes and will trigger an import or export when such events occur. Only used for <codeclass="language-plaintext highlighter-rouge">import</code>.</li>
<li>Free form <ahref="https://bunkat.github.io/later/parsers.html#text">Later style</a> text — can be things like <codeclass="language-plaintext highlighter-rouge">at 5:00 pm</code> or <codeclass="language-plaintext highlighter-rouge">every 2 hours</code>.</li>
</ul>
<p>See <ahref="http://bunkat.github.io/later/parsers.html#text">Later text parsing documentation</a> for more information.</p>
<ahref="https://l33t.codes/enigma-12-binkd-on-centos-7/">Blog entry on setting up ENiGMA + Binkd on CentOS7</a>. Note that this references an <strong>older version</strong>, so be wary of the <codeclass="language-plaintext highlighter-rouge">config.hjson</code> references!</li>
<li>
<ahref="https://medium.com/@alpha_11845/setting-up-ftn-style-message-networks-with-enigma%C2%BD-bbs-709b22a1ae0d">Setting up FTN-style message networks with ENiGMA½ BBS</a> by Alpha.</li>
