@@ -130,13 +130,6 @@ SendinBlue can handle.
130130 Anymail has no way to communicate an attachment's desired content-type
131131 to the SendinBlue API if the name is not set correctly.
132132
133- **No attachments with templates **
134- If you are sending using a SendinBlue template, their API doesn't support ordinary
135- file attachments. Attempting to send an attachment with a template will result in the
136- SendinBlue API error message, "Please don't pass attachment content & templateId in same
137- request, instead use attachment url only."
138- See the :ref: `templates <sendinblue-templates >` section below.
139-
140133**Single Reply-To **
141134 SendinBlue's v3 API only supports a single Reply-To address.
142135
@@ -226,19 +219,6 @@ If you want to use the template's sender, be sure to set ``from_email`` to ``Non
226219You can also override the template's subject and reply-to address (but not body)
227220using standard :class: `~django.core.mail.EmailMessage ` attributes.
228221
229- SendinBlue's template feature does not currently support providing attachment content
230- directly with the message---you'll get a SendinBlue API error if you try. If you must
231- send file attachments with SendinBlue templates, you can either upload them into
232- SendinBlue's template designer, or arrange to have the attachment content hosted on
233- a public URL and use Anymail's :attr: `~anymail.message.AnymailMessage.esp_extra `
234- to pass the URL to the SendinBlue API (see the Anymail SendinBlue integration tests
235- for an example of this). A better---and portable---option may be to avoid SendinBlue
236- templates and instead render the email in your Django code, allowing you to add any
237- file attachments you want. See :ref: `django-templates ` for details.
238-
239- (Note that SendinBlue doesn't support *inline * image attachments at all, whether you're
240- using a template or not.)
241-
242222
243223.. _new template language :
244224 https://help.sendinblue.com/hc/en-us/articles/360000268730
0 commit comments