| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
pkgsrc changes:
- Update MASTER_SITES (use https:// and avoid redirects)
- Delete (a bit outdated) comment about locking mechanisms
Since 02 Feb 2014 (post-1.6) the default locking mechanisms are
(directly from m4/locking.m4):
- aix*|cygwin*|linux*: fcntl
- freebsd*|*netbsd*|openbsd*|darwin*: flock
- everything else: dot
The original comment was probably about just NetBSD and maybe Solaris
(it's dated 1999). Solaris still uses the `dot' mechanisms by default
but we no longer have any local patches about locking.
- Delete (no more needed) `-O1' hack to CFLAGS
mh_strcasecmp() was completely replaced by strcasecmp() on 24 Mar 2013, and
hence present in 1.6. Forcing `-O1' for gcc is no longer needed.
- Adjust --sysconfdir CONFIGURE_ARGS per-upstream change, now the nmh
directory is created by nmh's configure so pass PKG_SYSCONFBASE instead of
PKG_SYSCONFDIR.
- Add support for the `test' phase
Add support for nmh tests. Modify patches/patch-ca accordingly in order to
adjust TEST_ENVIRONMENT to use the configuration files in $egdir instead of the
ones in $nmhetcdir.
Actually all tests are passed except an mhparam test that sposts the
$egdir/$nmetcdir kludge.
- Do not include bsd.prefs.mk two times (NFC)
- Add `oauth' PKG_OPTIONS (disabled by default) to enable OAuth2 support in
SMTP and POP auth via curl
Changes:
Release notes for nmh 1.7
=========================
Welcome to nmh, the new version of the classic MH mail handling system.
It's been over three years since the last release of nmh, and there have
been a number of significant changes since the last release. Long-time
MH and nmh uses should read careful the NOTEABLE CHANGES section, as there
are some significant changes to nmh behavior. Otherwise, please see the
README and INSTALL files for help on getting started with nmh.
For news of future releases, subscribe to the low-volume
https://lists.nongnu.org/mailman/listinfo/nmh-announce
---------------
NOTABLE CHANGES
---------------
The largest notable changes in the 1.7 release are:
- Complete unification of network security support. All network protocols
(currently, POP and SMTP) have been refactored to use a common set of
security routines. This means all protocols support all SASL mechanisms
(via the Cyrus-SASL library) and TLS. TLS support has been strengthened
to perform certificate name validation and to require TLS 1.1 as a
minimum protocol. Also, all protocols can make use of the OAuth2/XOAUTH
SASL mechanism, which is supported by Gmail.
- send(1) now supports adding switches to post(8) based on the address or
domain of the email address in the From: header; this more easily allows
users to support multiple identities.
- A generic facility for passing arguments to filter programs in repl(1)
by use of the -convertargs switch.
- Native support for the manipulation of iCalendar requests; see mhical(1)
for more details.
------------
NEW FEATURES
------------
The following are new features for the 1.7 release of nmh:
- When building from source, configure will derive ${prefix} from an existing
nmh installation if it finds one in your $PATH.
- Added welcome message when nmh detects that its version changed.
- The default locations for configuration files and support binaries
have been changed. Configuration files now install into ${sysconfdir}/nmh,
and support binaries are placed in ${libexecdir}/nmh. If you are upgrading
an existing installation you should look for old configuration files in
${sysconfdir} and merge any local customizations into the new files in
${sysconfdir}/nmh, then remove the old files. ${libdir} will also contain
obsolete support programs that should be removed.
- All TLS connections now perform certificate validation (including hostname
matching) by default; can be disabled on a per-application basis.
- post now defaults to port 587 on 'smtp' message submission.
- A value of 0 for the width switch of scan(1), inc(1), ap(1), dp(1),
fmttest(1), and mhl(1) now means as many characters as the format
engine can produce [Bug #15274]. That amount is limited by internal
buffers.
- If a component has trailing whitespace, e.g., body:component="> ",
mhl now trims that whitespace off when filtering blank text lines.
- An "rtrim" flag has been added to mhl to remove any trailing
whitespace from filtered text lines. A corresponding "nortrim" flag
has also been added.
- Added getmymbox and getmyaddr mh-format(5) function escapes.
- New -[no]changecur, -fixtype, -decodetypes, and -[no]crlflinebreaks switches
have been added to mhfixmsg(1).
- mhfixmsg now removes an extraneous trailing semicolon from header
parameter lists.
- Added -convertargs switch to repl(1), to pass arguments to programs
specified in the user's profile or mhn.defaults to convert message
content.
- Added mhical(1), to display, reply to, and cancel iCalendar (RFC 5545)
event requests.
- Added multiply mh-format(5) function.
- "mhparam bindir" prints the path to the directory containing the public
executables (${bindir}).
- New "-prefer" switch for mhshow (and mhlist and mhshow), to allow specifying
the preferred content types to show, if present in a multipart alternative.
- mh-format now has %(kilo) and %(kibi) functions, to allow printing
numbers with SI or IEC quantities, e.g. "10K", "2.3Mi".
- Support for the -sendmail flag to send/post to change the sendmail
binary when using the sendmail/pipe MTS.
- Added support to send(1) to specify switches to post(1) based on address or
domain name in From: header line in message draft.
- post(8) -snoop now attempts to decode base64-encoded SMTP traffic.
- folder(1) -nocreate now prints a warning message for a non-existent folder.
- mhfixmsg(1) now allows -decodetext binary, though 8bit is still the default.
- inc(1) and msgchk(1) now support TLS encryption natively.
- All network protocols support the XOAUTH authentication mechanism.
- Support for SMTPUTF8 (RFC 6531) has been added. mhshow(1) already supported
RFC 6532, assuming all 8-bit message header field bodies are UTF-8 and use
of a UTF-8 locale.
- mhfixmsg now replaces RFC 2047 encoding with RFC 2231 encoding of name and
filename parameters in Content-Type and Content-Disposition headers,
respectively.
- If a message body contains 8-bit bytes, post(8) uses SMTP 8BITMIME if the
server supports it. If not, post fails with a message to the user to
encode the message for 7-bit transport.
- Fewer lseek(2)s will be used when reading headers in the common case.
- ./configure's --enable-debug has been removed; it did nothing.
- configure now defaults to enabling each of TLS and Cyrus SASL if the
necessary headers and libraries are found.
- Moved build_nmh to top-level directory.
- Better error reporting for connections to network services.
---------
BUG FIXES
---------
- The format scanner no longer subtracts 1 from the width. This has the
effect of no longer counting the trailing newline in the output of
scan(1), inc(1), and the other programs that rely on the format scanner.
- The first character of some very short (less than 4 characters) message
bodies is no longer dropped.
- Single-character headers can be reliably formatted, etc., instead of
apparently being missing.
- mhfixmsg now adds a Content-Transfer-Encoding header at the message level,
if needed after decoding text parts.
- mhbuild now checks whether all text parts need a Content-Transfer-Encoding
header, not just those with a character set not specified.
- mhbuild no longer parses lines that start with # as directives with
-nodirectives.
- repl now makes sure that any Fcc header in a replied-to message is not
copied into the outgoing draft by default, and that the -fcc switch
actually works in the absence of a Fcc header in the replied-to message.
- A Content-ID is generated for message/external-body entities as required
by RFC 2045, even if -nocontentid is supplied to mhbuild.
- post will now expand aliases on a "From" line when doing a BCC [Bug #51098].
- scan can now handle empty files without violating an assert [Bug #51693].
- An error when writing an error message, e.g. EPIPE, no longer causes
recursion until the stack is exhausted.
-------------------
DEPRECATED FEATURES
-------------------
- Support for the MHPDEBUG environment variable is deprecated and will be
removed from a future nmh release. Instead, use the -debug switch to pick.
- With the move of support binaries from ${libdir} to ${libexecdir}/nmh, the
mostly undocumented 'libdir' mhparam(1) component has been replaced by a
new 'libexecdir' component. 'libdir' will be removed in a future release.
-----------------
OBSOLETE FEATURES
-----------------
- The undocumented -queue switch to post was deprecated in nmh 1.6, and was
removed in this release.
- conflict(8) was deprecated in nmh 1.6, and was removed in this release.
- mhtest(8) was deprecated in nmh 1.6, and was removed in this release.
- msh(1) was deprecated in nmh 1.6, and was removed in this release.
- Support in alias files for the the "*" address-group (everyone) was
deprecated in nmh 1.6, and was removed in this release.
- Support for multiple hostnames in the "servers" entry of mts.conf has
been removed.
- Support in alias files for expanding aliases based on group membership
(=) and primary group (+) has been removed.
As always, feedback is welcome.
|
|
Contributed by: Leonardo Taccari <iamleot@gmail.com>
Update mail/nmh to 1.6.
Changes:
The biggest changes in this release are in the arena of MIME handling.
Specifically relating to MIME composition and display. On the
composition front, mhbuild(1) will now automatically be run by send(1)
for all drafts. Specifically, mhbuild is now run with the new -auto
flag, which will suppress the processing of mhbuild directives and cause
mhbuild to silently exit if the draft is already MIME-formatted. When
invoking mhbuild manually via the "mime" command at the WhatNow? prompt,
mhbuild will behave as before and process mhbuild directives.
In both cases (automatic and manual invocation) mhbuild will encode email
headers according to RFC-2047 rules. Mhbuild also will use RFC 2231
encoding rules for MIME parameters when appropriate. In addition, the
attach system has been substantially reworked; the new header name is
now "Attach" (to better align with other MUA behavior) and cannot be
changed by the end-user. The existing "attach" command simply adds
the filename(s) to the draft in new Attach: headers, and the actual
file processing is done by mhbuild; this attachment processing will
take place in either automatic or manual mode.
On the display front, mhshow(1) will now automatically convert text
into the user's native character set using iconv, if nmh was built
with iconv support. Also, mhshow will now by default only display
text content that was not marked as an attachment. By default all
displayed content wll be run under one pager, as opposed to individual
pagers for each part as was in the past. Non-displayed parts will be
indicated using a marker string, which can be customized by a new
mh-format(5) string.
All nmh utilites now understand RFC 2231-encoded MIME parameters and
will automatically convert the encoded parameters into the native
character set, when appropriate (again, assuming nmh was built with
iconv support).
In other changes, sequence files are now locked using transactional
locks: locks that are held across sequence file reading, modification,
and writing. The locking algorithm used for spool files and nmh data
files is now runtime configurable.
For people that struggle with mh-format(5) files, a new utility for testing
them has been developed: fmttest(1). It includes the ability to trace the
execution of format instructions.
For users that wish to use Unix utilities on their mail, a new utility
to transform MIME messages to more easily-digestable format is now
available: mhfixmsg(1). It supports a number of options to control
the message transformation.
For users of spost(8), the support for spost has been rolled into post(8)
under a new sendmail/pipe MTS. A shell script emulating the old behavior
of spost has been provided.
|
|
changes:
-a "From:" header is now required for outgoing mail, custom component
files may need to be adjusted
-support for filters in mhl
-more fixes and new features, see the share/doc/nmh/NEWS file for details
-dragonfly support patches were integrated
|
|
|
|
- many bug fixes
- MM_CHARSET no longer needed; now uses iconv to decode RFC2047-encoded
headers and convert to current locale.
- various MIME improvements
- Take maintainership (ok'd by kim@).
- Replace DESCR with text from web site.
- Support user-destdir.
- Use --with-hash-backup instead of hacking config.h post-configure.
- Drop IRIX-specific part of fmt_scan.c patch-cd, and therefore drop patch-ck
and IRIX bits in Makefile.
- A tmac.h conf file (wtf?) is no longer installed.
- Update what's installed to share/doc/nmh.
- Update PLIST for added/removed/renamed files.
- Patches:
- Update patch-ca and patch-cd.
- Remove errno patches, upstream since XXX: patch-aa, patch-ab, patch-ad,
patch-ae, patch-ag, patch-ah, patch-ai, patch-aj, patch-ak, patch-al,
patch-am, patch-an patch-ao, patch-ap, patch-aq, patch-ar, patch-as,
patch-at, patch-au, patch-av, patch-aw, patch-ax, patch-az, patch-ba,
patch-bb, patch-bc, patch-bd, patch-be, patch-bf, patch-bg, patch-bh,
patch-bi
- patch-aa also had a patch for some fgetstr problem on NetBSD which no
longer seems to happen.
- Remove patch-cb; GCOS_HACK is referenced nowhere in nmh code (only
apparently outdated docs) or in any other pkgsrc patch; HAVE_SYS_PARAM_H
is already elsewhere in config.h, and sys/param.h is included in nmh.h.
- Remove patch-ce (http://savannah.nongnu.org/bugs/?1393 fixed in
uip/sortm.c r1.7).
- Remove patch-ci (fixed in uip/show.c r1.6).
- Remove patch-cj; $(etcdir)/tmac.h is gone and the folders/flists problems
were fixed (differently) in 2000.
- Remove patch-ck (CPPFLAGS support for the IRIX-specific part of patch-cd.
|
|
into the examples hierarchy and using bsd.pkg.install.mk to copy them into
place. While here, sort PLIST. Bump PKGREVISION to 6.
Patch from PR pkg/28978 made by Greg A. Woods with very slight modifications
by me.
|
|
|
|
|
|
rmdir -> ${RMDIR}
rm -> ${RM} (${RM} added to PLIST_SUBST)
chmod -> ${CHMOD}
chown -> ${CHOWN}
|
|
|
