/dev/joschi - Comments from "Exim 4 and policyd-weight"

Alexander Hosfeld: Exim 4 and policyd-weight

nospam@example.com (Alexander Hosfeld) — Sun, 28 Oct 2007 03:44:43 +0100

Exactly. policyd-weight doesn't close the socket, so exim's readsocket run in a timeout.

With policyd-weight 0.1.14 beta-12 there seems to be a new directive "TRY_BALANCE" which closes each socket after communication if set to '1'.

Andreas Vögele: Exim 4 and policyd-weight

nospam@example.com (Andreas Vögele) — Thu, 30 Aug 2007 16:06:05 +0200

Doesn't work for me. Neither with Debian's Exim 4.63 nor with Exim 4.67. According to the log file policyd-weight is called but it seems that the socket is never closed so that readsocket times out with "socket failure".

Jochen: Exim 4 and policyd-weight

nospam@example.com (Jochen) — Sat, 21 Apr 2007 02:02:50 +0200

If it is not a big hassle for you to upgrade, you should try it. TCP/IP-sockets in ACLs are supported since Exim 4.62, but there could have been some bugs conerning this functionality.

If you want to test policyd-weight first (or fix this bug ), you should replace the "defer" and "deny" verbs in /etc/exim/acl-check-policyd.conf (or whatever you have called the file) with "warn".

Yannick: Exim 4 and policyd-weight

nospam@example.com (Yannick) — Fri, 20 Apr 2007 21:41:29 +0200

Hmm, lsof -i shows many connections:
exim 3027 mailnull 3u IPv4 180038037 TCP localhost:51232->localhost:12525 (ESTABLISHED) etc.etc.
policyd-w 27266 polw 5u IPv4 180038020 TCP localhost:12525->localhost:51228 (ESTABLISHED) etc.etc.
===
exim_mainlog logs temp. rejects for every incoming message. Have exim 4.63, should I upgrade?

Jochen: Exim 4 and policyd-weight

nospam@example.com (Jochen) — Fri, 20 Apr 2007 14:17:41 +0200

Is the socket in /etc/exim/acl-check-policyd.conf correct? Is policyd-weight running? You could check with `netstat` or `lsof` whether policyd-weight has bound the correct network socket.

Anonymous: Exim 4 and policyd-weight

nospam@example.com () — Fri, 20 Apr 2007 00:40:36 +0200

Get a "Cannot connect to policyd-weight. Please try again later." error.
Hmm? I don't use a policyd.conf, just standards.