Log message:
Pullup ticket #5846 - requested by bsiegert
mail/spamassassin: security update

Revisions pulled up:
- mail/spamassassin/Makefile                                    1.132
- mail/spamassassin/distinfo                                    1.72
- mail/spamassassin/patches/patch-Makefile.PL                   1.3
- mail/spamassassin/patches/patch-ae                            1.14
- mail/spamassassin/patches/patch-lib_Mail_SpamAssassin_DnsResolver.pm deleted
- mail/spamassassin/patches/patch-lib_Mail_SpamAssassin_PerMsgStatus.pm deleted
- mail/spamassassin/patches/patch-sa-compile                    deleted
- mail/spamassassin/patches/patch-spamc_libspamc.c              1.2

-------------------------------------------------------------------
   Module Name:    pkgsrc
   Committed By:   bsiegert
   Date:           Thu Oct 18 19:54:32 UTC 2018

   Modified Files:
           pkgsrc/mail/spamassassin: Makefile distinfo
           pkgsrc/mail/spamassassin/patches: patch-Makefile.PL patch-ae
               patch-spamc_libspamc.c
   Removed Files:
           pkgsrc/mail/spamassassin/patches:
               patch-lib_Mail_SpamAssassin_DnsResolver.pm
               patch-lib_Mail_SpamAssassin_PerMsgStatus.pm patch-sa-compile

   Log message:
   Update spamassassin to 3.4.2.

   From Attila Fueloep in pull request NetBSD/pkgsrc#32.

   Apache SpamAssassin 3.4.2 contains numerous tweaks and bug fixes over the
   past three and 1/2 years.  As we release 3.4.2, we are preparing 4.0.0 which
   will move us into a full UTF-8 environment.  We expect one final 3.4.3
   release.

   As with any release there are a number of functional patches, improvements as
   well as security reasons to upgrade to 3.4.2.  In this case we have over 3
   years of issues being resolved at once.  And we are laying thr groundwork for
   version 4.0 which is is designed to more natively handle UTF-8.

   However, there is one specific pressing reason to upgrade.  Specifically, we
   will stop producing SHA-1 signatures for rule updates.  This means that while
   we produce rule updates with the focus on them working for any release from
   v3.3.2 forward, they will start failing SHA-1 validation for sa-update.

   *** If you do not update to 3.4.2, you will be stuck at the last ruleset
       with SHA-1 signatures in the near future. ***

   Full release notes at
   \ 
http://svn.apache.org/repos/asf/spamassassin/branches/3.4/build/announcements/3.4.2.txt.

   To generate a diff of this commit:
   cvs rdiff -u -r1.131 -r1.132 pkgsrc/mail/spamassassin/Makefile
   cvs rdiff -u -r1.71 -r1.72 pkgsrc/mail/spamassassin/distinfo
   cvs rdiff -u -r1.2 -r1.3 pkgsrc/mail/spamassassin/patches/patch-Makefile.PL
   cvs rdiff -u -r1.13 -r1.14 pkgsrc/mail/spamassassin/patches/patch-ae
   cvs rdiff -u -r1.5 -r0 \
       pkgsrc/mail/spamassassin/patches/patch-lib_Mail_SpamAssassin_DnsResolver.pm
   cvs rdiff -u -r1.3 -r0 \
       pkgsrc/mail/spamassassin/patches/patch-lib_Mail_SpamAssassin_PerMsgStatus.pm
   cvs rdiff -u -r1.1 -r0 pkgsrc/mail/spamassassin/patches/patch-sa-compile
   cvs rdiff -u -r1.1 -r1.2 \
       pkgsrc/mail/spamassassin/patches/patch-spamc_libspamc.c