We have set up spirus on 2 servers using 2 different accounts (my work account and my private account)

Both times we found problems setting up the MX. When we assign the MX to the planets filtering MX then we do find after an about an hour the stats in the Spirus control panel does start working, but the routing did not work correctly.

Today we were investigasting this problem to why our MX does not work properly. One issue happened this weekend when tech support checked our /etc/localdomains file and found the domain in question was not listed. When the domain was listed then it worked perfectly.

So we checked this out this morning and tried to set up a new domain

Firstly we checked our /etc/localdomains to see if our domain was listed. The domain was listed andwe double checked this.

We then changed our MX for this domain using cpanel.

Then we re-checked the /etc/localdomains file and the domain had dissapeared.

So we readded the domain to /etc/localdomains, restarted a few services and it worked fine.

So... is this a bug in cpanel? because this has happened on 2 machines.

Also second part of this thread is

When setting up.. does it take 48 hours for the filter to start filtering? Do we lose any mail at all while propogation??

Hey,

Looks like we are running the same setup and it also happened to us. Put a ticket in and the tech has to escalate it to Level 2.

"Shrugs".., I was bored and did a search on here and did what you did and it worked.

This would surely indicate a bug in the MX update script that should be officially report if anyone cares.

Thanks for the post! Saved my butt big time!

Also had to repair some mail db's and this wiped out the addresses i had added to /etc/localdomains

so if you ever have to make any repairs to mail boxes then it might be worth checking that the /etc/localdomains is intact.

Is there a way we can get the planet or some one acknowledge the bug??

would be nice to see this patched for sure

The "Change MX" function in Cpanel is working as expected, and is not a bug. It thinks that if you are changing the MX record, that you are going to be hosting the mail on some other server, hence it removes the domain from /etc/localdomains. Granted, it tries to be a bit too smart about it all, but it's not a bug.

makes sense.. thanks for the update

I think I've found a way around this.

1. Login with SSH, "su -" to root, and create a file /etc/spirus_localdomains and put the domains using spirus as MX into it, one per line. This file uses the same format as /etc/localdomains does so you should probably look at that first.

2. Using the Exim config editor in WHM, edit the raw config and add the following line in the first box ( the box is just under the line that says "#!!# cPanel Exim 4 Config", (make sure you save the current contents since you can totally mess up your email system with the raw config editor). If you've already modified "domainlist local_domains" in this box, then add " : lsearch;/etc/spirus_localdomains" to the end of it, instead.



3. Save the changes

Note that the line MUST be on a single line.

Caution: This appears to work on my system, with my configuration (WHM 10.1.0 cPanel 10.2.0-C131, RedHat Enterprise 3 i686 - WHM X v3.1.0 ). Use at your own risk! Editing the raw exim config can seriously screw up your system!!!

Note: This probably won't work for "relay_domains" because the definition of "domainlist relay_domains" is spread across 2 lines in the default definition from CPanel and I don't believe you can replace anything that's spread across multiple lines using the raw config editor in WHM.

-- David