Ruby on Rails Tuesday, September 12, 2017

It would be simpler to use a specific domain or subdomain and use a 3rd party service that can handle that for you like mailgun (or something like that).
Ex: 
http://mailgun-documentation.readthedocs.io/en/latest/quickstart-receiving.html

It's really easy to deploy, nothing to maintain (they handle that for you), you have just to handle a post request on your side.

so you can think your system in 2 ways:
- you have a single incoming email for all your customers (like : hello@mydomain.com) and when you receive an email you can check if (against your user DB) if you know (or not) the sender (it's simple 1 address for all customers, but it requires the customer to declare all emails source).
- you can generate a specific email for each of your customer (like : john_smith-432@mydomain.com) and when you receive an email, you know which customer to affect this email (but all of your customers needs to register/search/learn the generated email, so you have to onboard your users).



Le dimanche 10 septembre 2017 08:28:14 UTC+2, Aqib Hameed a écrit :
I want to design a software which has multiple emails against the brands, e.g Brand1 has email ema...@gmail.comemail2@gmail.com, and Brand2 has emails ema...@gmail.comemail4@gmail.com. So Customer send their query by email on ema...@gmail.com etc. So system  reads all emails against the brands on which customer send the emails.So which Gem is best in rails to reads the emails from multiple mailing box without forwarding the emails??? 

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/01bc978d-5839-4aa2-a9e7-bed783fe2d0e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment