Abobe Campaign - Spam assassin implementation.

Question

Hi There,

We are integrating Spamassassin with Adobe Campaign.

The rule update command results error in PROD. Same command worked fine in our lower env. Can you pls suggest any miss in our PROD implementation. Thanks.

"sa-update -D --nogpg --install /appl/adobe/nl6/temp/Mail-SpamAssassin-rules-3.4.4.r1873061.tgz"
**********************************************************************************************************************************
Mar 19 03:07:31.675 [115255] dbg: timing: total 76 ms - init: 73 (95.8%), parse: 0.57 (0.8%), extract_message_metadata: 1.00 (1.3%), get_uri_detail_list: 0.44 (0.6%)
Mar 19 03:07:31.675 [115255] dbg: plugin: Mail::SpamAssassin::Plugin::MIMEHeader=HASH(0x3fb67f0) implements 'finish_tests', priority 0
Mar 19 03:07:31.675 [115255] dbg: plugin: Mail::SpamAssassin::Plugin::Check=HASH(0x40e4a20) implements 'finish_tests', priority 0
Mar 19 03:07:31.675 [115255] dbg: generic: lint check of site pre files succeeded, continuing with channel updates
Mar 19 03:07:31.675 [115255] dbg: channel: using --install files /appl/adobe/nl6/temp/Mail-SpamAssassin-rules-3.4.4.r1873061.tgz{,.sha1,.asc}
cannot open /appl/adobe/nl6/temp/Mail-SpamAssassin-rules-3.4.4.r1873061.tgz.sha1

**********************************************************************************************************************************

kvthiyaga · Accepted Answer

Hi All, This issue with Spamassassin rule update 3.4.4 version. Downgrading it to 3.4.0, working fine, so it's live with rules update 3.4.0. Thanks.

Craig_Thonis · Answer

Hi,

If it worked in your lower environment and you were on the same builds of Campaign and Spam Assassin as Production, then I'd make sure you check the security and folder permissions on the Production server as the operator likely doesn't have access to the folder and files required.

Regards,

Craig

Sign up

Login with SSO

Login to the community

Login with SSO