Important Announcement: All NGINX mailman mailing lists are retiring on September 30

[Sergey Budnevich]

> On 25 Sep 2025, at 22:50, Ralph Seichter <ralph at ml.seichter.de> wrote:
> 
> * Sergey Budnevich:
> 
>> All NGINX mailman mailing lists are retiring on September 30, as the
>> NGINX development process has moved to GitHub.
> 
> Not only does this come at very short notice, it is also regrettable, in
> my opinion.

Sorry for the short notice, but a year ago my colleague wrote that we plan
to shut down the mailing lists after December 31, 2024, and we actually
ran them nine months longer: https://mailman.nginx.org/pipermail/nginx/2024-September/R7KBUUNTG3B2QAAMPS6M7YDOSVCMOZD7.html

The main reason for decommissioning is the lack of activity in the mailing
list — there are months with announcement emails only.

GitHub is not a replacement for a mailing list as a place for questions - it is
mainly for information about new releases, i.e., an announcements replacement.

community.nginx.org is intended as the mailing list replacement, as Ian
correctly mentioned. Also it is possible to use RSS feeds for both GitHub
and the forum.

> 
> GitHub may be a valid choice for your development process, but as a
> means of communicating with end users seeking support, mailing lists are
> far better suited. User-to-user communication is also better handled
> using mailing lists. Also, I find using proper MUAs is much more
> efficient than GitHub's web browser UI, and they even work in a TTY
> environment with low bandwidth.
> 
> Can you not keep the NGINX user mailing list active? That would not
> interfere with your developer processes on GitHub.
> 
> -Ralph
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> https://mailman.nginx.org/mailman/listinfo/nginx