[EMAIL PROTECTED] wrote:
In an older episode (Thursday 14 April 2005 00:54), Theo Van Dinter wrote:
In this case, however, it's not clear if he's running something like a
Fedora RPM version of SpamAssassin where he could just go ahead and update
at will, or if it's something like Barracuda/etc, where you really can't
just go changing things on your own. The flip side of that of course is
that you'll have vendor support who you can call and make requests of. ;)
at home, i am running debian linux with SpamAssassin version 3.0.2 running on
Perl version 5.8.4, or as debian puts it:
Installed: 3.0.2-1
Candidate: 3.0.2-1
== nothing newer available in debian.
at work, we do use a vendors' pre-installed SpamAssassin version 3.0.2 running
on Perl version 5.8.5 and Fedora Core release 3 (Heidelberg), rpms built by
the vendor:
spamassassin-3.0.2-1
spamassassin-tools-3.0.2-1
i will have to find out exactly which modifications have been applied to which
source by the vendor. anyway, further modifications are possible both from
the vendor or us, the owners. learning at home how to apply the fix at all
will make it easier to be able to judge / request / apply necessary changes
at work.
Here's the diff:
http://svn.apache.org/viewcvs.cgi/spamassassin/trunk/lib/Mail/SpamAssassin/PerMsgStatus.pm?rev=148873&r1=125891&r2=148873&makepatch=1&diff_format=u
