You've probably reached this page from reading an error message sent back to you from mail.bpfh.net which handles all of the mail for the bpfh.net domain.

bpfh.net runs with reasonably strict anti-spam filters. These are all implemented using sendmail with the check_mail, check_rcpt, check_relay and check_compat rulesets.

Have a look at the sendmail.cf rulesets used at BPFH.

The following anti-spam measures are in place:

	DNS checks
	One of the important checks is that the domain of the sender has to resolve to a real domain. If it does not then the mail is dropped. Quite a bit of spam can be dropped in this way.
	IP checking
	For some sites I block them by IP address.
	Domain blocking
	On getting spam which isn't caught by the above checks I'll often add the sending domain into a list of spamming domains. These domains are blocked from sending me EMail in the future. Sometimes I'll block quite high up the domain chain - for example I'm currently block all of the commerical and network domains with .tw thanks to all of the spam which has originated from those domains.
	EMail blocking
	When I get spam from a domain which I don't want to block out-right, I block just the EMail address.
	SPEWS
	The SPEWS anti-spam list via DNS
	RSL
	The RSL anti-spam list via DNS
	SBL
	The SBL anti-spam list via DNS
	ORDB
	The ORDB anti-spam list via DNS
	Relay checking
	To ensure that my site doesn't get used for relaying spam, there are anti-relay measures in place which ensure that spammers attempting to relay via my site are stopped in their tracks.

I also have several lists which I can use to allow a domain to short-circuit the above rules. This is often done when I want to get mail from a domain which is listed in the MAPS's database.

I review the results of the rulesets each night to ensure that the rules aren't suffering from false positives.