AntiRelayd...Please Help!!!

[gegervision]

Apparently after last nights updates shown the change logs below:

Exim updated to 4.69-5
Support for checking SPF and DomainKeys at SMTP time
Removed Antirelayd from init script
Updated init scripts to include --max-spare support for spamd
Patch libspf2 to address segfaults on x86-64 machines
Updated init scripts to use cPanel scripts to restart spamd

I can longer get AntiRelayd to restart and it will NOT write my alwaysrelay hosts file to relayhosts. This change now affect over 350 of my users whereby we take care of mail for their Exchange server. This is a major issue for us.

I called the Planet hosting where my servers are located and they were not aware of such a major change. They are opening a support ticket as well with cPanel to get a resolution.

Does anyone know of a work around for this issue?

[cpanelnick]

antirelayd was replaced with tailwatchd.

If you are still having trouble, please open a ticket @ https://tickets.cpanel.net/submit/

[gegervision]

Before we were able put hosts allowed to relay in the "alwaysrelay" file and the daemon would update "relayhosts" with those IPs. Now that is not happening...so how do I get my allowed relay IPs into "relayhosts." If I manually put them into "relayhosts" they get written over the second I close the file.

The Planet has opened a a ticket but I can't wait for their help. This is affect 350 Exchange server users.

[dwykofka]

This is a Major issue for me as well. All of our large customers that use exchange and relay via our servers can no longer send outbound email.

I have some very pissed off customers!

[cpanelkenneth]

Before we were able put hosts allowed to relay in the "alwaysrelay" file and the daemon would update "relayhosts" with those IPs. Now that is not happening...so how do I get my allowed relay IPs into "relayhosts." If I manually put them into "relayhosts" they get written over the second I close the file.

The Planet has opened a a ticket but I can't wait for their help. This is affect 350 Exchange server users.

Thank you for that information. I've filed a report with the developers about the matter.

[dwykofka]

I have downgraded several of my servers in order to get my customers back online.

in update config:
Switch to Stable

Then force a upcp

Then restart exim a couple of times (not sure why but it takes me 3-4 restarts to get it going).

Additionally I backed up my /etc/alwaysrelay files just in case.

[gegervision]

Could there be any adverse affects in downgrading to "Stable" version? My concern is causing more issues than we all have right now.

The real resolutions is for the developers to fix this ASAP as I'm sure it's affecting more users than they know. Downgrading is a quick fix but not long term because once the Stable build gets updated with these new settings we back in the same place we are right now.

All we need is the ability for some file whether /etc/alwaysrelay that will write safe IPs to the relayshosts.

I'm guessing since we have no other responses in this post that there is no simple resolution outside of downgrading to the Stable build.

Yikes!!!

[dwykofka]

I completely Agree with you, I downgraded because I could no longer afford to have so many customers "down".

[gegervision]

I downgraded as well to Stable build and am now backup and running. What a relief!!

I also notice that the new Release build add new DNS entries for ever host and overwrote ones I needed.

i.e. - for one of my Exchange 2003 I used webmail.theirdomain.com/exchange so I would have to retrain them where to go. Well the new release update overwrote my webmail A record with their new settings. They also added a new entry A record for whm.

THis is not good as who know what they are overwriting.

[dwykofka]

I dont have any overwritten DNS records but that "SCARES" me.

we have TONS of custom offsite dns a records for customers. If they are overwritten we will spend hours and hours trying to re-enter them.

Would a Staff member please comment on this?

[cpanelnick]

Could there be any adverse affects in downgrading to "Stable" version? My concern is causing more issues than we all have right now.

The real resolutions is for the developers to fix this ASAP as I'm sure it's affecting more users than they know. Downgrading is a quick fix but not long term because once the Stable build gets updated with these new settings we back in the same place we are right now.

All we need is the ability for some file whether /etc/alwaysrelay that will write safe IPs to the relayshosts.

I'm guessing since we have no other responses in this post that there is no simple resolution outside of downgrading to the Stable build.

Yikes!!!

The /etc/alwaysrelay functionality will be restored in tonight's builds.

[cpanelkenneth]

It's part of the Proxy Access feature:

Automatically create cpanel, webmail, webdisk and whm proxy subdomain DNS entries for new accounts. When this is initially enabled it will add appropriate proxy subdomain DNS entries to all existing accounts. (Use /scripts/proxydomains to reconfigure the DNS entries manually)

This feature is enabled by default in Tweak Settings. If one enters Tweak Settings after the upgrade and saves the Tweak Settings without unticking the boxes for the Proxy access feature appropriate A records are added to the zone files.. Hence DNS records for cpanel, whm, webdisk and whm will be added to all primary domains.

[dwykofka]

Yes but does that mean that it will overwrite the custom entries?

If so that is a serious flaw!

[gegervision]

it overwrote mine...so there is a flaw

[dwykofka]

[root@dnsclstr1 named]# cd /
[root@dnsclstr1 /]# cp -R /var/named /files/named3
[root@dnsclstr1 /]# echo Whew!
Whew!
[root@dnsclstr1 /]#