diff --git a/doc/html/accounting.shtml b/doc/html/accounting.shtml
index 3391be7e5c385460abbd0c7560d22382791ddbc6..7472a48a3bbf4b084d101453d3527c23bcac0070 100644
--- a/doc/html/accounting.shtml
+++ b/doc/html/accounting.shtml
@@ -193,7 +193,8 @@ a configuration.
 supported for job and step accounting only.</b> The infrastructure for
 PostgresSQL for use with associations is not yet supported, meaning
 sacctmgr will not work correctly.  If interested in adding this
-capability for PostgresSQL, please contact us at slurm-dev@lists.llnl.gov.
+capability for PostgresSQL, please contact us at
+<a href="mailto:slurm-dev@schedmd.com">slurm-dev@schedmd.com</a>.
 
 <p>To enable this database support
 one only needs to have the development package for the database they
@@ -777,7 +778,7 @@ as deleted.
 If an entity has existed for less than 1 day, the entity will be removed
 completely. This is meant to clean up after typographic errors.</p>
 
-<p style="text-align: center;">Last modified 10 June 2010</p>
+<p style="text-align: center;">Last modified 3 February 2012</p>
 
 <!--#include virtual="footer.txt"-->
 
diff --git a/doc/html/cons_res.shtml b/doc/html/cons_res.shtml
index b253dafd9c5c572002d50ca6c220330881004594..29c1bcbeeea4c379885a3dcd96fe6af157f563b4 100644
--- a/doc/html/cons_res.shtml
+++ b/doc/html/cons_res.shtml
@@ -152,7 +152,7 @@ resource plug-in and plan to make enhancement the plug-in as we get
 time as well as request from users to help us prioritize the features.
 
 Please send comments and requests about the consumable resources to
-<a href="mailto:slurm-dev@lists.llnl.gov">slurm-dev@lists.llnl.gov</a>.
+<a href="mailto:slurm-dev@schedmd.com">slurm-dev@schedmd.com</a>.
 
 <ol start=1 type=1>
   <li><b>Issue with --max_nodes, --max_sockets_per_node, --max_cores_per_socket and --max_threads_per_core</b></li>
@@ -446,6 +446,6 @@ one mpi process per node.</p>
 
 <p class="footer"><a href="#top">top</a></p>
 
-<p style="text-align:center;">Last modified 8 July 2008</p>
+<p style="text-align:center;">Last modified 3 February 2012</p>
 
 <!--#include virtual="footer.txt"-->
diff --git a/doc/html/help.shtml b/doc/html/help.shtml
index 431174fb1071c45b99689b288d507fe26cc8df17..98524eb211fffb117b003d9aa318ead72937b87c 100644
--- a/doc/html/help.shtml
+++ b/doc/html/help.shtml
@@ -13,13 +13,13 @@ helps you resolve the problem.</li>
 their support staff.</li>
 <li>Send a detailed description of the problem, the output from the command
 "scontrol show config", logs, back traces from any core files, etc. to
-<a href="mailto:slurm-dev@lists.llnl.gov">slurm-dev@lists.llnl.gov</a>.</li>
+<a href="mailto:slurm-dev@schedmd.com">slurm-dev@schedmd.com</a>.</li>
 </ol>
 
 <h1>Commercial Support</h1>
 <p>Several companies provide commercial support for SLURM including
 <a href="http://www.schedmd.com">SchedMD</a>.</p>
 
-<p style="text-align:center;">Last modified 30 June 2011</p>
+<p style="text-align:center;">Last modified 3 February 2012</p>
 
 <!--#include virtual="footer.txt"-->
diff --git a/doc/html/news.shtml b/doc/html/news.shtml
index f80b93474bf7c482e0237d6ba42cb69c18c6370d..d37ae9c90a3ac147d6b78096804d281e5a371fc9 100644
--- a/doc/html/news.shtml
+++ b/doc/html/news.shtml
@@ -85,7 +85,7 @@ of "AMD").</li>
 <h2><a name="25">Major Updates in SLURM Version 2.5 and beyond</a></h2>
 <p> Detailed plans for release dates and contents of additional SLURM releases
 have not been finalized. Anyone desiring to perform SLURM development should
-notify <a href="mailto:slurm-dev@lists.llnl.gov">slurm-dev@lists.llnl.gov</a>
+notify <a href="mailto:slurm-dev@schedmd.com">slurm-dev@schedmd.com</a>
 to coordinate activities. Future development plans includes:
 <ul>
 <li>Faster and more powerful job step management support  (e.g. step
@@ -124,6 +124,6 @@ trojan library, then that library will be used by the SLURM daemon with
 unpredictable results. This was fixed in SLURM version 2.1.14.</li>
 </ul>
 
-<p style="text-align:center;">Last modified 6 January 2012</p>
+<p style="text-align:center;">Last modified 3 February 2012</p>
 
 <!--#include virtual="footer.txt"-->
diff --git a/doc/html/slurm_ug_cfp.shtml b/doc/html/slurm_ug_cfp.shtml
index 3fa75ef124a2cee484851bbc31065c9975ec89b2..45212c8ebeeb843f8c7944f9956bb505ac46af26 100644
--- a/doc/html/slurm_ug_cfp.shtml
+++ b/doc/html/slurm_ug_cfp.shtml
@@ -22,7 +22,7 @@ SLURM</a>, a highly scalable Resource Manager and Job Scheduler</li>
 <p>Everyone who wants to present their own usage, developments, site report,
 or tutorial about SLURM is invited to send a short abstract including
 the presentation's expected duration to
-<a href="mailto:slurm_user_group@lists.llnl.gov">slurm_user_group@lists.llnl.gov</a>.</p>
+<a href="mailto:slurm_user_group@schedmd.com">slurm_user_group@schedmd.com</a>.</p>
 
 <p>IMPORTANT DATES:<br>
 April 30, 2011:      Submission of abstracts<br>
diff --git a/doc/html/slurm_ug_registration.shtml b/doc/html/slurm_ug_registration.shtml
index 339cfacc934ac024a9e4cdefae46fbe4a14bcb5f..e560340771e6a21c2cc57d40e43be10b474745e0 100644
--- a/doc/html/slurm_ug_registration.shtml
+++ b/doc/html/slurm_ug_registration.shtml
@@ -41,7 +41,7 @@
 	You should receive a confirmation of this initial stage within in a few days and
 	final confirmation by <b>August 26, 2011</b>.</p>
 
-      <FORM METHOD=POST ENCTYPE="text/plain" ACTION="mailto:slurm_user_group@lists.llnl.gov?subject=SLURM User Group Registration">
+      <FORM METHOD=POST ENCTYPE="text/plain" ACTION="mailto:slurm_user_group@schedmd.com?subject=SLURM User Group Registration">
 	<PRE>
 	  <table width="100%" border=0 cellspacing=0 cellpadding=0>
 	    <tr>
diff --git a/doc/html/troubleshoot.shtml b/doc/html/troubleshoot.shtml
index 676d79204b1ea9fbafdb267e44be151fefd50a0f..6d1647bae15c4a5b18a56bf983c664e425219085 100644
--- a/doc/html/troubleshoot.shtml
+++ b/doc/html/troubleshoot.shtml
@@ -54,7 +54,7 @@ using the command "<i>/etc/init.d/slurm start</i>").
 You should check the log file (<i>SlurmctldLog</i> in the
 <i>slurm.conf</i> file) for an indication of why it failed.
 If it keeps failing, you should contact the slurm team for help at
-<a href="mailto:slurm-dev@lists.llnl.gov">slurm-dev@lists.llnl.gov</a>.</li>
+<a href="mailto:slurm-dev@schedmd.com">slurm-dev@schedmd.com</a>.</li>
 
 <li>If slurmctld is running but not responding (a very rare situation),
 then kill and restart it (typically as user root using the commands
@@ -65,7 +65,7 @@ then kill and restart it (typically as user root using the commands
 and restart.
 Again check the log file for an indication of why it failed.
 At this point, you should contact the slurm team for help at
-<a href="mailto:slurm-dev@lists.llnl.gov">slurm-dev@lists.llnl.gov</a>.</li>
+<a href="mailto:slurm-dev@schedmd.com">slurm-dev@schedmd.com</a>.</li>
 
 <li>If it continues to fail without an indication as to the failure
 mode, restart without preserving state (typically as user root
@@ -165,7 +165,7 @@ the node of interest.
 Check the value of "Last slurmctld msg time" to determine
 if the slurmctld is able to communicate with the slurmd.
 If it keeps failing, you should contact the slurm team for help at
-<a href="mailto:slurm-dev@lists.llnl.gov">slurm-dev@lists.llnl.gov</a>.</li>
+<a href="mailto:slurm-dev@schedmd.com">slurm-dev@schedmd.com</a>.</li>
 
 <li>If slurmd is running but not responding (a very rare situation),
 then kill and restart it (typically as user root using the commands
@@ -179,7 +179,7 @@ then kill and restart it (typically as user root using the commands
 and restart.
 Again check the log file for an indication of why it failed.
 At this point, you should contact the slurm team for help at
-<a href="mailto:slurm-dev@lists.llnl.gov">slurm-dev@lists.llnl.gov</a>.</li>
+<a href="mailto:slurm-dev@schedmd.com">slurm-dev@schedmd.com</a>.</li>
 
 <li>If still not responding without an indication as to the failure
 mode, restart without preserving state (typically as user root
@@ -296,6 +296,6 @@ partition 000.
 </ol>
 <p class="footer"><a href="#top">top</a></p>
 
-<p style="text-align:center;">Last modified 7 July 2007</p>
+<p style="text-align:center;">Last modified 3 February 2012</p>
 
 <!--#include virtual="footer.txt"-->