messages().send(data) should allow setting of headers and options
See original GitHub issueIt would be awesome of I could give you arbitrary headers and options, that you would then transparently roll into the message posting.
e.g.
mailgun.messages().send({from: <sender>, 'h:Reply-To': <relay>, to: <recipient>})
Issue Analytics
- State:
- Created 9 years ago
- Comments:12
Top Results From Across the Web
messages().send(data) should allow setting of headers and ...
It would be awesome of I could give you arbitrary headers and options, that you would then transparently roll into the message posting....
Read more >HTTP Messages - MDN Web Docs - Mozilla
The start-line and HTTP headers of the HTTP message are collectively known as the head of the requests, whereas its payload is known...
Read more >About FCM messages | Firebase Cloud Messaging - Google
Use data messages when you want to process the messages on your client app. FCM can send a notification message including an optional...
Read more >Messages — Mailgun API documentation
Mailgun will build a MIME representation of the message and send it. ... But you will have to specify all advanced sending options...
Read more >HTTP/1.1: Header Field Definitions
The Accept request-header field can be used to specify certain media types which are acceptable for the response. Accept headers can be used...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hello, that should already work. What version of the library are you using? For example this works for me:
The received email will have header
Reply-To: noreply@mailgun.com
, and clicking reply to will set the to email tonoreply@mailgun.com
.Hi @bojand It’s a fair point, and I can understand why you want to keep it as per the mailgun api, I just found it odd in the first place that mailgun didn’t allow you to specify replyTo as a regular param ( the way that say nodemailer does ). I thought it could be a useful ease of use feature for your library to add it as a first class citizen rather then having to remember the quite clunky h:Reply-To syntax.
Up to you though 😃