Editing UUCP (section)

==Current uses and legacy==
One surviving feature of UUCP is the chat file format, largely inherited by the [[Expect]] software package.

UUCP was in use over special-purpose high cost links (e.g. marine satellite links) long after its disappearance elsewhere,<ref>{{cite web
|url=http://www.linuxjournal.com/article/1111
|title=Linux Goes To Sea
|access-date=2009-02-21
|author=Randolph Bentson
|date=August 1995
|archive-date=2008-02-26
|archive-url=https://web.archive.org/web/20080226063830/http://www.linuxjournal.com/article/1111
|url-status=live
}}</ref> and still remains in legacy use.{{citation needed|date=July 2014}} In addition to legacy use, in 2021 new and innovative UUCP uses are growing, especially for telecommunications in the [[high frequency|HF]] band, for example, for communities in the [[Amazon rainforest]] for email exchange and other uses. A patch to Ian's UUCP was contributed to UUCP Debian Linux package<ref>{{cite web
|url=https://metadata.ftp-master.debian.org/changelogs//main/u/uucp/uucp_1.07-27_changelog
|title=UUCP 1.07.27-changelog
|access-date=2021-01-10
|author=Rafael Diniz
|date=January 2021
|archive-date=2020-08-12
|archive-url=https://web.archive.org/web/20200812102840/http://metadata.ftp-master.debian.org/changelogs/main/u/uucp/uucp_1.07-27_changelog
|url-status=live
}}</ref> to adapt for the HERMES (High-Frequency Emergency and Rural Multimedia Exchange System) project, which provides UUCP HF connectivity.<ref>{{cite web
|url=https://www.rhizomatica.org/hermes/
|title=High-frequency Emergency and Rural Multimedia Exchange System
|access-date=2021-01-10
|author=Rafael Diniz
|date=January 2021}}</ref>

In the mid 2000s, UUCP over TCP/IP (often encrypted, using the [[Secure Shell|SSH]] protocol<ref name=UUCPssh/>) was proposed{{whom|date=December 2015}} for use when a computer does not have any fixed [[IP addresses]] but is still willing to run a standard [[mail transfer agent]] (MTA) like [[Sendmail]] or [[Postfix (software)|Postfix]].

Bang-like paths are still in use within the [[Usenet]] network, though not for routing; they are used to record, in the header of a message, the nodes through which that message has passed, rather than to direct where it will go next.<ref>{{cite IETF|title=Netnews Article Format|rfc=5536|sectionname=Path|section=3.1.5|page=14-16|author1=K. Murchison|author2=C. Lindsey|author3=D. Kohn|date=November 2009|publisher=[[Internet Engineering Task Force|IETF]]}}</ref> "Bang path" is also used as an expression for any explicitly specified [[routing]] path between network hosts. That usage is not necessarily limited to UUCP, IP routing, email messaging, or Usenet.

The concept of [[delay-tolerant networking]] protocols was revisited in the early 2000s.<ref>{{Cite conference |chapter= A Delay-Tolerant Network Architecture for Challenged Internets |pages= 27–34 |author= Kevin Fall |title= Proceedings of the 2003 conference on Applications, technologies, architectures, and protocols for computer communications - SIGCOMM '03 |publisher= ACM [[SIGCOMM]] |date= August 2003 |conference= 2003 Conference on Applications, Technologies, Architectures, and Protocols for Computer Communications |doi= 10.1145/863955.863960 |isbn= 978-1-58113-735-4 |doi-access= free }}</ref> Similar techniques as those used by UUCP can apply to other networks that experience delay or significant disruption.