Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 237
  • Last Modified:

How do I add a domain to my SPF record to only allow them to send from one mailbox account?

I have been asked by a company to configure my SPF record (presumably done through my mail host site i.e. names.co.uk) to allow their domain the ability to send-as on one of our mailboxes.  Their request appears to grant them the ability to send-as on any of our mailboxes, is this the case?  I am not sure how they can only have access to that particular e-mail address e.g. customerservice@mydomain.com.

Thanks
0
fuzzyfreak
Asked:
fuzzyfreak
  • 4
  • 3
2 Solutions
 
Dan McFaddenSystems EngineerCommented:
SPF has nothing to do with mailboxes.  It is a special DNS record that tells other mail servers, that are SPF aware, what servers are authorized to send emails for specific DNS domains.

Info about SPF:
1. http://www.openspf.org/Project_Overview
2. http://en.wikipedia.org/wiki/Sender_Policy_Framework

If you want to create a SPF record for a domain, you could use the following online wizards to help you create a properly formatted DNS record:

1. http://www.spfwizard.net/
2. http://www.microsoft.com/mscorp/safety/content/technologies/senderid/wizard/
 
Dan
0
 
Dan McFaddenSystems EngineerCommented:
You can test out your SPF record using this online tool:

http://mxtoolbox.com/spf.aspx

Dan
0
 
fuzzyfreakAuthor Commented:
Thanks Dan, so in answer to my question "Their request appears to grant them the ability to send-as on any of our mailboxes, is this the case?"
0
NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

 
Dan McFaddenSystems EngineerCommented:
No.  SPF helps prevent spoofing and forging of emails for a given DNS domain.  

It would be better to think of it as giving permission to send emails with your domain attached from their server(s).  Nothing to do with mailboxes.  SPF does not grant them access to mailboxes on your servers.  They could just create any number of email addresses they wanted... none of which would have to be related to an actual mailbox on your servers.

To quote Wikipedia:


SPF allows the owner of an Internet domain to specify which computers are authorized to send mail with sender addresses in that domain, using Domain Name System (DNS) records. Receivers verifying the SPF information in TXT records may reject messages from unauthorized sources before receiving the body of the message. Thus, the principles of operation are similar to those of DNS-based blackhole lists (DNSBL), except that SPF uses the authority delegation scheme of the Domain Name System.

What implementing SPF does is tell other mail servers that the mail servers listed in this special DNS record are allowed to be a source for emails originating from the DNS domain in question.  There is no user level authorization going on here.  This is at the server level communication... SMTP and DNS.

Someone would still need a mechanism to actually create these emails and send them through a server included the SPF record for the domain in question.  Realizing the source server may not (most likely will not) be a server your company controls.

If you already have an SPF record in place, you will need to add this other server to your record.  You are essentially granting this third party to right to forge emails to look like they are coming from your messaging system when they coming from a different messaging system.

SPF is not like granting someone "Send As" permission in Outlook on an Exchange Mailbox.

Dan
0
 
fuzzyfreakAuthor Commented:
Yes, sorry Dan I get that and realise my question should have been rephrased to avoid any mention of mailboxes, however your answer has made it even more clear to me and I appreciate the comprehensive clarification.
What I really wanted to know was, could this be open to abuse? - I am effectively giving this company permission to send through my DNS and look like it is coming from us - I guess it raised my sysadmin alarm bells and wondered if I could put something in place to only allow them to send e-mails that match customerservice@mydomain.com - which, I am assuming will not be possible.
0
 
Asif BacchusCommented:
Dan has given you an excellent explanation of how SPF works and it's all very good reading.  To answer your question succinctly however, no you cannot bind an SPF entry to one mailbox/address.  SPF applies to entire domains (or subdomains) and lists allowed servers, hostnames and IP addresses for that entire domain.  

Therefore, if you add your client's mailserver as a permitted sender for mydomain.com then you are saying that they are a valid sender for any address at mydomain.com regardless of the specific address/mailbox.

HTH
0
 
Dan McFaddenSystems EngineerCommented:
What I really wanted to know was, could this be open to abuse?
- theoretically yes, it could be abused.  Since this is a third party, who know what goes on in/on their servers.  There could be any number of things that could allow something to go wrong.  Hardware issues, software issues or misconfigurations... and let's no forget the people managing those servers or the people using.

wondered if I could put something in place to only allow them to send e-mails that match customerservice@mydomain.com
- see question 4 below.

My questions are:
1. why was this requested?
2. for what purpose will it be utilized?
3. is this an IT use or a Business use case?
4. could you give them an account on your mail server and grant them secure access to it? (think Exchange and OWA)
4a. would this solve the use case?

Dan
0
 
fuzzyfreakAuthor Commented:
Excellent and comprehensive answers to my questions.
0

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now