You can use any of the below scenarios when setting up your email, here are the pro's and con's to help you make your decision:



Scenario 1 (recommended for most users)


Client uses our default clientname.kma05.co.uk sender domain


Pros.  

  • Clean, simple out of the box set up, we do all the DNS config and if spammy emails go out, there’s no harm done


Cons.

  • A few email providers show the ‘Email delivered by clientname.KMA05.co.uk’ tooltip




Scenario 2


Client uses their own domain as the sender domain


Pros.

  • Great deliverability and very on brand


Cons

  • If spammy emails go out, the client’s own day to day emails may stop getting delivered.  Bad!

  • Can’t work if they’re already using a third party delivery provider, such as Google, as MX records will conflict

  • Requires client to configure their own DNS records



Scenario 3 (second recommendation)


Client uses their own sub-domain as the sender domain


Pros.

  • Great deliverability and very on brand

  • Will still work if they’re already using a third party delivery provider, such as Google, as MX records will no longer conflict

  • Although the send from email address will be from the subdomain email, the reply to can still be from the original client email, so email replies are still correctly routed to the correct email address


Cons

  • Sender email must also be from sub-domain, otherwise a few email providers will show the ‘Email delivered by comms.clientdomain.com’ tooltip. 

  • In the unlikely scenario that someone ‘replies all’ to an email (most email clients won’t allow this to happen), a bounce back will be generated from the ‘send from’ email address (however, the ‘reply to’ email address will still go through to the correct recipient)

  • Requires client to configure their own DNS records



Scenario 4


Client uses their own sub-domain as the sender domain AND sets up the subdomain email as a valid email address (this is something that only the client can do)


Pros.

  • Great deliverability and very on brand

  • Will still work if they’re already using a third party delivery provider, such as Google, as MX records will no longer conflict


Cons

  • Sender email must also be from sub-domain, otherwise a few email providers will show the ‘Email delivered by comms.clientdomain.com’ tooltip. 

  • Requires client to configure their own DNS records

  • Highly unlikely that the client will want to do this as it’s even more config for them, and there really is no benefit to them