Download websites that use Sympa

About Sympa

Running the announcement and discussion lists for a university, a ministry or a national research network is a job that existed long before email marketing became an industry, and Sympa was written to do it. Subscription handling, moderation queues, public archives, bounce processing and delegated list ownership are the whole of the product, with the list as the unit of administration rather than the campaign. Our record names Sympa Community against the project and dates it to 1995, though maintenance now sits with an independent community of contributors rather than with any one institution. The software ships under GPL v2, which is the main reason it turns up inside organisations that run their own mail infrastructure rather than renting it from a sending platform.

Our catalogue files Sympa under Email, and the label deserves a caveat. The audience for a list server of this kind is usually institutional rather than commercial, so a marketing technology researcher who reads the entry as evidence of outbound campaigning will draw the wrong conclusion. A better reading is infrastructure. An organisation running this software has decided that its membership lists, moderation policy and archives stay on hardware it controls, and it keeps staff willing to maintain a Perl application to hold that line.

Detection is where honesty matters. Mailing list traffic is mail, not HTTP, and none of it is visible to a web crawler. The software becomes detectable only when its web interface, the part subscribers use to join a list or read archives, is published on a hostname we crawl and is not sitting behind a login. Plenty of institutions expose no such interface, or expose it on an internal name that never appears in public DNS. Our figure should be read as a floor for public interfaces rather than as a measure of how many organisations run the software.

Two audiences care about that floor. Asset inventory and security teams care because a self hosted list server with a public web interface and a maintenance backlog is a genuine surface, and knowing where those interfaces are is the first step in an audit. Vendors selling hosted newsletter or membership products into education and government care for the opposite reason, because a self managed installation is the incumbent they have to displace, and displacement conversations start from a list of who has one.

As of August 2026 the number of hosts where we can see the interface stands at 1. A per domain lookup answers a question you already have, which is whether one named organisation runs the software. The downloadable list answers the harder question in the other direction, which is which hosts across the whole crawl expose the interface at all, so a sample can be built, checked against the pages themselves and revisited later without querying names one at a time.