had both lines:
Author: ...
WWW: ....
So standardize on that, and move them to the end of the file when necessary.
Also fix some more whitespace, and remove more "signature tags" of varying
forms, like -- name, etc.
s/AUTHOR/Author/
A few other various formatting issues
- Name
em@i.l
or variations thereof. While I'm here also fix some whitespace and other
formatting errors, including moving WWW: to the last line in the file.
my ports in the past 3 weeks while ports were broken on any 10.x
machines, which means I'm unable to maintain them. So let people know
that there's no available support for them until things are back to
normal (which also means that anyone with spare time will be able
to fix them without getting approval).
New stuff (from ftp://exim.inode.at/exim/ChangeLogs/NewStuff-4.77):
1. New options for the ratelimit ACL condition: /count= and /unique=.
The /noupdate option has been replaced by a /readonly option.
2. The SMTP transport's protocol option may now be set to "smtps", to
use SSL-on-connect outbound.
3. New variable $av_failed, set true if the AV scanner deferred; ie, when
there is a problem talking to the AV scanner, or the AV scanner running.
4. New expansion conditions, "inlist" and "inlisti", which take simple lists
and check if the search item is a member of the list. This does not
support named lists, but does subject the list part to string expansion.
5. Unless the new EXPAND_LISTMATCH_RHS build option is set when Exim was
built, Exim no longer performs string expansion on the second string of
the match_* expansion conditions: "match_address", "match_domain",
"match_ip" & "match_local_part". Named lists can still be used.
Relevant entries from ChangeLog at
ftp://exim.inode.at/exim/ChangeLogs/ChangeLog-4.77:
TK/01 DKIM Verification: Fix relaxed canon for empty headers w/o
whitespace trailer
TF/02 Fix a couple more cases where we did not log the error message
when unlink() failed. See also change 4.74-TF/03.
TF/03 Make the exiwhat support code safe for signals. Previously
Exim might lock up or crash if it happened to be inside a call
to libc when it got a SIGUSR1 from exiwhat.
The SIGUSR1 handler appends the current process status to the
process log which is later printed by exiwhat. It used to use
the general purpose logging code to do this, but several
functions it calls are not safe for signals.
The new output code in the SIGUSR1 handler is specific to the
process log, and simple enough that it's easy to inspect for
signal safety. Removing some special cases also simplifies the
general logging code. Removing the spurious timestamps from the
process log simplifies exiwhat.
PP/02 Raise smtp_cmd_buffer_size to 16kB.
Bugzilla 879. Patch from Paul Fisher.
PP/07 Make maildir_use_size_file an _expandable_ boolean.
Bugzilla 1089. Patch from Heiko Schlittermann.
PP/08 Handle ${run} returning more data than OS pipe buffer size.
Bugzilla 1131. Patch from Holger Weitz.
PP/09 Handle IPv6 addresses with SPF.
Bugzilla 860. Patch from Wolfgang Breyha.
PP/10 GnuTLS: support TLS 1.2 & 1.1.
Bugzilla 1156.
Use gnutls_certificate_verify_peers2() [patch from Andreas Metzler].
Bugzilla 1095.
PP/12 fix uninitialised greeting string from PP/03 (smtps client
support).
PP/13 shell and compiler warnings fixes for RC1-RC4 changes.
PP/14 fix log_write() format string regression from TF/03.
Bugzilla 1152. Patch from Dmitry Isaikin.
Other changes:
- the patch for XCLIENT was updated to match the latest Exim sources;
- removed already incorporated patch for exiqgrep;
- removed Makefile.options and simplified OPTIONS handling.
PR: ports/161095, ports/161482, ports/157180
you have new email.
It's simple, easy, fairly environment-independent, and "just works" without
tons of (Gnome|KDE|..) dependencies.
WWW: http://code.google.com/p/mailtray/
PR: ports/161114
Submitted by: Martin Tournoij <martin@arp242.net>
Approved by: miwi, wen (mentors implicit)
changing the version. Confirmed by the author via private e-mail.
He said that it's not a good practice and would avoid doing it in
the future.
Reported by: pontyhat (pavmail)
IMAP server to another quickly and safely.
It's smart enough not to copy messages that
already exist on the destination and robust
enough to deal with interruptions caused by
flaky connections or misbehaving servers.
WWW: https://github.com/rgrove/larch
PR: ports/158389
Submitted by: Eric Freeman <freebsdports@chillibear.com>
