2) In the sample configuration file, allow relaying from the IPv6 and
IPv4 localhost addresses.
This fixes relaying problems for folks using things like IPv6-enabled
mailman.
Bump PORTREVISION accordingly.
Reported by: Alexander Sabourenkov <lxnt@caravan.ru> (1)
Mark Edwards <mark@antsclimbtree.com> (2)
any emails that are received that come from an open relay as
determined by your choice of RBL checking service (i.e. bl.spamcop.net).
This is useful if you'd rather have the mail user agent (MUA) deal with
potential spam rather than just blocking it in case you loose
legitimate messages. Note that the X-RBL-Warning header is only set if
the site was found to be an open-relay.
For more information, see the rbl-milter website at:
WWW: http://opensource.confusticate.com/rbl-milter/
RBL-Milter was created by Jeremy Beker <gothmog@confusticate.com> and
the port is maintained by Ned Wolpert <wolpert@codeheadsystems.com>
PR: 45605
Submitted by: wolpert@codeheadsystems.com
Exchange server. The MS Exchange server gets upset that MessageWall sends
the "250 2.0.0 h1Q0Qc907062 Message accepted for delivery" and the "\r\n"
in different packets. The first patch works around this MS problem.
See http://messagewall.org/cgi-bin/ezmlm-browse.cgi?command=showthread&list=messagewall-discuss&month=200302&threadid=nnoiaogojliciagmgpbk
The other patch changes how MessageWall behaves when there are multiple
recipients to a message. MessageWall accepts the first recipient, but
defers the second with a temporary SMTP error. This can take some time
for all recipients to get the message when the sending side has a long
queue time. MessageWall does this since different recipients of a message
can have different profiles. We, along with a number of sites, use a
single profile for all inbound email. This patch, which must be enabled
when the port is built with -DMESSAGEWALL_ALLOW_MULT_RCPT, allows multiple
recipients, using the profile of the first recipient.
See: http://www.messagewall.org/cgi-bin/ezmlm-browse.cgi?command=showthread&list=messagewall-discuss&month=200303&threadid=lcjcimckfmdphlhpjjhn
PR: ports/50296
Submitted by: Douglas K. Rand <rand@meridian-enviro.com>
Approved by: maintainer timeout (12 days)
The cyrus port takes no steps to insure the deliver databases
are properly pruned. This can be quite easily accomplished
on a daily basis by adding a periodic file to take care of
this. This should be a model for other ports that require
daily/weekly/monthly actions. Why else did we bother to
break up the cron jobs into the /etc/periodic* structure?
PR: ports/26801
Submitted by: Nick Sayer <nsayer@quack.kfu.com>
Update to 2.31
Added IPv6 support, Better performance and scalability on
very busy mail servers, Support for Symantec CarrierScan
Server and F-Risk FPROTD virus-scanners, Documentation
fixes, etc...
PR: ports/50102
Submitted by: Andrey V. Pevnev <andrey@mgul.ac.ru>
SilkyMail is an Internet mail client that runs in your
browser. It can be used by itself, or in conjunction with
an IMAP or POP-capable client as part of a complete set of
messaging tools. (It works very nicely in conjunction with
Mulberry.)
It was designed by internet mail client experts to work in
high-scalability and diverse environments. It's not just
another webmail hack cut of rough cloth -- it's a real mail
program, that can be used by novice users and advanced users
a like, but with the independence of browser access. SilkyMail
is the smoothest mail client in a browser around.
PR: ports/47721
Submitted by: Aaron Voisine <voisine@yahoo.com>
mechanisms for detecting the availability of strcasestr(3) and only uses
autorespond's own strcasestr() version if needed.
NOTE: there is NO functionality change in autorespond-2.0.3 with respect
to 2.0.2.
Updated gotmail to 0.7.9 to get more hotmail spam.
PR: ports/50061
Submitted by: Bjorn Nelson <o_sleep@babbleheaven.com>
Reviewed by: Erwin Lansing <erwin@lansing.dk>
New port. (and my 30st port.. wheeee)
[can somebody give him ports-commit access please? - edwin]
smtprc is fully configurable, multithreaded open mail relay
scanner. It supports scanning of IP blocks, and can print
the results to a web page. It is intended for SysAdmins
to check IP blocks under their control.
PR: ports/48889
Submitted by: Michael L. Hostbaek <mich@freebsdcluster.org>
crashecho is FTN JAM/MSG tosser for a node.
CrashEcho is a successor of a CrashMail II tosser originally
written by Johan Billing.
PR: ports/45468
Submitted by: Cyril Margorin <cyrilm@immo.ru>
These are a collection of subroutines that encapsulate much
of the format-specific and tedious details of the JAM message
base format. The idea is that application programmers by
using these routines can concentrate on the more high-level
issues of their programs instead of worrying about their
JAM routines.
PR: ports/45467
Submitted by: Cyril Margorin <cyrilm@immo.ru>
This is a maintenance release, but there are a few edge cases where
backward compatibikity in the configure file was broken.
While upgrading is recommended, administrators are encouraged to
Update exim-4.12 -> exim-4.14:
This is a maintenance release, but there are a few edge cases where
backward compatibikity in the configure file was broken.
While upgrading is recommended, administrators are encouraged to
examine the README.UPDATING file in the distribution.
* Catch up to changes in the ports tree with respect to available
OpenLDAP releases. While backward compatibility is preserved,
administrators may use WITH_OPENLDAP1, WITH_OPENLDAP20 and
WITH_OPENLDAP21 for more fine-grained control of the OpenLDAP
release on which to depend.
Submitted by: Oliver Eikemeier <eikemeier@fillmore-labs.com>
