James,
> I just found that some of our internal mail is getting filtered. The
> issue is that a user uploads a file via a website and then the server
> sends the file, as the user that uploaded it, to our a ticket tracking
> system.
>
> Here is an example of a quarantine:
> Mar 22 21:20:05 relay1 amavis[2535]: (02535-11) Blocked SPAM, MYNETS
> LOCAL [10.20.195.102] [10.20.195.102]<[email protected]> ->
> <[email protected]>, quarantine: spam-EyxUzfJT2ylM.gz,
> Message-ID:<[email protected]>,
> mail_id: EyxUzfJT2ylM, Hits: 7.035, size: 222098, 1011 ms
>
> Is this the correct way to resolve this?:
> I added 10.20.195.0/24 10.10.14.0/24 10.10.200.0/24 to the line below in
> /etc/amavisd.conf
Yes, that's one way to do it, assigning a more permissive policy
to mail originating from internal networks, e.g.:
$policy_bank{'MYNETS'} = {
originating => 1,
spam_kill_level_maps => 9.5,
};
Alternatively you can play with SpamAssassin rules/scores and
apply a countermeasure to the specific rules that hit such
messages (see quarantined message for rule names that fired).
Mark
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
