problem with cpanel installing Mail SpamAssassin

[cPanelDavidG]

Thanks for the patch.

...However we are running Perl 5.8.7.

...

You may want to consider upgrading to Perl 5.8.8 (instructions are on the sticky thread about migrating to cPanel 11). This will reduce the number of issues you may experience with cPanel 11.

[opt2bout]

You may want to consider upgrading to Perl 5.8.8 (instructions are on the sticky thread about migrating to cPanel 11). This will reduce the number of issues you may experience with cPanel 11.

Done, thanks!

This doesn't appear to be the issue with the SpamAssassin changes.

Question: Does the way CP 11 handle SA checks inline affect how the message is rewritten if flagged as spam?

In earlier CP11 releases, if a rule flagged the message as spam, we still got the x-spam-report header populated correctly with the original Email message attached with the spam report in the body as well.

Now, just the Subject header gets rewritten.

What I'm trying to figure out is when this stopped happening, and if its the Exim configuration modified during the upcp or if its SA itself.

Does anyone know if going to Mailscanner instead gives us the original results?

[cPanelDavidG]

Done, thanks!

This doesn't appear to be the issue with the SpamAssassin changes.

Question: Does the way CP 11 handle SA checks inline affect how the message is rewritten if flagged as spam?

In earlier CP11 releases, if a rule flagged the message as spam, we still got the x-spam-report header populated correctly with the original Email message attached with the spam report in the body as well.

Now, just the Subject header gets rewritten.

What I'm trying to figure out is when this stopped happening, and if its the Exim configuration modified during the upcp or if its SA itself.

Does anyone know if going to Mailscanner instead gives us the original results?

I know some things recently changed with SA itself with regards to how it indicates something as spam. I also know that the Exim configuration is updated in some updates, hence we advise against modifying the configuration file directly - encouraging the use of the WHM interface as a means to customize the Exim configuration so your changes are preserved during updates.

[opt2bout]

I know some things recently changed with SA itself with regards to how it indicates something as spam. I also know that the Exim configuration is updated in some updates, hence we advise against modifying the configuration file directly - encouraging the use of the WHM interface as a means to customize the Exim configuration so your changes are preserved during updates.

We only use Exim to keep the configuration file. In fact, I've reset the configuration after our host provider got through changing things...not sure what they are doing, but I like most of my cPanel installs to be as canned as possible.

Can't find anything on SA's site to indicate that they've changed anything that would affect how the original message was attached along with the Spam report.

I see in the inline ACLs in the Exim config where the header is rewritten, but no code showing where the original message is added as an attachment to the spam reported message.

I guess we have to disable the inline rules and use the old spamassassin system until we can find a way to replicate this ourselves.

EDIT: Yes, disabling the ACL rules puts things back...messages are being processed, but the spam header rewrites, etc. ***SPAM*** are old school "[SPAM]" ... we didn't have to do this before. I'd prefer using the rules inside Exim's ACL, but not sure how to go about writing our own to do the necessary modification to the mail message like it did before.

[jackflash]

opt2bout:

I did an update today and am experiencing the same issue with the original e-mail being modified rather than attached. I would like to get them as attachments again. Can you provide a bit more detail about what ACL rules you removed/disabled?

Another point of interest: At update time, exim gave me errors about not being able to merge my modified exim.conf with the new file. Even though I manually tried to merge them as instructed, it didn't work and mail wasn't being processed. Therefore the big block of ACL rules in the advanced editor has the new default rules. I suspect this is where the problem lies, but don't know how to fix it.

Thanks.

[Edit: Since posting my question, I have selected the option "Use the old transport based spamassassin system instead of the new acl style one" on the Exim Configuration Editor page and now get spam with the original messages as attachments again. Odd, really, because I had been using a v11 release for the past few months (I think it was R11631) and the upgrade I made today to the current R16448 handles spam differently. What a shame that I'll have to miss out on some improved functionality, but I can't have false positives permanently altered either.]

[opt2bout]

[Edit: Since posting my question, I have selected the option "Use the old transport based spamassassin system instead of the new acl style one" on the Exim Configuration Editor page and now get spam with the original messages as attachments again. Odd, really, because I had been using a v11 release for the past few months (I think it was R11631) and the upgrade I made today to the current R16448 handles spam differently. What a shame that I'll have to miss out on some improved functionality, but I can't have false positives permanently altered either.]

I agree. i have searched for an alternative to use ACLs to modify/rewrite the message and keep the original message as an attachment, but from what I've read, this can't be done. Once the ACL portion of Exim is being processed, the message has already left SpamAssasin.