The following are some of the most frequently asked questions at CloudMailin. We're hoping to build this up into a bit more of a knowledge base so feel free to add more to the issue tracker on github.
Your emails should arrive within seconds (actually we aim for it to be milliseconds). Our email server doesn't poll for your emails, they will be received as soon as they are sent to the server. A little bit of processing and they're sent straight on to your app.
The CloudMailin website allows you to view all of your email addresses and to change the target location. Click here to view and edit your addresses.
Absolutely check out Forwarding and Custom Domains for more details.
Yes. Make sure you create a wildcard DNS entry then just enter *.yourdomain.com as your custom domain.
We recommend using either Forwarding or Custom Domains to do this.
You can also use a plus in your email address to create a disposable email address. Disposable email addresses allow you to use a unique email address for each user. As an example, a user given an email address in the form firstname.lastname@example.org could use email@example.com or firstname.lastname@example.org.
Checkout the HTTP POST Formats documentation.
We have tried to make things pretty robust, in fact we should be far better than most email hosting systems, however everyone makes mistakes and sometimes things happen that are beyond our control.
We're not going to offer you one of those silly agreements that says something like 99% uptime (3 days a year is a long time!) instead we're going to promise to do our best. If the site goes down we will receive emails (ironic we know), SMS messages and hopefully a bunch of tweets! We will get cracking as soon as possible and work our socks off to bring the site back to life. If the server is unavailable, almost all mail servers will retry a little later anyway.
Because of the way email and SMTP works most mail servers will try and resend your emails until the email is delivered or too many retries have occurred. We are considering adding a separate backup mail server to make sure this happens quicker but for now we are relying on the other server to resend the mail.
We have wired up a few fake targets you can use to test your emails.
|http://www.cloudmailin.com/target/200||will simulate a 200 response. This simulates the message successfully being delivered.|
|http://www.cloudmailin.com/target/404||will simulate a 404 response. This simulates your site not knowing anything about the page you have set as your target.|
|http://www.cloudmailin.com/target/500||will simulate a 500 response. This simulates something going wrong on your site and you asking the server to deliver the message later.|
On the address page within CloudMailin you should see the message and the status that your server returned to CloudMailin. Clicking on the details tab will also show additional information. The details also include the first 2kb of any failed response so that you can determine what may have gone wrong with your server.
You can use the details page for a delivery status to see all delivery attempts with the same message ID. Hopefully one of these is green.
You must make sure that your setup your DNS entries with either a CNAME or MX records pointing to CloudMailin before trying to enter a custom domain in the control panel. If you try to enter your custom domain first, it will fail to validate stating that the DNS records cannot be found. Take a look here for more information about setting up your custom domains.
Our servers predominantly based in EC2's US-EAST region (it is most likely these are the servers you will reach). This is to allow low latency and cut costs for the majority of our users. We do however make use of several other hosting providers to provide redundancy can add others upon request if required. Contact us for more details.