Frequent Asked Question?

Let's answer the most prominent questions, that's keeping you on the fence.
Does Mutant Mail Work with only Gmail as recipient or other emails work too?

Mutant Mail works with any and every Email ID as their recipient email id.
Including but not limited to Gmail, hotmail, yahoo, outlook, yandex, self hosted email etc.

Only requirement for Recipient email id is, it should exist outside the Mutant Mail system.
As it will need to hold all your emails.

Is it true, that you do not store or log any emails?

It is absolutely true.
We do not store, log or read any email that passes through our system.
That's why we have concept of recipient email id.
Your email ids (that are associated with Mutant Mail), are managed by your recipient email ids.
These  email ids store your real emails, contacts etc.

Mutant Mail only acts as routing system in between your client and your recipient email id.
Thus, it ensure your brandin/domain identity is maintained when you hit reply on your recipient email id.

How can you guys work without SMTP, IMAP etc?

It's very simple really.
We work at one level higher, at email level instead of nagging SMTP/IMAP etc.

That means, when you hit that reply button on your recipient email id for any email forwarded by Mutant Mail.
An email is sent from your recipient email id to our server, than we send one on your behalf with exact same content to your client, without them or you knowing about the process.

Your recipient email id, cannot be traced back at all in the email.

Can I send an email as well from my domains associated with Mutant Mail?

Of course you can.
But remember, our primary focus is to focus on the reply system instead of send system.

As monitor and reply is the main hassle with owning so many email ids. And that's exactly what we are trying to solve.

Can I keep using my domain on Google Workspace (G-Suite)?

At a time only one server can accept mailbox related to any domain.
But there is a workaround.

You can have your main domain associated with mutant mail and a subdomain associated with your Google Workspace(G-Suite).

That way Mutant Mail can route all admin, legal, anything @ example.com to your G-Suite [email protected]

And of course, when you will reply to those emails from your subdomain, your domain email id will be shown to the recipient and not your subdomain.

Flow is,

[email protected] -> [email protected](Mutant Mail) -> [email protected][G-Suite] (Received -> Replied[Just hit reply button]) -> [email protected](Mutant Mail) -> [email protected]

The only thing Mutant Mail needs is, control/destination mailbox should be outside the Mutant Mail system

Do you mind explain "Recipient Email IDs"?

Recipient Email IDs mean the destination or control email id, where actual emails will be stored.
This will be the inbox from where you receive, reply or send your email (can be Gmail/Yahoo/Hotmail or anything else) outside the Mutant Mail system.

Mutant Mail acts as a routing system in between your recipient email id and your destination email id,
to ensure when you hit reply email is received by user coming from your domain and not from the control inbox.

From field will be your domain's email id always.
If you want to set the name for your email ids, it can be set in the settings option.

Does this work with a regular gmail address or do I have to have a workspace account?

It does work with a regular Gmail address, on any other including G-suite or workspace account. 

The only condition being destination/recipient/control e-mail id should be outside of Mutant Mail system, 
that can even be G-suite on a subdomain.

If Mutant Mail act like email alias on forwarding any emails from any domain to the MAIN email address like Gmail, what is the rules or measures you put in the system so not become like "Email Spoofing".

It's the most important question for anyone on-boarding with us.
I am glad you asked it.

Let me first elaborate on the question from an overall perspective before getting into specifics of it.

Encryption, Security, and Privacy have been built in Mutant Mail at not just one, but multiple levels.

Security :
> At the Account level, you have an industry-standard choice to use two-factor authentication.
> At Email ID/Domain-Level, only the Control/Recipient/Destination Email ID has the option to Send, Receive and Reply to that particular email id of your Domain.
> Dmarc record to ensure, no email impersonation happens for your domain.

Encryption :
> Industry-standard GPG encryption is used for all emails passing through Mutant Mail.
> If you want to ensure, no snooping happens even at your destination/control/recipient Inbox, add your PGP key for each recipient you add.
Though remember to use a PGP decrypt client on your side to decrypt the message. On top of this, you can set rules, disable PGP encryption on specific emails.
> Though we do not store any sensitive data (we only ask for email id during sign up). Everything except your username is stored in the database in an encrypted format.

Privacy :
> We do not store, view, or log any record of email that passes through our servers. We only know to which email id each routing is going to happen (at email id level, domain level, or account level).
> We maintain bandwidth used through a counter, and since we do not know when those emails were sent, we reset bandwidth on 1st calendar day of each month and not a rolling window.
In short, we have left the choice with our customers, how secure they want to keep their data and enforce just a small part of what we offer as a requirement.

Now let's answer the specific for your question.

It's because we ask for your domain verification before your domain can be used in any way (and that requires a txt record).
For domains that are already attached with us. They can be controlled by their own recipient/destination/control email ids only.
Routing is maintained at the account level, domain level, and email id level.

If an email id that is not a recipient email id, attempts to send an email for your domain, it will be discarded, and not sent.

For any email id to be attached as control/recipient/destination email id, link authentication is used. Unless that destination email id is verified, it cannot be used.

Does this mean that I could potentially cancel my G-Suite subscription, as I mainly use it for my business email anyways, and instead, I can just use mutant mail and still have my emails go out from my domain.

Yes, your understanding is correct.

You can use Mutant Mail to send, receive and reply to your domain's(one or many) emails from any control/recipient/destination Inbox (Gmail, Yahoo, Hotmail, Yandex, Hey, Office365 anything).
The only condition is since Mutant Mail doesn't store any emails by itself, you need to have a destination inbox outside of the Mutant Mail system (can be anything), where your emails will be stored.
You will receive all your domain's email on your destination inbox, and when you reply, it will go as your domain's email instead of that control inbox to your recipient.

If you are still on the fence, give our free plan a shot.

How different is this from fastmail service?

The most important difference is, we don't store any emails at all. We have taken that out of the equation, because we all already have at least one email provider, that we trust with privacy.

Now since we have not used the service our self, it's difficult to say how they do forwarding and can you reply to those forwarded emails or not.
Also, since they store emails, it's doubtful that they help with the niche we are specifically into, to let you manage all your domain emails from a single Inbox.

There are two kinds of products on market, one that tries to do all. That's what FastMail seems to be doing, competing against Gmail directly.
Other types of products are niche-specific. That's Mutant Mail, we are a solution to a specific problem of managing all domain's emails, from one Inbox, on the server-side, without the hassle of logging into each email id. And our settings, features, roadmap reflect the same.

During the Setup process it's asking me to input a "real email address" that will be used as my forwarding address. Is this address changeable?

Yes, it's changeable.

All you need to do is, add another email id in the "Recipient Inbox" tab and verify it.
Then go to settings and mark it as default.

After that, you can delete the old email id in the "Recipient Inbox" tab.

The only condition is, none of the email ids should be used on any other Mutant Mail account.

Is there a setup document to explain how to setup. I want to try it but I am not sure what configuration needs to be done.

We have an extensive setup guide (including video) and knowledge base at https://www.mutantmail.com/knowledge-base/

And if you are stuck, just hit us on our support chat, and we will guide you.

If you go out of business what happenes to my emails?

It's an interesting question, considering we are in for a long haul.

Nonetheless, perfectly justified.

The answer is very simple, you continue to own and have access to it.

As we do not store any emails in the first place, they are stored with your recipient email id provider.

Does Mutant Mail work with CRM?

Our customers have reported that they have used Mutant Mail successfully with products like flowlu and a few other help/ticket CRM.

We don't see a reason, why it shouldn't work with other CRM.

Though since we do not support either of those CRM officially, we will certainly help in case you are stuck somewhere.

Does Mutant Mail work with MXRoute, or do they just overlap in features?

MXRoute is an Email Hosting. Very similar to Godaddy and others that provide email hosting.

Mutant Mail is a unique and innovative solution, that does email routing for you without storing any emails.

So in essence, you should be able to use Mutant Mail and MXRoute as recipient inbox.
Just like Gmail, Hotmail, Yahoo, Yandex, or any other.

A simple cycle would be,

[email protected] > [email protected]_one.com (Associated with Mutant Mail) > Recipient Inbox (MXRoute/Gmail/Hotmail/Yahoo/Yandex/G-suite anything) > Just hit reply > Mutant Mail jumps into action behind the scene > [email protected] receives an email from [email protected]_one.com

Can i continue to use my existing email clients (gmail in a browser, Zoho mail in a browser, or any of my emails using Outlook or another mail client) AT THE SAME TIME as using each email account with Mutant Mail? I do not want to disable any of my existing email clients while using Mutant Mail. Please provide full details with your answer.

Short answer is yes.
The long one is, you won't be needing so many email clients anymore.
You will be needing only one (or as many recipient email ids) you use, and any email client they support will work.

Think of Mutant Mail as Enriched Email Forwarding, where when you hit reply, your recipient receives a response from your email id.
So, essentially it will be like,

[email protected]_1 > [email protected]
[email protected]_2 > [email protected]
[email protected]_3 > [email protected]
[email protected]_4 > [email protected]

So, you only use the client for your recipient email id ([email protected]) and manage all the above domain's emails from it.
That recipient email id can be anything including Gmail, Hotmail, Yahoo, anything. The only condition is, it should exist outside of the Mutant Mail system.

The sequence will look like this,
[email protected] > [email protected]_one.com (Associated with Mutant Mail) > Recipient Inbox (MXRoute/Gmail/Hotmail/Yahoo/Yandex/G-suite anything) > Just hit reply > Mutant Mail jumps into action behind the scene > [email protected] receives an email from [email protected]_one.com

Though Mutant Mail does have a way to Send mail or initiate email conversation.
Its primary job is to ensure, you can reply to any email you receive with utmost simplicity, and yet keep your brand/domain's persona.

In case you need to send a lot of emails from a domain, you will need a parallel system in place to send emails from your domain, and receive/reply emails via Mutant Mail (for the same domain).

What do you mean by allowed domain, email ids, recipient email ids and disable catch all. I am bit confused with these terms.

We are glad you asked about clarity on these terms.

Mutant Mail works at the Domain level, through MX, SPF, DKIM, and DMARC records.

10 Domains: It will mean you can integrate up to 10 custom domains in your Mutant Mail account. You may have a website on them or not. Your existing website doesn't get disturbed, we only handle emails for them.

50 email ids: It means you can have up to 50 email ids created on the above domains, that are integrated with Mutant Mail.

Recipient email id: These will be destination/control/email id, where you will receive, reply and send emails from to manage the above email ids. Mutant Mail doesn't log or store any email. This is a real email id that will be outside the Mutant Mail system. It can be personal Gmail/Yahoo/Hotmail or anything else. When you reply via these recipient email id, your client will get the mail from your domain. You can also manage the above email ids with more than one recipient email id.

Catch-All: This option is used at the domain to create email ids on the fly. For eg, if you have domain_a associated with Mutant Mail, but have not created email id [email protected]_a.com. With catch-all enabled, whenever someone sends you an email at [email protected]_a.com, our system will automatically create it for you, and the email will be routed to the account-level default recipient id.

We understand, things can be confusing with solutions, as innovative as Mutant Mail.

If I use a GPG/OpenPGP key, that's at the account level, correct? So every email I receive will be encrypted. Will every email I *send* be encrypted, and is there anything special the recipient needs to do to open them?

We allow GPG/PGP at a finer level, and it's set at the individual recipient email id level.

Yes, once you set it from "Recipient Inbox", emails are encrypted only on forward flow and a client like thunderbird will be needed to handle decryption automatically.

Your clients don't need anything for that, as we don't encrypt that flow yet.

What is the difference between the "Delete" and "Forget" actions for an email ID?

The difference between Delete and Forget is due to the catch-all.

The delete can be used even if catch-all is enabled. It's a soft delete and a marker is kept in a database to ensure, the email id doesn't automatically get created on the fly when a new email is sent to the deleted email id.

Forget on the other hand is to completely delete the email id. If used, the email id and all its record are deleted from our database. But if it is being used on the catch-all enabled domain, the email id will be re-created on the fly as soon as it receives a new email.

Forget option doesn't contribute towards email id count, delete does, as a soft delete happens.

We send detailed information on this via email and similar things on the third day of onboarding.

Can I add a domain while using it for hosting website somewhere else along with Mutant Mail?

Absolutely. If you have a custom domain say example.com and you are using it to host a website somewhere else e.g. Godaddy or Namecheap then you can simply update the MX and TXT records to use it simultaneously with MutantMail for email.

Can I add a domain while using it for email somewhere else?

It depends.
If you are using same domain for sending at other provider or system (like autoresponder or send email from hosting), you can use Mutant Mail along side it.

But if you want to have couple of email ids going to your existing inbox and rest routed via Mutant Mail, than that's not possible.

This is because emails cannot be handled by multiple different mail servers at the same time, even if they have the same priority MX records. It can only be delivered to one mail server at a time which will typically be the MX record with the smallest number since this has the highest priority.

So, either migrate to MutantMail by removing the current provider's MX records and adding MutantMail's.
or if you would like to keep using your domain with your current email provider then add subdomain of it to MutantMail such as mail.example.com.

Using a subdomain will not interfere with your current email setup and you'll be able to create email ids like *@mail.example.com through MutantMail.

Does Attachements get encrypted too, when I enable bullet proof encryption?

Absolutely.

Attachements are part of the email body and are also encrypted if you have enabled encryption.

What is the maximum number of recipient or email ids I can attach or create on Mutant Mail?

It depends on the plan you are currently on.
In case you have a requirement that requires more than our current existing plan.

Just reach out to us. And we will happily create a custom plan on a discounted rate.

I keep getting a loop back email. Or why my email keeps coming back to me. What is wrong?

If you are tying to reply or send from an email id, but the email keeps coming back to yourself then most likely reason is, you are sending the message from an email address that is not listed as a verified recipient on your MutantMail account. 

If you try to reply or send from an alias using an unverified email address then the message will simply be forwarded to you as it would be if it was sent by any other sender. 

Please double check that you are indeed sending from a verified recipient email.

My email keeps getting rejected, what is wrong?

If you see the rejection message 5.7.1 Recipient address rejected: Address does not exist then this means that the alias has either been deleted or does not yet exist (and you do not have catch-all enabled), you must restore (or create) it before you can send/reply from it.

If you see the rejection message 5.7.1 Rejected due to missing/failed DMARC policy... then it is because your MutantMail recipient's domain either does not have a DMARC policy or it has failed DMARC checks.
This is usually because you have a verified recipient that is using your own domain which does not have a DMARC policy.

When replying or sending from an alias, additional checks are carried out to ensure it is not a spoofed email. Your MutantMail recipient's email domain must pass DMARC checks in order to protect against spoofed emails and to make sure that the reply/send from attempt definitely came from your recipient.
To resolve this you simply need to add a DMARC record, which can be easily done by clicking Re-verify in your custom domains section.

Can emails have attachments and what's the allowed size?

Yes you can add attachments to emails forwarded and replies. Attachments count towards your bandwidth.
The max email size is currently set to 10MB (including attachments).

How is my Bandwidth calculated?

Every time a new email is received Server calculates its size in bytes. A column in the database is then simply incremented by that size when the email is forwarded or a reply is sent. At the start of each month your bandwidth is reset to 0.
We don't use rolling 30 day total as the only way to do this would be to log the date and size of every single email received.

Blocked emails do not count towards your bandwidth (e.g. an alias is inactive or deleted).

What happens if I go over my Bandwidth limit in a given month?

If you get close to your limit (over 80%) you'll be sent an email letting you know. 

If you continue and go over your limit the server will start discarding emails until your bandwidth resets the next month or you upgrade your plan.

Will people see my recipient email id, when I reply to email forwarded by Mutant Mail?

No, your recipient email id will not be shown, the email will look as if it has come from your domain/brand instead.