[Bug 290347] mail/fetchmail: update to 6.5.7

From: <bugzilla-noreply_at_freebsd.org>
Date: Sat, 18 Oct 2025 14:16:12 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290347

            Bug ID: 290347
           Summary: mail/fetchmail: update to 6.5.7
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
               URL: https://gitlab.com/fetchmail/fetchmail/-/releases#fetc
                    hmail-657-released-2025-10-18-32215-loc
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: mandree@FreeBSD.org
                CC: chalpin@cs.wisc.edu
                CC: chalpin@cs.wisc.edu
             Flags: maintainer-feedback?(chalpin@cs.wisc.edu)
 Attachment #264690 maintainer-approval?(chalpin@cs.wisc.edu)
             Flags:

Created attachment 264690
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=264690&action=edit
fetchmail update to 6.5.7 (patch for git am)

Author: Matthias Andree <mandree@FreeBSD.org>
Date:   Sat Oct 18 16:12:19 2025 +0200

    mail/fetchmail: update to 6.5.7

    Adds Italian translation, which was revived by Luca Vercelli (thanks!)

    Changelog:     
https://gitlab.com/fetchmail/fetchmail/-/releases#fetchmail-657-released-2025-10-18-32215-loc
    PR:             TBC
    MFH:            2025Q4
    Approved by:    (pending)
-------------------------------------------------------------------------------
fetchmail-6.5.7 (released 2025-10-18, 32215 LoC):

## BUGFIXES:
* When authenticating to an SMTP server, the AUTH LOGIN method (which didn't
  become a proposed standard, and is only the third method fetchmail would try,
  if CRAM-MD5 and PLAIN weren't offered) required that the server returned
  a 334 code followed by a blank and by a decodable base64 challenge we ignored
  anyways.  This is in line with RFC 4952.
    However, to improve compatibility, fetchmail now accepts anything that
  starts with "334 " and disregards the remainder of the line.
  At the same time, AUTH LOGIN was deprecated. AUTH PLAIN should be available
  everywhere AUTH LOGIN is, and is specified in IETF RFC 4616.
* When authenticating to an SMTP server, i. e. esmtpname/esmtppassword are
  defined, check for errors, and skip servers that do not understand EHLO,
  because we cannot negotiate supported authentication schemes with them.
  This should avoid attempting to send a lot of messages and see them rejected.
* When authenticating to an SMTP server, do not send client abort "*" when
  we receive any other server reply but 334.
* Extend 6.5.6's RFC-5321 address-literal fix to MAIL FROM. This might
  apply when we only have a server's IP address and need to quality
  addresses without domain. Fixes Debian Bug#1080025.
* SMTP AUTH can now look up passwords from the .netrc file - for that,
  fetchmail's esmtpname setting must match the login for the given host in
  .netrc. Fixes Debian Bug#1056651 by Ticker Berkin.
* Improve the GSSAPI (Kerberos V) build, which was pretty hard to get working.
  This was improved. Recommendation:
  - For autoconf builds (./configure), be sure to have the desired krb5-config
  executable early on $PATH before running ./configure.
  - For meson builds, be sure to list the path to your krb5-gssapi.pc file on
  PKG_CONFIG_PATH.  (meson will fall back to krb5-config, so if that's on PATH,
  that should also work.)

## TRANSLATION UPDATES were contributed by these fine people - thank you!
* The Italian translation is back - it had been missing from earlier 6.5.X
  since it had fallen too far behind with the last update in 2010.
* cs:    Petr Pisar [Czech]
* eo:    Keith Bowes [Esperanto]
* es:    Cristian Othón Martínez Vera [Spanish]
* fr:    Frédéric Marchal [French]
* it:    Luca Vercelli [Italian]
* ja:    Takeshi Hamasaki [Japanese]
* pl:    Jakub Bogusz [Polish]
* ro:    Remus-Gabriel Chelu [Romanian]
* sq:    Besnik Bleta [Albanian]
* sv:    Göran Uddeborg [Swedish]

-------------------------------------------------------------------------------

-- 
You are receiving this mail because:
You are the assignee for the bug.