SUP-RECOVER-SOURCES(1)
π sup-recover-sources(1) π
okay bestie, so this is the man page for sup-recover-sources, part of the Sup mail setup, and honestly it's giving rescue mission energy π¦
β¨ NAME β¨
sup-recover-sources β rebuild a lost Sup source configuration file π
πΈ SYNOPSIS πΈ
sup-recover-sources [options] [source uri...]
π DESCRIPTION π
So basically, this little icon rebuilds a lost sources.yaml file for you. How? It reads messages from a list of sources and then, for each source, it figures out the most prevalent source_id field of the messages from that source in the index. lowkey genius honestly β¨
The only non-deterministic component to this is that if the same message appears in multiple sources, those sources may be mis-diagnosed by this program. π like, it's doing its best but it can get confused, no cap.
Here's the vibe check on the logic: if the first N messages (that's --scan-num below, iykyk) all have the same source_id in the index, the source will be added to sources.yaml. Otherwise, the distribution will be printed, and you will have to add it by hand. π so close yet so far.
Also, heads up bestie β the offset pointer into the sources will be set to the end of the source, so you will have to run sup-import --rebuild for each new source after doing this. fr fr, don't skip that part. π
π OPTIONS π
--unusualβ Mark sources as 'unusual'. Only usual sources will be polled by hand (default:false) π«Ά--archiveβ Mark sources as 'archive'. New messages from these sources will not appear in the inbox (default:false) π--scan-num Nβ Number of messages to scan per source (default:10) π-h,--helpβ Show help message π
π FILES π
$HOME/.sup/sources.yamlβ Configuration file for Sup mail sources β¨
π SEE ALSO π
sup(1), sup-config(1), sup-add(1), sup-import(1) π
π REPORTING BUGS π
You are welcome to submit bug reports to the Sup issue tracker, located at
<https://github.com/sup-heliotrope/sup/issues>
not me begging you to file your bugs properly, the devs will literally love you for it π«Ά
π¦ CONTACT INFORMATION π¦
- The Sup web page:
<http://supmua.org/> - Code repository:
<https://github.com/sup-heliotrope/sup/> - Sup Wiki:
<https://github.com/sup-heliotrope/sup/wiki/> - Sup IRC channel:
#sup @ freenode.net - Mailing list:
supmua@googlegroups.comsupmua+subscribe@googlegroups.com- Archives:
<https://groups.google.com/d/forum/supmua/>
β COPYRIGHT β
Copyright Β© 2006-2009 William Morgan <mworgan-sup@masanjin.net>
Copyright @ 2013-2014 Sup developers
Permission is granted to copy and distribute this manual under the terms of the GNU General Public License; either version 2 or (at your option) any later version.
π AUTHORS π
Sup was originally written by William Morgan <wmorgan-sup@masanjin.net> and is now developed and maintained by the Sup developers. π
and that's the whole page, bestie β this was Sup User Manual, dated April 9, 2012, and the source/version line is SUP-RECOVER-SOURCES(1). go forth and recover those sources, you main character π β¨
π¦ where this page comes from
- debian bookworm: sup-mail 1.1-1 Β· GPL-2.0-or-later
- debian trixie: sup-mail 1.3-1 Β· GPL-2.0-or-later
- ubuntu jammy: sup-mail 1.0-6 Β· GPL-2.0-or-later
- ubuntu noble: sup-mail 1.1-1 Β· GPL-2.0-or-later
- ubuntu questing: sup-mail 1.3-1
- ubuntu resolute: sup-mail 1.3-1build1 Β· GPL-2.0-or-later
- ubuntu stonking: sup-mail 1.4-2 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms