User Tools

Site Tools

Trace:
majordomo_on_sdf

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
majordomo_on_sdf [2022/08/25 18:39] – [Interacting with majordomo-based Mail lists (mlists) on SDF] zilogmajordomo_on_sdf [2024/09/05 05:00] (current) – ts” hc9
Line 3: Line 3:
 ==== Intro ==== ==== Intro ====
  
-Since the early days of networked computing email has been used for group comunications which takes advantage of its ability to address a message to multiple recipients. SDF hosts several email lists or "mlists" which are managed via //Majordomo//, a mlist manager.  Unlike more modern mlist managers which generally have a web interface, //Majordomo// interaction is via short commands sent via email to a mail alias generally of the same name.  On SDF //Majordomo// commands are sent to ''majordomo@sdf.org'' (the domain may be left off when logged into SDF shell session). These commands and more are documented in the ''majordomo(8)'' manpage (type '//man majordomo//' to view within your SDF shell session). A condensed help offering is also available via the 'help' command sent directly to //Majordomo//.+Since the early days of networked computing email has been used for group comunications which takes advantage of its ability to address a message to multiple recipients. SDF hosts several email lists or “mlists” which are managed via //Majordomo//, a mlist manager.  Unlike more modern mlist managers which generally have a web interface, //Majordomo// interaction is via short commands sent via email to a mail alias generally of the same name.  On SDF //Majordomo// commands are sent to ''majordomo@sdf.org'' (the domain may be left off when logged into SDF shell session). These commands and more are documented in the ''majordomo(8)'' manpage (type ‘//man majordomo//’ to view within your SDF shell session). A condensed help offering is also available via the ‘help’ command sent directly to //Majordomo//.
  
 ==== SDF Mlist Basics ==== ==== SDF Mlist Basics ====
 +
 Although there are several commands listed in the //Majordomo// documentation users only needs to know a few of them.  For simplicity the examples below make use of the native BSD ''mail(1)'' email client used within an SDF shell session: Although there are several commands listed in the //Majordomo// documentation users only needs to know a few of them.  For simplicity the examples below make use of the native BSD ''mail(1)'' email client used within an SDF shell session:
  
Line 25: Line 26:
 </code> </code>
  
-Note that the  //-s 'subject line'// entries shown above are strictly informational; //Majordomo// doesn't read them.+Note that the  //-s// ‘//subject line//’ entries shown above are strictly informational; //Majordomo// doesn't read them.
  
 If you wish to subscribe using an email address other than the one associated with your SDF account simply append it to the end of the command line: If you wish to subscribe using an email address other than the one associated with your SDF account simply append it to the end of the command line:
Line 41: Line 42:
 </code> </code>
  
-If you ever need a reminder as to which -- if any -- SDF mlists you are currently subscribed to:+If you ever need a reminder as to which – if any – SDF mlists you are currently subscribed to:
  
 <code> <code>
Line 47: Line 48:
 $ echo 'which' | mail -s 'Current mlist subscriptions' majordomo@sdf.org $ echo 'which' | mail -s 'Current mlist subscriptions' majordomo@sdf.org
 </code> </code>
 +
 ==== Reading the Mlist Archives ==== ==== Reading the Mlist Archives ====
 +
 While //Majordomo// supports digests and archive file requests it appears most SDF mlists don't offer these so the only option for reading archived messages is browsing them from within an SDF shell session.  The public mlist archives are stored under the following directory on the SDF cluster (the main SDF hosts): While //Majordomo// supports digests and archive file requests it appears most SDF mlists don't offer these so the only option for reading archived messages is browsing them from within an SDF shell session.  The public mlist archives are stored under the following directory on the SDF cluster (the main SDF hosts):
  
Line 97: Line 100:
 For guidance on using ''mail(1)'' see [[traditional_mail_1_mailx_1|An Introduction to Various BSD mailx style E-mail Clients on SDF]]. For guidance on using ''mail(1)'' see [[traditional_mail_1_mailx_1|An Introduction to Various BSD mailx style E-mail Clients on SDF]].
  
-There is also **mabro** , an SDF user-contributed SDF Mlist Archive BROwser -- just a shell script -- which uses the forementioned //mail// MUA to make browsing the mlist archives a bit easier. **mabro** is located on the SDF cluster at ///sys/sdf/bin/mabro//.  Basic usage is shown below:+There is also **mabro** , an SDF user-contributed SDF Mlist Archive BROwser – just a shell script – which uses the forementioned //mail// MUA to make browsing the mlist archives a bit easier. **mabro** is located on the SDF cluster at ///sys/sdf/bin/mabro//.  Basic usage is shown below:
  
 <code> <code>
Line 132: Line 135:
  [06] anonradio-l.1512        [35] anonradio-l.1805        [64] anonradio-l.2010  [06] anonradio-l.1512        [35] anonradio-l.1805        [64] anonradio-l.2010
  [07] anonradio-l.1601        [36] anonradio-l.1806        [65] anonradio-l.2011  [07] anonradio-l.1601        [36] anonradio-l.1806        [65] anonradio-l.2011
- ...+ …
  
 Enter item [#], do new [s]earch, [l]ist ALL mlists, or [q]uit: Enter item [#], do new [s]earch, [l]ist ALL mlists, or [q]uit:
Line 147: Line 150:
 |  **f /<keyword>** | search for thread containing //<keyword>// | |  **f /<keyword>** | search for thread containing //<keyword>// |
  
-Messages display using your PAGER (//more// is default); use arrow keys, page up/down, or spacebar to navigate or '**q**' to quit.+Messages display using your PAGER (//more// is default); use arrow keys, page up/down, or spacebar to navigate or ‘**q**’ to quit.
  
 **Note**: the archives are //read-only// and can't be modified so accidentally (or intentionally) deleting messages has no effect. **Note**: the archives are //read-only// and can't be modified so accidentally (or intentionally) deleting messages has no effect.
 +
 ==== Additional Info ==== ==== Additional Info ====
  
 === References: === === References: ===
 +
   * Majordomo v1 FAQ (mostly of interest to admins): [[http://manual.sdf.org/majordomo/FAQ]]   * Majordomo v1 FAQ (mostly of interest to admins): [[http://manual.sdf.org/majordomo/FAQ]]
-  * Majordomo wikipedia page: [[https://en.wikipedia.org/wiki/Majordomo_(software)]]+  * Majordomo wikipedia page: [[wp>Majordomo_(software)|Majordomo_(software)]]
   * archive of //GreatCircle.com/majordomo//: [[https://web.archive.org/web/20120102123822/http://www.greatcircle.com/majordomo/]]   * archive of //GreatCircle.com/majordomo//: [[https://web.archive.org/web/20120102123822/http://www.greatcircle.com/majordomo/]]
  
 === Books covering Mojordomo: === === Books covering Mojordomo: ===
 +
   * //Managing Mailing Lists: Majordomo, LISTSERV, Listproc, and SmartList// by Alan Schwartz   * //Managing Mailing Lists: Majordomo, LISTSERV, Listproc, and SmartList// by Alan Schwartz
   * //Managing Internet Information Services// by Cricket Liu et.al.   * //Managing Internet Information Services// by Cricket Liu et.al.
 +
majordomo_on_sdf.1661452745.txt.gz · Last modified: 2022/08/25 18:39 by zilog