use XML::LibXML;
use XML::LibXSLT;
-my $canonical_url = 'http://www.exim.org/';
+my $canonical_url = 'https://www.exim.org/';
## Parse arguments
my %opt = parse_arguments();
$chapter->appendTextChild(
'canonical_url',
sprintf(
- 'http://www.exim.org/exim-html-current/doc/html/spec_html/%sch-%s.html',
+ 'https://www.exim.org/exim-html-current/doc/html/spec_html/%sch-%s.html',
$prepend_chapter, $chapter_title
)
);
<!-- Canonical -->
<xsl:variable name="html.head.append">
- <link rel="canonical" href="http://www.exim.org/credits.html"/>
+ <link rel="canonical" href="https://www.exim.org/credits.html"/>
</xsl:variable>
<!-- CONTENT -->
<p>Built/maintains the website.</p>
</li>
<li>
- <a href="https://grepular.com/">Mike Cardwell</a>, of <a href="http://cardwellit.com/">Cardwell IT Ltd.</a>
+ <a href="https://grepular.com/">Mike Cardwell</a>, of <a href="https://cardwellit.com/">Cardwell IT Ltd.</a>
<p>Redesigned and built the current layout/style of the website, in 2010.</p>
</li>
<li>
- <xsl:text>Jennifer Greenley, of </xsl:text><a href="http://www.sharpblue.com/">Sharpblue</a>
+ <xsl:text>Jennifer Greenley, of </xsl:text><a href="https://sharpblue.com/">Sharpblue</a>
<p>Designed the new Exim logo, in 2002.</p>
</li>
</ul>
<xsl:variable name="html.head.append">
<!-- Canonical -->
- <link rel="canonical" href="http://www.exim.org/docs.html"/>
+ <link rel="canonical" href="https://www.exim.org/docs.html"/>
<!-- CSS -->
<link rel="stylesheet" type="text/css" href="docs.css"/>
</h2>
<!-- General Doc Info -->
- <p>Exim has a set of documentation released with it. A text file of the main documentation is released as part of the Exim tar archive. Additionally, postscript and texinfo forms of the documentation are available in separate tar archives on the ftp sites. There is also a <a href="http://www.uit.co.uk/exim-book/">book</a>.</p>
+ <p>Exim has a set of documentation released with it. A text file of the main documentation is released as part of the Exim tar archive. Additionally, postscript and texinfo forms of the documentation are available in separate tar archives on the ftp sites. There is also a <a href="https://www.uit.co.uk/the-exim-smtp-mail-server">book</a>.</p>
- <p>User supported documentation, FAQs and hints can be found in the <a href="http://wiki.exim.org/">wiki</a>.</p>
+ <p>User supported documentation, FAQs and hints can be found in the <a href="https://wiki.exim.org/">wiki</a>.</p>
<p>There are 3 main sets of documentation for Exim, all of which are also available below in html form.</p>
<link rel="stylesheet" type="text/css" href="mailman21.css"/>
<!-- Canonical -->
- <link rel="canonical" href="http://www.exim.org/howto/mailman21.html"/>
+ <link rel="canonical" href="https://www.exim.org/howto/mailman21.html"/>
</xsl:variable>
<h4><a href="#index" id="verpmm">VERP within Mailman</a></h4>
- <p><a href="http://cr.yp.to/proto/verp.txt">VERP</a> (Variable Envelope Return Paths) encodes the (original) receipient address in the sender address. The reason for doing this is that it means bounces are sent to an address which has the original recipient address encoded in it - meaning you know which recipient address caused the bounce. This makes automatic bounce handling very effective - the normal method of parsing the bouncing address out of the bounce message is very prone to failure, especially in the case of foreign MTAs which use different addressing standards, or where mail forwarding is involved.</p>
+ <p><a href="https://cr.yp.to/proto/verp.txt">VERP</a> (Variable Envelope Return Paths) encodes the (original) receipient address in the sender address. The reason for doing this is that it means bounces are sent to an address which has the original recipient address encoded in it - meaning you know which recipient address caused the bounce. This makes automatic bounce handling very effective - the normal method of parsing the bouncing address out of the bounce message is very prone to failure, especially in the case of foreign MTAs which use different addressing standards, or where mail forwarding is involved.</p>
- <p>VERP will send one email, with a separate envelope sender (return path), for each of your subscribers - this means that it will generate more traffic since you cannot bundle up deliveries together. An <a href="http://wiki.list.org/display/DOC/So+what+is+this+VERP+stuff">analysis of the costs of VERP</a> can be found in the <a href="http://wiki.list.org/">Mailman WIKI</a>.</p>
+ <p>VERP will send one email, with a separate envelope sender (return path), for each of your subscribers - this means that it will generate more traffic since you cannot bundle up deliveries together. An <a href="https://wiki.list.org/display/DOC/So+what+is+this+VERP+stuff">analysis of the costs of VERP</a> can be found in the <a href="https://wiki.list.org/">Mailman WIKI</a>.</p>
<p>VERP settings within Mailman are done on a per-installation basis - ie they affect all the lists within the installation. To configure VERP within Mailman read the information in ~mailman/Mailman/Default.py for the options that start with VERP. In a nutshell, all you need to do to enable VERP with Exim is to add these lines to ~mailman/Mailman/mm_cfg.py:</p>
<p>I would recommend that mailing lists now scan for both spam and viruses on incoming mail - this is due to the potential for a compromised windows machine belonging to a subscriber managing to distribute unwanted content via the list. This causes problems not only to the list reputation, but also to the list manager who will get many many bounces from subscribers who do content scanning on their own incoming mail.</p>
- <p>The best way to do this is using the <a href="http://duncanthrax.net/exiscan-acl/">exiscan</a> extension along with a virus scanner such as <a href="http://duncanthrax.net/exiscan-acl/">clam-av</a> and a spam content scanner such as <a href="http://www.spamassassin.org/">SpamAssassin</a>. Configuring these is beyond the scope of this document, however Tim Jackson has a very good set of <a href="http://www.timj.co.uk/linux/Exim-SpamAndVirusScanning.pdf">PDF documentation</a> on integrating these.</p>
+ <p>The best way to do this is using the <a href="https://duncanthrax.net/exiscan-acl/">exiscan</a> extension along with a virus scanner such as <a href="https://duncanthrax.net/exiscan-acl/">clam-av</a> and a spam content scanner such as <a href="https://spamassassin.apache.org/">SpamAssassin</a>. Configuring these is beyond the scope of this document, however Tim Jackson has a very good set of <a href="http://www.timj.co.uk/linux/Exim-SpamAndVirusScanning.pdf">PDF documentation</a> on integrating these.</p>
<p>One thing to note is that if you add full SpamAssassin headers onto list messages this bulks up the messages significantly. These headers are also available to list subscribers, which might make it easier for someone malicious to work out how to evade your spam scanning strategy. I would suggest that Spam headers are not added for Mailman incoming mail, or minimal (short) headers added, or that they are stripped somewhere. However having minimal headers on means that you can, for example, moderate all messages which have a given spam rating (as well as bouncing messages with a very high rating).</p>
<!-- Canonical -->
<xsl:variable name="html.head.append">
- <link rel="canonical" href="http://www.exim.org/howto/mirroring.html"/>
+ <link rel="canonical" href="https://www.exim.org/howto/mirroring.html"/>
</xsl:variable>
<!-- CONTENT -->
<h3>Tell people about it</h3>
- <p><a href="http://bugs.exim.org/enter_bug.cgi?product=Infrastructure&component=Mirrors&bug_severity=wishlist">Register
+ <p><a href="https://bugs.exim.org/enter_bug.cgi?product=Infrastructure&component=Mirrors&bug_severity=wishlist">Register
a bug</a> in the Exim Bugzilla under
Infrastructure/Mirrors so that the mirmon information can be
- updated. Join the <a href="http://www.exim.org/mailman/listinfo/exim-mirrors">exim-mirrors</a>
+ updated. Join the <a href="https://www.exim.org/mailman/listinfo/exim-mirrors">exim-mirrors</a>
list so we can tell you of any changes to mirroring practice.</p>
</xsl:template>
<!-- Canonical -->
<xsl:variable name="html.head.append">
- <link rel="canonical" href="http://www.exim.org/howto/rbl.html"/>
+ <link rel="canonical" href="https://www.exim.org/howto/rbl.html"/>
</xsl:variable>
<!-- CONTENT -->
<xsl:value-of select="$html.head.title"/>
</h2>
- <p>The MAPS (Mail Abuse Protection System) RBL (Realtime Blackhole List) was the first application of a way of using a DNS list as a means of identifying hosts that have been associated with the sending of spam mail. A full description of the service and the technology and ethics behind it can be found at <a href="http://www.mail-abuse.org/rbl/">http://www.mail-abuse.org/rbl/</a> along with more general mail policy information at <a href="http://www.mail-abuse.org/">http://www.mail-abuse.org/</a>.</p>
+ <p>The MAPS (Mail Abuse Protection System) RBL (Realtime Blackhole List) was the first application of a way of using a DNS list as a means of identifying hosts that have been associated with the sending of spam mail. A full description of the service and the technology and ethics behind it could once be found at <a href="http://www.mail-abuse.org/rbl/">http://www.mail-abuse.org/rbl/</a> along with more general mail policy information at <a href="http://www.mail-abuse.org/">http://www.mail-abuse.org/</a>.</p>
<p>In the few years since MAPS started operating, other similar services although with different aims, procedures and reliabilities have been introduced - MAPS itself has a number of these (ie MAPS/DUL which maintains lists of dial up modems). At this point in time there are many 10s of services with varying charters - lists of these can be found at <a href="http://relays.osirusoft.com/">http://relays.osirusoft.com/</a> and <a href="http://spamblock.outblaze.com/spamchk.html">http://spamblock.outblaze.com/spamchk.html</a>. The services are now normally referred to as a DNS Block List (DNSBL), rather than RBLs, however you will find that earlier Exim documentation (ie for version 3.x) will use the older term.</p>
<link rel="stylesheet" type="text/css" href="{$staticroot}/css/index.css"/>
<!-- Canonical -->
- <link rel="canonical" href="http://www.exim.org/"/>
+ <link rel="canonical" href="https://www.exim.org/"/>
</xsl:variable>
<!-- Summary -->
<p id="summary">
- <a href="http://www.exim.org/">
+ <a href="https://www.exim.org/">
<img src="i/exim-blue-ld-87x65.png" alt="Exim Logo" width="87" height="65"/>
</a>
<xsl:text>Exim is a message transfer agent (MTA) developed at the </xsl:text>
- <a href="http://www.cam.ac.uk/" title="University of Cambridge Home page">University of Cambridge</a>
+ <a href="https://www.cam.ac.uk/" title="University of Cambridge Home page">University of Cambridge</a>
<xsl:text> for use on Unix systems connected to the Internet. It is freely available under the terms of the </xsl:text>
- <a href="http://www.gnu.org/licenses/gpl.html" title="GPL Information">GNU General Public Licence</a>
+ <a href="https://www.gnu.org/licenses/gpl.html" title="GPL Information">GNU General Public Licence</a>
<xsl:text>. In style it is similar to </xsl:text>
- <a href="http://freshmeat.net/projects/smail/" rel="nofollow">Smail 3</a>
+ <a href="http://freecode.com/projects/smail/" rel="nofollow">Smail 3</a>
<xsl:text>, but its facilities are more general. There is a great deal of flexibility in the way mail can be routed, and there are extensive facilities for checking incoming mail. Exim can be installed in place of </xsl:text>
- <a href="http://www.sendmail.org/" title="Sendmail home page" rel="nofollow">Sendmail</a>
+ <a href="https://www.proofpoint.com/us/sendmail-open-source" title="Sendmail home page" rel="nofollow">Sendmail</a>
<xsl:text>, although the configuration of Exim is quite different.</xsl:text>
</p>
<xsl:text>You may wish to purchase </xsl:text>
<a href="https://www.uit.co.uk/the-exim-smtp-mail-server">The Exim SMTP Mail Server</a>
<xsl:text> book, written by the original author of Exim, </xsl:text>
- <a href="http://en.wikipedia.org/wiki/Philip_Hazel">Philip Hazel</a>
+ <a href="https://en.wikipedia.org/wiki/Philip_Hazel">Philip Hazel</a>
<xsl:text>.</xsl:text>
</p>
<!-- Canonical -->
<xsl:variable name="html.head.append">
- <link rel="canonical" href="http://www.exim.org/maillist.html"/>
+ <link rel="canonical" href="https://www.exim.org/maillist.html"/>
</xsl:variable>
<!-- CONTENT -->
<!-- Canonical -->
<xsl:variable name="html.head.append">
- <link rel="canonical" href="http://www.exim.org/mirrors.html"/>
+ <link rel="canonical" href="https://www.exim.org/mirrors.html"/>
</xsl:variable>
<!-- CONTENT -->
<p>A list of mirror sites is maintained within mirmon - see the links below for lists of mirrors and their current status:-</p>
<ul>
<li>
- <a href="http://www.exim.org/mirmon/ftp_mirrors.html">Download Mirrors</a>
+ <a href="https://www.exim.org/mirmon/ftp_mirrors.html">Download Mirrors</a>
</li>
<li>
- <a href="http://www.exim.org/mirmon/www_mirrors.html">Website Mirrors</a>
+ <a href="https://www.exim.org/mirmon/www_mirrors.html">Website Mirrors</a>
</li>
</ul>
<head>
<link rel="stylesheet" type="text/css" href="{$staticroot}/css/common.css"/>
- <meta name="author" content="The Exim Project. <http://www.exim.org/>"/>
+ <meta name="author" content="The Exim Project. <https://www.exim.org/>"/>
<meta name="copyright" content="Copyright ©1995-2012 The Exim Project. All rights reserved"/>
<meta name="description" content="{$html.head.description}"/>
<meta name="keywords" content="{$html.head.keywords}"/>
<li> <a href="{$docroot}/docs.html">Documentation</a> </li>
<li> <a href="{$docroot}/maillist.html">Mailing Lists</a> </li>
<li> <a href="http://wiki.exim.org/">Wiki</a> </li>
- <li> <a href="http://www.exim.org/bugzilla/">Bugs</a> </li>
+ <li> <a href="https://bugs.exim.org/">Bugs</a> </li>
<li> <a href="{$docroot}/credits.html">Credits</a> </li>
<li class="img">
<xsl:text>Website design by </xsl:text>
<a href="https://grepular.com/">Mike Cardwell</a>
<xsl:text>, of </xsl:text>
- <a href="http://cardwellit.com/">Cardwell IT Ltd.</a>
+ <a href="https://cardwellit.com/">Cardwell IT Ltd.</a>
</div>
<!-- Side Bars -->