Enabling SPF Checking

[mixx941]

Hi everyone.

Quick question here about enabling SPF checking in WHM. I checked the option in the Exim config editor and saved (and it's still checked when I reload the page and look), however when it restarts I still get this message:

SPF is disabled in exim or unavailable, enabling SPF for SpamAssassin

Any ideas?

Thanks in advance.

-Mark
WHM 11.23.0
cPanel 11.23.0-B24213 (CURRENT)
FreeBSD 6.1-RELEASE

[greengiant]

I am also seeing this problem. Anyone find a solution?

[wemail]

I am also seeing this problem. Anyone find a solution?

I was told last week that we have to await Exim v4.69-5 to have the non-SA version of inward SPF checking. There is however some rather conflicting info in the latest "sticky" about cPanel 11.23.3, so I am a bit confused now!

[cpanelnick]

The SPF enabled exim binaries are only in EDGE/CURRENT.

They should be in RELEASE later this week once most people have upgraded.

[mixx941]

Hi, thanks for the replies.

The SPF enabled exim binaries are only in EDGE/CURRENT.

They should be in RELEASE later this week once most people have upgraded.

I was (and still am) on CURRENT and cPanel updates every night, however I still get the above error about it being disabled or unavailable. From WHM's top right info:

WHM 11.23.0 cPanel 11.23.3-C25049

The exim version is showing as: exim-4.68-0

Thanks again.

-Mark

[cPanelTodd]

Could you submit a ticket at https://tickets.cpanel.net/submit/in...eqtype=tickets so we can take a deeper look into this to pinpoint the cause for the errors?

[mixx941]

Sure, ticket submitted.

Thanks,

-Mark

[wemail]

The SPF enabled exim binaries are only in EDGE/CURRENT.

They should be in RELEASE later this week once most people have upgraded.

We have had a RELEASE upcp and are still on Exim 4.68-1. The system shows WHM 11.23.0 cPanel 11.23.3-R25133.

Presumably "later this week" now means the week begun 8 June?

[wemail]

Seem this is the case. We are now on "exim-4.69-5_cpanel_maildir" since last night.

Came as a bit of a surprise as it seems to have activated SPF checking without me changing anything in the config! Rather annoying as I am now getting reports of undeliverable email - not everybody has their SPF records set up yet, although they have had a lot of warning.

Even more worrying, I still haven't worked out what to do to activate SRS, so all our forwarding is probably broken until I can!!

[PPNSteve]

we're on WHM 11.23.2 cPanel 11.23.3-C25623 and getting the same error as well.. exim (exim-4.69-6_cpanel_maildir)

solutions yet?

[mixx941]

I'm not sure if you guys are also on FreeBSD, but the reply I got from support was that there is no automatic way to rebuild Exim with SPF checking on FreeBSD at this time like there is on Linux. The technician rebuilt the port manually with SPF checking enabled.

Hope that helps,

-Mark

[wemail]

In reply to mixx941 - we have two servers both on CENTOS Enterprise 5 i686, and we too have WHM 11.23.2 cPanel 11.23.3-R25623 with Exim 4.69-6_cpanel_maildir

We desperately want to have SPF working to block incoming SPAM, but with SRS also activated to "mend" the fact that SPF "breaks" forwarding - we are heavily dependent on forwarding. The SRS solution in the Wiki isn't complete - doesn't work as shown, so must need some additional tweaking.

(We are also quite interested in DomainKeys, but lets sort out one new feature at a time)!

[internetfab]

Anyone gotten SRS to work on cPanel yet? Isn't it included in the current/release builds?

[cpanelkenneth]

SRS is included in the Exim 4.69-x RPMs as a convenience for those that need it. SRS itself is unsupported by cPanel, meaning all issues pertaining to configuration and integration are not handled by cPanel and are not supported at this time. As with SPF, SRS support is considered Experimental by the Exim project and may or may not work.

[wemail]

The problem is some ISPs are enforcing SPF checking, and rejecting legitimate email, particularly if forwarded (without SRS rewriting).

Users are therefore saying that it isn't "experimental" any more, and asking us to activate it for their domains. (The two year trial indicated in RFC4408 expired some weeks ago).

We will however only activate SPF when we have SRS working too - to prevent broken forwarding.