How to install PRM (Process Resource Monitor) Published: Apr 01, 2004
  • Rating


Set Exim to Properly Reject Invalid Email the right way and let your Cpanel server run a little easier.

Tired of seeing your mail queue fill up with bounce messages to non-existant spammer email addresses? By default, if an email comes into your server addressed to an invalid recipient, Exim will accept the message from the delivering agent, and then generate a return email to them explaining that the address is invalid. With this little tweak, you can make exim tell the delivering agent that that address is invalid at the time the message is being delivered, meaning no more spam returns cluttering up your queue! Can I get an Amen!? Read on!

This is curtesy of cyberspirit in the cpanel forums. Original thread is loacted here.

Method 1)
1. Open WHM and click on Exim Configuration Editor

2. Click on the Switch to Advanced Mode button.

3. Scroll down until you see the section on ACL's. You'll see three boxes. In the middle box, locate the section that reads - See Section A:

Method 2) Recommended

Login into SSH and su to root

2. pico /etc/exim.conf

3. Ctrl + W and type in: accept  domains   Notice the two spaces. Look for something like this below.

Section A:
accept  domains = +local_domains
accept  domains = +relay_domains
accept  hosts = +relay_hosts
accept  condition = ${perl{checkrelayhost}{$sender_host_address}}


accept domains = +local_domains


accept domains = +relay_domains

add the following:

message = unknown user
verify = recipient

Make sure each line lines up. You might need to add two spaces before each line. The final section will look like this:

accept domains = +local_domains
message = unknown user
verify = recipient
accept domains = +relay_domains
accept hosts = +relay_hosts
accept condition = ${perl{checkrelayhost}{$sender_host_address}}

Scroll all the way to the bottom and click on Save.

That's it! Welcome to much smaller mail queues!
  • Rating


Related Articles

Comments (6)

  • Gravatar - Edward
    Edward 01:13, April 5, 2004
    Tested this script with a resource hog of a perl script for testing purposes, and it work great. It killed it when I hit the resource limit.
  • Gravatar - Robert Saylor
    Robert Saylor 16:47, April 5, 2004
    I've been using this for a while and it really does work. There is now some control over what the users can do on the server. The only problem is when enabled it interfears with my backup forcing me to shut down the resource monitor once per week while the backup runs.
  • Gravatar - Rudy
    Rudy 21:40, September 23, 2006
    I use it on two webservers. One of them was overloaded big time by certain users (running corrupt scripts). It does a great job!
  • Gravatar - James
    James 17:59, December 5, 2006
    Hi,<br />
    I am looking at this script. Looks very handy for my situation. But as Robert pointed out, the script might caused problem when server backup is run.<br />
    <br />
    I am having about 1400 of accounts in my server, and FUll backup is scheduled on daily basis. WIll this cause problems??<br />
    <br />
    But I thought that "this script was not intended to monitor root processes but rather user land tasks." Is backup process perform under "root" user??<br />
    <br />
    Thanks foryour kind advise.<br />
    James<br />
  • Gravatar - Rudi
    Rudi 13:55, January 31, 2007
    Please update this tread, as the script doesn't exist at the given URL any more
  • Gravatar - Jamyn
    Jamyn 17:43, May 13, 2008

Add Your Thoughts is a hosting directory, not a web host.

Copyright © 1998-2017