Project Settings

To enable all the functionality provided by bluefox.email, you need to fill in all the project settings. If you want to use different domains or sending emails for different environments (e.g., staging or production), create separate projects for each environment.

Project Logo

Users can add, update, or delete a custom logo for their project. This logo will be displayed on the subscription preferences page and double opt-in confirmation page success message to provide branding consistency.

To manage the project logo:

• Add or update: Click upload, select an image, and save.

• Delete: Click remove logo and confirm.

AWS Credentials

Our platform sends emails using your AWS SES, ensuring high deliverability and preventing spammers from using our platform.

Note

For AWS SES to work smoothly with bluefox.email, you’ll need at least these permissions:

ses:SendEmail, ses:SendRawEmail, ses:ListIdentities, ses:GetSendQuota

This is the minimum set needed to send emails, verify identities, and keep an eye on your send limits.

First, set up your AWS Access Key ID, Secret Access Key, Sender Identities, AWS region, and sending limit.

The access key must be able to send emails via SES from the region and the sending email you set up. The sending limit should be lower or equal to the actual AWS SES sending limit. Keep in mind, that your sending limit in "sandbox" is only 1 per second!

Your AWS Credentials Are Secure

We store your credentials encrypted, so even in the very unlikely event of data leakage, attackers won't be able to use your credentials.

Use STS ( Security Token Service )

STS (Security Token Service) is AWS's secure method for temporary, limited-privilege credentials. It's more secure than long-lived access keys because credentials automatically expire and don't need to be stored in your application.

Here's how to set it up:

1. Click the Use STS button and expand the instructions banner
2. Follow the step-by-step guide to create and configure your AWS role
3. Copy the generated RoleArn.
4. Paste the RoleArn into the input field here:

5. Fill up rest of the input fields and once done hit Save AWS Credentials.

Once configured, bluefox.email will use your Role ARN to securely generate temporary credentials on demand, eliminating the security risks of storing permanent access keys.

Important Notes

• You cannot use both STS and regular AWS credentials simultaneously. If you want to switch from STS to standard AWS credentials, you must first remove your STS configuration.
• You cannot remove AWS credentials (either STS or standard) if you have scheduled campaigns or running automations that depend on them.

Managing Sender Identities

In this section, you can manage the sender names and email addresses that will appear to your recipients. These identities define the sender details used for your emails. By default, emails will use the default identity. If you wish to use a specific identity for an email, you can configure it in the advanced settings of the email.

• Adding a new identity
  To add a new identity, click the "add identity" button and provide the sender name and email address.

  

• Default identity
  When adding identities, the first sender identity is automatically set as the default identity.

  • To change the default identity, click the "set as default identity" icon next to any other sender identity.
  • The default identity is used automatically when no specific sender identity is selected for an email.

  

• Deleting an identity
  If a sender identity is no longer needed, you can delete it by clicking the trash icon next to the sender identity.

  

Advanced Settings

The Advanced Settings feature, available in email cards for Campaign, Transactional, and Triggered Emails, allows you to customize key email-sending options, providing flexibility in managing sender identities and reply-to addresses.

Sender Identity Selection

The sender identity field lets you choose the identity used to send the email. By default, the system automatically selects the default identity, but you can select another identity from the list of available options.

Reply-To Email Address

The reply-to email address field allows you to specify where replies to your email should be sent.

Bounce & Complaint Webhooks

To know the bounce and complaint numbers of your emails, set up our webhooks in AWS SNS.

To set up the hooks, expand the banner:

... and follow the instructions. After finishing, click on Run Test button and if everything is good you should see this:

The Identity Name column displays the identities configured in your project. The green tick marks in the Bounce Hook and Complaint Hook columns indicate that the webhooks have been successfully set up for each identity. If any webhook fails to configure correctly, you can revisit the setup and re-test.

Additionally, the red Reset Bounce Webhook and Reset Complaint Webhook buttons allow you to reset and reconfigure the webhooks if needed. This ensures that your setup remains flexible and can be updated whenever required. Once all green ticks are visible, the webhooks are fully operational, confirming that bounce and complaint events will be tracked effectively.

API Keys

To work with our API from the server side, create at least one API key.

Include our API keys in the Authorization header of your HTTP requests as a bearer token.

Authorization: Bearer <API_KEY>

For bounces and complaints, it is added as a query string.

Periodically rotate sensitive info like API keys for security reasons. We use different colors to indicate the age of the API key as a reminder:

• Green: less than a month old
• Yellow: 1-6 months old
• Red: more than 6 months old

Security Warning

Since an API key is very sensitive information, never use it in your frontend code. Always use it from your backend.

Domain Whitelist

The domain whitelist ensures that sign-up requests are only processed from authorized domains, enhancing security during the sign-up process. If your frontend is making requests, you must add its domain to the whitelist to authorize them.

Security Note

The domain whitelist applies only to frontend requests. If your requests are coming from a backend server, you should use API keys instead, as backend requests do not require domain whitelisting.

• To add a domain: Navigate to project settings → domain whitelist, click create, enter the domain, and save. This ensures that requests from the frontend are recognized and approved.

• To edit an existing domain: Navigate to project settings → domain whitelist, locate the domain, and click on the edit icon. Make the necessary changes and save them.

• To delete a domain: Navigate to project settings → domain whitelist, find it in the domain whitelist, click the delete icon, and confirm the deletion. Once removed, any sign-up requests from that domain will no longer be authorized.

Contact Properties

Contact properties allow users to define custom attributes for contacts at the project level. These properties appear in the contacts table and can be filled when adding or editing a contact.

Add new Property

To add a new property, navigate to project settings → contact properties, click create, enter the property name and type, then save. The property will be available in the contact management interface.

Each contact property includes:

• Property Name: The user-defined name.

• API Name: The system-generated name used when sending or retrieving data via API.

• Type: The data type of the property, which can be string, boolean, date, or number.

Reserved Properties

Some properties are reserved and cannot be created. These include status, pausedUntil, email, accountId, projectId, customFields, contactId, subscriberListId, unsubscribeLink, pauseSubscriptionLink.

Delete Property

To delete a property, go to project settings → contact properties, locate the property in the table, and click the delete icon. Confirm the deletion, and the property will be removed from both the contacts table and the contact creation/editing interface.