WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/libexec/spamd/Makefile?h=jd%2Fqueueboosts 2015-02-07T10:45:19Z 2015-02-07T10:45:19Z henning henning@openbsd.org 2015-02-07T10:45:19Z urn:sha1:a2913c44cb7f5c198ff8f2f723e9cc379cd5785c Rationale: when you publish DANE records for certificate pinning, you MUST offer TLS on the indicated service. Not offering TLS is verboten since that would re-open the door for a MitM. This is obviously fundamentally incompatible with having spamd in front of your mailservers - spamd kinda is a MitM here, but intentional and utterly valid. DANE is desirable because it allows one to not have to trust the broken SSL CA model, and, depending on the mode chosen, even show the SSL cert mafia the middle finger by not needing them at all. ok reyk jsing bob 2013-08-21T16:13:29Z millert millert@openbsd.org 2013-08-21T16:13:29Z urn:sha1:51210d5c4143f40e4bb22955bd7f630657489cf1 with backwards compatibility for records with 32-bit times. OK deraadt@ beck@ 2007-03-04T03:19:41Z beck beck@openbsd.org 2007-03-04T03:19:41Z urn:sha1:98babcad66c249fea6b5d43e49c6cf1927a97ae9 This adds an HMAC protected synchronization protocol for use by spamd and spamlogd. - spamd can receive updates from other hosts for GREY, WHITE, and TRAPPED db entries, and will update the local /var/db/spamd accordingly. - spamd can send updates when it makes changes to the GREY or TRAPPED entries in the db to other hosts running spamd. (Note it does not send WHITE entries because the other spamd will see the GREY changes and have complete information to make appropritate decisions) - spamlogd can send updates for WHITE db entries that it performs on the local db to other hosts running spamd, which will then apply them on remote hosts. note that while this diff provides synchronization for changes made to the spamd db by the daemons, it does *not* provide for sychonizing changes to the spamd db made manually with the spamdb command. Synchronization protocol and most of the work by reyk@, with a bunch of the spamd, and spamlogd stuff by me. testing mostly at the U of A, running happily there under big load. ok reyk@ jmc@ 2005-05-24T22:23:04Z millert millert@openbsd.org 2005-05-24T22:23:04Z urn:sha1:b051393d7dd4f18c8c5c2603032c4db6eb790c0c 2004-02-26T07:28:54Z beck beck@openbsd.org 2004-02-26T07:28:54Z urn:sha1:1f68c1d423a18ba467ea103f8d8bc128a0f56830 originates from a paper by Evan Harris which can be found at http://projects.puremagic.com/greylisting/. This implementation makes spamd allow for non-blacklisted addresses to be treated as "greylisted". where they are tracked in a db file, and whitelisted by addition to a pf table when the same envelope from and to are retried from the same source IP address. Testing by many, ok deraadt@ 2003-07-02T22:44:11Z deraadt deraadt@openbsd.org 2003-07-02T22:44:11Z urn:sha1:a84cba683c5c538c8f1f4acfdf70af740e018525 2003-03-08T18:17:04Z beck beck@openbsd.org 2003-03-08T18:17:04Z urn:sha1:6c461b1bd50fc00358312a61065ea2856f31a008 2003-03-02T23:55:11Z cloder cloder@openbsd.org 2003-03-02T23:55:11Z urn:sha1:f2aeda32ce6c5017f5f4084f65c7705f61358622 -ansi -Wstrict-prototypes, update the Makefile to reflect that. 2003-03-02T19:21:59Z beck beck@openbsd.org 2003-03-02T19:21:59Z urn:sha1:461ebb7f34cf6f742c3acfe08a118e45d5b5daa9 which configures individual blacklists sources and deals with whitelists. Perl still needs some stylistic changes as suggested by bmc which will go in shortly. ok deraadt@ 2003-02-14T05:32:02Z jason jason@openbsd.org 2003-02-14T05:32:02Z urn:sha1:b88e1712598e69b30a39c91b767d25f5f5482f29