Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Mandrill Inbound Email routing

Tags:

mandrill

having a bit of a conceptual issue here:

Using mandrill for sending email - ok. Configured mandrill for receiving email. the documentation states that incoming messages are posted to an URL. This means that such a page should exist and parse the messages.

Ideally incoming messages should end in my inbox. how can this be accomplished?

Do i have to make changes at the DNS level to route inbound email to my SMTP mail server?

like image 421
user1144596 Avatar asked Aug 12 '13 20:08

user1144596


People also ask

What is inbound email routing?

Inbound email routing accepts and parses the contents and attachments of any emails sent to a unique email address that is provided to you by MailerSend, or any incoming email for a connected domain or subdomain. It then sends the parsed results to your chosen application's URL.

How do I see inbound emails in Salesforce?

Using the handleInboundEmail method in that class, you can access an InboundEmail object to retrieve the contents, headers, and attachments of inbound email messages, as well as perform many functions.


1 Answers

Mandrill's incoming features are completely optional.

Unless your application needs to programmatically process incoming mail (e.g. post-by-email for a blogging platform), and you can't easily do it without using Mandrill, you can pretend Mandrill's inbound features don't even exist.

If all you need is plain old incoming mail, just configure an MX record like usual.

Even if you need to use Mandrill's inbound features, that's best done on a subdomain. To quote the docs:

All email sent to this domain will be sent to Mandrill instead of traditional email inboxes, so it's a good idea to use a subdomain, like "inbound.yourdomain.com" that doesn't already exist.

like image 113
colinm Avatar answered Sep 27 '22 20:09

colinm