Exim 4.60

Modem,

This kind of error looks like the one I had some time ago. I found out that it had something to do with the administration of spamassassin in /home/<user>/.spamassassin. If there is a file called "bayes.lock" in this directory, you're in trouble.

The simple solution is to switch off spamassassin for this user in the controlpanel, delete all the files in /home/<user>/.spamassassin and switch spamassassin back on.
 
Working well with RH9 rpm, Exim 4.60, SA, ClamAV and RBS :)

I'm ready to speed up Imap by adding Dovecot now, right?
 
torp said:
Working well with RH9 rpm, Exim 4.60, SA, ClamAV and RBS :)

I'm ready to speed up Imap by adding Dovecot now, right?
Click to expand...
could you share what you did on your RH9 box for the other RH9 users?
 
RoRoo said:
could you share what you did on your RH9 box for the other RH9 users?
Click to expand...

I followed the instructions in this forum, and they worked :)

I put together instructions as follows (to get antivirus, spamblock and spamassassin):

1) Grab most recent version of Spamassassin and Clamd (SA is in http://files.directadmin.com/services/9/)
2) Upgrade Exim:
wget http://files.directadmin.com/services/9/da_exim-4.60-1.i386.rpm
rpm -Uvh da_exim-4.60-1.i386.rpm
Click to expand...
3) Update to latest exim.conf
mv /etc/exim.conf /etc/exim.conf.bak
mv /etc/exim.rpmnew /etc/exim.conf
Click to expand...
4) Edit new exim.conf to include in line 1:
av_scanner = clamd:127.0.0.1 3310
Click to expand...
5) Added ACL to exim.conf to deny messages with virus:
check_message:
# Reject virus infected messages.
deny message = This message contains a virus or other harmful content ($malware_name)
malware = *

warn message = X-Antivirus-Scanner: Scanned with Exiscan. You should still use an antivirus.
accept
Click to expand...
6) Uncomment spamassassin configs in the next section of exim.conf, to enable SA
7) Updated blacklists and whitelist for spamblock:
touch /etc/virtual/bad_sender_hosts
chown mail:mail /etc/virtual/bad_sender_hosts
chmod 644 /etc/virtual/bad_sender_hosts
touch /etc/virtual/blacklist_domains
chown mail:mail /etc/virtual/blacklist_domainschmod 644 /etc/virtual/blacklist_domains
touch /etc/virtual/blacklist_senders
chown mail:mail /etc/virtual/blacklist_senders
chmod 644 /etc/virtual/blacklist_senders
touch /etc/virtual/whitelist_domains
chown mail:mail /etc/virtual/whitelist_domains
chmod 644 /etc/virtual/whitelist_domains
touch /etc/virtual/whitelist_hosts
chown mail:mail /etc/virtual/whitelist_hosts
chmod 644 /etc/virtual/whitelist_hosts
touch /etc/virtual/whitelist_senders
chown mail:mail /etc/virtual/whitelist_senders
chmod 644 /etc/virtual/whitelist_senders
Click to expand...
8) Restarted exim:
/etc/init.d/exim restart
Click to expand...

That's everything I did, exactly, from beginning to end, and it works.
 
thnx will check this at 3 am when most clients are sleeping ;)
 
Hi
after upgrade to exim 4.6 get these error ,

service exim restart
Shutting down exim:
Starting exim: /usr/sbin/exim: error while loading shared libraries: libdb-4.2.so: cannot open shared object file: No such file or directory

any help plz
 
Hi Guys,

Installed exim 4.60 and spamblocker 2.0 and it is working great!

The readme about spamblocker is removed from this threat because Jeff is working on it I guess.....but how can I put some server ip's in the whitelist.

Because spamblocker is working perfectly......well too perfect because its blocks a mailserver of one of our biggest ISP's. Planet.nl, its mailserver is in the list of the spamcop.net. So it bounces.......

Any pointers?

Tnx in advance!

Dennis
 
Dennis,

Add the following mailservers (and maybe others) to /etc/virtual/whitelist_hosts
============================

#
# home
#
smtpq1.groni1.gr.home.nl
smtpq2.groni1.gr.home.nl
smtpq3.groni1.gr.home.nl
smtpq3.tilbu1.nb.home.nl
#
# wxs
#
smtp13.wxs.nl
smtp14.wxs.nl
smtp15.wxs.nl
smtp16.wxs.nl
smtp17.wxs.nl
smtp18.wxs.nl
smtp19.wxs.nl
smtp50.wxs.nl
psmtp01.wxs.nl
psmtp02.wxs.nl
psmtp03.wxs.nl
psmtp04.wxs.nl
#
# gmail
#
xproxy.gmail.com
==========================
 
Thank you Ed for the quick reply!

But I still get a reject.......restarted exim, added the whitelist_hosts file.......

what more can i do?

Regards,

Dennis
 
Last edited:
Dennis,

The exact name of the failing nameserver shoud be in /var/log/exim/rejectlog. Add this name to the whitelist-file. Call me if you really can't find the problem.
 
hail said:
Hi
after upgrade to exim 4.6 get these error ,

service exim restart
Shutting down exim:
Starting exim: /usr/sbin/exim: error while loading shared libraries: libdb-4.2.so: cannot open shared object file: No such file or directory

any help plz
Click to expand...

I had this error with libdb-4.1.so on my CentOS 4 server.

I installed this package to fix it : compat-db

yum install compat-db
 
Dennis said:
The readme about spamblocker is removed from this threat because Jeff is working on it I guess.....
Click to expand...
I'm not sure what you mean. I removed the README and made it a separate file, available here.
but how can I put some server ip's in the whitelist.
Click to expand...
There are several whitelist files:
Code: 
/etc/virtual/whitelist_domains
/etc/virtual/whitelist_hosts
/etc/virtual/whitelist_senders
It's all explained in the README.

You can buy the SpamBlocker Plugin but it certainly isn't required.

Jeff
 
getUP said:
Code: 
wget [url]http://files.directadmin.com/services/da_exim-4.60-1.src.rpm[/url]
rpm -ivh da_exim-4.60-1.src.rpm
cd /usr/src/redhat/SPECS
rpmbuild -bb exim.spec
cd /usr/src/redhat/RPMS/i386
rpm -Uvh --force --nodeps da_exim-4.60-1.i386.rpm

This should do it.
Click to expand...

How would we run the installation in CentOS?
 
The exact same way. I just upgraded 5 minutes ago and I run CentOS. Just make sure to restart exim once done...

Dave~
 
Last edited:
No because on the second step where you would run the file it needs the /usr/src/redhat/SPECS directory which does not exist on CentOS and when you run rpm -ivh da_exim-4.60-1.src.rpm it gives you this message "error: cannot create %sourcedir /usr/src/redhat/SOURCES" so i was wondering how could i by pass this to be able to run it on CentOS?
 
Last edited:
OK. I CUT N PASTED EVERYTHING EXACTLY. Worked just fine. I run CentOS 4.1 so I *guess* it does work for some centOS users. Worked last time too upgrading to 4.54.

LOL- UPDATE:

#cat /etc/redhat-release
CentOS release 4.2 (Final)

Dave~
 
Last edited:
I am running CentOS 4.2 but i think i am getting it to work i just ran into another command not working after creating the directories manually so that one would work.
 
You must log in or register to reply here.
Back
Top