Yeah, put the plugin files in your local config directory... that's the
same directory that has you local.cf file.
If you want to only enable the WRONG_MX rule for a particular domain,
you'll have to configure per user or domain scoring.
None of this is specific to this particular plugin. Please seek help on
the users lists.
Daryl
On 6/11/2006 3:16 PM, Mike L wrote:
I have Windows 2003 , Perl 5.8.8, Spam Assassin Latest Build
SpamAssassin source directory is c:\mail-spamassassin-3.12
Spam is getting fitlered.
I have an outside spam filter that has its own mx records.
But some spammers are sending to our mailserver directly, hence we now
are implementing SA.
If I understand, your plugin will check the mx order and if it is going
directly to the box (highest mx), it will block it as spam since it
should have gone to the 10 then the 20 then the 30 and almost never go
to the 50 record(directly to the box)
I would like to know if I need to modify local.cf http://local.cf or
if i just place this in the same local as local.cf http://local.cf
does it automatically work?
Is this a beter email?
On 6/11/06, *Daryl C. W. O'Shea* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Not really. I have no idea how you've got your SA setup on Windows and
you haven't asked anything specific.
Daryl
On 6/11/2006 1:57 PM, Mike L wrote:
Thanks Daryl, but can you give me a little more info?
On 6/11/06, *Daryl C. W. O'Shea* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Mike L wrote:
I have SpamAssassin install with Perl 5.8.8 on a W2K3 box.
SA is the latest version.
I would like to setup the following
I need to know how to setup wrongmx.pm http://wrongmx.pm
http://wrongmx.pm
http://wrongmx.pm and
wrongmx.cf http://wrongmx.cf http://wrongmx.cf
http://wrongmx.cf so that email
that does not go to my spam
filter first will be deleted. I also want to do this for
only one
domain
on my server, we have 26 domains.
I wouldn't do that. There's lots of legit mail that will
show up at
your lower preference MXes for no apparent reason. Lotus
Domino seems
to do it quite often.
In any case, you'd add both files to your local config directory.
Comment out or set the scores to zero for the WRONG_MX rule
and then
assign a score on a per domain basis for the rule.
Daryl
