- Fix _send inconsistent return format (PR #106)
- Allow django_backend to take advantage of message_streams (PR #103)
- Encoding issues (PR #91)
- Add message_stream attribute to PMMail (PR #94)
- Setting to return message IDs in django backend (PR #89)
- Fix for sending batch emails with templates (PR #87)
- Allow empty "to" field if "bcc" is populated (PR #83)
- EmailMultiAlternatives content_subtype fix (PR #82)
- Postmark metadata support (PR #75)
- Postmark templates support (PR #63)
- EmailMessage.reply_to fix and housekeeping
- Account for EmailMessage.reply_to (#68)
- Added inline images support (#47)
- Fix for attachments in Python 3 (issue #66, PR #67)
- Tornado mixin (tigrus)
- PMJSONEncoder unicode changes (mattrobenolt)
- Handle inactive recipient errors (nicholasserra)
- Fix base64 encoding in Django API for attachments (thanosd)
- Fix for using content subtype in Django backend for HTML email (ryankuczka)
- Fix for Python 3 support (issue #42, PR #43) (mflaxman)
- Minor code cleanup (Stranger6667)
- Fix for Django 1.5+ ugettext_lazy strings being improperly converted (#11, #41) (justinabrahms, rduffield)
- Demo brought up to Django 1.6 (catskul)
- Added message_id property to messages for post-send record-tracking (jdavisp3)
- Added in .track_opens to support open tracking See: http://developer.postmarkapp.com/developer-build.html#open-tracking
- Added POSTMARK_TRACK_OPENS setting to the Django backend (danxshap)
- Don't require
content_subtypein Django backend to be set to"html"(danxshap)
- Merged proper handling of content_subtype in the Django backend - thanks Josh Owen!
- Merged in Python 3 support - thanks Jacob!
- Moving minimum Python version to 2.6. If you need 2.4 support, please continue to use v0.3.2!
- Uses simplejson if installed for faster C _speedups
- PMBatchMail properly chunks large message sets
- Django backend uses PMBatchMail properly
- Use https by default
- Proper testing API key out of the box
- Cleaned up some PMBatchMail properties
- Added a few utility methods (add_message, remove_message) to PMBatchMail
- Added proper value checking to PMBatchMail pre-send
- A BIG THANKS to all new contributors!
- Added batch-messaging support (PMBatchMail object) (deeGraYve) See http://developer.postmarkapp.com/developer-build.html#batching-messages
- Merged in support for adding a tag through the Django backend (joelryan2k)
- Merged in support for POSTMARK_TEST_MODE overriding and beter settings defaults (benhodgson)
- Merged in email mime import fix from brimcfadden
- Merged in POSTMARK_TEST_MODE Django setting from maraujop
- Merged with frozenskys/master to bring in PMBounceManager
- Support for multiple to/cc (limit: 20 per)
- Changed .recipient to .to (legacy support for .recipient left in)
- Tag support (.tag) added
- Fixed the email endpoint
- Fixed a Django backend issue for multiple recipients (max 20)
- Added a new PMBounceManager Class that allows easy access to the PostMark bounce API.
- Added ".cc" property for carbon copy recipients. Changed django_backend to support multiple recipients, and to use "to" rather than "recipients" on the django mail object to prevent accidental leakage of BCC recipients.
- Added ".reply_to" property. The "ReplyTo" custom header is unallowed by Postmark now, and their documentation has been updated to reflect the change. http://developer.postmarkapp.com
- Major fix to the way properties were being used, fixes doc strings in properties
- "custom_headers" is now always a dict, even if set to None
- Added 'custom_headers' property (must be a dictionary) to PMMail object
- Added optional 'test' argument to send function to print JSON message instead of actually sending it
- Initial release