You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by he...@apache.org on 2022/04/03 09:39:10 UTC

svn commit: r1899531 - in /spamassassin: branches/3.4/ branches/3.4/build/ branches/3.4/ldap/ branches/3.4/lib/ branches/3.4/lib/Mail/SpamAssassin/ branches/3.4/lib/Mail/SpamAssassin/Plugin/ branches/3.4/spamd-apache2/ branches/3.4/spamd/ trunk/ trunk/...

Author: hege
Date: Sun Apr  3 09:39:09 2022
New Revision: 1899531

URL: http://svn.apache.org/viewvc?rev=1899531&view=rev
Log:
Fix and sslify some documentation urls

Modified:
    spamassassin/branches/3.4/INSTALL
    spamassassin/branches/3.4/INSTALL.VMS
    spamassassin/branches/3.4/PACKAGING
    spamassassin/branches/3.4/README
    spamassassin/branches/3.4/USAGE
    spamassassin/branches/3.4/build/README
    spamassassin/branches/3.4/ldap/README
    spamassassin/branches/3.4/lib/Mail/SpamAssassin/Conf.pm
    spamassassin/branches/3.4/lib/Mail/SpamAssassin/Plugin.pm
    spamassassin/branches/3.4/lib/Mail/SpamAssassin/Plugin/Shortcircuit.pm
    spamassassin/branches/3.4/lib/Mail/SpamAssassin/Plugin/SpamCop.pm
    spamassassin/branches/3.4/lib/spamassassin-run.pod
    spamassassin/branches/3.4/sa-compile.raw
    spamassassin/branches/3.4/sa-learn.raw
    spamassassin/branches/3.4/sa-update.raw
    spamassassin/branches/3.4/spamd-apache2/README.apache
    spamassassin/branches/3.4/spamd/README
    spamassassin/branches/3.4/spamd/spamd.raw
    spamassassin/trunk/INSTALL
    spamassassin/trunk/INSTALL.VMS
    spamassassin/trunk/PACKAGING
    spamassassin/trunk/README
    spamassassin/trunk/USAGE
    spamassassin/trunk/build/README
    spamassassin/trunk/ldap/README
    spamassassin/trunk/lib/Mail/SpamAssassin/Conf.pm
    spamassassin/trunk/lib/Mail/SpamAssassin/Plugin.pm
    spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/Shortcircuit.pm
    spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/SpamCop.pm
    spamassassin/trunk/lib/spamassassin-run.pod
    spamassassin/trunk/sa-compile.raw
    spamassassin/trunk/sa-learn.raw
    spamassassin/trunk/sa-update.raw
    spamassassin/trunk/spamd-apache2/README.apache
    spamassassin/trunk/spamd/README
    spamassassin/trunk/spamd/spamd.raw

Modified: spamassassin/branches/3.4/INSTALL
URL: http://svn.apache.org/viewvc/spamassassin/branches/3.4/INSTALL?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/branches/3.4/INSTALL (original)
+++ spamassassin/branches/3.4/INSTALL Sun Apr  3 09:39:09 2022
@@ -49,9 +49,6 @@ Note that you can upgrade SpamAssassin u
 as you take care to read the caveats in the file UPGRADE.   Upgrading
 will not delete your learnt Bayes data or local rule modifications.
 
-If you're using SunOS 4.1.x, see
-http://wiki.spamassassin.org/w/BuildingOnSunOS4 for build tips.
-
 
 Installing SpamAssassin for Personal Use (Not System-Wide)
 ----------------------------------------------------------
@@ -62,7 +59,7 @@ These steps assume the following, so sub
   - The location of the procmail executable is /usr/bin/procmail
 
 Many more details of this process are at
-http://wiki.apache.org/spamassassin/SingleUserUnixInstall
+https://wiki.apache.org/spamassassin/SingleUserUnixInstall
 
 1. Uncompress and extract the SpamAssassin archive, using "unzip" or
    "tar xvfz", in a temporary directory.
@@ -119,7 +116,7 @@ http://wiki.apache.org/spamassassin/Sing
 caughtspam
 
 Also, see the file procmailrc.example and
-http://wiki.apache.org/spamassassin/UsedViaProcmail
+https://wiki.apache.org/spamassassin/UsedViaProcmail
 
 8. Now, you should be ready to send some test emails and ensure everything
    works as expected.  First, send yourself a test email that doesn't
@@ -136,7 +133,7 @@ http://wiki.apache.org/spamassassin/Used
    don't lose incoming email.
 
    Note: one possible cause for this is the use of smrsh on the MTA system;
-   see http://wiki.spamassassin.org/w/ProcmailVsSmrsh for details.
+   see https://wiki.apache.org/spamassassin/ProcmailVsSmrsh for details.
 
 9. You can now customize SpamAssassin.  See README for more information.
 
@@ -197,7 +194,7 @@ CPAN
 ----
 
 Most of the modules listed below are available via the Comprehensive Perl
-Archive Network (CPAN, see http://www.cpan.org/ for more information).
+Archive Network (CPAN, see https://www.cpan.org/ for more information).
 While each module is different, most can be installed via a few simple
 commands such as:
 
@@ -346,7 +343,7 @@ version is too low for them to be used.
 
     There seems to be a bug in libdb 4.1.25, which is
     distributed by default on some versions of Linux.  See
-    http://wiki.apache.org/spamassassin/DbFileSleepBug for details.
+    https://wiki.apache.org/spamassassin/DbFileSleepBug for details.
 
 
   - Net::SMTP (from CPAN)
@@ -471,7 +468,7 @@ What Next?
 Take a look at the USAGE document for more information on how to use
 SpamAssassin.
 
-The SpamAssassin Wiki <http://wiki.spamassassin.org/> contains
+The SpamAssassin Wiki <https://wiki.apache.org/spamassassin/> contains
 information on custom plugins, extensions, and other optional modules
 included with SpamAssassin.
 

Modified: spamassassin/branches/3.4/INSTALL.VMS
URL: http://svn.apache.org/viewvc/spamassassin/branches/3.4/INSTALL.VMS?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/branches/3.4/INSTALL.VMS (original)
+++ spamassassin/branches/3.4/INSTALL.VMS Sun Apr  3 09:39:09 2022
@@ -30,6 +30,6 @@ Notes on building SpamAssassin on VMS
 
   - bug 1099 in the SA Bugzilla is being used to track progress.
 
-        http://issues.apache.org/SpamAssassin/show_bug.cgi?id=1099
+        https://issues.apache.org/SpamAssassin/show_bug.cgi?id=1099
 
 

Modified: spamassassin/branches/3.4/PACKAGING
URL: http://svn.apache.org/viewvc/spamassassin/branches/3.4/PACKAGING?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/branches/3.4/PACKAGING (original)
+++ spamassassin/branches/3.4/PACKAGING Sun Apr  3 09:39:09 2022
@@ -289,25 +289,25 @@ Resources
 ---------
 
 [BUGZILLA] SpamAssassin bug database:
-  <http://issues.apache.org/SpamAssassin/>
+  <https://issues.apache.org/SpamAssassin/>
 
 [DEBPERL] Debian Perl Policy, Chapter 3: Packaged Modules:
-  <http://www.debian.org/doc/packaging-manuals/perl-policy/ch-module_packages.html>
+  <https://www.debian.org/doc/packaging-manuals/perl-policy/ch-module_packages.html>
 
 [GNUMAKECMD] GNU make manual: Make Conventions: Variables for Specifying
   Commands
-  <http://www.gnu.org/manual/make-3.79.1/html_chapter/make_14.html#SEC119>
+  <https://www.gnu.org/software/make/manual/html_node/Command-Variables.html#Command-Variables>
 
 [MANEUMM616] The man page for ExtUtils::MakeMaker 6.16:
-  <http://search.cpan.org/author/MSCHWERN/ExtUtils-MakeMaker-6.16/lib/ExtUtils/MakeMaker.pm#Default_Makefile_Behaviour>
+  <https://search.cpan.org/author/MSCHWERN/ExtUtils-MakeMaker-6.16/lib/ExtUtils/MakeMaker.pm#Default_Makefile_Behaviour>
 
 [MM00779] makemaker-at-perl-dot-org: Michael G Schwern: "Re: MakeMaker
   problems with relocation" (PREFIX was broken):
-  <http://www.mail-archive.com/makemaker@perl.org/msg00779.html>
+  <https://www.mail-archive.com/makemaker@perl.org/msg00779.html>
 
 [P5P94113] perl5-porters: Michael G Schwern: "Re: OS X's vendorlib default
   seems wrong" (description of different repositoreis):
-  <http://archive.develooper.com/perl5-porters@perl.org/msg94113.html>
+  <https://archive.develooper.com/perl5-porters@perl.org/msg94113.html>
 
 [RHBUG78053] Red Hat bug 78053: "incompatible changes in behavior of
   MakeMaker; affects rpm build process" (introduction of DESTDIR):

Modified: spamassassin/branches/3.4/README
URL: http://svn.apache.org/viewvc/spamassassin/branches/3.4/README?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/branches/3.4/README (original)
+++ spamassassin/branches/3.4/README Sun Apr  3 09:39:09 2022
@@ -71,9 +71,9 @@ spamassassin-users mailing list[2]. If y
 sure it's a bug after checking the Wiki), please file a report in our
 Bugzilla[3].
 
-	[1]: http://wiki.apache.org/spamassassin/
-	[2]: http://wiki.apache.org/spamassassin/MailingLists
-	[3]: http://issues.apache.org/SpamAssassin/
+	[1]: https://wiki.apache.org/spamassassin/
+	[2]: https://wiki.apache.org/spamassassin/MailingLists
+	[3]: https://issues.apache.org/SpamAssassin/
 
 Please also be sure to read the man pages.
 
@@ -298,7 +298,7 @@ these translations, so that they can be
 distribution. Please file a bug in our Bugzilla[4], and attach your
 translations. You will, of course, be credited for this work!
 
-	[4]: http://issues.apache.org/SpamAssassin/
+	[4]: https://issues.apache.org/SpamAssassin/
 
 
 Disabled code

Modified: spamassassin/branches/3.4/USAGE
URL: http://svn.apache.org/viewvc/spamassassin/branches/3.4/USAGE?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/branches/3.4/USAGE (original)
+++ spamassassin/branches/3.4/USAGE Sun Apr  3 09:39:09 2022
@@ -84,7 +84,7 @@ If you use procmail, or haven't decided
 If you want to use SpamAssassin site-wide:
 
   - take a look at the notes on the Wiki website, currently at
-    <http://wiki.apache.org/spamassassin/UsingSiteWide>.  You will probably
+    <https://wiki.apache.org/spamassassin/UsingSiteWide>.  You will probably
     want to use 'spamd' (see below).   You may want to investigate the
     new Apache mod_perl module, in the 'spamd-apache2' directory, too.
 
@@ -105,7 +105,7 @@ The Auto-Whitelist
 ------------------
 
 The auto-whitelist is enabled using the 'use_auto_whitelist' option.
-(See http://wiki.apache.org/spamassassin/AutoWhitelist for details on
+(See https://wiki.apache.org/spamassassin/AutoWhitelist for details on
 how it works, if you're curious.)
 
 
@@ -161,7 +161,7 @@ Other Installation Notes
   - A very handy new feature is SPF support, which allows you to check
     that the message sender is permitted by their domain to send from the
     IP address used.  This has the potential to greatly cut down on mail
-    forgery.  (see http://spf.pobox.com/ for more details.)
+    forgery.
 
 
   - MDaemon users should add this line to their "local.cf" file:
@@ -219,7 +219,7 @@ Other Installation Notes
     to do this, take a look here [1] for a simple forwarding-based
     alternative.
 
-      [1]: http://wiki.apache.org/spamassassin/SpamTrapping
+      [1]: https://wiki.apache.org/spamassassin/SpamTrapping
 
 
   - Scores and other user preferences can now be loaded from, and Bayes
@@ -242,7 +242,7 @@ Other Installation Notes
 
 
   - Lots more ways to integrate SpamAssassin can be read at
-    http://wiki.SpamAssassin.org/ .
+    https://wiki.apache.org/spamassassin/ .
 
 
 (end of USAGE)

Modified: spamassassin/branches/3.4/build/README
URL: http://svn.apache.org/viewvc/spamassassin/branches/3.4/build/README?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/branches/3.4/build/README (original)
+++ spamassassin/branches/3.4/build/README Sun Apr  3 09:39:09 2022
@@ -354,7 +354,7 @@ APACHE SPAMASSASSIN RELEASE PROCEDURE
 
 - Check the README file for any items to change.
 
-- Review the CREDITS to update Committers - http://whimsy.apache.org/
+- Review the CREDITS to update Committers - https://whimsy.apache.org/
   can help with this.
 
 - Review the CREDITS to update Copyright
@@ -368,7 +368,7 @@ APACHE SPAMASSASSIN RELEASE PROCEDURE
   development mailing list to make the release.  Post the URL,
   SHA sums, and proposed release announcement mail to the dev list.  
 
-    http://people.apache.org/~kmcgrail/devel/ qualifies as "discreet".
+    https://people.apache.org/~kmcgrail/devel/ qualifies as "discreet".
 
   Pre-releases and RCs require just lazy consensus -- ie. no objections.
 
@@ -378,14 +378,14 @@ APACHE SPAMASSASSIN RELEASE PROCEDURE
     https://dist.apache.org/repos/dist/dev/SpamAssassin
 
 - (for a pre or rc release), - upload .tar.gz (not .bz2) tarball to CPAN
-  at http://pause.cpan.org/:
+  at https://pause.cpan.org/:
 
         https://pause.perl.org/pause/authenquery?ACTION=add_uri
 
   See notes below for issues on indexing but the tar should be named in a 
   manner that CPAN will process it as a Developer Release per
 
-  http://www.cpan.org/modules/04pause.html#developerreleases
+  https://www.cpan.org/modules/04pause.html#developerreleases
 
   As of 2014-02-05, adding -TRIAL to the filename should work. For example:
 
@@ -487,7 +487,7 @@ APACHE SPAMASSASSIN RELEASE PROCEDURE
   make it clear that this is an unofficial "test build" by placing it
   in your public_html dir:
 
-        http://people.apache.org/~kmcgrail/devel/ for example
+        https://people.apache.org/~kmcgrail/devel/ for example
 
   NOTE: It's also feasible that you could publish via SVNPubSub as noted 
   below but using the SVN repository at:
@@ -506,7 +506,7 @@ APACHE SPAMASSASSIN RELEASE PROCEDURE
   [note: Symlinks may not work on all mirrors even though there may be 
   documentation to the contrary.]
 
-  As documented at http://www.apache.org/dev/release.html, SpamAssassin
+  As documented at https://www.apache.org/dev/release.html, SpamAssassin
   as of 2014-02-26 publishes tarballs by manipulating the repo on svn.
 
   svn co https://dist.apache.org/repos/dist/release/spamassassin/ release
@@ -516,7 +516,7 @@ APACHE SPAMASSASSIN RELEASE PROCEDURE
 
     Only the most recent version of each supported release line should be
     stored.  The archives will auto update.  
-    See http://www.apache.org/dev/release#archived.
+    See https://www.apache.org/dev/release#archived.
   - Commit 
   - Wait 24 hours before you announce to allow mirrors to update
 
@@ -573,7 +573,7 @@ APACHE SPAMASSASSIN RELEASE PROCEDURE
     svn delete -m "updating for new release"  $repo/tags/spamassassin_current_release_3.4.x
     svn copy -m "updating for new release" $repo/tags/spamassassin_release_$vers $repo/tags/spamassassin_current_release_3.4.x
 
-- upload release .tar.gz (not .bz2) tarball to CPAN at http://pause.cpan.org/:
+- upload release .tar.gz (not .bz2) tarball to CPAN at https://pause.cpan.org/:
 
         https://pause.perl.org/pause/authenquery?ACTION=add_uri
 
@@ -607,7 +607,7 @@ APACHE SPAMASSASSIN RELEASE PROCEDURE
 
 - Add the new version to the Bugzilla versions list:
 
-        http://issues.apache.org/SpamAssassin/editversions.cgi?product=Spamassassin&action=add
+        https://issues.apache.org/SpamAssassin/editversions.cgi?product=Spamassassin&action=add
 
 - Add a milestone for the next version to the Bugzilla milestones list:
 
@@ -632,7 +632,7 @@ APACHE SPAMASSASSIN RELEASE PROCEDURE
 
         https://issues.apache.org/SpamAssassin/editmilestones.cgi?product=Spamassassin
 
-- Update http://en.wikipedia.org/wiki/SpamAssassin
+- Update https://en.wikipedia.org/wiki/SpamAssassin
 
 
 

Modified: spamassassin/branches/3.4/ldap/README
URL: http://svn.apache.org/viewvc/spamassassin/branches/3.4/ldap/README?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/branches/3.4/ldap/README (original)
+++ spamassassin/branches/3.4/ldap/README Sun Apr  3 09:39:09 2022
@@ -68,7 +68,7 @@ our inetOrgPerson subclass.
 Here's an example for openldap's /etc/openldap/schema/inetorgperson.schema :
 
   # SpamAssassin
-  # see http://SpamAssassin.org/ .
+  # see https://SpamAssassin.org/ .
   attributetype ( 2.16.840.1.113730.3.1.217
           NAME 'spamassassin'
           DESC 'SpamAssassin user preferences settings'
@@ -97,9 +97,6 @@ If you do not see the above text, then t
 you should see any error messages reported. <username> should be the user
 that was passed to spamd and is usually the user executing spamc.
 
-If you need to set up LDAP, a good guide is here:
-http://yolinux.com/TUTORIALS/LinuxTutorialLDAP.html
-
 To test LDAP support using the SpamAssassin test suite, you need to
 perform a little bit of manual configuration first.  See the file
 "ldap/README.testing" for details.
@@ -111,6 +108,6 @@ operation of LDAP support may change at
 ******
 
 Please send any comments to <kris at koehntopp.de> and file bugs via
-<http://issues.apache.org/SpamAssassin/>.
+<https://issues.apache.org/SpamAssassin/>.
 
 Kristian Köhntopp

Modified: spamassassin/branches/3.4/lib/Mail/SpamAssassin/Conf.pm
URL: http://svn.apache.org/viewvc/spamassassin/branches/3.4/lib/Mail/SpamAssassin/Conf.pm?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/branches/3.4/lib/Mail/SpamAssassin/Conf.pm (original)
+++ spamassassin/branches/3.4/lib/Mail/SpamAssassin/Conf.pm Sun Apr  3 09:39:09 2022
@@ -46,7 +46,7 @@ directories.
 The following web page lists the most important configuration settings
 used to configure SpamAssassin; novices are encouraged to read it first:
 
-  http://wiki.apache.org/spamassassin/ImportantInitialConfigItems
+  https://wiki.apache.org/spamassassin/ImportantInitialConfigItems
 
 =head1 FILE FORMAT
 
@@ -1279,7 +1279,7 @@ operated by spammers, open relays, or op
 conceivably relay spam, but will not originate it, and will not forge header
 data. DNS blacklist checks will never query for hosts on these networks. 
 
-See C<http://wiki.apache.org/spamassassin/TrustPath> for more information.
+See C<https://wiki.apache.org/spamassassin/TrustPath> for more information.
 
 MXes for your domain(s) and internal relays should B<also> be specified using
 the C<internal_networks> setting. When there are 'trusted' hosts that
@@ -2539,7 +2539,7 @@ default heuristics.
 
 (Note for MTA developers: we would prefer if the use of a single header be
 avoided in future, since that precludes 'downstream' spam scanning.
-C<http://wiki.apache.org/spamassassin/EnvelopeSenderInReceived> details a
+C<https://wiki.apache.org/spamassassin/EnvelopeSenderInReceived> details a
 better proposal, storing the envelope sender at each hop in the C<Received>
 header.)
 
@@ -2896,7 +2896,7 @@ by newlines.
 C<X-Spam-Relays-Internal> and C<X-Spam-Relays-External> represent a portable,
 pre-parsed representation of the message's network path, as recorded in the
 Received headers, divided into 'trusted' vs 'untrusted' and 'internal' vs
-'external' sets.  See C<http://wiki.apache.org/spamassassin/TrustedRelays> for
+'external' sets.  See C<https://wiki.apache.org/spamassassin/TrustedRelays> for
 more details.
 
 =back
@@ -2955,9 +2955,7 @@ zone.  There's a few things to note:
 
 Duplicated IPs are only queried once and reserved IPs are not queried.
 Private IPs are those listed in
-C<https://www.iana.org/assignments/ipv4-address-space>,
-C<http://duxcw.com/faq/network/privip.htm>,
-C<http://duxcw.com/faq/network/autoip.htm>, or
+C<https://www.iana.org/assignments/ipv4-address-space>, or
 C<https://tools.ietf.org/html/rfc5735> as private.
 
 =item the 'set' argument
@@ -3010,7 +3008,7 @@ IP address from the most recent 'untrust
 above.  That's because we're talking about the trustworthiness of the
 IP address data, not the source header line, here; and in the case of 
 the most recent header (the 'firsttrusted'), that data can be trusted.
-See the Wiki page at C<http://wiki.apache.org/spamassassin/TrustedRelays>
+See the Wiki page at C<https://wiki.apache.org/spamassassin/TrustedRelays>
 for more information on this.
 
 =item Selecting just the last external IP

Modified: spamassassin/branches/3.4/lib/Mail/SpamAssassin/Plugin.pm
URL: http://svn.apache.org/viewvc/spamassassin/branches/3.4/lib/Mail/SpamAssassin/Plugin.pm?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/branches/3.4/lib/Mail/SpamAssassin/Plugin.pm (original)
+++ spamassassin/branches/3.4/lib/Mail/SpamAssassin/Plugin.pm Sun Apr  3 09:39:09 2022
@@ -882,7 +882,7 @@ only spamd calls this API.
 =item result
 
 The C<'result: ...'> line for this scan.  Format is as described
-at B<http://wiki.apache.org/spamassassin/SpamdSyslogFormat>.
+at B<https://wiki.apache.org/spamassassin/SpamdSyslogFormat>.
 
 =back
 
@@ -1216,8 +1216,8 @@ Mail::SpamAssassin(3)
 
 Mail::SpamAssassin::PerMsgStatus(3)
 
-http://wiki.apache.org/spamassassin/PluginWritingTips
+https://wiki.apache.org/spamassassin/PluginWritingTips
 
-http://issues.apache.org/SpamAssassin/show_bug.cgi?id=2163
+https://issues.apache.org/SpamAssassin/show_bug.cgi?id=2163
 
 =cut

Modified: spamassassin/branches/3.4/lib/Mail/SpamAssassin/Plugin/Shortcircuit.pm
URL: http://svn.apache.org/viewvc/spamassassin/branches/3.4/lib/Mail/SpamAssassin/Plugin/Shortcircuit.pm?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/branches/3.4/lib/Mail/SpamAssassin/Plugin/Shortcircuit.pm (original)
+++ spamassassin/branches/3.4/lib/Mail/SpamAssassin/Plugin/Shortcircuit.pm Sun Apr  3 09:39:09 2022
@@ -306,6 +306,6 @@ sub compile_now_finish {
 
 =head1 SEE ALSO
 
-C<http://issues.apache.org/SpamAssassin/show_bug.cgi?id=3109>
+C<https://issues.apache.org/SpamAssassin/show_bug.cgi?id=3109>
 
 =cut

Modified: spamassassin/branches/3.4/lib/Mail/SpamAssassin/Plugin/SpamCop.pm
URL: http://svn.apache.org/viewvc/spamassassin/branches/3.4/lib/Mail/SpamAssassin/Plugin/SpamCop.pm?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/branches/3.4/lib/Mail/SpamAssassin/Plugin/SpamCop.pm (original)
+++ spamassassin/branches/3.4/lib/Mail/SpamAssassin/Plugin/SpamCop.pm Sun Apr  3 09:39:09 2022
@@ -35,7 +35,7 @@ SpamAssassin as a DNSBL.
 Note that spam reports sent by this plugin to SpamCop each include the
 entire spam message.
 
-See http://www.spamcop.net/ for more information about SpamCop.
+See https://www.spamcop.net/ for more information about SpamCop.
 
 =cut
 
@@ -114,7 +114,7 @@ guess will be used as the From: address
 =item spamcop_to_address user@example.com   (default: generic reporting address)
 
 Your customized SpamCop report submission address.  You need to obtain
-this address by registering at C<http://www.spamcop.net/>.  If this is
+this address by registering at C<https://www.spamcop.net/>.  If this is
 not set, SpamCop reports will go to a generic reporting address for
 SpamAssassin users and your reports will probably have less weight in
 the SpamCop system.

Modified: spamassassin/branches/3.4/lib/spamassassin-run.pod
URL: http://svn.apache.org/viewvc/spamassassin/branches/3.4/lib/spamassassin-run.pod?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/branches/3.4/lib/spamassassin-run.pod (original)
+++ spamassassin/branches/3.4/lib/spamassassin-run.pod Sun Apr  3 09:39:09 2022
@@ -122,8 +122,8 @@ Report this message as manually-verified
 message read from STDIN to various spam-blocker databases.  Currently,
 these are the Distributed Checksum Clearinghouse
 C<https://www.dcc-servers.net/dcc/>, Pyzor
-C<http://pyzor.org/>, Vipul's Razor
-C<http://razor.sourceforge.net/>, and SpamCop C<http://www.spamcop.net/>.
+C<https://www.pyzor.org/>, Vipul's Razor
+C<http://razor.sourceforge.net/>, and SpamCop C<https://www.spamcop.net/>.
 
 If the message contains SpamAssassin markup, the markup will be stripped
 out automatically before submission.  The support modules for DCC, Pyzor,
@@ -277,7 +277,7 @@ circumstances are available with an area
 For more information about which areas (also known as channels) are available,
 please see the documentation at:
 
-	L<http://wiki.apache.org/spamassassin/DebugChannels>
+	L<https://wiki.apache.org/spamassassin/DebugChannels>
 
 =item B<-x>, B<--nocreate-prefs>
 
@@ -292,7 +292,7 @@ Unix message folder format.
 
 Specify that the input message(s) are in UW .mbx format.  mbx is
 the mailbox format used within the University of Washington's IMAP
-implementation; see C<http://www.washington.edu/imap/>.
+implementation; see C<https://en.wikipedia.org/wiki/UW_IMAP>.
 
 =back
 
@@ -310,7 +310,7 @@ C<Mail::SpamAssassin>
 
 =head1 BUGS
 
-See <http://issues.apache.org/SpamAssassin/>
+See <https://issues.apache.org/SpamAssassin/>
 
 =head1 AUTHORS
 

Modified: spamassassin/branches/3.4/sa-compile.raw
URL: http://svn.apache.org/viewvc/spamassassin/branches/3.4/sa-compile.raw?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/branches/3.4/sa-compile.raw (original)
+++ spamassassin/branches/3.4/sa-compile.raw Sun Apr  3 09:39:09 2022
@@ -700,7 +700,7 @@ C<re2c> can match strings much faster th
 match many simple strings in parallel, and compiling that to native object
 code.  Not all SpamAssassin rules are amenable to this conversion, however.
 
-This requires C<re2c> (see C<http://re2c.org/>), and the C
+This requires C<re2c> (see C<https://re2c.org/>), and the C
 compiler used to build Perl XS modules, be installed.
 
 Note that running this, and creating a compiled ruleset, will have no
@@ -777,7 +777,7 @@ I<area> is the area of the code to instr
 
 For more information about which areas (also known as channels) are
 available, please see the documentation at
-L<http://wiki.apache.org/spamassassin/DebugChannels>.
+L<https://wiki.apache.org/spamassassin/DebugChannels>.
 
 =item B<-h>, B<--help>
 
@@ -803,7 +803,7 @@ C<Mail::SpamAssassin::Plugin::Rule2XSBod
 
 =head1 BUGS
 
-See <http://issues.apache.org/SpamAssassin/>
+See <https://issues.apache.org/SpamAssassin/>
 
 =head1 AUTHORS
 

Modified: spamassassin/branches/3.4/sa-learn.raw
URL: http://svn.apache.org/viewvc/spamassassin/branches/3.4/sa-learn.raw?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/branches/3.4/sa-learn.raw (original)
+++ spamassassin/branches/3.4/sa-learn.raw Sun Apr  3 09:39:09 2022
@@ -845,7 +845,7 @@ diagnostic output on bayes, learn, and d
 For more information about which areas (also known as channels) are available,
 please see the documentation at:
 
-        C<http://wiki.apache.org/spamassassin/DebugChannels>
+        C<https://wiki.apache.org/spamassassin/DebugChannels>
 
 Higher priority informational messages that are suitable for logging in normal
 circumstances are available with an area of "info".

Modified: spamassassin/branches/3.4/sa-update.raw
URL: http://svn.apache.org/viewvc/spamassassin/branches/3.4/sa-update.raw?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/branches/3.4/sa-update.raw (original)
+++ spamassassin/branches/3.4/sa-update.raw Sun Apr  3 09:39:09 2022
@@ -2159,7 +2159,7 @@ diagnostic output on channel, gpg, and h
 
 For more information about which areas (also known as channels) are
 available, please see the documentation at
-L<http://wiki.apache.org/spamassassin/DebugChannels>.
+L<https://wiki.apache.org/spamassassin/DebugChannels>.
 
 =item B<-h>, B<--help>
 
@@ -2196,7 +2196,7 @@ Mail::SpamAssassin(3)
 Mail::SpamAssassin::Conf(3)
 spamassassin(1)
 spamd(1)
-<http://wiki.apache.org/spamassassin/RuleUpdates>
+<https://wiki.apache.org/spamassassin/RuleUpdates>
 
 =head1 PREREQUISITES
 
@@ -2204,7 +2204,7 @@ C<Mail::SpamAssassin>
 
 =head1 BUGS
 
-See <http://issues.apache.org/SpamAssassin/>
+See <https://issues.apache.org/SpamAssassin/>
 
 =head1 AUTHORS
 

Modified: spamassassin/branches/3.4/spamd-apache2/README.apache
URL: http://svn.apache.org/viewvc/spamassassin/branches/3.4/spamd-apache2/README.apache?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/branches/3.4/spamd-apache2/README.apache (original)
+++ spamassassin/branches/3.4/spamd-apache2/README.apache Sun Apr  3 09:39:09 2022
@@ -46,7 +46,7 @@ available separately on CPAN.
 
 BUGS
   
-See <http://issues.apache.org/SpamAssassin/> to report a bug.
+See <https://issues.apache.org/SpamAssassin/> to report a bug.
 
 Please include perl, Apache and mod_perl versions. 
 

Modified: spamassassin/branches/3.4/spamd/README
URL: http://svn.apache.org/viewvc/spamassassin/branches/3.4/spamd/README?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/branches/3.4/spamd/README (original)
+++ spamassassin/branches/3.4/spamd/README Sun Apr  3 09:39:09 2022
@@ -112,7 +112,7 @@ you will need to either
 
   2. Alternatively, let the users train their individual Bayes database.
 
-http://wiki.apache.org/spamassassin/SiteWideBayesFeedback can be very
+https://wiki.apache.org/spamassassin/SiteWideBayesFeedback can be very
 helpful here.
 
 We have implemented an auto-learning algorithm (option 'bayes_auto_learn', on
@@ -194,7 +194,7 @@ There are no known bugs with this setup.
 are now running it on their production mail systems.  However, you should
 still test it completely in *your environment* before trusting all your
 mail to it.  If you discover compilation, runtime, or load-performance
-bugs, please open a ticket at http://issues.apache.org/SpamAssassin/
+bugs, please open a ticket at https://issues.apache.org/SpamAssassin/
 
 There is an issue if you run spamd using the standard perl installation
 on Mac OS X and certain *BSD-flavored UNIX platforms.  spamd will change

Modified: spamassassin/branches/3.4/spamd/spamd.raw
URL: http://svn.apache.org/viewvc/spamassassin/branches/3.4/spamd/spamd.raw?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/branches/3.4/spamd/spamd.raw (original)
+++ spamassassin/branches/3.4/spamd/spamd.raw Sun Apr  3 09:39:09 2022
@@ -3651,7 +3651,7 @@ circumstances are available with an area
 For more information about which areas (also known as channels) are available,
 please see the documentation at:
 
-	C<http://wiki.apache.org/spamassassin/DebugChannels>
+	C<https://wiki.apache.org/spamassassin/DebugChannels>
 
 =item B<-4>, B<--ipv4only>, B<--ipv4-only>, B<--ipv4>
 

Modified: spamassassin/trunk/INSTALL
URL: http://svn.apache.org/viewvc/spamassassin/trunk/INSTALL?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/trunk/INSTALL (original)
+++ spamassassin/trunk/INSTALL Sun Apr  3 09:39:09 2022
@@ -49,9 +49,6 @@ Note that you can upgrade SpamAssassin u
 as you take care to read the caveats in the file UPGRADE.   Upgrading
 will not delete your learnt Bayes data or local rule modifications.
 
-If you're using SunOS 4.1.x, see
-http://wiki.spamassassin.org/w/BuildingOnSunOS4 for build tips.
-
 
 Installing SpamAssassin for Personal Use (Not System-Wide)
 ----------------------------------------------------------
@@ -62,7 +59,7 @@ These steps assume the following, so sub
   - The location of the procmail executable is /usr/bin/procmail
 
 Many more details of this process are at
-http://wiki.apache.org/spamassassin/SingleUserUnixInstall
+https://wiki.apache.org/spamassassin/SingleUserUnixInstall
 
 1. Uncompress and extract the SpamAssassin archive, using "unzip" or
    "tar xvfz", in a temporary directory.
@@ -119,7 +116,7 @@ http://wiki.apache.org/spamassassin/Sing
 caughtspam
 
 Also, see the file procmailrc.example and
-http://wiki.apache.org/spamassassin/UsedViaProcmail
+https://wiki.apache.org/spamassassin/UsedViaProcmail
 
 8. Now, you should be ready to send some test emails and ensure everything
    works as expected.  First, send yourself a test email that doesn't
@@ -136,7 +133,7 @@ http://wiki.apache.org/spamassassin/Used
    don't lose incoming email.
 
    Note: one possible cause for this is the use of smrsh on the MTA system;
-   see http://wiki.spamassassin.org/w/ProcmailVsSmrsh for details.
+   see https://wiki.apache.org/spamassassin/ProcmailVsSmrsh for details.
 
 9. You can now customize SpamAssassin.  See README for more information.
 
@@ -197,7 +194,7 @@ CPAN
 ----
 
 Most of the modules listed below are available via the Comprehensive Perl
-Archive Network (CPAN, see http://www.cpan.org/ for more information).
+Archive Network (CPAN, see https://www.cpan.org/ for more information).
 While each module is different, most can be installed via a few simple
 commands such as:
 
@@ -320,7 +317,7 @@ version is too low for them to be used.
 
     There seems to be a bug in libdb 4.1.25, which is
     distributed by default on some versions of Linux.  See
-    http://wiki.apache.org/spamassassin/DbFileSleepBug for details.
+    https://wiki.apache.org/spamassassin/DbFileSleepBug for details.
 
 
   - Net::SMTP (from CPAN)
@@ -438,7 +435,7 @@ What Next?
 Take a look at the USAGE document for more information on how to use
 SpamAssassin.
 
-The SpamAssassin Wiki <http://wiki.spamassassin.org/> contains
+The SpamAssassin Wiki <https://wiki.apache.org/spamassassin/> contains
 information on custom plugins, extensions, and other optional modules
 included with SpamAssassin.
 

Modified: spamassassin/trunk/INSTALL.VMS
URL: http://svn.apache.org/viewvc/spamassassin/trunk/INSTALL.VMS?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/trunk/INSTALL.VMS (original)
+++ spamassassin/trunk/INSTALL.VMS Sun Apr  3 09:39:09 2022
@@ -30,6 +30,6 @@ Notes on building SpamAssassin on VMS
 
   - bug 1099 in the SA Bugzilla is being used to track progress.
 
-        http://issues.apache.org/SpamAssassin/show_bug.cgi?id=1099
+        https://issues.apache.org/SpamAssassin/show_bug.cgi?id=1099
 
 

Modified: spamassassin/trunk/PACKAGING
URL: http://svn.apache.org/viewvc/spamassassin/trunk/PACKAGING?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/trunk/PACKAGING (original)
+++ spamassassin/trunk/PACKAGING Sun Apr  3 09:39:09 2022
@@ -289,25 +289,25 @@ Resources
 ---------
 
 [BUGZILLA] SpamAssassin bug database:
-  <http://issues.apache.org/SpamAssassin/>
+  <https://issues.apache.org/SpamAssassin/>
 
 [DEBPERL] Debian Perl Policy, Chapter 3: Packaged Modules:
-  <http://www.debian.org/doc/packaging-manuals/perl-policy/ch-module_packages.html>
+  <https://www.debian.org/doc/packaging-manuals/perl-policy/ch-module_packages.html>
 
 [GNUMAKECMD] GNU make manual: Make Conventions: Variables for Specifying
   Commands
-  <http://www.gnu.org/manual/make-3.79.1/html_chapter/make_14.html#SEC119>
+  <https://www.gnu.org/software/make/manual/html_node/Command-Variables.html#Command-Variables>
 
 [MANEUMM616] The man page for ExtUtils::MakeMaker 6.16:
-  <http://search.cpan.org/author/MSCHWERN/ExtUtils-MakeMaker-6.16/lib/ExtUtils/MakeMaker.pm#Default_Makefile_Behaviour>
+  <https://search.cpan.org/author/MSCHWERN/ExtUtils-MakeMaker-6.16/lib/ExtUtils/MakeMaker.pm#Default_Makefile_Behaviour>
 
 [MM00779] makemaker-at-perl-dot-org: Michael G Schwern: "Re: MakeMaker
   problems with relocation" (PREFIX was broken):
-  <http://www.mail-archive.com/makemaker@perl.org/msg00779.html>
+  <https://www.mail-archive.com/makemaker@perl.org/msg00779.html>
 
 [P5P94113] perl5-porters: Michael G Schwern: "Re: OS X's vendorlib default
   seems wrong" (description of different repositoreis):
-  <http://archive.develooper.com/perl5-porters@perl.org/msg94113.html>
+  <https://archive.develooper.com/perl5-porters@perl.org/msg94113.html>
 
 [RHBUG78053] Red Hat bug 78053: "incompatible changes in behavior of
   MakeMaker; affects rpm build process" (introduction of DESTDIR):

Modified: spamassassin/trunk/README
URL: http://svn.apache.org/viewvc/spamassassin/trunk/README?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/trunk/README (original)
+++ spamassassin/trunk/README Sun Apr  3 09:39:09 2022
@@ -71,9 +71,9 @@ spamassassin-users mailing list[2]. If y
 sure it's a bug after checking the Wiki), please file a report in our
 Bugzilla[3].
 
-	[1]: http://wiki.apache.org/spamassassin/
-	[2]: http://wiki.apache.org/spamassassin/MailingLists
-	[3]: http://issues.apache.org/SpamAssassin/
+	[1]: https://wiki.apache.org/spamassassin/
+	[2]: https://wiki.apache.org/spamassassin/MailingLists
+	[3]: https://issues.apache.org/SpamAssassin/
 
 Please also be sure to read the man pages.
 
@@ -298,7 +298,7 @@ these translations, so that they can be
 distribution. Please file a bug in our Bugzilla[4], and attach your
 translations. You will, of course, be credited for this work!
 
-	[4]: http://issues.apache.org/SpamAssassin/
+	[4]: https://issues.apache.org/SpamAssassin/
 
 
 Disabled code

Modified: spamassassin/trunk/USAGE
URL: http://svn.apache.org/viewvc/spamassassin/trunk/USAGE?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/trunk/USAGE (original)
+++ spamassassin/trunk/USAGE Sun Apr  3 09:39:09 2022
@@ -84,7 +84,7 @@ If you use procmail, or haven't decided
 If you want to use SpamAssassin site-wide:
 
   - take a look at the notes on the Wiki website, currently at
-    <http://wiki.apache.org/spamassassin/UsingSiteWide>.  You will probably
+    <https://wiki.apache.org/spamassassin/UsingSiteWide>.  You will probably
     want to use 'spamd' (see below).   You may want to investigate the
     new Apache mod_perl module, in the 'spamd-apache2' directory, too.
 
@@ -105,7 +105,7 @@ The Auto-Whitelist
 ------------------
 
 The auto-whitelist is enabled using the 'use_auto_whitelist' option.
-(See http://wiki.apache.org/spamassassin/AutoWhitelist for details on
+(See https://wiki.apache.org/spamassassin/AutoWhitelist for details on
 how it works, if you're curious.)
 
 
@@ -152,7 +152,7 @@ Other Installation Notes
   - A very handy new feature is SPF support, which allows you to check
     that the message sender is permitted by their domain to send from the
     IP address used.  This has the potential to greatly cut down on mail
-    forgery.  (see http://spf.pobox.com/ for more details.)
+    forgery.
 
 
   - MDaemon users should add this line to their "local.cf" file:
@@ -210,7 +210,7 @@ Other Installation Notes
     to do this, take a look here [1] for a simple forwarding-based
     alternative.
 
-      [1]: http://wiki.apache.org/spamassassin/SpamTrapping
+      [1]: https://wiki.apache.org/spamassassin/SpamTrapping
 
 
   - Scores and other user preferences can now be loaded from, and Bayes
@@ -233,7 +233,7 @@ Other Installation Notes
 
 
   - Lots more ways to integrate SpamAssassin can be read at
-    http://wiki.SpamAssassin.org/ .
+    https://wiki.apache.org/spamassassin/ .
 
 
 (end of USAGE)

Modified: spamassassin/trunk/build/README
URL: http://svn.apache.org/viewvc/spamassassin/trunk/build/README?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/trunk/build/README (original)
+++ spamassassin/trunk/build/README Sun Apr  3 09:39:09 2022
@@ -399,7 +399,7 @@ make
 
 - Check the README file for any items to change.
 
-- Review the CREDITS to update Committers - http://whimsy.apache.org/
+- Review the CREDITS to update Committers - https://whimsy.apache.org/
   can help with this.
 
 - Review the CREDITS to update Copyright
@@ -413,7 +413,7 @@ make
   development mailing list to make the release.  Post the URL,
   SHA sums, and proposed release announcement mail to the dev list.  
 
-    http://people.apache.org/~kmcgrail/devel/ qualifies as "discreet".
+    https://people.apache.org/~kmcgrail/devel/ qualifies as "discreet".
 
   Pre-releases and RCs require just lazy consensus -- ie. no objections.
 
@@ -423,14 +423,14 @@ make
     https://dist.apache.org/repos/dist/dev/SpamAssassin
 
 - (for a pre or rc release), - upload .tar.gz (not .bz2) tarball to CPAN
-  at http://pause.cpan.org/:
+  at https://pause.cpan.org/:
 
         https://pause.perl.org/pause/authenquery?ACTION=add_uri
 
   See notes below for issues on indexing but the tar should be named in a 
   manner that CPAN will process it as a Developer Release per
 
-  http://www.cpan.org/modules/04pause.html#developerreleases
+  https://www.cpan.org/modules/04pause.html#developerreleases
 
   As of 2014-02-05, adding -TRIAL to the filename should work. For example:
 
@@ -532,7 +532,7 @@ make
   make it clear that this is an unofficial "test build" by placing it
   in your public_html dir:
 
-        http://people.apache.org/~kmcgrail/devel/ for example
+        https://people.apache.org/~kmcgrail/devel/ for example
 
   NOTE: It's also feasible that you could publish via SVNPubSub as noted 
   below but using the SVN repository at:
@@ -557,7 +557,7 @@ make
   [note: Symlinks may not work on all mirrors even though there may be 
   documentation to the contrary.]
 
-  As documented at http://www.apache.org/dev/release.html, SpamAssassin
+  As documented at https://www.apache.org/dev/release.html, SpamAssassin
   as of 2014-02-26 publishes tarballs by manipulating the repo on svn.
 
   svn co https://dist.apache.org/repos/dist/release/spamassassin/ release
@@ -567,7 +567,7 @@ make
 
     Only the most recent version of each supported release line should be
     stored.  The archives will auto update.  
-    See http://www.apache.org/dev/release#archived.
+    See https://www.apache.org/dev/release#archived.
   - Commit 
   - Wait 24 hours before you announce to allow mirrors to update
 
@@ -638,7 +638,7 @@ make
     svn delete -m "updating for new release"  $repo/tags/spamassassin_current_release_3.4.x
     svn copy -m "updating for new release" $repo/tags/spamassassin_release_$vers $repo/tags/spamassassin_current_release_3.4.x
 
-- upload release .tar.gz (not .bz2) tarball to CPAN at http://pause.cpan.org/:
+- upload release .tar.gz (not .bz2) tarball to CPAN at https://pause.cpan.org/:
 
         https://pause.perl.org/pause/authenquery?ACTION=add_uri
 
@@ -672,7 +672,7 @@ make
 
 - Add the new version to the Bugzilla versions list:
 
-        http://issues.apache.org/SpamAssassin/editversions.cgi?product=Spamassassin&action=add
+        https://issues.apache.org/SpamAssassin/editversions.cgi?product=Spamassassin&action=add
 
 - Add a milestone for the next version to the Bugzilla milestones list:
 
@@ -697,7 +697,7 @@ make
 
         https://issues.apache.org/SpamAssassin/editmilestones.cgi?product=Spamassassin
 
-- Update http://en.wikipedia.org/wiki/SpamAssassin
+- Update https://en.wikipedia.org/wiki/SpamAssassin
 
 
 

Modified: spamassassin/trunk/ldap/README
URL: http://svn.apache.org/viewvc/spamassassin/trunk/ldap/README?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/trunk/ldap/README (original)
+++ spamassassin/trunk/ldap/README Sun Apr  3 09:39:09 2022
@@ -68,7 +68,7 @@ our inetOrgPerson subclass.
 Here's an example for openldap's /etc/openldap/schema/inetorgperson.schema :
 
   # SpamAssassin
-  # see http://SpamAssassin.org/ .
+  # see https://SpamAssassin.org/ .
   attributetype ( 2.16.840.1.113730.3.1.217
           NAME 'spamassassin'
           DESC 'SpamAssassin user preferences settings'
@@ -97,9 +97,6 @@ If you do not see the above text, then t
 you should see any error messages reported. <username> should be the user
 that was passed to spamd and is usually the user executing spamc.
 
-If you need to set up LDAP, a good guide is here:
-http://yolinux.com/TUTORIALS/LinuxTutorialLDAP.html
-
 To test LDAP support using the SpamAssassin test suite, you need to
 perform a little bit of manual configuration first.  See the file
 "ldap/README.testing" for details.
@@ -111,6 +108,6 @@ operation of LDAP support may change at
 ******
 
 Please send any comments to <kris at koehntopp.de> and file bugs via
-<http://issues.apache.org/SpamAssassin/>.
+<https://issues.apache.org/SpamAssassin/>.
 
 Kristian Köhntopp

Modified: spamassassin/trunk/lib/Mail/SpamAssassin/Conf.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin/Conf.pm?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/trunk/lib/Mail/SpamAssassin/Conf.pm (original)
+++ spamassassin/trunk/lib/Mail/SpamAssassin/Conf.pm Sun Apr  3 09:39:09 2022
@@ -46,7 +46,7 @@ directories.
 The following web page lists the most important configuration settings
 used to configure SpamAssassin; novices are encouraged to read it first:
 
-  http://wiki.apache.org/spamassassin/ImportantInitialConfigItems
+  https://wiki.apache.org/spamassassin/ImportantInitialConfigItems
 
 =head1 FILE FORMAT
 
@@ -1320,7 +1320,7 @@ operated by spammers, open relays, or op
 conceivably relay spam, but will not originate it, and will not forge header
 data. DNS blacklist checks will never query for hosts on these networks. 
 
-See C<http://wiki.apache.org/spamassassin/TrustPath> for more information.
+See C<https://wiki.apache.org/spamassassin/TrustPath> for more information.
 
 MXes for your domain(s) and internal relays should B<also> be specified using
 the C<internal_networks> setting. When there are 'trusted' hosts that
@@ -2646,7 +2646,7 @@ default heuristics.
 
 (Note for MTA developers: we would prefer if the use of a single header be
 avoided in future, since that precludes 'downstream' spam scanning.
-C<http://wiki.apache.org/spamassassin/EnvelopeSenderInReceived> details a
+C<https://wiki.apache.org/spamassassin/EnvelopeSenderInReceived> details a
 better proposal, storing the envelope sender at each hop in the C<Received>
 header.)
 
@@ -2999,7 +2999,7 @@ by newlines.
 C<X-Spam-Relays-Internal> and C<X-Spam-Relays-External> represent a portable,
 pre-parsed representation of the message's network path, as recorded in the
 Received headers, divided into 'trusted' vs 'untrusted' and 'internal' vs
-'external' sets.  See C<http://wiki.apache.org/spamassassin/TrustedRelays> for
+'external' sets.  See C<https://wiki.apache.org/spamassassin/TrustedRelays> for
 more details.
 
 =back
@@ -3058,9 +3058,7 @@ zone.  There's a few things to note:
 
 Duplicated IPs are only queried once and reserved IPs are not queried.
 Private IPs are those listed in
-C<https://www.iana.org/assignments/ipv4-address-space>,
-C<http://duxcw.com/faq/network/privip.htm>,
-C<http://duxcw.com/faq/network/autoip.htm>, or
+C<https://www.iana.org/assignments/ipv4-address-space>, or
 C<https://tools.ietf.org/html/rfc5735> as private.
 
 =item the 'set' argument
@@ -3113,7 +3111,7 @@ IP address from the most recent 'untrust
 above.  That's because we're talking about the trustworthiness of the
 IP address data, not the source header line, here; and in the case of 
 the most recent header (the 'firsttrusted'), that data can be trusted.
-See the Wiki page at C<http://wiki.apache.org/spamassassin/TrustedRelays>
+See the Wiki page at C<https://wiki.apache.org/spamassassin/TrustedRelays>
 for more information on this.
 
 =item Selecting just the last external IP

Modified: spamassassin/trunk/lib/Mail/SpamAssassin/Plugin.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin/Plugin.pm?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/trunk/lib/Mail/SpamAssassin/Plugin.pm (original)
+++ spamassassin/trunk/lib/Mail/SpamAssassin/Plugin.pm Sun Apr  3 09:39:09 2022
@@ -911,7 +911,7 @@ only spamd calls this API.
 =item result
 
 The C<'result: ...'> line for this scan.  Format is as described
-at B<http://wiki.apache.org/spamassassin/SpamdSyslogFormat>.
+at B<https://wiki.apache.org/spamassassin/SpamdSyslogFormat>.
 
 =back
 
@@ -1255,8 +1255,8 @@ Mail::SpamAssassin(3)
 
 Mail::SpamAssassin::PerMsgStatus(3)
 
-http://wiki.apache.org/spamassassin/PluginWritingTips
+https://wiki.apache.org/spamassassin/PluginWritingTips
 
-http://issues.apache.org/SpamAssassin/show_bug.cgi?id=2163
+https://issues.apache.org/SpamAssassin/show_bug.cgi?id=2163
 
 =cut

Modified: spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/Shortcircuit.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/Shortcircuit.pm?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/Shortcircuit.pm (original)
+++ spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/Shortcircuit.pm Sun Apr  3 09:39:09 2022
@@ -308,6 +308,6 @@ sub compile_now_finish {
 
 =head1 SEE ALSO
 
-C<http://issues.apache.org/SpamAssassin/show_bug.cgi?id=3109>
+C<https://issues.apache.org/SpamAssassin/show_bug.cgi?id=3109>
 
 =cut

Modified: spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/SpamCop.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/SpamCop.pm?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/SpamCop.pm (original)
+++ spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/SpamCop.pm Sun Apr  3 09:39:09 2022
@@ -35,7 +35,7 @@ SpamAssassin as a DNSBL.
 Note that spam reports sent by this plugin to SpamCop each include the
 entire spam message.
 
-See http://www.spamcop.net/ for more information about SpamCop.
+See https://www.spamcop.net/ for more information about SpamCop.
 
 =cut
 
@@ -114,7 +114,7 @@ guess will be used as the From: address
 =item spamcop_to_address user@example.com   (default: generic reporting address)
 
 Your customized SpamCop report submission address.  You need to obtain
-this address by registering at C<http://www.spamcop.net/>.  If this is
+this address by registering at C<https://www.spamcop.net/>.  If this is
 not set, SpamCop reports will go to a generic reporting address for
 SpamAssassin users and your reports will probably have less weight in
 the SpamCop system.

Modified: spamassassin/trunk/lib/spamassassin-run.pod
URL: http://svn.apache.org/viewvc/spamassassin/trunk/lib/spamassassin-run.pod?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/trunk/lib/spamassassin-run.pod (original)
+++ spamassassin/trunk/lib/spamassassin-run.pod Sun Apr  3 09:39:09 2022
@@ -123,8 +123,8 @@ Report this message as manually-verified
 message read from STDIN to various spam-blocker databases.  Currently,
 these are the Distributed Checksum Clearinghouse
 C<https://www.dcc-servers.net/dcc/>, Pyzor
-C<http://pyzor.org/>, Vipul's Razor
-C<http://razor.sourceforge.net/>, and SpamCop C<http://www.spamcop.net/>.
+C<https://www.pyzor.org/>, Vipul's Razor
+C<http://razor.sourceforge.net/>, and SpamCop C<https://www.spamcop.net/>.
 
 If the message contains SpamAssassin markup, the markup will be stripped
 out automatically before submission.  The support modules for DCC, Pyzor,
@@ -287,7 +287,7 @@ circumstances are available with an area
 For more information about which areas (also known as channels) are available,
 please see the documentation at:
 
-	L<http://wiki.apache.org/spamassassin/DebugChannels>
+	L<https://wiki.apache.org/spamassassin/DebugChannels>
 
 =item B<-x>, B<--nocreate-prefs>
 
@@ -302,7 +302,7 @@ Unix message folder format.
 
 Specify that the input message(s) are in UW .mbx format.  mbx is
 the mailbox format used within the University of Washington's IMAP
-implementation; see C<http://www.washington.edu/imap/>.
+implementation; see C<https://en.wikipedia.org/wiki/UW_IMAP>.
 
 =back
 
@@ -320,7 +320,7 @@ C<Mail::SpamAssassin>
 
 =head1 BUGS
 
-See <http://issues.apache.org/SpamAssassin/>
+See <https://issues.apache.org/SpamAssassin/>
 
 =head1 AUTHORS
 

Modified: spamassassin/trunk/sa-compile.raw
URL: http://svn.apache.org/viewvc/spamassassin/trunk/sa-compile.raw?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/trunk/sa-compile.raw (original)
+++ spamassassin/trunk/sa-compile.raw Sun Apr  3 09:39:09 2022
@@ -700,7 +700,7 @@ C<re2c> can match strings much faster th
 match many simple strings in parallel, and compiling that to native object
 code.  Not all SpamAssassin rules are amenable to this conversion, however.
 
-This requires C<re2c> (see C<http://re2c.org/>), and the C
+This requires C<re2c> (see C<https://re2c.org/>), and the C
 compiler used to build Perl XS modules, be installed.
 
 Note that running this, and creating a compiled ruleset, will have no
@@ -777,7 +777,7 @@ I<area> is the area of the code to instr
 
 For more information about which areas (also known as channels) are
 available, please see the documentation at
-L<http://wiki.apache.org/spamassassin/DebugChannels>.
+L<https://wiki.apache.org/spamassassin/DebugChannels>.
 
 =item B<-h>, B<--help>
 
@@ -803,7 +803,7 @@ C<Mail::SpamAssassin::Plugin::Rule2XSBod
 
 =head1 BUGS
 
-See <http://issues.apache.org/SpamAssassin/>
+See <https://issues.apache.org/SpamAssassin/>
 
 =head1 AUTHORS
 

Modified: spamassassin/trunk/sa-learn.raw
URL: http://svn.apache.org/viewvc/spamassassin/trunk/sa-learn.raw?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/trunk/sa-learn.raw (original)
+++ spamassassin/trunk/sa-learn.raw Sun Apr  3 09:39:09 2022
@@ -846,7 +846,7 @@ diagnostic output on bayes, learn, and d
 For more information about which areas (also known as channels) are available,
 please see the documentation at:
 
-        C<http://wiki.apache.org/spamassassin/DebugChannels>
+        C<https://wiki.apache.org/spamassassin/DebugChannels>
 
 Higher priority informational messages that are suitable for logging in normal
 circumstances are available with an area of "info".

Modified: spamassassin/trunk/sa-update.raw
URL: http://svn.apache.org/viewvc/spamassassin/trunk/sa-update.raw?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/trunk/sa-update.raw (original)
+++ spamassassin/trunk/sa-update.raw Sun Apr  3 09:39:09 2022
@@ -2223,7 +2223,7 @@ diagnostic output on channel, gpg, and h
 
 For more information about which areas (also known as channels) are
 available, please see the documentation at
-L<http://wiki.apache.org/spamassassin/DebugChannels>.
+L<https://wiki.apache.org/spamassassin/DebugChannels>.
 
 =item B<-h>, B<--help>
 
@@ -2260,7 +2260,7 @@ Mail::SpamAssassin(3)
 Mail::SpamAssassin::Conf(3)
 spamassassin(1)
 spamd(1)
-<http://wiki.apache.org/spamassassin/RuleUpdates>
+<https://wiki.apache.org/spamassassin/RuleUpdates>
 
 =head1 PREREQUISITES
 
@@ -2268,7 +2268,7 @@ C<Mail::SpamAssassin>
 
 =head1 BUGS
 
-See <http://issues.apache.org/SpamAssassin/>
+See <https://issues.apache.org/SpamAssassin/>
 
 =head1 AUTHORS
 

Modified: spamassassin/trunk/spamd-apache2/README.apache
URL: http://svn.apache.org/viewvc/spamassassin/trunk/spamd-apache2/README.apache?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/trunk/spamd-apache2/README.apache (original)
+++ spamassassin/trunk/spamd-apache2/README.apache Sun Apr  3 09:39:09 2022
@@ -46,7 +46,7 @@ available separately on CPAN.
 
 BUGS
   
-See <http://issues.apache.org/SpamAssassin/> to report a bug.
+See <https://issues.apache.org/SpamAssassin/> to report a bug.
 
 Please include perl, Apache and mod_perl versions. 
 

Modified: spamassassin/trunk/spamd/README
URL: http://svn.apache.org/viewvc/spamassassin/trunk/spamd/README?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/trunk/spamd/README (original)
+++ spamassassin/trunk/spamd/README Sun Apr  3 09:39:09 2022
@@ -112,7 +112,7 @@ you will need to either
 
   2. Alternatively, let the users train their individual Bayes database.
 
-http://wiki.apache.org/spamassassin/SiteWideBayesFeedback can be very
+https://wiki.apache.org/spamassassin/SiteWideBayesFeedback can be very
 helpful here.
 
 We have implemented an auto-learning algorithm (option 'bayes_auto_learn', on
@@ -194,7 +194,7 @@ There are no known bugs with this setup.
 are now running it on their production mail systems.  However, you should
 still test it completely in *your environment* before trusting all your
 mail to it.  If you discover compilation, runtime, or load-performance
-bugs, please open a ticket at http://issues.apache.org/SpamAssassin/
+bugs, please open a ticket at https://issues.apache.org/SpamAssassin/
 
 There is an issue if you run spamd using the standard perl installation
 on Mac OS X and certain *BSD-flavored UNIX platforms.  spamd will change

Modified: spamassassin/trunk/spamd/spamd.raw
URL: http://svn.apache.org/viewvc/spamassassin/trunk/spamd/spamd.raw?rev=1899531&r1=1899530&r2=1899531&view=diff
==============================================================================
--- spamassassin/trunk/spamd/spamd.raw (original)
+++ spamassassin/trunk/spamd/spamd.raw Sun Apr  3 09:39:09 2022
@@ -3620,7 +3620,7 @@ circumstances are available with an area
 For more information about which areas (also known as channels) are available,
 please see the documentation at:
 
-	C<http://wiki.apache.org/spamassassin/DebugChannels>
+	C<https://wiki.apache.org/spamassassin/DebugChannels>
 
 =item B<-4>, B<--ipv4only>, B<--ipv4-only>, B<--ipv4>