Hi Anthony, Anthony J. Bentley wrote on Sun, Feb 15, 2015 at 03:19:48AM -0700:
> More importantly, though, it matches groff. Yes. We shouldn't change mandoc(1) without changing groff(1) in parallel. > Here is a patch that corrects spamd(8). I can look at pages that > use it for headers later... a quick grep reveals less than 20. OK schwarze@ for the patch below. Ingo > Index: libexec/spamd/spamd.8 > =================================================================== > RCS file: /cvs/src/libexec/spamd/spamd.8,v > retrieving revision 1.125 > diff -u -p -u -p -r1.125 spamd.8 > --- libexec/spamd/spamd.8 7 Feb 2015 18:05:57 -0000 1.125 > +++ libexec/spamd/spamd.8 15 Feb 2015 10:17:38 -0000 > @@ -268,11 +268,11 @@ regularly scans the > .Pa /var/db/spamd > database and configures all whitelist addresses as the > .Xr pf 4 > -.Aq spamd-white > +<spamd-white> > table, > allowing connections to pass to the real MTA. > Any addresses not found in > -.Aq spamd-white > +<spamd-white> > are redirected to > .Nm . > .Pp > @@ -385,7 +385,7 @@ spamtrap address, > it is blacklisted for 24 hours by adding the host to the > .Nm > blacklist > -.Aq spamd-greytrap . > +<spamd-greytrap>. > Spamtrap addresses are added to the > .Pa /var/db/spamd > database with the following > @@ -468,7 +468,7 @@ a slightly modified > .Xr pf.conf 5 > ruleset is required, > redirecting any addresses found in the > -.Aq spamd > +<spamd> > table to > .Nm . > Any other addresses > @@ -488,7 +488,7 @@ like: > .Pp > .Xr spamd-setup 8 > can also be used to load addresses into the > -.Aq spamd > +<spamd> > table. > It has the added benefit of being able to remove addresses from > blacklists, and will connect to
