dictionary attack stopped working

[hostseeker]

I installed the great Dictionary Attack script from Chirpy about a year ago on 2 servers, it worked great. Then about 2 weeks ago it stopped working on 1 server but not the other!

I can not figure out why, the files are still there, permissions still the same, ACL's in exin.conf still the same. The only updating has been the normal Cpanel updates, both servers update automatically to the release version. Both servers run RHE Linux and are at the same provider.

Any suggestions as where to start looking to fix the script?

[hicom]

Hard to tell if there are no errors, did you check the Exim error_log ?

Try copying the exim config file from the working server and see if that resolves it. We do our modifications to exim config manually, and after we're done modifying the file, we chmod it so cPanel can't overwrite or change things in the file.

It could also be the /etc/exim.pl scripts have changed

[lloyd_tennison]

Just a note - Cpanel can and does overwrite it if it is chmod'd or chattr'd. And you get no warning when they do it.

[hicom]

Not from the servers i've managed, cPanel never been able to overwrite exim config even after an exim upgrade

[lloyd_tennison]

Hmm

buildeximconf: system('cp','-fv','/etc/exim.conf'

eximup:my @STRIPCHATTR = ( '/etc/rc.d/init.d/exim', '/etc/exim.conf', '/etc/exim.pl', '/usr/sbin/sendmail', '/usr/lib/sendmail' );
eximup:unlink('/etc/exim.conf');

is what I have always seen happen.

[chirpy]

Should have nothing to do with exim.pl or exim configuration issues. So long as you are using the exim configuration editor changes will be kept and as lloyd_tennison says, you should never edit exim.conf directly as it will be overwritten or, if you chattr it or other exim files, will break email delivery at some point in the future.

As to the original problem:

1. Make sure that you have not chattr'd any exim files, i.e.:

lsattr /etc/exim*

should show all files with a load of dashes (no letters intermingled with the dashes)

2. If that's OK (if not remove them) run:

/scripts/buildeximconf

3. If you use MailScanner, run:

/scripts/mailscannerupdate

4. Restart exim

5. If it still doesn't work. Make sure that the /tmp partition isn't full (or corrupted if a virtual partition)

6. Try resetting exim back to defaults and reinstalling the ACL as per our site.

To reset to defaults:

/scripts/resetecimtodefaults

If you do this on a server running MailScanner from my script, you should probably upgrade using my MailScanner script to set everything back up in exim correctly.