I figured that when I edit anything through WHM, I'm working basically
with the files "exim.conf.buildtest" & "exim.conf.local" - which then
change the file "exm.conf". So, if I make the changes in all three files
from root then it stays even after daily update. There are two more files
with default configurations - "exim.conf.dist" &
"exim.conf.mailman2.exiscan.dist".
I think they meant for replacing exim with the default configuration. I
still couldn't figure out a way to bypass the dns check for some IPs. I was
wondering, if I can use rules like: "require verify = sender :
!+rbl_whitelist".
I didn't check it but I was thinking of testing different things with my
one of my
clients online. Any suggestion would be highly appreciated.
Thank you once again...
Khalid
----- Original Message -----
From: "Mark Smith" <exim-users@???>
To: "'KHALID SHAWKAT'" <iquest@???>; <exim-users@???>
Sent: Thursday, July 14, 2005 8:41 PM
Subject: RE: [exim] how to stop exim from reverse lookup check
fortrustedIPs...
|> -----Original Message-----
| > From: KHALID SHAWKAT [mailto:iquest@bellsouth.net]
|
| > My question is how can I keep both of the options in both
| > files (exim.conf & exim.conf.local)
| > and stop exim checking my client's IPs? I have another issue,
| > which is some of my client's business partners can not send emails to
them
| even after
| > putting them in white list. They are either getting rejected messages
| because of the failed
| > hostname lookup or blacklisted IPs. I was wondering if you can point me
to
| the right
| > direction. I believe that we made
| > some progress and probably moving to the right direction.
| >
| > Thank you once again for all your support...
| >
| >
| > Khalid
| >
|
| I've always avoided using WHM's Exim config editor because it was too
| difficult to try to understand the obscure way it works, and where it put
| things. So I can't be much help there.
|
| The quickest way to get it working would be to bypass WHM's editor
| altogether and just create your own version of exim.conf in /etc. That
will
| work fine - just make sure you keep a copy of the file, because on the
rare
| occasions that cPanel updates Exim with a new version, it will overwrite
| your exim.conf. Then you'll just need to copy it back again.
|
| - Mark
|
