mailgun

Jersey switch on Content Type dynamically

两盒软妹~` 提交于 2019-12-11 09:52:55
问题 A similar question is here: Supporting both Multipart and Application Url Encoded parameters in Jersey I have an API endpoint (in Jersey) that can accepts POST request. The content types are either: form-urlencoded, or multipart. The two types of request arrive at the same path. How do I switch on that? For the urlencoded request, I want to get argument: @FormParam("recipient") String recipient For multipart request, I want to get: @FormDataParam("file") InputStream uploadedInputStream,

mailgun/parse-server(heroku) not working

点点圈 提交于 2019-12-11 09:49:38
问题 Having two iOS apps (let us name them appA and appB) both using parse-server hosted on heroku and mailgun , I am facing the problem describe hereafter. Let me first say that the two apps are unrelated except for the fact they both have user accounts and mail mailgun is used on both to send a confirmation mail when a user creates an account. appA is working fine, meaning confirmation mail is sent when a new account is created. But appB is no longer working, meaning no confirmation mail is sent

Sending a string attachment using Mailgun

大城市里の小女人 提交于 2019-12-11 09:13:45
问题 Is it possible to send an attachment as a string using Mailgun - i.e. similar to the way this can be done in PHPMailer, using AddStringAttachment() . The Mailgun documentation seems to only relate to attaching files. I found this article, but I'm not sure what language the code is written in and don't understand how I could adapt to php. 回答1: $mg = new Mailgun('mailgun-api-key'); $msg = $mg->MessageBuilder(); $msg->setFromAddress($from); $msg->setSubject($subject); $msg->setTextBody($textBody

Link inside verification-mail not working

回眸只為那壹抹淺笑 提交于 2019-12-11 08:04:20
问题 Could somebody explain, or better tell me how to fix this problem? The link found in the "account creation verification email" on Parse-Server (/Heroku), is not working. The relevant code in index.js is like this: var api = new ParseServer({ databaseURI: ....., cloud: ....., appId: ....., .......... publicServerURL: process.env.PARSE_PUBLIC_SERVER_URL || 'https://myapp.herokuapp.com', appName: 'WonderApp', .......... verifyUserEmails: true, emailAdapter: { module: 'parse-server-mailgun',

Parsing JSON Response in PHP

落花浮王杯 提交于 2019-12-11 07:45:46
问题 I have a MailGun account and I am making a PHP script that will grab attachments of emails sent to the MailGun email address I have set up. When an email is sent to the address, MailGun sends a notification to my PHP script below with a URL to the full message content in JSON. I then go to grab that message. It works fine up until that. I get the full JSON message -- the issue is trying to work with the JSON. Here is what I have so far for the PHP script // Grab contents of message ( Already

Laravel - Failed to authenticate on SMTP server with .. using 2 possible authenticators

↘锁芯ラ 提交于 2019-12-11 07:31:10
问题 I saw this questions were asked many times. I tried many of them and nothing working. I am using laravel and mailgun api to send email. I am geting this error Failed to authenticate on SMTP server with username "postmaster@noreplay.padelmatch.se" using 2 possible authenticators and also in my dedicated server log I get 2018-05-30 13:37:32 dovecot_login authenticator failed for (domain.com) [198.20.114.174]:40412: 535 Incorrect authentication data (set_id=email@sub.subdomain.com) 2018-05-30 13

What port to use sending email with SMTP (mailgun) in rails app on production server (DigitalOcean)?

南楼画角 提交于 2019-12-11 05:09:18
问题 I have a rails app deployed at a digital ocean droplet configured with capistrano and mailgun, but I'm having trouble sending emails, task which I do using delayed_jobs. The thing is every time it tries to send an email I get connection timeout (verified using RAILS_ENV=production bin/delayed_jobs run in the server) and I found out that for some reason digital ocean does not allow from default for you to access through port 587 (and indeed, running telnet smtp.mailgun.org 587 takes a very

Mailgun: wildcard subdomain “from-address” for SaaS

萝らか妹 提交于 2019-12-11 04:42:08
问题 I've a small SaaS where each client gets a subdomain (stackexchange.my-saas.com) I've a mailgun account where my main domain is setup and I've created a wildcard SPF record in my DNS and if I add additional domains to my mailgun account with a subdomain, they all verifies correctly. My question is, do I need to add every new clients subdomain as a new domain in mailgun when I have the wildcard SPF record set or can i "legally" just create a from-address for each new client so the header of

Mailgun Server response: 550 Sender rejected

跟風遠走 提交于 2019-12-11 04:35:42
问题 Recently I ran into a problem trying to send email using the mailgun API because mailgun uses the domain registered with mailgun in the 'sender' field for the email 'envelope' map. The failed response error message I got was: Server response: 550 postmaster@mg.example.com Sender rejected I followed the directions in the mailgun documentation for verifying my domain and used the recommended best practice of creating the 'mg' subdomain for my mailgun email routing. After adding the text records

Mailgun POST /messages API always throw 401 forbidden

女生的网名这么多〃 提交于 2019-12-11 04:07:25
问题 I am trying to send Mailgun POST /messages API request in Android using retrofit library. Following is retrofit request: HTTP POST https://api:key-xxx/v3/sandboxxxx/messages Cache-Control: no-cache Content-Type: application/x-www-form-urlencoded Content-Length: 148 from=Excited+User+%3Cmailgun%40sandboxxxxmailgun.org%3E&to=vir.jain%40gmail.com&subject=Hello&text=Testing+awesomeness Response: HTTP 401 https://api:key-xxx/v3/sandboxxxx.mailgun.org/messages (1966ms) Server: nginx/1.7.9 Date: Mon