curses.buildlink2.mk. This was wrong because we _really_ do want to
express that we want _n_curses when we include the buildlink2.mk file.
We should have a better way to say that the NetBSD curses doesn't
quite work well enough. In fact, it's far better to depend on ncurses
by default, and exceptionally note when it's okay to use NetBSD curses
for specific packages. We will look into this again in the future.
fix a buffer overflow in mutt's IMAP client code which
was identified by Core Security Technologies, and fixed by Edmund
Grimley Evans. A more detailed advisory will be published by Core
Security.
This happens to close PR pkg/20814, filed while I was updating the package. :-)
have it be automatically included by bsd.pkg.mk if USE_PKGINSTALL is set
to "YES". This enforces the requirement that bsd.pkg.install.mk be
included at the end of a package Makefile. Idea suggested by Julio M.
Merino Vidal <jmmv at menta.net>.
(/etc -> PKG_SYSCONFDIR and /usr/local -> PREFIX). Also remove references
to the mutt_dotlock program and do not install its manpage because it does
not get installed. Bump PKGREVISION to 3.
Approved by tron, the maintainer.
standard directory share/examples/mutt instead of beeing in
share/doc/mutt/samples. Provide a compatibility symlink.
Also avoid direct installation of files under PKG_SYSCONFDIR. Instead
force mutt to install them inside the examples directory and let
bsd.pkg.install.mk copy them to the right place.
Bump PKGREVISION to 2.
Approved by tron (the maintainer) and wiz.
1.2.5.1 include:
- Better mh support: Mutt now supports .mh_sequences files.
Currently, the "unseen", "flagged", and "replied" sequences are
used to store mutt flags (the names are configurable using the
$mh_seq_unseen, $mh_seq_flagged, and $mh_seq_replied configuration
variables). As a side effect, messages in MH folders are no longer
rewritten upon status changes.
- The "trashed" flag is supported for maildir folders. See
$maildir_trash.
- POP folder support. You can now access a POP mailbox just like an
IMAP folder (with obvious restrictions due to the protocol).
- URL syntax for remote folders. You can pass things like
pop://account@host and imap://account@host/folder as arguments for
the -f command line flag.
- STARTTLS support. If $ssl_starttls is set (the default), mutt
will attempt to use STARTTLS on servers advertising that
capability.
- $preconnect. If set, a shell command to be executed if mutt fails
to establish a connection to the server. This is useful for
setting up secure connections; see the muttrc(5) for details.
- $tunnel. Use a pipe to a command instead of a raw socket. See
muttrc(5) for details. (Basically, it's another way for setting
up secure connections.)
- More new IMAP/POP-related variables (see muttrc(5) for details):
$connect_timeout, $imap_authenticators, $imap_delim_chars,
$imap_peek, $pop_authenticators, $pop_auth_try_all,
$pop_checkinterval, $pop_delete, $pop_reconnect, $use_ipv6.
- The following IMAP/POP-related variables are gone:
$imap_checkinterval, $imap_cramkey, $pop_port.
- There's a new imap-fetch-mail function, which forces a check for
new messages on an IMAP server.
- The new-mailbox function was renamed to create-mailbox, and is
bound to C instead of n by default.
For a complete overview of all new features look in the "NEWS" file.
* Honor ${PKG_SYSCONFDIR} for the location of the config files
(Muttrc, mime.types).
* Rearrange lines slightly to minimize differences between mutt/Makefile
and mutt-devel/Makefile to simplify updating mutt when the next release
(1.4?) is released.
buildlink.mk files and mark as USE_BUILDLINK_ONLY. Move sample Muttrc
and mime.types files to ${PREFIX}/share/doc/mutt/samples, and ddd
DEINSTALL/INSTALL scripts to handle copying and removing those files to and
from ${PREFIX}/etc.
first component is now a package name+version/pattern, no more
executable/patchname/whatnot.
While there, introduce BUILD_USES_MSGFMT as shorthand to pull in
devel/gettext unless /usr/bin/msgfmt exists (i.e. on post-1.5 -current).
Patch by Alistair Crooks <agc@netbsd.org>
This release fixes at least one grave IMAP error which may lead to
confusing display and other strangeness, and our instances of the
"wuftpd format bug", which had (mostly) the effect that your IMAP
server's operator could break into your computer with some work.
more. Change since version 1.0.1i:
- heavily improved IMAP support (thanks to Brandon Long
and Brendan Cully for their work),
- support for using IMAP over SSL (thanks to Tommi
Kommulainen),
- a completely changed interface for configuring mutt's
PGP support. It's now format-based, and much more
flexible than it used to be in the past.
- a split of the old edit-message command into
resend-message and edit-message. While the former gives
you what could be described as "recall from arbitrary
folders", the latter can be used to low-level modify
messages.
- the weeding paradigma has changed. Instead of options
controlling weeding behaviour for all kinds of purposes,
there is one global $weed option which is toggled when
you use what used to be known as display-headers (now
display-toggle-weed). That is, you have some kind of
"WYSIWYG" support with weeding.
- we have a muttrc (5) manual page now, and it's even
up-to-date.
- you can better control your messages' header and
envelope from headers
- the message commands on the attachment menu have been
rewritten. Just try replying to an attachment, and
you'll see what happens. ;-)
- mailing list support has changed. You may wish to
rename your "lists" commands to "subscribe". But please
read README.UPGRADE before!
- Bug fixes of all sorts.
This is another version from the release candidate series. The reason
for immediately releasing this version is a buffer overflow in the
text/enriched handler which can be triggered by means of
suitably-formatted e-mail messages. Thus, we recommend you upgrade
your mutt installations immediately.
Against 1.0pre1, there are several build changes (building this
version of mutt with SGI's cc should work), and back-ports of
IMAP-related bug fixes from the unstable branch.
Almost all changes from 0.95.7 concern the build process, which
should work now on those platforms for which problems where reported
with 0.95.7. postfix and qmail users may be interested in the new
$bounce_delivered configuration variable.
- The $in_reply_to configuration variable is gone. The In-Reply-To
header currently only contains the message-id of the message to
which the reply refers. This is to make sure that this header is
correctly formatted.
- Lots of bugs present in 0.95.6 were fixed.
This version fixes several bugs from 0.95.5, including the "erratic
maildir behaviour" which has been with us for quite some time, and
certain IMAP-related problems.
Major changes since 0.95.3:
- Mutt up to version 0.95.3 was affected by a temporary file relateda
race condition which could lead to security-relevant problems.
- We have fixed a bug which would lead to crazy behaviour when a
message was listed in it's own References header.
- IMAP and MIME should mix better now.
