[Tickets #4904] Re: A Postfix policy daemon to manage white/blacklisting

bugs@bugs.horde.org bugs at bugs.horde.org
Wed Jan 17 01:47:17 PST 2007


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=4904
-----------------------------------------------------------------------
 Ticket             | 4904
 Updated By         | robb at wtg.cw.com
 Summary            | A Postfix policy daemon to manage white/blacklisting
 Queue              | Ingo
 Version            | HEAD
 Type               | Enhancement
 State              | Feedback
 Priority           | 1. Low
 Owners             | 
-----------------------------------------------------------------------


robb at wtg.cw.com (2007-01-17 01:47) wrote:

I understand your reservations. My main reasoning behind this is to avoid
accepting email you are not going to deliver, call me a zealot but I think
this is bad.

The daemon should be fairly simple to write, could probably be writen to
run from php on the command line and should share a bit of code with Ingo.
Reading directly from the horde_prefs table seems to make the most sense. I
worry that anything outside of the Horde project would not necessarily be
well maintained and would have to duplicate code to de-serialize Horde's
preferences.

The next best alternative to this I can see is it being posible for Ingo
to write it's black/whitelist out to a external database table without
serialization. This could be good in that other external apps might be
able to refer to this table for the information they require.

I'm willing to put a bounty of $100 on either of these two solutions (not
both :o)




More information about the bugs mailing list