Gary V wrote:
> LDB wrote:
>
>
>>I am using amavisd-new 2.4.2 with postfix 2.2.8. It is filtering
>>like it is suppose to but it is filtering after I have authenticated
>>against SASL. The message is marked as SPAM for some reason.
>>I get messages like the following from postfix ..
>
>
>>ANy ideas ..
>
>
> It's not unusual, sasl or not, for mail from dynamic addresses to be
> marked as spam. Look at the headers of the mail that was quarantined
> to see what rules hit to make up the score of 5.034 for your message.
> This is why some method of whitelisting sasl users is sought.
>
> This issue was discussed just a few days ago, among other times:
> http://marc.theaimsgroup.com/?l=amavis-user&m=115545447013492&w=2
>
> You may have another issue that is unrelated to your problem, but you
> may wish to be aware of. When sending mail to amavisd-new via lmtp:
>
>
>>Aug 20 15:00:50 ldb-jab amavis[13001]: (13001-04-2) sending LMTP response for
>><[EMAIL PROTECTED]>: "250 2.5.0 Ok [EMAIL PROTECTED], DSN sent (554 5.7.1
>>Rejected, id=13001-04-2 - SPAM)"
>
>
> It may send an extra response like this when (depending on
> $final_spam_destiny setting) it should have been suppressed.
>
> See:
> http://marc.theaimsgroup.com/?l=amavis-user&m=115429690221041&w=2
>
> If this is a concern for you, in lieu of patching amavisd-new, switching from
> lmtp to smtp would also work around the problem.
>
> Gary V
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> 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/
>
>
Thank you .. I ended up defining an authorization submission policy
(per instructions on the website).
Like you stated/implied, the policies for submitting and receiving
should be different.
$interface_policy{'10026'} = 'AUTH';
$policy_bank{'AUTH'} = {
# enable admin notifications for malware originating from our users:
virus_admin_maps => ["[EMAIL PROTECTED]"],
spam_admin_maps => ["[EMAIL PROTECTED]"],
# be slightly more permissive on spam levels for mail from our users:
spam_kill_level_maps => 7.0,
spam_dsn_cutoff_level_maps => 15,
bypass_banned_checks_maps => 1, # allow sending any file type or name
final_bad_header_destiny => D_BOUNCE # block invalid headers
};
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
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/
