patches I used.
Does anyone have an ETA for an official update.
Thank,
Ted Hatfield
PrismNet Ltd.
IO.COM.
--- spamass-milter.cpp 2006-03-23 21:41:36.0 +
+++ spamass-milter.cpp 2010-03-23 16:44:54.570023100 +
@@ -129,9 +129,11 @@ int daemon(int nochdir, int noclose);
static const
On Mon, 10 May 2010, Robert Huff wrote:
Ted Hatfield writes:
spamass-milter-0.3.0_9 appears to be an update to fix the
security vulnerability referenced by CVE-2010-1132.
The current ported version appears to be 0.3.1_9?
Robert Huff
as well as a link to the code that purported to fix the
problem, hoping that you would have a better idea of what else I might
have broken when I "fixed" the problem.
If you require something from me that I can provide please let me know and
I'll do my best to get it to you.
Th
ucate/convice me that I should
make the effort to switch from procmail to maildrop.
I've been using procmail now for 16 years and I'm very happy with it's
performance. Moving to maildrop would be a significant amount of effort
for both me and my users.
Ted Hatfield
__
A quick google search shows
re-alpine
http://sourceforge.net/projects/re-alpine/develop
http://re-alpine.sourceforge.net/
The continuation of the Alpine email client from University of Washington.
Maybe you would like to create a port.
Ted Hatfield
On Mon, 17 Oct 2011, Marco Beishuizen
rd is overworked. If I had the time to move to dovecot/sieve or
maildrop as a local delivery agent I would have done so by now.
Ted Hatfield
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
On Tue, 19 Dec 2017, Matthias Andree wrote:
Am 19.12.2017 um 01:30 schrieb Ted Hatfield:
On Mon, 18 Dec 2017, Matthias Andree wrote:
Am 18.12.2017 um 00:17 schrieb Dave Horsfall:
Doing my regular update, and...
Upgrading procmail from 3.22_9 to 3.22_10...
Good grief; who'
er based upon my experience I am betting that there are a lot of
systems still out there that are still using procmail.
I think if you choose to drop support for procmail you should do as
Kevin suggests and give a warning and a firm date when support will stop.
This will give people a chance
being used by quite a number of people.
I think that as long as someone is willing to patch the software when
vulnerabilities come up we should keep the port available.
Ted Hatfield
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.o
.py file rather
than mm_cfg.py, and the files Defaults.py and Defaults.pyc didn't change
when I did a pkg update.
Since I have DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST set in my mm_cfg.py
file I assume it's safe to reset these variables in the Defaults.py file
but I haven't taken the
10 matches
Mail list logo
