-----BEGIN PGP SIGNED MESSAGE-----
Lazy git that I am I only quite recently configured DMARC for
bsdly.net, and it actually had at least some of the desired effect:
that domain's mail traffic started coming through to Google-hosted
domains, and whenever somebody makes a new contribution to the
spamtraps collection, I get reports from DMARC-reporting domains as
well as the usual traces in the greylist.
The only downside is, the traditional forwarding that mailing lists do
*also* triggers the DMARC dark magic, and there is a significant risk
that messages sent with senders in DMARC domains via the mailing list
to recipients with a somewhat DMARC-aware setup will be discarded.
However, the solution or workaround is to set up the mailing list for
the DMARC magic to do some benign rewriting of headers - the message
at  describes how the FreeBSD list admins solved the problem for
If the OpenBSD list admins are reading this: would it be possible to
make a similar change in the OpenBSD mailing list configuration?
All the best,
 http://www.bsdly.net/~peter/traplist.shtml, also
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd: 220.127.116.11: disconnected after 42673 seconds.
-----END PGP SIGNATURE-----