whitelist for policyd ?

[macbishop]

Hello.

I have a recipient address that it's rejected for policyd.

In first time

Code:

retrying too fast. penalty: 30 seconds x 0 retries

and in second attempt

Code:

Mail appeared to be SPAM or forged

How can I clean it in policyd ?

Debian 4.0
trunk 974

[rbtux]

add

check_client_access hash:/etc/postfix/policyd_whitelist,

before

check_policy_service inet:127.0.0.1:12525


then open /etc/postfix/policyd_whitelist and put:

ip.of.problem.server OK

in there.

You can also do that with the recipient address (use check_recipient_access instead of check_client_access) but that is not recommandable because the sending server is the problem here...

[macbishop]

rbtux Wrote:add

check_client_access hash:/etc/postfix/policyd_whitelist,

before

check_policy_service inet:127.0.0.1:12525


then open /etc/postfix/policyd_whitelist and put:

ip.of.problem.server OK

in there.

You can also do that with the recipient address (use check_recipient_access instead of check_client_access) but that is not recommandable because the sending server is the problem here...

ok. rbtux, I will try

thanks.

[macbishop]

runs fine. but...
why policyd filter this IP and postgrey not ?

[joximu]

policyd-weight is not the same as postgrey.

policyd-weight: is like several Blacklists and some other spam-recognition tools combined together and weighted...
So: you'll need a whitelist for the poor guy sending from a spamming IP address.

postgrey: it forces the mailserver to send the first mail to a certain person twice, so the old spam senders were sorted out.
You'll need a white list there for the mail servers which do not comply to the rfc standards (there once were some windows smtp machines which did not send a mail twice...)

/J

[macbishop]

joximu Wrote:policyd-weight is not the same as postgrey.

policyd-weight: is like several Blacklists and some other spam-recognition tools combined together and weighted...
So: you'll need a whitelist for the poor guy sending from a spamming IP address.

postgrey: it forces the mailserver to send the first mail to a certain person twice, so the old spam senders were sorted out.
You'll need a white list there for the mail servers which do not comply to the rfc standards (there once were some windows smtp machines which did not send a mail twice...)

/J

ok. thanks for the clarification

[pgentoo]

RE:
check_recipient_access
check_client_access

So can you point both checks to the same file, and mix IP's, hostnames, and senders in this one file? Or do you have to keep these separate and reference different files?

Also, i see that policyd supports getting all these items from mysql. Is there a reason we didn't setup ispcp like this? Future plans? http://policyd.sourceforge.net/readme.html

Anyone running with this stuff in the DB? It would be REALLY nice to allow users to change these settings for their spam filtering...

Thanks,
pGentoo

[kilburn]

Beware that policyd-weight (the one used in ispcp) is not the same as policyd (the one you're mentioning)!

[pgentoo]

Hrm, i have both installed on my system... So maybe only one of them is being used?

[kilburn]

It depends on how many check_policy_service directives you have in the smtpd_recipient_restrictions of /etc/postfix/main.cf. As additional info, ispcp uses port 12525 for policyd-weight and 60000 for postgrey.