I want to display received emails. suppose we sent one document or message through our gmail address to [email protected]. i need to grep those emails to my apps. for this what i can do. please help me here i want to deliver my application ASAP.

Hello,
I tried to install mailgun 0.7 with 'bundle install' and got this error message:

Could not find gem 'multimap (>= 0) ruby', which is required by gem 'mailgun (~> 0.7) ruby', in any of the sources.

On https://rubygems.org/gems/multimap : "This gem has been yanked".

I installed gem multimap from manually downloaded but I cannot use this way with deploying on Heroku hosting.

Hi HashNuke,

How can I adding several email addresses into one maillist in one time?
I tried to using following method, but it's only support to add one address.
It will cause timeout err when there are a plenty amount of address.

# Adds a mailing list member with a given address
    # NOTE Use create instead of add?
    def add(member_address, options={})
      params = {:address => member_address}
      Mailgun.submit :post, list_member_url, params.merge(options)
    end

This is the only thing I feel like this gem is missing. Is there a way to batch send?

When I perform a Mailgun().routes.create or Mailgun().routes.update command, I get the following error:

{                                           
  "message": "'action' parameter is missing"
}                                           

I debugged the problem and found that at https://github.com/HashNuke/mailgun/blob/master/lib/mailgun/base.rb#L71 RestClient is not recognizing the parameters hash passed to it and not posting parameters to Mailgun, even though it has data.

Here's my test code:

  def self.create(pattern)                                                     
    mailgun.routes.create "Catch-all route for #{ENV['MAILGUN_ROUTE_DOMAIN']}",
      DEFAULT_PRIORITY,                                                        
      [:match_recipient, pattern],                                             
      [[:forward, endpoint_url], [:stop]]                                      
  end                                                                          

  # ...

  describe '.create' do                                         
    let(:pattern) { '.*@.*.test.com' }                      

    it 'creates a route' do                                     
      VCR.use_cassette :email_route_create do                   
        EmailRoute.create pattern                               

        expect(EmailRoute.existing_route(pattern)).to be_present
      end                                                       
    end                                                         

  end                                                           

Here's a dump of my VCR cassette during a create:

---                                                                                
http_interactions:                                                                 
- request:                                                                         
    method: post                                                                   
    uri: https://api:[email protected]/v2/routes
    body:                                                                          
      encoding: UTF-8                                                              
      string: ''                                                                   
    headers:                                                                       
      Accept:                                                                      
      - "*/*; q=0.5, application/xml"                                              
      Accept-Encoding:                                                             
      - gzip, deflate                                                              
      User-Agent:                                                                  
      - Ruby                                                                       
  response:                                                                        
    status:                                                                        
      code: 400                                                                    
      message: BAD REQUEST                                                         
    headers:                                                                       
      Server:                                                                      
      - nginx/1.4.7                                                                
      Date:                                                                        
      - Wed, 27 Aug 2014 00:50:55 GMT                                              
      Content-Type:                                                                
      - application/json                                                           
      Content-Length:                                                              
      - '48'                                                                       
      Connection:                                                                  
      - keep-alive                                                                 
    body:                                                                          
      encoding: UTF-8                                                              
      string: |-                                                                   
        {                                                                          
          "message": "'action' parameter is missing"                               
        }                                                                          
    http_version:                                                                  
  recorded_at: Wed, 27 Aug 2014 00:53:28 GMT                                       
recorded_with: VCR 2.9.2                                                           

Hi guys - bit unsure if / how this can be used to attached custom data to messages in order to have it returned from Mailgun via webhook...

To add this header to your message:

API: Pass the following parameter, “v:my-custom-data” => “{“my_message_id”: 123}”.

How send email with subscription url? I not found api method

I am working on this and will submit a PR in the next day or two.

• replace debugger with byebug for use with ruby 2
  • https://stackoverflow.com/questions/30674161/bundle-install-error-error-failed-to-build-gem-native-extension
• add support for webhooks
  • https://documentation.mailgun.com/api-webhooks.html
• add support for addresses (validate)
  • https://documentation.mailgun.com/api-email-validation.html

You get the following error:

ArgumentError: options must be a hash.

I traced the error to the JSON gem.

Two possible fixes:

1. use JSON.parse directly in base.rb
   https://github.com/flori/json/blob/master/lib/json/common.rb#L466
2. pass an empty hash to JSON(RestClient.send(method, url, parameters))
   https://github.com/HashNuke/mailgun/blob/master/lib/mailgun/base.rb#L75

I am looking for mail receiving functions

Copy-pasting the example in the README yields a Mailgun::Error:

irb(main):013:0> @mailgun.routes.create "Description for the new route", 1,
irb(main):014:0*        [:match_recipient, "[email protected]"],
irb(main):015:0*        [[:forward, "http://my-site.com/incoming-mail-route"],
irb(main):016:1*           [:stop]]
Mailgun::Error: 'action' parameter is missing

Great gem! Thanks for all the effort put in. A question on usage though, if I configure a domain in an initializer I would've assumed that I wouldn't also need to specify the domain in routes list method call. ie

# Initialize your Mailgun object:
Mailgun.configure do |config|
  config.api_key = 'your-api-key'
  config.domain  = 'your-mailgun-domain'
end

@mailgun = Mailgun()
# I'd expect this line to work
@mailgun.routes.list() # but it returns 'key not found: :domain'

# Instead I need to use this
@mailgun = Mailgun(domain: Mailgun.domain)
@mailgun.routes.list() # And now this works

Thoughts?

I'm trying to validate an email according to the docs, but I keep getting this error. I thought maybe the docs are out of date but after digging I'm not actually sure how to call it properly.

irb>   @mailgun.list_members.update(
    '[email protected]',  
    email, "Q", 
    {:gender => 'male'}, 
    :subscribed => 'no'
)

{
     "member" => {
        "subscribed" => true,
              "name" => "Q",
              "vars" => {},
           "address" => "[email protected]'"
    },
    "message" => "Mailing list member has been updated"
}

Tried to follow the exemples in the doc, am I doing it wrong?

Hi,

Does this gem support to receive emails to rails app ?

Thanks.

Hi, Is it possible to get members of list by vars?
What I have is:

@mailgun.list_members('MY_LIST').list()
=> [{"address"=>"[email protected]", "name"=>"", "subscribed"=>true, "vars"=>{}},
 ]

I'm trying to do something like this:

@mailgun.list_members('MY_LIST').list({ vars: { type: 'daily'}})
=> [,
 ]

and getting the same array.

But when I try to do like this:

@mailgun.list_members(MY_LIST).list({ address: '[email protected]'})
=> []

It gives correct response.
How can I use vars correctly?

v 0.11
Converting to test mode for my test suite. This code sends a message not in test mode

@mailgun = Mailgun(api_key: ENV['MAILGUN_API_KEY'], domain: ENV['MAILGUN_DOMAIN'], test_mode: true )
message_params = {
      from: ENV['MAILGUN_USER_NAME'],
      to: "[email protected]",
      subject: "You've been invited to join the BlueStreak Platform!",
      html: html_output.to_str
    }.merge(opts)
   @mailgun.messages.send_email(message_params)

And (part of) the mailgun logs for my request:

...
flags": {
        "is-routed": false,
        "is-authenticated": true,
        "is-system-test": false,
        "is-test-mode": false
    },
...

Note the "is-test-mode": false

An email hit an OpenSSL error that mailgun couldn't rescue because the OpenSSL::SSL::SSLError class doesn't have an http_code method.

2018-01-25T18:30:59.158Z 21699 WARN: NoMethodError: undefined method `http_code' for #<OpenSSL::SSL::SSLError:0x000000082bb2d8>
2018-01-25T18:30:59.158Z 21699 WARN: /usr/local/rvm/gems/ruby-2.4.0/gems/mailgun-0.11/lib/mailgun/base.rb:95:in `rescue in submit'

How about merging some of the pull requests and wrapping into a new release?

I could really do with some of the new functionality in my project.

Thanks, Darren.

I have tried 2 gems for mailgun. I tried it first and no success delivering emails.
Then I tried https://github.com/jorgemanrubia/mailgun_rails success with 10 seconds.

Maybe docs need some update or its not that good with rails. ( Just my 2 cents )

title is self explanatory

Great work on the Rails gem. After trying to integrate it with my Rails application I'm stumbling on a couple of problems. What I did to recreate my situation:

1. Add config to a mailgun.rb initializer:

Mailgun.configure do |config|
  config.api_key = ENV['MAILGUN_API_KEY']
  config.domain  = ENV['MAILGUN_DOMAIN']
end

1. Trying to send an email from a controller:
   Mailgun.messages.send_email(parameters)

Problems:
It doesn't recognize the messages method.

Things I have tried:
Put Mailgun in an instance variable:

@mailgun = Mailgun()

If I do the above, it asks me for the :domain which I need to set apart from the initializer (huh?). The second downside to this is that I can only make it work by connecting without an initializer directly from the application controller with a before_filter, but that is less from ideal because I don't want to connect again to the Mailgun API every single refresh.

I'm really stuck here, thanks.

The "#or alternatively:" part should be something like this:
@mailgun = Mailgun(:domain => ENV['mg-domain'], :api_key => ENV['mg-api-key']) or
@mailgun = Mailgun(:domain => 'your-domain', :api_key => 'your-api-key')

Otherwise will get error like this:

Please consider editing the readme :)

Rails 4.2.1
using in integration with figaro

The link to the homepage in the gem is to a repo that doesn't exist. It was confusing when I was trying to confirm that the code in github was what I was looking at from rubygems :)