Can anybody point me to the documentation for the penpals feature?
Google: penpals site:http://www.ijs.si/ doesn't come up with much.
tnx!
Terry
--
___
AMaViS-user mailing
Terry,
Can anybody point me to the documentation for the penpals feature?
For starters please read RELEASE_NOTES, starting with:
new feature: pen pals soft-whitelisting lowers spam score ...
If anything is left unanswered by that documentation,
please ask.
Mark
Terry,
Can anybody point me to the documentation for the penpals feature?
For starters please read RELEASE_NOTES, starting with:
new feature: pen pals soft-whitelisting lowers spam score ...
If anything is left unanswered by that documentation,
please ask.
Thanks! That does it.
I
But With this configuration penpals is use for outgoing mail? because
With penpals the outgoing and the incoming mail must pass through
amavisd
you have to turn on originating = 1, in POLICY-OUT and define
$penpals_bonus_score and probably $bounce_killer_score
i prefere to have also a
Hi,
I use postfix with amavisd-new and penpals
With penpals the outgoing and the incoming mail must pass through amavisd.
It's OK for incoming with a content filter in postfix and a check in
amavis with spamassassin and amavis.
but for outgoing how to get outgoing mails only through penpals
On Mon, 23 Mar 2009 21:07:24 +0100, LEVEAU Stanislas wrote:
Hi,
I use postfix with amavisd-new and penpals With penpals the outgoing and
the incoming mail must pass through amavisd. It's OK for incoming with a
content filter in postfix and a check in amavis with spamassassin and
amavis.
Thank Thomas
For example :
Incoming mail : use the existing default policy bank (it has no name).
This bank
loads the settings in the config file (typically amavisd.conf).
Outgoing mail :
Postfix configuration in master.cf :
127.0.0.1:2525 inet n - n - - smtpd
-o
Jo,
My understanding (and I've seen this work) is that it can match just
the message-id, so that someone replying to an alias or a forwarded
message matches the penpal. (this is the case here)
Yes, it should work this way. There are a couple of other restrictions,
like recipient must be
On Sep 16, 2008, at 4:17 AM, Michael Scheidell wrote:
[EMAIL PROTECTED]
Also check the sid and rid from maddr table.
Penpals also matches the ENVELOPE FROM and ENVELOPE TO, not the
header from
and two. (amavisd-new 2.6 might have added header checks also.. I
think it
has the option to
Is it not supposed to check incoming? Anyone know how to make this work
on incoming emails? Here is what I get in my maillog:
Mar 4 13:01:37 dev amavis[77896]: (77896-09) penpals: bonus 98.967, age
0 0:07:00 (420), SA score 0.000, [EMAIL PROTECTED] replying to
[EMAIL PROTECTED], ref
Wazir,
Thanks for your response. That's what I had thought when I started
looking into this, but then I tried it on another box and got the same
results. Here is what I have in amavisd.conf file:
@local_domains_maps = read_hash($MYHOME/etc/local_domains);
.. and in my local_domains file:
Jo,
Jo Rhett wrote:
I see no documentation of determining SMTP-AUTH users from AM.PDP
protocol.
Sorry, I found this in the amavisd-milter documentation. It sets
SMTP_AUTH policy bank for you.
The possibility of passing policy bank names through AM.PDP protocol
are documented in
Mark Martinec wrote:
'originating' is implicitly set by mynets, but you can set it
explicitly, typically from a policy bank.
Mark, I just went back through the documentation and all I can find is a
hack for postfix to use different TCP ports to set different policy banks.
Example use:
Jo Rhett wrote:
I see no documentation of determining SMTP-AUTH users from AM.PDP protocol.
Sorry, I found this in the amavisd-milter documentation. It sets
SMTP_AUTH policy bank for you.
In general the amavisd document is far too postfix-specific. Would you
accept patches which separated
I've got it set up for penpals support according to the release notes.
Messages are being saved in msgs table, but there's no evidence that
penpals support is working at all. log_level2 shows no penpals
comments.
* @mynetworks and @local_domains_maps must reflect reality,
allowing
Okay, so here is the guilty code:
elsif (!c('originating') $sender ne ''
lookup(0,$sender,@{ca('local_domains_maps')})) {}
# no bonus to senders from outside using local domain, can't trust
them
I'm not sure what sets originating, but it seems to read that if
it's a
Jo,
Okay, so here is the guilty code:
elsif (!c('originating') $sender ne ''
lookup(0,$sender,@{ca('local_domains_maps')})) {}
# no bonus to senders from outside using local domain, can't trust
them
I'm not sure what sets originating, but it seems to read that if
On Jan 3, 2008, at 5:05 PM, Mark Martinec wrote:
'originating' is implicitly set by mynets, but you can set it
explicitly, typically from a policy bank.
Understood. It doesn't affect this, however:
* One of the major sources of false spam reports is mail coming from
the blackberry servers.
I know this must be something I've overlooked as it just seem so
silly that penpals would work in reverse order.
All outbound email from my location sends through a SMTP server which
forwards to the AMAVIS filtering server before leaving the
network. Inbound email comes into the AMAVIS
Of additional note, when I add a little more debugging code to
amavisd in the penpals sections, it seems regardless if a domain is
local or not (or even in cases where @local_domain_maps is undefined
i find the following:
lookup(0,$sender,@{ca('local_domains_maps')}) ALWAYS returns Y
This is
Nate,
In this setup, there are thousands of domains being scanned, and
amavis as well as postfix utilize a mysql db to determine where
to forward the email after it's scanned via a postfix transport
table. With this setup, I typically leave @mynetworks and
@local_domains_maps undefined and
Nate,
Of additional note, when I add a little more debugging code to
amavisd in the penpals sections, it seems regardless if a domain is
local or not (or even in cases where @local_domain_maps is undefined
i find the following:
lookup(0,$sender,@{ca('local_domains_maps')}) ALWAYS returns Y
At 05:29 PM 9/7/2007, Mark Martinec wrote:
Of additional note, when I add a little more debugging code to
amavisd in the penpals sections, it seems regardless if a domain is
local or not (or even in cases where @local_domain_maps is undefined
i find the following:
Hi,
I currently have postfix listening on port 25 with amavis, and
on 2525 that only allows SASL authenticated users and no amavis.
Is there any way of passing the SASL authenticated users through
amavis with no checking so that it can build up a penpals list?
Or passing the fact that the mail
Lawrence,
I currently have postfix listening on port 25 with amavis, and
on 2525 that only allows SASL authenticated users and no amavis.
Is there any way of passing the SASL authenticated users through
amavis with no checking so that it can build up a penpals list?
Or passing the fact that
I am very interested in setting up the penpals feature and I see that this
relies upon SQL logging. README.sql-mysql.txt gives some info but I do not
find it very clear. I figure I need to create a database, say, amavisd, and
then create the 'msgs' table like shown in the docs?
CREATE TABLE
Peter,
I am very interested in setting up the penpals feature and I see that this
relies upon SQL logging. README.sql-mysql.txt gives some info but I do not
find it very clear. I figure I need to create a database, say, amavisd,
and then create the 'msgs' table like shown in the docs?
See
Hi!
Thanks for the penpals feature!
However sometimes, the replies that should be white-listed are sent
using different from-addresses. In this case, the current
pen-pal-feature won't work.
But if the follow-up correspondence is a real reply, the References or
In-Reply-To headers will contain
28 matches
Mail list logo
