Mail appeared to be SPAM or forged

[pstanbra]

(09-10-2011 10:09 PM)kilburn Wrote:  First of all, this is simply policyd-weight doing its job, so it will not be fixed because it is not a bug.



In the later case, the problem is that the sender's ISP is badly configured. At this point you have three options: (1) Notify the user's ISP about their misconfiguration, and wait for them to solve it;

I would not say it is in configured. The client simply sends mail through his ISPs SMTP server.

(2) Disable policyd-weight completely by removing the corresponding "check_policy_service" line from /etc/postfix/main.cf (there are two policy_services, one is postgrey and the other policyd-weight);

Surely everyone with this version on isp-control faces these problems. There are many people out there if not most that have a domain based email address sending through an external SMTP server or smarthost. Is it wise to simply disable this checking or is there another workaround? If this affects so many people - why is it not disabled by default?
This comment comes from using things such as plesk and control panel where there is no such user config needed - install and go is all that is needed.

or (3) Add a sender_dependent whitelist and list the badly configured ISPs there.

too many clients to manage - ok for one off problems i guess

---

http://isp-control.net/forum/thread-1506...eight.conf
This post helped me deal with policyd-weight.
This has *i think* resolved part of the problem.

Still having issues with users Sending mail TO a blacklisted IP