receiving email

[nahum]

any suggestions for the best way to receive email in a Rails 3.1 app?  Gem or external service making API calls??

--nahum

[Tim Uckun]

Depends on how much infrastructure you control. I have used .forward
files pipe the email to a ruby program which then used gurgitate (kind
of dating myself there) to parse the email and did whatever I wanted
to with it. The nice thing about this approach was that you could
actually use gmail/google apps to get the email and then forward it
to user...@ip.add.re.ss the gmail account acted as a queue and an
archive for the mail. These days I guess you'd use tmail or something
I doubt gurgitate is being maintained.

Another way to go might be to pull the emails via pop/imap from your
mail infrastructure.

Finally there is http://dbmail.org/ which takes the emails and puts
them in a database for you. You can just tap right into the database.

> --
> You received this message because you are subscribed to the Google Groups
> "WellRailed" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/wellrailed/-/tItIv4eqjScJ.
> To post to this group, send email to wellr...@googlegroups.com.
> To unsubscribe from this group, send email to
> wellrailed+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/wellrailed?hl=en.

[Y. Thong Kuah]

Use IMAP to retrieve the mail or if you have access to the mail server, dump into a file and parse it using the Mail gem ?

On Fri, Jan 13, 2012 at 1:23 PM, nahum <nahum...@gmail.com> wrote:

any suggestions for the best way to receive email in a Rails 3.1 app?  Gem or external service making API calls??

--nahum

--

You received this message because you are subscribed to the Google Groups "WellRailed" group.
To view this discussion on the web visit https://groups.google.com/d/msg/wellrailed/-/tItIv4eqjScJ.
To post to this group, send email to wellr...@googlegroups.com.
To unsubscribe from this group, send email to wellrailed+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/wellrailed?hl=en.

--
Best regards,
Y. Thong Kuah

http://kuahyeow.com

[Nahum Wild]

I continued googling and found http://cloudmailin.com/ and also https://github.com/titanous/mailman. the first looks like what I want except I can't use my own domain with the free account :-(

--nahum

[Malcolm Locke]

On Fri, Jan 13, 2012 at 01:32:17PM +1300, Tim Uckun wrote:
> Depends on how much infrastructure you control. I have used .forward
> files pipe the email to a ruby program which then used gurgitate (kind
> of dating myself there) to parse the email and did whatever I wanted
> to with it. The nice thing about this approach was that you could
> actually use gmail/google apps to get the email and then forward it
> to user...@ip.add.re.ss the gmail account acted as a queue and an
> archive for the mail. These days I guess you'd use tmail or something
> I doubt gurgitate is being maintained.

+1 for this kind of approach. I'd personally configure the mail server
to deliver specific recipient messages directly to required script
rather than using .forward, providing you have that level of control.
This usually gives you a little more flexibility, and allows you to
control the delivery response based on the return code of your script
(exit 0 for message accepted, exit 1 for 'temporary failure, try again
later', exit 2 for 'permanent delivery failure'). This may or may not
be useful for your case.

How you do it depends on the mail server software.

This approach is nice and easy to test because you can just pipe
messages on stdin to your script.

Malc

[Y. Thong Kuah]

Hmm looks like https://mailgun.net/pricing has the same problem

[Gordon Anderson]

hi Nahum

For me its a +1 on the iMapping off of gmail.  I used the tlsmail gem to cron downloading of pictures from an email address which I then propogate to flickr, facebook, twitter and google plus.  

Cheers

G

[Glen Barnes]

You could try Sendgrid. We use Sendgrid for our outgoing email and are happy with them. They also have an inbound email service which we will be implementing over the next few months.

[nahum]

Postmarkapp has just announced processing incoming email:

http://blog.postmarkapp.com/post/15687406657/introducing-postmark-inbound-easily-parse-replies-other

Sendgrid docs didn't have anything obvious about processing incoming email - but they do look a whole lot cheaper than postmark.


--nahum

[Glen Barnes]

SendGrid Parse API  ;-) http://docs.sendgrid.com/documentation/api/parse-api-2/