How to Change a Service Email Address

This document aims to explain the process for changing the email address for one or more of your services. There are a number of reasons as to why you may want to do this, such as a rebranding of your Institution, as part of a merger, or maybe due to the renaming of a particular service.

The changing of your Email Address is a paid service and should be organised via your Key Account Manager

Overview of The Process

1. Main institution contact gets in contact with their Key Account Manager requesting an email address change, your request should include:

A contact within your IT department who has knowledge of your institution email setup
Your current email address utilised by the platform
The new email address (that we will be changing it to), we require up to three pieces of information here:
1. Your 'From Address' (this is the address that users will receive emails from): ie future@careers.university.ac.uk
2. Your 'Reply-to Address' (this is the address that the user will appear to be responding to). This can be left blank if you only intend to send emails from this address, or often it is the same as your 'From Address'
3. Your 'To Address' (this is the recipient address for testing purposes only)

With DKIM, we highly recommend that you utilise an email address with a subdomain ie future@careers.university.ac.uk for routing emails from a From Address - you can still use a Reply-to Address like future@uni.ac.uk .

Any timescales you would like to adhere to
Any queries in relation to the costing processes
Your Key Account Manager will then raise a Technical Integration Helpdesk request, including you and your technical contact in the communication.

2. Our Technical Integration team will communicate with your IT department in regards to next steps, seen below. These can vary depending on how your Institution implements email routing.

Technical Note: unless absolutely not an option, we utilise DKIM as a preferred solution to email routing. DKIM is now the industry standard and will help us to support ongoing service improvements. DKIM also gives a better service to your users as the email will appear to arrive directly from your instituion and does not require a physical routing solution or an @targetconnect.net address. The remainder of these instructions will assume that the new email address utilises DKIM with a subdomain.

3. Your IT team will need to create two DNS records:

	Record 1	Record 2
Name of Record	<subdomain>.university.ac.uk	mailtcex._domainkey.<subdomain>.<university>.ac.uk
Record Type	CNAME	CNAME
Points To	tcmailservice.targetconnect.net	To be confirmed at time of change

You can also apply a DMARC policy to this subdomain by creating a TXT record _dmarc.<subdomain>.university.ac.uk should you like to do so

4. We will generate DKIM keys and publish them along with SPF on our side, you won't have to worry about adding anything to your own SPF record

We use a 2048 bit DKIM key

5. We will prepare our back end and test email delivery/signing for the subdomain we've set up

6. We will set up the service addresses (from, reply-to, to address) on the platform as per your initial instructions

7. Your institution should then conduct final mailing tests from the system

Throughout the process, our Technical Integration and Customer Success teams will be on hand to help

Root Domain Setup

While we do not advise using a root domain for your email ie careers@university.ac.uk as opposed to careers@department.university.ac.uk, we can support it and the steps are broadly similar to a subdomain setup above. The key difference is that your IT team will need to create/edit different records in comparison to step 3. They will need to:

Add an 'include:tcmailservice.targetconnect.net' statement to the SPF record of your domain ie 'university.ac.uk'
Add a new CNAME DNS record 'mailtcex._domainkey.<rootdomain>.ac.uk' that points to 'dkim_<rootdomain>_ac_uk.targetconnect.net'