Django Scaleway Email
A small Django package that allows you to use Scaleway's transactional email API.
Requirements
To use this backend, you need an account with Scaleway and follow their setup guide for the transactional email service.
You can then create an IAM Application and generate a new API key for it.
Ensure the application has the TransactionalEmailEmailFullAccess permission.
Installation
-
Install the package with your package manager of choice:
pip install django-scaleway-email
-
Set your
EMAIL_BACKENDand configure your secrets:EMAIL_BACKEND = "django_scaleway_email.backend.EmailBackend" SCALEWAY_EMAIL_PROJECT_ID = "your-project-id" SCALEWAY_EMAIL_API_KEY = "your-api-key"
-
Done! You can now use
django.core.mail.send_mailetc. to send emails!
Django 6.1 MAILERS
Alternatively, this email backend supports Django's new MAILERS setting:
MAILERS = {
"default": {
"BACKEND": "django_scaleway_email.backend.EmailBackend",
"OPTIONS": {
"project_id": "YOUR_PROJECT_ID",
"api_key": "YOUR_API_KEY",
# optional:
"region": "fr-par",
"version": "v1alpha1",
"api_url": "", # overwrite the full API endpoint
},
}
}
Limitations
Scaleway imposes a few limitations on emails. Here's a short summary:
- Max. 10 recipients per email
- Max. 10 attachments
- Max. total email size is 2 MB
- Only certain types of attachments are allowed, see ATTACHMENT_TYPES
1 maintainer
Release files for django-scaleway-email 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| django_scaleway_email-0.2.1.tar.gz | 4.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_scaleway_email-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.7 kB
Release files / django_scaleway_email-0.2.1.tar.gz
| Download URL | django_scaleway_email-0.2.1.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
047d644d01696a822cfd988075fa5b3597e78581dee1c19dafc22f1c26a59dc8
|
|
BLAKE2b-256 checksum How to use checksums |
f785f027b134f8e9cb33df33bbdabeb33383277bdb5c5d7a9abe167aa13b211b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logRelease files / django_scaleway_email-0.2.1-py3-none-any.whl
| Download URL | django_scaleway_email-0.2.1-py3-none-any.whl |
|---|---|
| Size | 5.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a29227b54f1a1454eefed53d5ab8d8c584418629094d77dd59e94d4c376c6b17
|
|
BLAKE2b-256 checksum How to use checksums |
947ca9c7c32ce89fa7217329b8ff67370854f55378c31e0953cbb54b74c96455
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency log
