FreeBSD port ja-p5-Mail-SpamAssassin needs adoption
FreeBSD is committed to keeping the most up to date, current versions of all major software packages and utilities. We need your help in doing this. Any FreeBSD users, with ports experience, who use the Japanese version of SpamAssassin: We need someone to adopt that port, move it to a slave port of mail/p5-Mail-SpamAssassin. Work with that maintainer (me) so that all new updates cascade down to the Japanese version. All you need to so is make sure the ja-* specific parts are up to date since the master port will keep the ja-* port automagically up to date with generic SA code. If you want this port, see the information in FreeBSD porters handbook, and do what it asks. (if you don't know, and can't find the information, you might not want to do this). Mention in your submission that you are working with the portmaintainer of mail/p5-Mail-SpamAssassin (me: use email address reference: scheid...@freebsd.org) -- Michael Scheidell, CTO o: 561-999-5000 d: 561-948-2259 *| *SECNAP Network Security Corporation * Best Mobile Solutions Product of 2011 * Best Intrusion Prevention Product * Hot Company Finalist 2011 * Best Email Security Product * Certified SNORT Integrator __ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.spammertrap.com/ __
Freebsd Port for SpamAssassin 3.3.2 posted
Official port for SpamAssassin 3.3.2 posted. Freebsd users can update their ports tree and upgrade to the current 3.3.2 version of SpamAssassin. All current Freebsd versions are supported. If you have any problems with Freebsd portions of the port, please open a pr so we can track it. If you loaded the pre-official port from our web site, you are advised to install the official port. Remember that SA does not come with current rules, so while installing the port you must run sa-update, or you must run sa-update after you install the port. Happy Hunting! -- Michael Scheidell, CTO o: 561-999-5000 d: 561-948-2259 *| *SECNAP Network Security Corporation * Best Mobile Solutions Product of 2011 * Best Intrusion Prevention Product * Hot Company Finalist 2011 * Best Email Security Product * Certified SNORT Integrator __ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.secnap.com/products/spammertrap/ __
FreeBSD port for SA 331
Not officially released yet, so consider this RC quality. ports committers always make minor changes before committing the port update. http://www.freebsd.org/cgi/query-pr.cgi?pr=144911 it incorporates the DKIM.pm patch to add back in unwhitelist_dkim the pkg-install will try to ask you to install sa rules via sa-update, if possible. any problems or comments, please open a Freebsd PR at www.freebsd.org/support -- Michael Scheidell, CTO Phone: 561-999-5000, x 1259 *| *SECNAP Network Security Corporation * Certified SNORT Integrator * 2008-9 Hot Company Award Winner, World Executive Alliance * Five-Star Partner Program 2009, VARBusiness * Best Anti-Spam Product 2008, Network Products Guide * King of Spam Filters, SC Magazine 2008 __ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.secnap.com/products/spammertrap/ __
Re: SA 3.30 FreeBSD port ready for testing
The updated onever seems to be there few days after the original submission: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/143654 http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/143654 LuKreme wrote: On 5-Feb-2010, at 08:38, Michael Scheidell wrote: I have uploaded the patch files for the SA 3.30 FreeBsd port. It has been tested on 7.1 amd64 and i386. What's the status? Looks to me like the port was pulled at your request? http://www.freebsd.org/cgi/query-pr.cgi?pr=143582 -- View this message in context: http://old.nabble.com/SA-3.30-FreeBSD-port-ready-for-testing-tp27469547p27518020.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: SA 3.30 FreeBSD port ready for testing
On 5-Feb-2010, at 08:38, Michael Scheidell wrote: I have uploaded the patch files for the SA 3.30 FreeBsd port. It has been tested on 7.1 amd64 and i386. What's the status? Looks to me like the port was pulled at your request? http://www.freebsd.org/cgi/query-pr.cgi?pr=143582
SA 3.30 FreeBSD port ready for testing
I have uploaded the patch files for the SA 3.30 FreeBsd port. It has been tested on 7.1 amd64 and i386. http://www.freebsd.org/cgi/query-pr.cgi?pr=143582 Category: ports Responsible:freebsd-ports-bugs Synopsis: MAINTAINER UPDATE mail/p5-Mail-SpamAssassin update to 3.3.0 Arrival-Date: Fri Feb 05 15:30:04 UTC 2010 Anyone wishing to get an early start: KEEP IN MIND, the ports committees may make minor (or major) modifications to the port prior to releasing it. If you put this early version on, you may need to force an upgrade later. Please report any SA specific problems to SA users list. Any FreeBsd problems, please open a FreeBSD PR. Emails to me about any specific problems might be lost. -- Michael Scheidell, CTO Phone: 561-999-5000, x 1259 *| *SECNAP Network Security Corporation * Certified SNORT Integrator * 2008-9 Hot Company Award Winner, World Executive Alliance * Five-Star Partner Program 2009, VARBusiness * Best Anti-Spam Product 2008, Network Products Guide * King of Spam Filters, SC Magazine 2008 __ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.secnap.com/products/spammertrap/ __
RC1 for Freebsd port of 3.30.
I am the official Freebsd ports maintainer for SA. I have RC1 of the Freebsd port ready for testing. post request here. note: everything is up for changing as I test. looks like it installs on 7.1, amd64, perl 5.8.9. Looking to test perl 5.8.8, 5.10.0, threaded perl 5.10.0, i386, 7.2 and freebsd 6.4 -- Michael Scheidell, CTO Phone: 561-999-5000, x 1259 *| *SECNAP Network Security Corporation * Certified SNORT Integrator * 2008-9 Hot Company Award Winner, World Executive Alliance * Five-Star Partner Program 2009, VARBusiness * Best Anti-Spam Product 2008, Network Products Guide * King of Spam Filters, SC Magazine 2008 __ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.secnap.com/products/spammertrap/ __
Freebsd port p5-Mail-DKIM to .30.1
Amavisd-new (2.6rc) needs Mail::DKIM .30.1. for outbound signing, and even for SpamAssassin, this version fixes some issues with some gmail and yahoo email, and also has some significant performance increases. I have tested it with the Freebsd SpamAssassin port, and it does seem to decrease scan times when looking at debug times. The Freebsd port system has the p5-Mail-DKIM port upgraded to .30.1 now, and all Freebsd SpamAssassin users are encouraged to upgrade. The following commands will update your ports system and p5-Mail-DKIM port. #portsnap fetch update #portupgrade p5-Mail-DKIM If you are running spamd or amavisd-new, you may with to restart those programs. -- Michael Scheidell, CTO Main: 561-999-5000, Office: 561-939-7259 *| *SECNAP Network Security Corporation Winner 2008 Technosium hot company award. www.technosium.com/hotcompanies/ http://www.technosium.com/hotcompanies/ Official port maintainer, FreeBSD SpamAssassin port. _ This email has been scanned and certified safe by SpammerTrap(tm). For Information please see http://www.spammertrap.com _
Re: Freebsd Port of SA 3.2.1
(now if we could decide how to fix/check umask. No real way of knowing if it's a install/reinstall, Only flag is during portupgrade I think. I see, I thought the ports Makefile explicitly makes these directories if missing, but now I see the perl makefile does it: ... Installing /usr/local/bin/spamd Installing /usr/local/bin/sa-update Writing /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/Mail/SpamAssassin/.packlist /usr/local/bin/perl5.8.8 -MExtUtils::Command -e mkpath /usr/local/etc/mail/spamassassin And the ExtUtils::Command::mkpath (by calling File::Path) just applies the current umask when creating directories. There exists a ExtUtils::Command::chmod, although perhaps it would not be appropriate to use it, in case directories existed from before. I noticed the ports install _does_ issue a warning: === Warning: your umask is 0027. If this is not desired, set it to an appropriate value and install this port again by ``make reinstall''. So perhaps this suffices (for somebody actually reading it :), especially if my http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5507 gets accepted to facilitate port-festum troubleshooting. Mark
Re: [AMaViS-user] Freebsd Port of SA 3.2.1
Hi It works fine on several Freebsd 5.x i386 machines. sa-compile works too. No problem so far after a few million scans. Thank you. I will try your updated version for amd64 at the end of this week. Regards, Thomas Michael Scheidell wrote: If anyone wants a 'pre release' of the Freebsd sa 3.2.1 portfile, you can download it here: http://www.secnap.com/downloads/sa321.tgz Instructions: rm everything in /usr/ports/mail/p5-Mail-SpamAssassin, untar above there, make or portupgrade it. Some dependencies that have not been committed to freebsd ports are also needed. One I just stumbled upon, for anyone using Mail::SPF: in SA INSTALL doc: If using Mail::SPF note that NetAddr::IP (required by Mail::SPF) versions up to and including version 4.006 include a bug that will slow down the entire perl interpreter. NetAddr::IP version 4.007 or later fixes this. (freebsd ports still has 4.004, but here are patches against ../ports/net-mgmt/p5-NetAddr-IP) You need these patches in /usr/ports/net-mgmt/p5-NetAddr-IP http://www.secnap.com/downloads/netaddrip.patch See http://www.freebsd.org/cgi/query-pr.cgi?pr=113638 Also, you need patches for re2c =.12.0 (ports has .11.1), Razor 2.8.2_1 (ports has 2.8.2) http://www.secnap.com/downloads/re2c.tgz (ports package, clean out ../ports/devel/re2c and untar this) See: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/112501 If you use Razor, you should update it: http://www.secnap.com/downloads/razor.patch (patches against ../ports/mail/razor-agents) see http://www.freebsd.org/cgi/query-pr.cgi?pr=112522 Anyone with freebsd and want to see something (universal!, not site specific), send me an explaination of what it is, what it does, and if you include that and patches against the current 3.2.0, it will likely be included in freebsd 3.2.1 port since I am the official ports maintainer. (note: thanks jimmy I have included the libspamc* support as you requested in http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/106441 -- UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity. Dennis Ritchie
Re: Freebsd Port of SA 3.2.1
At 10:47 PM 6.12.2007 -0400, Michael Scheidell wrote: If anyone wants a 'pre release' of the Freebsd sa 3.2.1 portfile, you can download it here: http://www.secnap.com/downloads/sa321.tgz Instructions: rm everything in /usr/ports/mail/p5-Mail-SpamAssassin, untar above there, make or portupgrade it. Some dependencies that have not been committed to freebsd ports are also needed. One I just stumbled upon, for anyone using Mail::SPF: in SA INSTALL doc: If using Mail::SPF note that NetAddr::IP (required by Mail::SPF) versions up to and including version 4.006 include a bug that will slow down the entire perl interpreter. NetAddr::IP version 4.007 or later fixes this. (freebsd ports still has 4.004, but here are patches against ../ports/net-mgmt/p5-NetAddr-IP) You need these patches in /usr/ports/net-mgmt/p5-NetAddr-IP http://www.secnap.com/downloads/netaddrip.patch See http://www.freebsd.org/cgi/query-pr.cgi?pr=113638 Also, you need patches for re2c =.12.0 (ports has .11.1), Razor 2.8.2_1 (ports has 2.8.2) http://www.secnap.com/downloads/re2c.tgz (ports package, clean out ../ports/devel/re2c and untar this) See: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/112501 If you use Razor, you should update it: http://www.secnap.com/downloads/razor.patch (patches against ../ports/mail/razor-agents) see http://www.freebsd.org/cgi/query-pr.cgi?pr=112522 Anyone with freebsd and want to see something (universal!, not site specific), send me an explaination of what it is, what it does, and if you include that and patches against the current 3.2.0, it will likely be included in freebsd 3.2.1 port since I am the official ports maintainer. (note: thanks jimmy I have included the libspamc* support as you requested in http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/106441 -- Michael Scheidell, CTO SECNAP Network Security Corporation Keep up to date with latest information on IT security: Real time security alerts: http://www.secnap.com/news Michael: Many thanks for your upgrade to the port. I am using FBSD-6.2 amd64 and ran into this problem when running make: bunch of other stuff all okay stopped here: Manifying blib/man3/Mail::SpamAssassin::Plugin::RelayCountry.3 make -f spamc/Makefile spamc/libspamc.so gcc -Wl,-R/usr/local/lib/perl5/5.8.8/mach/CORE spamc/libspamc.c spamc/utils.c -o spamc/libspamc.so -shared -L/usr/local/lib -lz /usr/bin/ld: /var/tmp//cchaPM1S.o: relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC /var/tmp//cchaPM1S.o: could not read symbols: Bad value *** Error code 1 (^_^) Happy trails, Jack L. Stone System Admin Sage-american
Re: Freebsd Port of SA 3.2.1
Jack L. Stone wrote:
At 10:47 PM 6.12.2007 -0400, Michael Scheidell wrote:
If anyone wants a 'pre release' of the Freebsd sa 3.2.1 portfile, you
can download it here:
http://www.secnap.com/downloads/sa321.tgz
Instructions: rm everything in /usr/ports/mail/p5-Mail-SpamAssassin,
untar above there, make or portupgrade it.
Some dependencies that have not been committed to freebsd ports are also
needed.
One I just stumbled upon, for anyone using Mail::SPF: in SA INSTALL
doc:
If using Mail::SPF note that NetAddr::IP (required by Mail::SPF)
versions up to and including version 4.006 include a bug that will
slow down the entire perl interpreter. NetAddr::IP version 4.007 or
later fixes this.
(freebsd ports still has 4.004, but here are patches against
../ports/net-mgmt/p5-NetAddr-IP)
You need these patches in /usr/ports/net-mgmt/p5-NetAddr-IP
http://www.secnap.com/downloads/netaddrip.patch
See http://www.freebsd.org/cgi/query-pr.cgi?pr=113638
Also, you need patches for re2c =.12.0 (ports has .11.1), Razor
2.8.2_1 (ports has 2.8.2)
http://www.secnap.com/downloads/re2c.tgz (ports package, clean out
../ports/devel/re2c and untar this)
See: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/112501
If you use Razor, you should update it:
http://www.secnap.com/downloads/razor.patch (patches against
../ports/mail/razor-agents)
see http://www.freebsd.org/cgi/query-pr.cgi?pr=112522
Anyone with freebsd and want to see something (universal!, not site
specific), send me an explaination of what it is, what it does, and if
you include that and patches against the current 3.2.0, it will likely
be included in freebsd 3.2.1 port since I am the official ports
maintainer.
(note: thanks jimmy I have included the libspamc* support as you
requested in
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/106441
--
Michael Scheidell, CTO
SECNAP Network Security Corporation
Keep up to date with latest information on IT security: Real time
security alerts:
http://www.secnap.com/news
Michael: Many thanks for your upgrade to the port.
I am using FBSD-6.2 amd64 and ran into this problem when running make:
bunch of other stuff all okay
stopped here:
Manifying blib/man3/Mail::SpamAssassin::Plugin::RelayCountry.3
make -f spamc/Makefile spamc/libspamc.so
gcc -Wl,-R/usr/local/lib/perl5/5.8.8/mach/CORE spamc/libspamc.c
spamc/utils.c -o spamc/libspamc.so -shared -L/usr/local/lib -lz
/usr/bin/ld: /var/tmp//cchaPM1S.o: relocation R_X86_64_32 can not be used
when making a shared object; recompile with -fPIC
/var/tmp//cchaPM1S.o: could not read symbols: Bad value
*** Error code 1
looks like a 64bit compile error.
what does uname -p show?
Try this patch to Makefile (if you want to mess with compile options, be
my guest).
--- Makefile.orig Tue Jun 12 22:43:19 2007
+++ MakefileWed Jun 13 09:56:03 2007
@@ -230,18 +230,23 @@
.endif
post-build:
+.if ${ARCH} == i386
@(cd ${BUILD_WRKSRC}; ${SETENV} ${MAKE_ENV} ${MAKE}
${MAKE_FLAGS} ${MAKEFILE} ${MAKE_ARGS} spamc/libspamc.so)
.if !defined(WITHOUT_SSL)
@(cd ${BUILD_WRKSRC}; ${SETENV} ${MAKE_ENV} ${MAKE}
${MAKE_FLAGS} ${MAKEFILE} ${MAKE_ARGS} spamc/libsslspamc.so)
.endif
+.endif
pre-install:
@${SH} ${PKGINSTALL} ${PKGNAME} PRE-INSTALL
+.if ${ARCH} == i386
${INSTALL_DATA} ${WRKSRC}/spamc/libspamc.so ${PREFIX}/lib
${INSTALL_DATA} ${WRKSRC}/spamc/libspamc.h ${PREFIX}/include
.if !defined(WITHOUT_SSL)
${INSTALL_DATA} ${WRKSRC}/spamc/libsslspamc.so ${PREFIX}/lib
.endif
+.endif
+
.if ${OSVERSION} 50
@${SED} -i s| /etc/rc.subr| ${PREFIX}/etc/rc.subr|
work/sa-spamd.sh
.endif
(^_^)
Happy trails,
Jack L. Stone
System Admin
Sage-american
_
This email has been scanned and certified safe by SpammerTrap(tm).
For Information please see http://www.spammertrap.com
_
Re: Freebsd Port of SA 3.2.1
Michael,
I am using FBSD-6.2 amd64 and ran into this problem when running make:
bunch of other stuff all okay
stopped here:
Manifying blib/man3/Mail::SpamAssassin::Plugin::RelayCountry.3
make -f spamc/Makefile spamc/libspamc.so
gcc -Wl,-R/usr/local/lib/perl5/5.8.8/mach/CORE spamc/libspamc.c
spamc/utils.c -o spamc/libspamc.so -shared -L/usr/local/lib -lz
/usr/bin/ld: /var/tmp//cchaPM1S.o: relocation R_X86_64_32 can not be used
when making a shared object; recompile with -fPIC
/var/tmp//cchaPM1S.o: could not read symbols: Bad value
looks like a 64bit compile error.
It is not a compile error. Somebody forgot to put a -fPIC option
when compiling code for a shareable library.
It happens to work on i386, but is wrong anyway.
+.if ${ARCH} == i386
...
+.endif
Please don't do that!
Mark
Re: Freebsd Port of SA 3.2.1
I am using FBSD-6.2 amd64 and ran into this problem when running make:
bunch of other stuff all okay
stopped here:
Manifying blib/man3/Mail::SpamAssassin::Plugin::RelayCountry.3
make -f spamc/Makefile spamc/libspamc.so
gcc -Wl,-R/usr/local/lib/perl5/5.8.8/mach/CORE spamc/libspamc.c
spamc/utils.c -o spamc/libspamc.so -shared -L/usr/local/lib -lz
/usr/bin/ld: /var/tmp//cchaPM1S.o: relocation R_X86_64_32 can not be
used when making a shared object; recompile with -fPIC
/var/tmp//cchaPM1S.o: could not read symbols: Bad value
looks like a 64bit compile error.
It is not a compile error. Somebody forgot to put a -fPIC option
when compiling code for a shareable library.
It happens to work on i386, but is wrong anyway.
+.if ${ARCH} == i386
+.endif
Please don't do that!
Both of the following cc commands need option -fPIC in order
to be able to build a shareable library:
gcc -fPIC -Wl,-R/usr/local/lib/perl5/5.8.8/mach/CORE spamc/libspamc.c
spamc/utils.c -o spamc/libspamc.so -shared -L/usr/local/lib -lz
gcc -fPIC -DSPAMC_SSL -Wl,-R/usr/local/lib/perl5/5.8.8/mach/CORE
spamc/libspamc.c spamc/utils.c -o spamc/libsslspamc.so
-shared -L/usr/local/lib -lssl -lcrypto -lz
This way it will build on any architecture, not just on Intel in 32-bit mode.
This seem to be a SpamAssassin issue, and is not specific to FreeBSD ports.
Mark
RE: Freebsd Port of SA 3.2.1
-Original Message-
From: Jack L. Stone [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 13, 2007 9:29 AM
To: Michael Scheidell; [EMAIL PROTECTED]
Cc: users@spamassassin.apache.org; [EMAIL PROTECTED]
Subject: Re: Freebsd Port of SA 3.2.1
At 10:47 PM 6.12.2007 -0400, Michael Scheidell wrote:
If anyone wants a 'pre release' of the Freebsd sa 3.2.1
portfile, you
can download it here:
http://www.secnap.com/downloads/sa321.tgz
I am using FBSD-6.2 amd64 and ran into this problem when running make:
bunch of other stuff all okay
stopped here:
Manifying blib/man3/Mail::SpamAssassin::Plugin::RelayCountry.3
make -f spamc/Makefile spamc/libspamc.so gcc
-Wl,-R/usr/local/lib/perl5/5.8.8/mach/CORE spamc/libspamc.c
spamc/utils.c -o spamc/libspamc.so -shared -L/usr/local/lib -lz
/usr/bin/ld: /var/tmp//cchaPM1S.o: relocation R_X86_64_32 can
not be used when making a shared object; recompile with -fPIC
/var/tmp//cchaPM1S.o: could not read symbols: Bad value
*** Error code 1
Give this a shot:
http://www.secnap.com/downloads/sa321.tgz
I added this to post-build: (mind the wrap)
post-build:
+ @(cd ${BUILD_WRKSRC}/spamc; ${SED} -e '/^CCDLFLAGS/s/-Wl/-DPIC
-fPIC -Wl/' Makefile Makefile.lib)
This based on other makefile with both -DPIC and -fPIC in it, and darn
if I know why spamc/Makefile doesn't have it there.
_
This email has been scanned and certified safe by SpammerTrap(tm).
For Information please see http://www.spammertrap.com
_
Re: Freebsd Port of SA 3.2.1
+.if ${ARCH} == i386
+.endif
Please don't do that!
Both of the following cc commands need option -fPIC in order
to be able to build a shareable library:
gcc -fPIC -Wl,-R/usr/local/lib/perl5/5.8.8/mach/CORE spamc/libspamc.c
spamc/utils.c -o spamc/libspamc.so -shared -L/usr/local/lib -lz
gcc -fPIC -DSPAMC_SSL -Wl,-R/usr/local/lib/perl5/5.8.8/mach/CORE
spamc/libspamc.c spamc/utils.c -o spamc/libsslspamc.so
-shared -L/usr/local/lib -lssl -lcrypto -lz
This way it will build on any architecture, not just on Intel in 32-bit
mode.
This seem to be a SpamAssassin issue, and is not specific to FreeBSD ports.
Now on:
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5515
Mark
Freebsd Port of SA 3.2.1
If anyone wants a 'pre release' of the Freebsd sa 3.2.1 portfile, you can download it here: http://www.secnap.com/downloads/sa321.tgz Instructions: rm everything in /usr/ports/mail/p5-Mail-SpamAssassin, untar above there, make or portupgrade it. Some dependencies that have not been committed to freebsd ports are also needed. One I just stumbled upon, for anyone using Mail::SPF: in SA INSTALL doc: If using Mail::SPF note that NetAddr::IP (required by Mail::SPF) versions up to and including version 4.006 include a bug that will slow down the entire perl interpreter. NetAddr::IP version 4.007 or later fixes this. (freebsd ports still has 4.004, but here are patches against ../ports/net-mgmt/p5-NetAddr-IP) You need these patches in /usr/ports/net-mgmt/p5-NetAddr-IP http://www.secnap.com/downloads/netaddrip.patch See http://www.freebsd.org/cgi/query-pr.cgi?pr=113638 Also, you need patches for re2c =.12.0 (ports has .11.1), Razor 2.8.2_1 (ports has 2.8.2) http://www.secnap.com/downloads/re2c.tgz (ports package, clean out ../ports/devel/re2c and untar this) See: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/112501 If you use Razor, you should update it: http://www.secnap.com/downloads/razor.patch (patches against ../ports/mail/razor-agents) see http://www.freebsd.org/cgi/query-pr.cgi?pr=112522 Anyone with freebsd and want to see something (universal!, not site specific), send me an explaination of what it is, what it does, and if you include that and patches against the current 3.2.0, it will likely be included in freebsd 3.2.1 port since I am the official ports maintainer. (note: thanks jimmy I have included the libspamc* support as you requested in http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/106441 -- Michael Scheidell, CTO SECNAP Network Security Corporation Keep up to date with latest information on IT security: Real time security alerts: http://www.secnap.com/news _ This email has been scanned and certified safe by SpammerTrap(tm). For Information please see http://www.spammertrap.com _
RE: pre-release of SA 3.18_2 Freebsd port
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, April 30, 2007 11:55 AM To: Michael Scheidell Cc: users@spamassassin.apache.org; [EMAIL PROTECTED] Subject: Re: pre-release of SA 3.18_2 Freebsd port Michael Scheidell writes: Fixes several issues: #1, on FreeBSD 6.2: SpamAssassin Bug 5313: spamd error: 'prefork: select returned -1! recovering: Bad file descriptor' http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5313 Patches backported from 3.20rc3 by [EMAIL PROTECTED] by the way, it'd be great if that patch could be attached to the upstream bug report -- we may want to apply it. Keep an eye on bug 5422, also ;) I guess my brain is fried, had to do booth duty at a trade show... That patch came from 3.20 (I think) and is in just released 3.2? Also, I think I am going to skip 3.18. working on 3.2 right now. (sa-compile giving me problems) What is bug 5422 and is in it sa 3.20 released? _ This email has been scanned and certified safe by SpammerTrap(tm). For Information please see http://www.spammertrap.com _
Re: pre-release of SA 3.18_2 Freebsd port
Michael Scheidell writes: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, April 30, 2007 11:55 AM To: Michael Scheidell Cc: users@spamassassin.apache.org; [EMAIL PROTECTED] Subject: Re: pre-release of SA 3.18_2 Freebsd port Michael Scheidell writes: Fixes several issues: #1, on FreeBSD 6.2: SpamAssassin Bug 5313: spamd error: 'prefork: select returned -1! recovering: Bad file descriptor' http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5313 Patches backported from 3.20rc3 by [EMAIL PROTECTED] by the way, it'd be great if that patch could be attached to the upstream bug report -- we may want to apply it. Keep an eye on bug 5422, also ;) I guess my brain is fried, had to do booth duty at a trade show... That patch came from 3.20 (I think) and is in just released 3.2? yep. Also, I think I am going to skip 3.18. working on 3.2 right now. (sa-compile giving me problems) What is bug 5422 and is in it sa 3.20 released? Bug 5422 is the fundamental fix for what bug 5313 works around, I think. it'll be in 3.2.1. --j.
pre-release of SA 3.18_2 Freebsd port
Fixes several issues: #1, on FreeBSD 6.2: SpamAssassin Bug 5313: spamd error: 'prefork: select returned -1! recovering: Bad file descriptor' http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5313 Patches backported from 3.20rc3 by [EMAIL PROTECTED] #2, fix sa-update directory to be consistent with Freebsd structure. (thanks [EMAIL PROTECTED] #3, need minimum versions (for security reasons) of Zlib, HTML-Parser, Archive-Tar, and gnupg (will use 1.47 or 2.x) I am the official port maintainer for SpamAssassin Port on Freebsd, so this will be sent to ports Wednesday if there are no problems. I am especially interested in Freebsd 6.2 users testing spamd. pre-release of port found here: http://www.secnap.com/downloads/sa318_2.tgz Thanks. -- Michael Scheidell, CTO SECNAP Network Security Corp. See us at SecureWorld in Atlanta, May 1-2, In Philadelphia May 16-17. Click here for free or discounted event and seminar tickets: http://www.secnap.com/events _ This email has been scanned and certified safe by SpammerTrap(tm). For Information please see http://www.spammertrap.com _
Re: pre-release of SA 3.18_2 Freebsd port
Michael Scheidell writes: Fixes several issues: #1, on FreeBSD 6.2: SpamAssassin Bug 5313: spamd error: 'prefork: select returned -1! recovering: Bad file descriptor' http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5313 Patches backported from 3.20rc3 by [EMAIL PROTECTED] by the way, it'd be great if that patch could be attached to the upstream bug report -- we may want to apply it. Keep an eye on bug 5422, also ;) --j. #2, fix sa-update directory to be consistent with Freebsd structure. (thanks [EMAIL PROTECTED] #3, need minimum versions (for security reasons) of Zlib, HTML-Parser, Archive-Tar, and gnupg (will use 1.47 or 2.x) I am the official port maintainer for SpamAssassin Port on Freebsd, so this will be sent to ports Wednesday if there are no problems. I am especially interested in Freebsd 6.2 users testing spamd. pre-release of port found here: http://www.secnap.com/downloads/sa318_2.tgz Thanks. -- Michael Scheidell, CTO SECNAP Network Security Corp. See us at SecureWorld in Atlanta, May 1-2, In Philadelphia May 16-17. Click here for free or discounted event and seminar tickets: http://www.secnap.com/events _ This email has been scanned and certified safe by SpammerTrap(tm). For Information please see http://www.spammertrap.com _
Re: FreeBSD port of SpamAssassin 3.0.0 (continued)
On Sun, 26 Sep 2004, Justin Mason wrote: On Sat, Sep 25, 2004 at 01:21:19PM -0400, Dan Mahoney, System Admin wrote: On Sat, 25 Sep 2004, Mathieu Arnold wrote: Does this mean we're going to get/need a port in for the IP::Country::Fast module? I can create it if you like. (I haven't been able to find a useful documentation on creating a port 00 is there one?) A menu-based config (like the one for the mod_php) port would probably be useful as well, to enable things like SSL, and database support. guys -- bear in mind that IP:C:F is an optional module, so I wouldn't worry about it too much. I know, but it should be there for the sake of completeness. I read that the country filters are off by default, how does one turn them on? -Dan --j. +-le 25/09/2004 02:20 -0700, Pat Lashley ?crivait : | --On Saturday, September 25, 2004 08:59:03 +0200 Mathieu Arnold | [EMAIL PROTECTED] wrote: | | +-Le 24/09/2004 18:20 -0700, Pat Lashley a dit : || SA 3.0 should probably be a separate port rather than an update || to the existing SA port; due to the lack of backwards compatability || in the API. For example, it would break the Exim port which by || default includes the ExiScan patches. (The Exim port would still || build; but the SpamAssassin support would fail at run time.) | | I don't think we will keep the old spamassassin. The 2.64 version will be | the only one working with 5.005_03, but well... It's not possible to have | SA3 work with 5.005_03 (believe me, I tried). | So, a few days before committing the SA3 update, I'll send a mail with the | patch I plan to commit to maintainers of ports depending on SA264 for them | to update/patch/whatever. | | That seems like an awfully short transition period. Why not | a separate 3.0 port for a while; with the old one being deprecated? | Then remove the 2.64 port once the dependant ports have been updated | and in the field long enough for some serious testing? I don't want to have a SA3 port, I'm more in favor of a SA264 port designed for perl 5.005_03 as the databases/p5-DBI-137 port. This is still under discussion. -- Mathieu Arnold -- We need another cat. This one's retarded. -Cali, March 8, 2003 (3:43 AM) Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- -- Hey, call me anything you like. I'm Dan to my friends, gushi to my close friends, 'hey, you' to my girlfriend, 'mrrow?' to my cat, and 'why the hell is the router on fire?' to my job. -Dan Mahoney 12/2/02 Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org ---
Re: FreeBSD port of SpamAssassin 3.0.0 (continued)
--On Friday, September 24, 2004 04:37:05 -0400 Dan Mahoney, System Admin [EMAIL PROTECTED] wrote: I've gotten a Makefile mostly tuned for sa3, based on the FreeBSD port makefile for 2.64. I've added most of the dependencies, but FreeBSD doesn't have ports for Net::SMTP or IP::Country::Fast, so those two features can't be auto- installed unless the ports maintainer comes up with them. Net::SMTP is part of the perl 5.8 port. SA 3.0 should probably be a separate port rather than an update to the existing SA port; due to the lack of backwards compatability in the API. For example, it would break the Exim port which by default includes the ExiScan patches. (The Exim port would still build; but the SpamAssassin support would fail at run time.) -Pat
Re: FreeBSD port of SpamAssassin 3.0.0 (continued)
--On Saturday, September 25, 2004 00:21:44 -0400 David Brodbeck [EMAIL PROTECTED] wrote: For example, it would break the Exim port which by default includes the ExiScan patches. (The Exim port would still build; but the SpamAssassin support would fail at run time.) Sure about that? I'm running Exim with Exiscan version 22, built from the port, and it's working fine with SpamAssassin 3.0. Are you using SA via the spam ACL clauses; or do you have it set up as a filter? In the past, ExiScan has had to be updated to adapt to changes to the SpamAssasin output. The last couple of updates have supported both of the most recent 2.x SA versions; but I've seen nothing about 3.0 support. I'm not certain that it won't work; but I wouldn't expect it to. Even if it appears to work, I wouldn't trust it until there's been an announcement on the Exim lists. And, just as a note, the latest ExiScan is 27, for Exim 4.42. -Pat
Re: FreeBSD port of SpamAssassin 3.0.0 (continued)
Pat Lashley wrote: For example, it would break the Exim port which by default includes the ExiScan patches. (The Exim port would still build; but the SpamAssassin support would fail at run time.) Sure about that? I'm running Exim with Exiscan version 22, built from the port, and it's working fine with SpamAssassin 3.0.
Re: FreeBSD port of SpamAssassin 3.0.0 (continued)
+-le 25/09/2004 02:20 -0700, Pat Lashley écrivait : | --On Saturday, September 25, 2004 08:59:03 +0200 Mathieu Arnold | [EMAIL PROTECTED] wrote: | | +-Le 24/09/2004 18:20 -0700, Pat Lashley a dit : || SA 3.0 should probably be a separate port rather than an update || to the existing SA port; due to the lack of backwards compatability || in the API. For example, it would break the Exim port which by || default includes the ExiScan patches. (The Exim port would still || build; but the SpamAssassin support would fail at run time.) | | I don't think we will keep the old spamassassin. The 2.64 version will be | the only one working with 5.005_03, but well... It's not possible to have | SA3 work with 5.005_03 (believe me, I tried). | So, a few days before committing the SA3 update, I'll send a mail with the | patch I plan to commit to maintainers of ports depending on SA264 for them | to update/patch/whatever. | | That seems like an awfully short transition period. Why not | a separate 3.0 port for a while; with the old one being deprecated? | Then remove the 2.64 port once the dependant ports have been updated | and in the field long enough for some serious testing? I don't want to have a SA3 port, I'm more in favor of a SA264 port designed for perl 5.005_03 as the databases/p5-DBI-137 port. This is still under discussion. -- Mathieu Arnold
Re: FreeBSD port of SpamAssassin 3.0.0 (continued)
+-le 25/09/2004 13:21 -0400, Dan Mahoney, System Admin écrivait : | On Sat, 25 Sep 2004, Mathieu Arnold wrote: | | Does this mean we're going to get/need a port in for the IP::Country::Fast | module? I can create it if you like. | | (I haven't been able to find a useful documentation on creating a port 00 | is there one?) I can add it, not a problem, I'll have a look at this on Monday. | A menu-based config (like the one for the mod_php) port would probably be | useful as well, to enable things like SSL, and database support. SSL is the only thing you need to have to get compiled in, so I'll had some kind of WITH_SSL thing. Database support is enabled if you enable it in the config, and if you want to enable it, you're surely already have DBI and the appropriate DBD modules, and I'm not going to add cases for all DBD:: Modules we have in the tree. | -Dan | | +-le 25/09/2004 02:20 -0700, Pat Lashley écrivait : | | --On Saturday, September 25, 2004 08:59:03 +0200 Mathieu Arnold | | [EMAIL PROTECTED] wrote: | | | | +-Le 24/09/2004 18:20 -0700, Pat Lashley a dit : | || SA 3.0 should probably be a separate port rather than an update | || to the existing SA port; due to the lack of backwards compatability | || in the API. For example, it would break the Exim port which by | || default includes the ExiScan patches. (The Exim port would still | || build; but the SpamAssassin support would fail at run time.) | | | | I don't think we will keep the old spamassassin. The 2.64 version will | | be the only one working with 5.005_03, but well... It's not possible to | | have SA3 work with 5.005_03 (believe me, I tried). | | So, a few days before committing the SA3 update, I'll send a mail with | | the patch I plan to commit to maintainers of ports depending on SA264 | | for them to update/patch/whatever. | | | | That seems like an awfully short transition period. Why not | | a separate 3.0 port for a while; with the old one being deprecated? | | Then remove the 2.64 port once the dependant ports have been updated | | and in the field long enough for some serious testing? | | I don't want to have a SA3 port, I'm more in favor of a SA264 port designed | for perl 5.005_03 as the databases/p5-DBI-137 port. This is still under | discussion. | | -- | Mathieu Arnold | | | -- | | We need another cat. This one's retarded. | | -Cali, March 8, 2003 (3:43 AM) | | Dan Mahoney | Techie, Sysadmin, WebGeek | Gushi on efnet/undernet IRC | ICQ: 13735144 AIM: LarpGM | Site: http://www.gushi.org | --- -- Mathieu Arnold
Re: FreeBSD port of SpamAssassin 3.0.0 (continued)
--On Saturday, September 25, 2004 12:47:20 -0400 David Brodbeck [EMAIL PROTECTED] wrote: And, just as a note, the latest ExiScan is 27, for Exim 4.42. Is that in the ports tree yet? I know they've been under a freeze for a while now. Yep, that's the current port versions. -Pat
FreeBSD port
I am working on creating a drop-in replacement for the FreeBSD port, although it is likely the committers will create their own in due time. -Dan -- I want to see how you see. -SK, 6/2/99, 4:30 AM Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org ---
