First, it's useful to know that a Sender Policy Framework (SPF) is a system designed to identify and protect against email fraud by providing a way to allow corresponding email providers to check that messages sent from a particular domain are coming from a server authorized to send email on that domain's behalf. Without this important bit of information specified within your website's DNS records, some email clients may filter or block your email messages.
Setting up SPF can sound like a confusing process, but you don't need to be an expert in this area to get the job done -- you just need the help of someone who is. That's why you will want to ask your IT staff, website administrator, someone at your ISP to help you.
If you want to learn more about SPF, or if your technical person does, direct them to: http://www.openspf.org/. The Deploying SPF section is a good one to read and the folks who read the forums can likely help with any configuration questions that come up.
In addition to setting up your in-office email to work with SPF, the technical person assisting you will need to configure your DNS record to work with thedatabank's servers. You can tell them that thedatabank said this is what should be added to the record:
|v=spf1 ip4:188.8.131.52 ip4:184.108.40.206 ip4:220.127.116.11 ip4:18.104.22.168 include:spf.protection.outlook.com -all|
By adding the above info to your organization's DNS record, you are telling the world that it's okay that thedatabank is sending email on behalf of your organization. Not only that, but with this task out of the way, you'll be ensuring more messages actually reach the inbox of your organization's supporters.