# How to configure a custom sender identity

By default, the sender address of all emails coming from an Eventscase platform would be <noreply@eventscase.com>. If you would like to use  a custom sender identity that includes your own domain, you have two options:

## Use Eventscase's Mandrill account

{% hint style="danger" %}
Please confirm with your Project Manager first if this is a viable step. Whitelabelling options have to be included in your contract and your use of our transactional email platform has to be assessed first by our team. You may only use Eventscase's Mandrill account if your use is limited to sending automatic emails or simple announcements to your confirmed attendees.
{% endhint %}

### Step 1: Purchase or secure your own domain from a domain registrar if you still do not have one

### Step 2: Provide an email address that contains your domain to your project manager (e.g., <firstnamelastname@yourdomain.com>)

### Step 3: You would need to set up DNS records. Create two CNAME records for the Domainkeys Identified Mail (DKIM)

Create two CNAME records: one with the name `mte1._domainkey.yourdomain.com` with the value `dkim1.mandrillapp.com`, and another with the name `mte2._domainkey.yourdomain.com` and the value `dkim2.mandrillapp.com`&#x20;

### Step 4: Create a TXT record for the Domain-based Message Authentication, Reporting, and Conformance (DMARC)

Create and save a TXT record in your DNS with a name of `_dmarc.yourdomain.com` and a value of `v=DMARC1; p=none`

{% hint style="info" %}
For steps 3 and 4, replace *`yourdomain.com`* with the domain you're setting up. Some domain hosts automatically add `yourdomain.com` after the initial value—contact your domain provider for any specifics.
{% endhint %}

### Step 5: Configure the SPF record (Optional)

If you don’t already have an SPF record, add the following to your DNS:

```
v=spf1 include:spf.mandrillapp.com ~all
```

If your domain already has an existing SPF record, just modify it by adding the following mechanism: <mark style="background-color:yellow;">include:spf.mandrill.com</mark>

Here is ane example. You modify this:

```
v=spf1 +a +mx +ip4:31.170.123.22 include:secureserver.net ~all
```

To this:

```
v=spf1 +a +mx +ip4:31.170.123.22 include:secureserver.net include:spf.mandrillapp.com ~all
```

### Step 6: Inform your Project Manager that you have already created the necessary DNS records. Please also provide your desired sender address (e.g., <events@yourdomain.com>, <noreply@yourdomain.com>, etc.).

### Step 7: Once your Project Manager has confirmed that the sender address has been set up, you may now send test emails to yourself and verify this information

## Use your own Mandrill account

{% hint style="success" %}
We highly recommend that you use your own Mandrill account if you are going to send out mass emails to your contact list. If the nature of your emails is related to marketing or RSVP-ing, you would need to secure your own Mandrill account. Please consult your Project Manager before proceeding since whitelabelling options also have to be included in your contract to make this change.
{% endhint %}

We have to set up the integration between Eventscase and Mandrill in order for all outgoing emails from your platform to come from a sender address that utilises your custom domain.

### Step 1: Create a Mailchimp account and add Mandrill

Create a [Mailchimp](https://www.mailchimp.com/) account if you do not already have one and [add Mandrill](https://mailchimp.com/en/help/add-or-remove-transactional-email/).

### Step 2: Purchase your domain (from a domain registrar) if you do not have one and configure it in Mandrill&#x20;

You will need to set up your domain so that Eventscase can send emails from Mandrill. Go to ***Settings > Domains > Sending Domains***, enter in your domain, and click on ***+*** ***Add***:

<figure><img src="/files/vGsDAiBphy8swNQycWMa" alt=""><figcaption></figcaption></figure>

A domain that has not been set up yet will look like this:

<figure><img src="/files/cQrBfS7eQmgJo9YMKY62" alt=""><figcaption></figcaption></figure>

### Step 3: For the "Verified domain" column, click on "View details" and add your email address. You will receive a verification link. Simply follow instructions within the email.

<figure><img src="/files/0I0nsSzGtwmcKVESlrQy" alt=""><figcaption></figcaption></figure>

### Step 4: You would need to set up DNS records. Create two CNAME records for the Domainkeys Identified Mail (DKIM).

Create two CNAME records: one with the name `mte1._domainkey.yourdomain.com` with the value `dkim1.mandrillapp.com`, and another with the name `mte2._domainkey.yourdomain.com` and the value `dkim2.mandrillapp.com`&#x20;

### Step 5: Create a TXT record for the Domain-based Message Authentication, Reporting, and Conformance (DMARC)

Create and save a TXT record in your DNS with a name of `_dmarc.yourdomain.com` and a value of `v=DMARC1; p=none`

{% hint style="info" %}
For steps 4 and 5, replace *`yourdomain.com`* with the domain you're setting up. Some domain hosts automatically add `yourdomain.com` after the initial value—contact your domain provider for any specifics.
{% endhint %}

### Step 6: Configure the SPF record (Optional)

If you don’t already have an SPF record, add the following to your DNS:

```
v=spf1 include:spf.mandrillapp.com ~all
```

If your domain already has an existing SPF record, just modify it by adding the following mechanism: <mark style="background-color:yellow;">include:spf.mandrill.com</mark>

Here is ane example. You modify this:

```
v=spf1 +a +mx +ip4:31.170.123.22 include:secureserver.net ~all
```

To this:

```
v=spf1 +a +mx +ip4:31.170.123.22 include:secureserver.net include:spf.mandrillapp.com ~all
```

### Step 7: After completing steps 3-5, click on "Test DNS Settings".

A successful configuration would look like this:

<figure><img src="/files/lG8NLSWyPsxuZVblKswr" alt=""><figcaption></figcaption></figure>

### Step 8: Create API Keys for Eventscase

Go to Settings and click on ***+*** ***New API Key***:

<figure><img src="/files/ptrrnig4hkgWq5gimAkb" alt=""><figcaption></figcaption></figure>

Name your API key into something like Eventscase API and click on ***Create API Key*** when you're ready:

<figure><img src="/files/I1ZQKTWkSu64f6VUCEGi" alt=""><figcaption></figcaption></figure>

You may now extract your API key and give it to your Project Manager at Eventscase so he/she can complete the integration:

<figure><img src="/files/jykSwwuVWJhow8ZCDHgB" alt=""><figcaption></figcaption></figure>

Example API key:

```
FJ9ywcqgJToePC9zYSeiOp
```

{% hint style="danger" %}
Your Mailchimp API key is like a password. Keep it safe and only share it to your Project Manager at Eventscase.
{% endhint %}

### Step 9: Inform your Project Manager of your desired sender address (e.g., <events@yourdomain.com>, <noreply@yourdomain.com>, etc.)

### Step 10: Once your Project Manager has confirmed that the sender address has been set up, you may now send test emails to yourself and verify this information


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.eventscase.com/miscellaneous/helpful-articles/how-to-configure-a-custom-sender-identity.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.