search

brack3t / Djrill

[INACTIVE/UNMAINTAINED] Djrill is an email backend and new message class for Django users that want to take advantage of the Mandrill transactional email service from MailChimp.
BSD 3-Clause "New" or "Revised" License
319 stars 64 forks source link

Metadata not submitting properly #43

Closed m1ket closed 11 years ago

m1ket commented 11 years ago

I have set up a number of metadata variables to send to Mandrill. I have registered these variables for indexing in Mandrill. However, the metadata isn't registering properly in Mandrill.

I'm trying to figure out if there's a way I can debug the Djrill code to physically see that the metadata is being sent properly.

Does anyone have any advice?

Example metadata code:

msg.metadata = { 'first_name': user.first_name, 'last_name': user.last_name }

m1ket commented 11 years ago

Turns out Mandrill have API logs that are accessible in their backend. I can see the JSON with the Metadata I sent over through Djrill.

Log also says that it was a valid API call, the JSON has passed through a validator, the metadata keys are in my custom metadata index list.

Is there anything I'm missing?

I've sent a ticket to Mandrill to try and get them to help.

medmunds commented 11 years ago

Could you post the JSON of one of the calls that doesn't work? (And/or compare the metadata fields in it to the Mandrill API spec.)

There have been cases in the past where we (well, I) misread the Mandrill spec, and Djrill generated valid JSON that was not a valid Mandrill API call. I thought I'd fixed them all, but maybe missed something.

On Sun, Jul 28, 2013 at 11:57 AM, m1ket notifications@github.com wrote:

Turns out Mandrill have API logs that are accessible in their backend. I can see the JSON with the Metadata I sent over through Djrill.

Log also says that it was a valid API call, the JSON has passed through a validator, the metadata keys are in my custom metadata index list.

Is there anything I'm missing?

I've sent a ticket to Mandrill to try and get them to help.

— Reply to this email directly or view it on GitHubhttps://github.com/brack3t/Djrill/issues/43#issuecomment-21688716 .

medmunds commented 11 years ago

@m1ket did you get any feedback on this from Mandrill support?

If the Mandrill API logs are showing that Djrill is sending the metadata to Mandrill, I don't think there's much we can do on Djrill's end to help.

Please feel free to reopen this issue with additional info if you're still seeing the problem. (An example of the failing JSON from Mandrill's API log would be helpful to diagnose.)