Closed cjpitch23 closed 3 years ago
Why all recipients should be added to the to
field?
Also, please add appropriate tests. Your change is a black box right now.
Why all recipients should be added to the
to
field?
I was having an issue where recipients in the bcc
field weren't being sent the email. I looked at the Mailgun API and the messages.mime
route requires that bcc
and cc
recipients be added to the to
parameter.
https://documentation.mailgun.com/en/latest/api-sending.html#sending
Maybe I am misunderstanding it, but whenever I changed the code, I didn't have any more issues.
Also, please add appropriate tests. Your change is a black box right now.
I will add the tests.
Yup, its always nice to share the source of your information. Otherwise I have no idea why the change was being made.
Following is the relevant source for the change
Yup, its always nice to share the source of your information. Otherwise I have no idea why the change was being made.
Haha Yeah I suppose a screen shot of the information would have been the more direct approach than just linking the documentation. I'm just happy I helped out a little bit.
I ran the code through the linter and corrected the semi colon issue. I ran the tests and they all cleared. Since the bugfix is covered by send email using mailgun driver
test, it seems to be excessive to add another test just to test the recipients in the mailgun driver..
These tests are failing because there is no .env
with the api keys for the different mail drivers, right? Am I suppose to do something to fix that?
Nope. And thanks for the fix
I'm glad I could contribute a little bit. Thank you guys, Adonis is awesome.
Added bcc and cc to 'to' for MIME
Proposed changes
Added
bcc
andcc
recipients to theto
key on the form for MIME to be able to process and send out emails.Types of changes
What types of changes does your code introduce?
Put an
x
in the boxes that applyChecklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...