with UUCP and as written in Postfix
@url{http://www.postfix.org/UUCP_README.html, documentation}.
-Search for @code{uucp} related strings in @code{master.cf} and replace
+Search for @verb{|uucp|} related strings in @file{master.cf} and replace
command to NNCP ones:
@verbatim
@end verbatim
then add transport map, telling that mail for example.com domain can be
-reached through NNCP transport to node @code{bob}:
+reached through NNCP transport to node @emph{bob}:
@verbatim
example.com nncp:bob
@end verbatim
Now, all mail will be stored in NNCP @ref{Spool, spool}, that after
-exchanging and tossing will call local @code{sendmail} command to
+exchanging and tossing will call local @command{sendmail} command to
deliver them just that was happened on the same machine.
@node UsecaseUnreliable
% nncp-file another_file bob:movie.avi
@end verbatim
-will queue two files for sending to @code{bob} node. Fire and forget!
+will queue two files for sending to @code{emph} node. Fire and forget!
Now this is daemon's job (or offline transfer) to send this file part by
part to remote system when it is available.
choice. Just send files as shown in previous section, but use removable
media for transferring packets to other nodes.
-Assume that you send two files to @code{bob} node. Insert USB storage
+Assume that you send two files to @emph{bob} node. Insert USB storage
device, mount it and run:
@verbatim
% nncp-xfer -node bob /media/usbstick
@end verbatim
-to copy all outbound packets related to @code{bob}'s node. Use
-@code{-force} option to forcefully create related directory on USB
+to copy all outbound packets related to @emph{bob}'s node. Use
+@option{-force} option to forcefully create related directory on USB
storage if they are missing (for example when running for the first
time).
-If you use single storage device to transfer data both to @code{bob} and
-@code{alice}, then just omit @code{-node} option to copy all existing
+If you use single storage device to transfer data both to @emph{bob} and
+@emph{alice}, then just omit @option{-node} option to copy all existing
outgoing packets to that storage device.
@verbatim
@end verbatim
to find all packets related to their node and copy them locally for
-further processing. @code{nncp-xfer} is the only command used with
+further processing. @ref{nncp-xfer} is the only command used with
removable devices.
@node UsecaseF2F
@verbatim
% nncp-call bob
@end verbatim
-will try to connect to @code{bob}'s node known TCP addresses (taken from
+will try to connect to @emph{bob}'s node known TCP addresses (taken from
configuration file) and send all related outbound packets and retrieve
those the Bob has. All interrupted transfers will be automatically
resumed.
@end verbatim
That configuration file tells that we have got two known neighbours:
-@code{bob} and @code{bob-airgap}. @code{bob} can be reached via online
-connection using @code{lan} address. @code{bob-airgap} can be reached by
-sending intermediate relay packet through the @code{bob}.
+@emph{bob} and @emph{bob-airgap}. @emph{bob} can be reached via online
+connection using @emph{lan} address. @emph{bob-airgap} can be reached by
+sending intermediate relay packet through the @emph{bob}.
-Any command like @code{nncp-file myfile bob-airgap:} will automatically
-create an encapsulated packet: one for the destination endpoint, and
-other carrying it for intermediate relaying node.
+Any command like @command{nncp-file myfile bob-airgap:} will
+automatically create an encapsulated packet: one for the destination
+endpoint, and other carrying it for intermediate relaying node.
Pay attention that relaying node knows nothing about the packet inside,
but just its size and priority. Transition packets are encrypted too.
-@code{bob} can not read @code{bob-airgap}'s packets.
+@emph{bob} can not read @emph{bob-airgap}'s packets.
@node UsecaseCensor
@section Network censorship bypassing