sa_spam_modified_sub, -> spam_subject_tag2_maps (still trying to resolve)
mikeg at rockisland.com
Fri Aug 10 22:27:16 CEST 2012
Still trying to sort this out.
Is there a document that describes each LDAP attribute and how it relates to amavis?
I'm trying (unsuccessfully) to replicate our existing 2.6.4 setup with 2.8.0.
Why was amavisSpamModifiesSubj support removed from amavisd?
I just need the ability to either turn ON or OFF subject modification on a per user basis.
I'm not seeing that with the current information available to me: /share/docs/amavis-new/ or amavis.org website.
It would be great to have 'amavisSpamModifiesSubj' support back, or some clues on how to regain what we had before without having to:
- re-code Squirrelmail plugin
- add new LDAP attributes to 4000+ customer records
- copy existing LDAP attribute setting to new attribute
- create maps, ccat, or whatever the new 2.8.0 will require to regain functionality.
Surely we can't be the only ones using LDAP and trying to conditionally turn on or off subject modification?
Rock Island Technology Solutions, Inc.
San Juan Islands, WA. 360-378-5884 x201
> -----Original Message-----
> From: amavis-users-bounces+mikeg=rockisland.com at amavis.org
> [mailto:amavis-users-bounces+mikeg=rockisland.com at amavis.org] On Behalf
> Of Mike Greene
> Sent: Wednesday, August 08, 2012 4:48 PM
> To: amavis-users at amavis.org
> Subject: RE: sa_spam_modified_sub, -> spam_subject_tag2_maps
> Since posting yesterday I've made a little bit of progress on my
> upgrade, but I've only managed to present more questions than
> resolutions so far.
> We are upgrading from Amavis 2.6.4 to 2.8.0
> In our amavis.conf file we have:
> $sa_spam_modifies_subj = 0;
> $sa_spam_subject_tag = '***SPAM*** '
> We do an ldap lookup to see if 'amavisSpamModifiesSubj' = true and if
> it is we add ***SPAM*** to the subject and via dovecot-sieve (based on
> X-Spam-Flag) we'd pass the message directly to the inbox, if set to
> 'false' we wouldn't modify the subject and via dovecot-sieve we'd
> redirect the message into a spam folder.
> I've since upgraded the amavis-schema to the latest and modified my
> amavis.conf file to include the following:
> @spam_subject_tag_maps = (); # N.B.: inconsistent name
> @spam_subject_tag2_maps = ( q_ldap_s('amavisSpamSubjectTag2'), );
> @spam_subject_tag3_maps = ();
> For the mail account I'm testing with I set amavisSpamSubjectTag2= true
> thinking it would insert the ***SPAM*** on the subject line, however it
> didn't, it would insert the value of the attribute, which in this case
> was "true" ie; "trueSome Spammy Subject Line" I changed the attribute
> value to ***SPAM*** and now it does insert that into the subject line,
> so I'm getting closer.
> Further testing shows that the subject is modified regardless of what I
> have "amavisSpamModifiedSubj" set to, which is understandable since
> that isn't supported anymore. I guess what I'm looking for now is how
> do I conditionally turn on and off the insertion of the ***SPAM*** text
> in the subject line.
> Another question is, am I going about this the right way? I think I'm
> on the right path but before I head too far down this road I want to be
> sure I'm addressing this problem correctly. I still need to modify our
> squirrelmail plugin to update the proper ldap attributes and populate
> all our mail users settings to the new values, so obviously I want to
> get this part right before tackling all the 'other stuff'.
> Mike Greene
> Rock Island Technology Solutions, Inc.
> San Juan Islands, WA. 360-378-5884 x201
More information about the amavis-users