New exim and SpamAssassin

You upgraded exim.pl, not Exim itself. Spamassassin would not be listed in exim.pl, it is listed in exim.conf

Also if you are running custombuild 2.0, Spamassassin is included automatically in exim.conf with this line:

Code: 
.include_if_exists /etc/exim.spamassassin.conf
 
@ditto:

Quick question: Do you know how custombuild 2 manages my SpamBlocker file, which handles the SpamAssassin code slightly differently?

Or if not ditto, anyone else?

I'm going to build out a new system tonight and I'll watch this time, but my recolletion is I haven't allowed CB to update exim.conf.

Jeff
 
nobaloney said:
Quick question: Do you know how custombuild 2 manages my SpamBlocker file, which handles the SpamAssassin code slightly differently?
Click to expand...

I don't really know. I have not manually installed your SpamBlocker file, but I am using the default exim.conf provided by DirectAdmin in CB 2, I see this in the top of exim.conf:

"SpamBlocker.exim.conf.2.1.1-release"

However that release version should not mean anything much, because I have noticed that CB 2.0 several times has patched my exim.conf, without changing the version at the top, and not changing the date at the top in the file.

I would recommend that you just take a backup of exim.conf and the run ./build exim_conf and then use a program to see the diff between the files. I found this in the cb 2.0 faq http://forum.directadmin.com/showthread.php?t=44743

Automatic exim.conf changes after installation/update of ClamAV/SpamAssassin (it uses includes of /etc/exim.spamassassin.conf and /etc/exim.clamav.conf in /etc/exim.conf.
Click to expand...

eximconf - update exim configuration file (/etc/exim.conf) using "./build exim_conf" or "./build all". Possible values: yes/no (default: no).
Click to expand...
 
I'm guessing that until/unless we know otherwise from John, that we presume that users of SpamBlocker 4 should likely not allow CustomBuild to touch exim.conf. Personally I manage exim.conf manually.

John?

Jeff
 
This is way back from mid-August, but I think I had created a version of SB 4.2 with the mentioned lines:
http://files1.directadmin.com/services/exim.conf-SpamBlockerTechnology-v4.2.txt

If you use the above version of the SB 4.2, that may answer your question about the lines.

Here is the diff from Jeff's original:
http://files1.directadmin.com/services/exim.conf-SpamBlockerTechnology-v4.2.to-DA.diff

We also don't include 127.0.0.1 in the pophosts line in our exim.conf files.. just opinion there, either could be ok depending on your needs.
Also includes a few wording changes.. all mentioned in the diff.

I had plans to make 4.2 the default, but realized there are quite a few more files needed in /etc/virtual/* so I put that on hold for now.

John
 
Very good link, John. I hadn't realized you'd done that. I'm going to look over yours vs mine as part of my steps towards a new updated version.

Let's try to work together on that early in the New Year. Not necessarily to make 4.2 the default, but for me to work (perhaps with you) to make sure I include everything you've added over the years, and also many (most?) of the features suggested by other uses here oin these forums. Together we can hopefully make DirectAdmin's exim implementation the best one out there :).

And once the new version is done perhaps we can find a few people willing to work on a community version so it won't be so many years between version updates :).

Your point aboout 127.0.0.1 is duly noted, but let's not any of us forget that my version is very customizable, has lots of edit points, and a full documentation file here (nobaloney.net).

Jeff
 
You must log in or register to reply here.
Back
Top