Wwhat files in what order does WHM exim conf rebuild use

dmgens

Well-Known Member
Dec 10, 2006
51
0
156
Folks:

I'm trying to understand the the files that go into rebuilding of exim.conf that is done by WHM.

if the file /etc/exim.conf.dist is that the basic file, then how are exim.local and exim.local.options merged with it?

This seems to be complex to me, I bet that it's really simple actually, I just need some guidance.

Thanks
 

cPanelDavidG

Technical Product Specialist
Nov 29, 2006
11,212
13
313
Houston, TX
cPanel Access Level
Root Administrator
Folks:

I'm trying to understand the the files that go into rebuilding of exim.conf that is done by WHM.

if the file /etc/exim.conf.dist is that the basic file, then how are exim.local and exim.local.options merged with it?

This seems to be complex to me, I bet that it's really simple actually, I just need some guidance.

Thanks
The easiest way to modify the Exim configuration is using the Exim Configuration Editor in WHM. If you want to edit the contents of exim.conf, just click on the Advanced Editor button on that WHM screen.
 

dmgens

Well-Known Member
Dec 10, 2006
51
0
156
Thanks, But...

cPanelDavidG

I Have tried that and I get that annoying message:

" cPanel was unable to automatically merge your Exim configuration with the new settings that shipped
with the build you have installed (11.24.4-STABLE_36281) because you have a custom ACL configuration
which cannot be automatically configured. ", etc.

So I followed the instructions and updated the /etc/exim.config.local file by adding my ACLs to it after @[email protected] and before @[email protected] it still complains, is that normal?
 

cPanelDavidG

Technical Product Specialist
Nov 29, 2006
11,212
13
313
Houston, TX
cPanel Access Level
Root Administrator
cPanelDavidG

I Have tried that and I get that annoying message:

" cPanel was unable to automatically merge your Exim configuration with the new settings that shipped
with the build you have installed (11.24.4-STABLE_36281) because you have a custom ACL configuration
which cannot be automatically configured. ", etc.

So I followed the instructions and updated the /etc/exim.config.local file by adding my ACLs to it after @[email protected] and before @[email protected] it still complains, is that normal?
Hmm...

Can you paste the ACLs you are attempting to add?
 

dmgens

Well-Known Member
Dec 10, 2006
51
0
156
Posting the acls

Here they are:

They actually work if you put them in the exim.conf file, but cPanel complains then:

#++# HELO ACL's
check_helo:
#

accept condition = ${if match {$sender_host_address} {127.0.0.1} {yes}{no}}
accept condition = ${if match {$sender_host_address} {albq.qwest.net ([192.168.0.65])}{yes}{no}}

drop condition = ${if match {$sender_helo_name} {.*[.].*} {no}{yes}}
message = Your mail server announcement ($sender_helo_name) [$sender_host_address] \
is a single word rather than a FQDN. This is \
in breach of RFC2821(A)
log_message = Bad HELO: Not FQDN (A)

drop condition = ${if match {$sender_helo_name} {localhost[.]*.*} {yes}{no}}
message = you are not ($sender_helo_name) (B)
log_message = not me (B)

# drop from ip only

drop condition = ${if match {$sender_helo_name}{^[0-9]\{1,3\}[.][0-9]\{1,3\}[.][0-9]\{1,3\}[.][0-9]\{1,
3\}\$} {yes}{no}}
message = IPs ($sender_helo_name) are not compliant in HELO
log_message = IPs ($sender_helo_name) are not compliant in HELO (C)


accept

#--# end of HELO ACL's
 

cPanelKenneth

cPanel Development
Staff member
Apr 7, 2006
4,607
79
458
cPanel Access Level
Root Administrator
Here they are:

They actually work if you put them in the exim.conf file, but cPanel complains then:

#++# HELO ACL's
check_helo:
#

accept condition = ${if match {$sender_host_address} {127.0.0.1} {yes}{no}}
accept condition = ${if match {$sender_host_address} {albq.qwest.net ([192.168.0.65])}{yes}{no}}

drop condition = ${if match {$sender_helo_name} {.*[.].*} {no}{yes}}
message = Your mail server announcement ($sender_helo_name) [$sender_host_address] \
is a single word rather than a FQDN. This is \
in breach of RFC2821(A)
log_message = Bad HELO: Not FQDN (A)

drop condition = ${if match {$sender_helo_name} {localhost[.]*.*} {yes}{no}}
message = you are not ($sender_helo_name) (B)
log_message = not me (B)

# drop from ip only

drop condition = ${if match {$sender_helo_name}{^[0-9]\{1,3\}[.][0-9]\{1,3\}[.][0-9]\{1,3\}[.][0-9]\{1,
3\}\$} {yes}{no}}
message = IPs ($sender_helo_name) are not compliant in HELO
log_message = IPs ($sender_helo_name) are not compliant in HELO (C)


accept

#--# end of HELO ACL's
What you provided above works for me, once I fixed a syntax error. It may be due to posting on the forum, but the following line needs to be a consecutive line in the configuration file:

Code:
drop condition = ${if match {$sender_helo_name}{^[0-9]\{1,3\}[.][0-9]\{1,3\}[.][0-9]\{1,3\}[.][0-9]\{1,3\}\$}{yes}{no}}
When I pasted it from the forum, the line wrapped to a new line.
 

dmgens

Well-Known Member
Dec 10, 2006
51
0
156
They work if you edit the exim file directly

Kenneth:

But I can't get the WHM exim configuration system to put them there, Don't know why, and yes the last regex wraps at the lease excuse. I'll attach my exim.conf.local file, maybe that will give some more info

Thanks for you help and time
 

Attachments

cPanelKenneth

cPanel Development
Staff member
Apr 7, 2006
4,607
79
458
cPanel Access Level
Root Administrator
Kenneth:

But I can't get the WHM exim configuration system to put them there, Don't know why, and yes the last regex wraps at the lease excuse. I'll attach my exim.conf.local file, maybe that will give some more info

Thanks for you help and time
I suggest you open a support ticket regarding this issue. I'm not able to duplicate your scenario on 11.24.4-CURRENT