My Exim Configuration Changes Don't "Stick"

[gcutrer]

The only change I'm making is through WHM in
Service_Configuration-->Exim_Configuration_Editor

I change the Subject line prefix for spam from ***SPAM*** to [SPAM] (just because I have several employees with that filter on their email client)

Setting changes; I look at the exim.conf via SSH and the setting has changed.

The next morning, the setting is back to ***SPAM***

Is this a feature or a bug? If I change the RBL preferences will they reset as well? I'm guessing this is on the updates nightly??

This is from the /scripts/upcp log emailed to me:

>>
Updating SMTP (exim) Server...Exim (maildir) Setup Script Version 20.0
Fetching version information from http://httpupdate.cpanel.net/eximinstall/version (STABLE)....Fetching http://httpupdate.cpanel.net/eximinstall/version (0)[email protected]%......Done
Done
This is the exim 4.69 installer release number 23.1 for platform centos 5.3
exim is up to date. Use eximup --force to force a reinstall
...Done
<<


Can anyone shed any light on the correct procedure for making config changes permanent?

 

[david510]

Do the following from the command line.

chattr +i /etc/exim.conf

 

[gcutrer]

Well, that would solve the problem for now, until I go back and want to change something via WHM and then can't remember I've set the bit on the file to not updateable. I'll then pull the rest of my hair out and eventually remember then slap myself in the head.

Meanwhile, it's supposed to work, isn't it? And since there was no update last night (see log file entry) why the change back to default in exim.conf ????

 

[cPanelDavidG]

Have you tried configuring this in the Basic Exim Configuration editor as well? What were the results?

Just a reminder, this setting is:

** SpamAssassinTM: Text to add to the subject line of messages marked as spam ($spam_score and others [see ?] are acceptable). [?]

 

[gcutrer]

Tried but no luck with chattr. Exim configuration keeps reverting.

Regarding your suggestion to use the Exim Configuration Editor in WHM. That's what I'm talking about! That's what I'm using!

I've tried the chattr command on the /etc/exim.conf file.

No, the settings keep reverting.

Here, for clarity, is the problem again:

I want to change just a few settings for Exim, via the WHM.

I login to WHM. I navigate to the 'Exim Configuration Editor.'

I check a few checkboxes to change some settings. I Save the configuration.

I check later in the day. My changes are still OK. They're there.

Spam has slowed to a trickle because of the new changes.

Next day I login to WHM and go to the Exim Configuration Editor.
The changes I made are not there. The checkboxes I checked are now "unchecked." The configuration is exactly like it was BEFORE I made the changes.

Of course, an update has run the night before.

My previous WHM server did not have this problem. Changes in Exim "stuck." Is it this version of WHM that's the problem? Is it a setting I'm overlooking?

I guess I can write a script to replace the Exim config file each morning with the one I've saved and restart Exim. But that would be kind of a kludge, wouldn't it? When WHM is supposed to work?

Help?!

 

[sawbuck]

DavidG would be the one to give you a definitive answer.

What cPanel/WHM version?

Our experience lately (using CURRENT 40255) has been with Custom RBLs. Similar behavior that you are experiencing which is now fixed in BETA making its way to EDGE. Can't say that will address your issue.

You might consider submitting a ticket as the cPanel staff has been very responsive, even to those who don't have external licenses.

HTH

 

[cPanelDon]

I believe the symptoms described should be corrected in the latest builds of cPanel/WHM version 11.25. If needed, you may optionally save a custom backup of the preferences by copying the following two files:

Exim Configuration Editor (Basic):

/etc/exim.conf.localopts

Exim Configuration Editor (Advanced):

/etc/exim.conf.local

 

[cPanelDon]

As sawbuck mentioned, it will help to know the full cPanel version number of the affected system. The following command may be used to obtain the full version number via root SSH access:

# cat /usr/local/cpanel/version && echo