In your config above you have Spamassassin and Policyd(v2 Cluebringer).
Email was fed to Policyd, because of this configuration
smtpd_end_of_data_restrictions = check_policy_service inet:127.0.0.1:10031
That means postfix will send email to Policyd who listen at port 10031. You can find out about check_policy_service parameter in this page: Postfix SMTP ...
I would recommend you to upgrade to postfix 2.8+ and deploy postscreen; this is specifically designed as a zombie/DNSBL triage server and handles multiple blacklists at high speed.
It also offers fully-weighted black/whitelist scoring, explicit whitelisting, and more.
With respect to your second question, I suggest you check out spamass-milter; an in-line ...
According to the logs, the message was rejected by list dnsbl.sorbs.net.
As described on Introduction from Using SORBS
As a prospective user of the SORBS lists the most important question
you need to ask yourself is: Do I understand the listing criteria for
the list(s) I plan to use?
Then, you have a number of choices/decisions to make:
I realize this question is old, but it may help others that stumble upon it.
Just define a quota linked to your default policy that tracks the sender over a period of 3600 seconds,
And then apply a limit to said quota:
No, you can't
The quota counters get incremented by number of recipient. That is, if I send one mail message to 6 recipients, it will be blocked. What must I change in order to make policyd track number of messages instead of number of recipients?
Of course it will blocked. When you send email to 6 recipients, basically postfix (in Zimbra) will send copy ...
Do you really mean that Postfix sends a bounce? Or do you mean it rejects the incoming message with a 5xx code and then the sending MTA sends a bounce? Also, you don't say how policyd is configured - it tells Postfix whether to REJECT (5xx) or DEFER (4xx), and I'm guessing you want the latter so that the sending MTA retries until the user is under quota ...
In case of Postfix version 2.10 or newer, you can try to solved those problem by using smtpd_relay_restriction feature. Snippet from postfix documentation explains how to use them properly.
Relay policy is specified under smtpd_relay_restrictions, and the spam blocking policy under smtpd_recipient_restrictions.
Then your configuration should like this
Both software created with different purpose.
Postgrey purpose is for do greylisting, e.g. soft reject whenever client connect on first attempt.
Policyd primary purpose was adding some advanced policy control for postfix. It can configured to perform various smtp response (REJECT, HOLD, ACCEPT, etc) based on various statistic from sender/recipient/client. ...
Zimbra is email and collaborative suits. It uses postfix as MTA. You can optionally enable policyd to provide limiting features such as quota or throttle.
Every configuration can be altered by web interface or CLI. Direct editing to configuration file / database shouldn't be done. Zimbra could overwrite it when upgrading or restarting.
You defined the policy check in smtpd_*_restrictions, therefore it will never be queried for mail generated locally, because this kind of mails is injected into the Postfix queue using the pickup(8) service. To circumvent this, you will need to modify master.cf and add a content_filter instance to the pickup(8) service (and of course, you will also need to ...
It is the normal behavior.
Please do NOT use relays.ordb.org. It is dead for five years.
Please do NOT use list.dsbl.org. It is dead for three years.
Don't use SBL, XBL and SBL-XBL if you already use ZEN! See http://www.spamhaus.org/zen/
Your Postfix setup is heavily broken!!!
And you do not know that recipients can't be "blacklisted". Only IPs or ...
That is all you need to do with Postfix but you need to fill up mysql database used by Policyd.
Copy web files from webui dir to web accessible dir.
Open the page and set up what you want (quotas, limits etc.).
Do not forget to create some kind of user/pass access control (for example via .htaccess/.htpasswd file...