Hi folks,
I've a question about user preferences.
What if a mail has multiple addressees?
If they use different settings is it possible
that some of them receives a potential spam while others do not?
How tagging does work in this case? Each recipients
get a different header with its own scores?
On Tue, 16 Nov 2010, Noel Jones wrote:
On 11/16/2010 12:17 PM, Matias Banchoff wrote:
Hello,
I have a question regarding the $forward_method variable.
I have two postfix servers and only one amavis server installed. Is
it possible to have amavis check mails from both postfix
I would like to reconfigure my setup to use AMaViS as a before-queue
content filter -- rejecting messages scoring above 25 (or maybe 30),
accepting (and quarantining) messages scoring between 5 and 25 (or
30), and delivering mail scoring below 5.
I guess before queue filtering and quarantine
Dear folks, especially developers,
I wonder if it is possible to introduce a new configuration
variable (let's say $sa_user) that could hold a username.
Amavisd should run spamassasin code with this uid, therefore
SA could use ~username/.spamassassin/user_prefs in order to customize
its rules.
My test mails from MTA0 went through MTA1, MTA2, and MTA1 again
and back to MTA0. MTA1 and MTA2 are configured to use service of amavisd.
Amavisd received them 3 times. I expected that effective scan
will be done at first time only because when MTAs receive message
from each other the
...Passed CLEAN [IPv6:MTA0_IPV6] [IPv6:MTA0_IPV6] My address -
Mailing list address, ..., Hits: -3.107,... 3027 ms
...Passed CLEAN, NO_DSN [MTA1_IPV6] [IPv6:MTA0_IPV6] My address -
Mailing list address, ..., Hits: -1.307,... 2325 ms
...Passed CLEAN, TRUSTED [IPv6:MTA2_IPv6]
Changelog writes:
| What's new in amavisd-new 2.6.3:
| - added a configuration variable @client_ipaddr_policy, which maps smtp
| client's IP address lookup lists to a policy bank name.
In this context what does client mean? So far I thought it is the
MTA that passes mail to check to amavisd-new.
| What's new in amavisd-new 2.6.3:
| - added a configuration variable @client_ipaddr_policy, which maps smtp
| client's IP address lookup lists to a policy bank name.
In this context what does client mean? So far I thought it is the
MTA that passes mail to check to amavisd-new. However it
Is there any way to put a (cryptographically signed) certificate
into the header at the first scan like this Already checked ?
This mark could be recognized in all the following rounds so
amavisd could pass the message without further checks.
A simple Received: by ... header is not
I have a spam filter host (actually it is a cluster but this does not matter)
that serves 2-3 MTAs simultaneously.
One of them is a list server the other is my smart host as well
as MX.
Now if I send a message to a mailing list. The following happens:
1. My desktop machine passes the mail to the
10 matches
Mail list logo
