mailgun

So I'm using Laravel 5.1 and trying to integrate with Mailgun. Well, that's easy, but now I'm trying to send custom variables from my application along with my emails. I'm actually switching our application over from Mandrill because of their "new direction" and such. With them, I could supply the variables and tags via the email headers, but with Mailgun, that only works when you send via SMTP. In Laravel, Mail::send() uses an API call, so in theory I'd add the metadata there with "v:my-custom-data" => "{"this_id": 123}" , but I'd like to avoid altering core classes like that. I also

I am attempting to build an anonymous customer feedback form which forwards the content to an email address. I've been looking into Mailgun ( http://documentation.mailgun.com/api-sending.html ), but I am confused where I could put in my API key. I am attempting to make a POST request with jQuery, could someone point me to an example of sending an email? superEb According to the Authentication section of Mailgun's API Intro , they require Basic Auth, which is accomplished in code by adding the following HTTP header: Authorization: Basic base64($username:$password) For Mailgun, they mention

I am trying to send mail only to Bcc but unable to send. Code given below is working fine with To and Bcc but when i try to send only with Bcc it fails. I tried passing empty string with To but didnt work. I am using mailgun php API. function send_mail($email,$subject,$msg,$bcc) { $api_key=""; $domain =""; $ch = curl_init(); curl_setopt($ch, CURLOPT_HTTPAUTH, CURLAUTH_BASIC); curl_setopt($ch, CURLOPT_USERPWD, 'api:'.$api_key); curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); curl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'POST'); curl_setopt($ch, CURLOPT_URL, 'https://api.mailgun.net/v2/'.$domain.'

Mailgun is telling me to set up a TXT record for mg.mydomain.com with a value of v=spf1 ... plus a CNAME record for email.mg.mydomain.com with value mailgun.org . I did that, and mailgun verified my domain no problem. The issue is when I send emails, certain receiving mail servers are rejecting my emails with message "Sender address rejected: Domain not found". I'm pretty sure this is because "mg.mydomain.com" doesn't exist -- I don't have a CNAME for it. However, I can't create a CNAME for it because it's already used for the TXT record. So now I don't know what to do. Can I put this v=spf1

after failed to find a solution for my problem in the mailgun documentation, I will explain what I'm looking for. Today I'm using phpList to send out my newsletter (It works perfect!), I have HTML pages that I just include in the phpList application to send it out. (I'm using SMTP method to send news out). I wonder if I can do the same with mailgun (for sure can, but how?), is it possible to just include the path of my HTML pages to send it out? (I do not have interest to type my html code in the script, it must be in the path otherwise I have no interest in use mailgun). Take a look to my

I'm trying to figure out how to send mails using the MailGun Golang API without having it sent 'on behalf of'. This is how the From address currently looks (where foo.com is the sender's email domain and bar.com is my domain): john=foo.com@mail.bar.com on behalf of John Smith <john@foo.com> What do I need to do so that it looks like this instead: John Smith <john@foo.com> I've set up SPF and DKIM according to the MailGun instructions and everything passes as being correct. I've also used SetDKIM(true) when I'm sending out the mail. Is there some setting I'm missing or additional validation I

I'm using Mailgun for a site I maintain, usually Mailgun works great, but I am encountering a strange problem. My script calls the HTTP API to send messages using Mailgun, these then show up in my log as being "accepted", but then take a very long time to be "delivered", often failing to be delivered at all and simply remaining as "accepted". Has anyone experienced a similar error or could anyone suggest a way to fix it? I'm guessing it's in the arguments supplied to the API but I can't for the life of me figure out the problem. The problem exists for different recipient domains and different