You mean your local users are sending spam? You should be talking to those users…not us. 
A default configuration, as installed by install.sh, will only allow relaying in the following circumstances:
The sending client authenticates using SASL. They have a valid user name and password on your system.
Or, the sending client is “local”. Either running on the machine itself, or on an IP that you’ve specified in your mynetworks setting.
Note that in either case, the From: address is irrelevant. Any email can send with any From: address they want…and there are all sorts of reasons this is a legitimate thing (mailing lists with special From magic, users using multiple email addresses for various tasks, etc.).
It sounds like you’re wanting to go about this from entirely the wrong end. You need to solve your spam problem…not prevent people from sending out email with an address not on your approved list. Spammers don’t care what address is in the From: field. Find out how someone is spamming through your box, and fix that.
You’ve probably had an exploited user account. Someone broke in either via a brute force password attack (due to weak passwords), or due to an exploit in a web application. Once they were in, they setup a bot to send spam 24 hours a day. Since they’re local, they have nothing preventing them from sending out as much spam as your bandwidth allows. The RBL would be absolutely right to list you, if you’ve got an exploited system sending out spam.
If you do insist on using a map, rather than solving the real problem, you need to leave off the ".db" part of the file name. The db is generated by Postfix from the plain text file.
Also, the smtpd_client_restrictions doesn’t have a “check_sender_access” directive. I assume you really wanted “smtpd_sender_restrictions”, which does have check_sender_access. Reading the manpage makes me think you might need a separate file; virtual seems to be a slightly different format from access (access only has one field, while virtual has two). But maybe it’ll ignore the second field when used in this context. That seems pretty likely, actually…
But, again, that’s not going to solve your problem. You have either have a gross misconfiguration of mynetworks (which needs to be fixed), or you have an exploited user account (which really needs to be fixed). Putting your fingers in your ears and saying, “LALALALALALA, I can’t hear you!” is roughly the solution you’ve proposed…and I don’t think that’s the right tactic. 