Repository navigation
Record the sponsor email route on newsletter bookings and reply in thread from report --send - #392
Merged
Merged
Conversation
…read from report --send email-sponsor sends set slot.route (to, cc, sender, threadRef) and copy it onto the slot's send Tasks. newsletter report prints it; report --send replies in the Gmail thread from orin@ and closes the Task with the Gmail message id; a missing route is a 422. newsletter route adopts an already-sent email-sponsor message.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
email-sponsor sends set slot.route (to, cc, sender, threadRef) and copy it onto
the slot's send Tasks. newsletter report prints it; report --send replies in the
Gmail thread from orin@ and closes the Task with the Gmail message id; a missing
route is a 422. newsletter route adopts an already-sent email-sponsor message.