Lead engineer at MailChimp here. Funny you should mention it, but tomorrow we're going to be launching Google Authenticator and YubiKey integrations with AlterEgo so you can use those as you like. We're also working on a Duo integration, but no ETA there.
There are a few things that we think set Mandrill apart from the pack. Our application is designed with responsiveness in mind, and we have mobile application on both of the major platforms so you can get access to your email stats and reputation wherever you are. We have search and analytics deeply ingrained in the application in a way that is fairly unique - letting you see your emails in context and trying to derive the context for you when we can. We also integrate deeply with the main MailChimp product. They use the same underlying delivery engine, the same templating and content personalization systems, and we have a heavy discount for users of both products.
Mandrill's still a rapidly iterating product for us, but we think we can take the same sense of usability and power that we have in MailChimp and extend it to email more broadly.
Not yet. The inbound system right now is really basic - we'll parse out the messages and deliver them to a webhook, but we won't munge it much beyond breaking apart attachments and things.
Yes - the pricing is flat rate. Right now charging for inbound emails is turned off since the feature is so new and basic, but inbound emails will be indexed and tracked the same as outbound emails, so they'll be charged the same.
That's one of the reasons we chose that name for the brand. Since Mandrill is an infrastructure service, we wanted it to feel more serious and aggressive than MailChimp.
We built on top of our own internal job scheduling systems that we use for email to handle retries, batching, and concurrency handling so we don't overwhelm your servers. It's all custom stuff, though.
Both MailChimp and Mandrill look great, but I have a pricing question. Is it possible to use Mandrill to send out newsletters since your Mandrill pricing is WAY cheaper than your pay as you go newsletter pricing?
I've been looking for a newsletter service that charges me reasonable rates for pay as you go sending of a monthly/semi-monthly email newsletter, using the pay as you go product, it would cost me $30 per 1,000 emails, whereas Mandrill's per email rates start around $0.90 per 1,000. You say that both are using the same infrastructure, so why is sending email newsletters with MailChimp 33x more expensive?
Yes - you can use Mandrill for newsletters if you want to code your own subscription logic and store your own list of emails. MailChimp is quite a bit more expensive than Mandrill, but it does a lot more too. MailChimp stores more analytics than Mandrill does and stores it longer. It handles scheduling, batch testing, social integrations and content management in ways that Mandrill really doesn't. MailChimp also has analytics and profiles for list subscribers that Mandrill doesn't have.
If Mandrill does everything you need it to do and you can do the rest on your own, you should use Mandrill. It is, as you note, much cheaper.
First of all congratulations! I was hoping you would be developing such a product after I saw last year's announcement on STS. One question, is there a ruby gem to work with the API coming up, or is it left up to the internet to develop that?
I've tried to sign up but you wouldn't take my password ("the input must contain at least one number or symbol"). Although a minimum length make sense, requiring a symbol doesn't. Would be great if you could remove it!
I've not tried to signup but according to the error you're reporting, you must either have a number OR a symbol, so you're not required to put a symbol.
Having said that, have you ever tried to fulfil the requirements for a strong Active Directory password? :)
So how does this compare to something like SendGrid? More or less a direct competitor? I noticed you can only send mail via the API (no SMTP relay). Any other notable differences?
We're trying to make Mandrill a stable email platform for all uses, so in that way we're similar to SendGrid. Where we're really trying to focus isn't so much in just the delivery of the email, though we do have a ton of experience doing that well.
Mandrill is a product that is trying to make your application-driven emails as easily tracked, tested, and understood as the bulk email you'd send using MailChimp. It's still early days for the product and we're still iterating rapidly, but that's where we're trying to get.
We're also integrated with MailChimp itself. We've got a big discount for paid MailChimp users that want to use Mandrill, and you can share templates between Mandrill and MailChimp easily. We'll be integrating more deeply in the future - really trying to make a one-stop shop for email-related needs for businesses.
I think deep integration with MailChimp is a huge reason to use Mandrill. I'm not and have never been a paid MailChimp customer, but this might get me there.
I currently use MailGun for transactional e-mail, and CampaignMonitor for marketing e-mail. MailGun's UI is really rough, so Mandrill is pulling me in for that reason alone, and CampaignMonitor pretty great but I haven't use it lately any way.
Have you considered discounts for developers deploying individual accounts for clients?
Cancel that -- you CAN do a simple SMTP relay. Looks like a solid service. I'll consider switching. Your free plan is about twice what SendGrid offers.
Just gave it a quick spin here and we got the SMTP relay working and tracking e-mails within 2 minutes. Very impressive. We'll play around with the API soon, it looks promising :)
It's really simple right now. We add a List-Unsubscribe header to each email which in supporting email clients (like gmail) adds an unsubscribe button to the report spam button that's always there. If the recipient unsubscribes in that way, we treat it as an unsubscribe. The more traditional subscription model isn't supported by Mandrill at this time. You'd need to build your own or use MailChimp for that. I recommend MailChimp, it's pretty good at handling subscription-based email like that ;)
Well, supporting unsubscribes in transactional emails can sometimes make sense, like with notification or confirmation emails where the user might want the option to not receive them. With others, like receipts or signup confirmations it makes less sense. For now, we presume that you're going to do the right thing and implement unsubscribes if it makes sense for the emails you're sending. We've got a feature coming to make that process easier, but it's still going to be a decision that the sender is going to need to make.
I suppose something that carries some operational information and/or that is worth to be tracked, like "you've subscribed to our service", "your order is ready for shipping", "this is your password reset link", "your credit card has been charged.." etc opposed to mails like "hi Deb, how was the party last night?" that are merely informative / casual conversation (of course nothing stops you from sending this kind of mails with "transactional mail providers" and keepin track of relative metrics :))
Another distinction is that you typically send transaction email to a single person, because some transaction has happened. Bulk email you send a (perhaps customized) email to an entire list of recipients in one go.
You can customize DKIM without a dedicated IP. You do need to have a paid plan to get the dedicated IP, but that's really because you need at least a few hundred thousand emails per month of volume before getting a dedicated IP. With lower volumes (like anything that can fit in the free plan), the sending reputation of one of our shared IP addresses is certainly better than a dedicated IP with no reputation.
A viable solution going forward is to have browsers implement both the vendor-prefixed and non-vendor-prefixed versions of a property, but use the vendor-prefixed one preferentially. That would allow developers to use one non-prefixed rule in the common case where all supporting browsers implement the rule in the same way, but developers can target particular browsers if they deviate. Or if you're worried about the standard deviating, support vendor-rule and x-rule at the same time.
For the current webkit- mess, it's probably best to just have the vendors implement each others prefixes on a case-by-case basis (when you know the semantics are the same). There are way fewer browser vendors than there are website developers, and it's much easier to get them all in a room to agree on something.
This is only hypocritical if when Stallman says "phone", he always means "cell phone". Just to be a devil's advocate, he could be talking about a landline which generally doesn't track movement, doesn't run software, and doesn't get turned into a listening device.
I actually reject people without pet projects for an entirely different reason. I can find out much more about how you behave as a developer and whether or not you'd fit in with our company by reading your code than I can from any kind of interview or whiteboard challenge. Ideally you'd actually hire the prospective developer for a short contract project before hiring, but that has significant challenges and costs as well.
Think of a carpenter that claimed to be amazing at producing furniture, but had none to show you. Would you trust them on how well he could BS you in an interview? It's not about passion or dedication. If you, producer of code, can show me code you've produce, I'm taking a much lower risk on hiring you. And fortunately, there are enough people around with code to show that rejecting others is a pretty easy filtering decision to make.
Then give them a coding problem that takes a short amount of time but allows you to evaluate their skills. I relish these opportunities and respect the companies that ask me to do them.
To keep with your metaphor, ask the carpenter to make you a cabinet door.
Again, I agree with others here... if you're passionate about the startup you're working at (and you should be), that is your side project. I distrust people who work at startups that have side projects.
Any coding problem that could feasibly be completed in an acceptable amount of time would be too small to actually tell me what I want to know. I mostly don't want to know what algorithms you're aware of or how quickly you can type. I want to know how you structure and modularize code. I want to know how you debug things. I want to know if you can refactor well. In short, I want to know about how you handle building and maintaining real software. If I hired people to do coding problems all day, that would be another thing, but I don't.
A coding problem is less illustrative than a decent--LOC is always suspect, but let's say 10,000 LOC--corpus of work. Something to show much more than a toy problem.
Better still, however, is collaboration with open source projects--you can see individual communication between people as well as the developer's ability to enter a foreign codebase and be productive, (hopefully) without introducing bugs due to ill-advised changes without understanding what's being changed.
(We don't look at side projects or open source at my current employer. I wish we did.)
