# Dokumentasi Django 5.2.8

# Mengirim surel

Although Python provides a mail sending interface via the `smtplib` module, Django provides a couple of light wrappers over it. These wrappers are provided to make sending email extra quick, to help test email sending during development, and to provide support for platforms that can't use SMTP.

Kode tinggal dalam modul `django.core.mail`.

## Quick examples

Use `send_mail()` for straightforward email sending. For example, to send a plain text message:

    from django.core.mail import send_mail

    send_mail(
        "Subject here",
        "Here is the message.",
        "from@example.com",
        ["to@example.com"],
        fail_silently=False,
    )

When additional email sending functionality is needed, use `EmailMessage` or `EmailMultiAlternatives`. For example, to send a multipart email that includes both HTML and plain text versions with a specific template and custom headers, you can use the following approach:

    from django.core.mail import EmailMultiAlternatives
    from django.template.loader import render_to_string

    # First, render the plain text content.
    text_content = render_to_string(
        "templates/emails/my_email.txt",
        context={"my_variable": 42},
    )

    # Secondly, render the HTML content.
    html_content = render_to_string(
        "templates/emails/my_email.html",
        context={"my_variable": 42},
    )

    # Then, create a multipart email instance.
    msg = EmailMultiAlternatives(
        subject="Subject here",
        body=text_content,
        from_email="from@example.com",
        to=["to@example.com"],
        headers={"List-Unsubscribe": "<mailto:unsub@example.com>"},
    )

    # Lastly, attach the HTML content to the email instance and send.
    msg.attach_alternative(html_content, "text/html")
    msg.send()

Surat dikirim menggunakan rumah SMTP dan port ditentukan dalam pengaturan `EMAIL_HOST` dan `EMAIL_PORT`. Pengaturan `EMAIL_HOST_USER` dan `EMAIL_HOST_PASSWORD` settings, jika disetel, digunakan untuk mengotentifikasi pada peladen SMTP, dan pengaturan `EMAIL_USE_TLS` dan `EMAIL_USE_SSL` mengendalikan apakah hubungan aman digunakan.

Catatan

Kumpulan karakter dari surel dikirim dengan `django.core.mail` akan disetel ke nilai dari pengaturan `DEFAULT_CHARSET` anda.

## `send_mail()`

send_mail(subject, message, from_email, recipient_list, *, fail_silently=False, auth_user=None, auth_password=None, connection=None, html_message=None)

Dalam kebanyakan kasus, anda dapat mengirim surel menggunakan `django.core.mail.send_mail()`.

Parameter `subject`, `message`, `from_email` dan `recipient_list` dibutuhkan.

- `subject`: Sebuah string.

- `message`: Sebuah string.

- `from_email`: Sebuah string. Jika `None`, Django aan menggunakan nilai dari pengaturan `DEFAULT_FROM_EMAIL`.

- `recipient_list`: Sebuah daftar dari string, setiap alamat surel. Setiap anggota dari `recipient_list` akan melihat penerima lain dalam bidang "To:" dari pesan surel.

The following parameters are optional, and must be given as keyword arguments if used.

- `fail_silently`: A boolean. When it's `False`, `send_mail()` will raise an `smtplib.SMTPException` if an error occurs. See the `smtplib` docs for a list of possible exceptions, all of which are subclasses of `SMTPException`.

- `auth_user`: Pilihan nama pengguna untuk digunakan mengautentifikasi ke peladen SMTP. Jika ini tidak disediakan, Django akan menggunakan nilai dari pengaturan `EMAIL_HOST_USER`.

- `auth_password`: Sandi pilihan digunakan untuk mengautentifikasi ke peladen SMTP. Jika ini tidak disediakan, Django akan menggunakan nilai dari pengaturan `EMAIL_HOST_PASSWORD`

- `connection`: Backend surel pilihan digunakan untuk mengirim surat. Jika tidak ditentukan, sebuah instance dari backend awalan akan digunakan. Lihat dokumentasi pada Email backends 1 untuk rincian lebih.

- `html_message`: Jika `html_message` disediakan, surel dihasilkan akan berupa surel multipart/alternative dengan `message` sebagai jenis isi text/plain dan `html_message` sebagai jenis isi text/html.

Nilai kembalian akan berupa angka dari pesan terkirim yang berhasil (yang dapat berupa `0` atau `1` sejak itu hanya daoat mengirim satu pesan).

Deprecated since version 6.0: Passing `fail_silently` and later parameters as positional arguments is deprecated.

## `send_mass_mail()`

send_mass_mail(datatuple, *, fail_silently=False, auth_user=None, auth_password=None, connection=None)

`django.core.mail.send_mass_mail()` diperuntukkan untuk menangani penyuratan elektronik masal.

`datatuple` adalah sebuah tuple yang setiap unsur adalah dalam bentuk ini:

    (subject, message, from_email, recipient_list)

`fail_silently`, `auth_user`, `auth_password` and `connection` have the same functions as in `send_mail()`. They must be given as keyword arguments if used.

Each separate element of `datatuple` results in a separate email message. As in `send_mail()`, recipients in the same `recipient_list` will all see the other addresses in the email messages' "To:" field.

Sebagai contoh, kode berikut akan mengirim dua pesan berbeda pada dua kumpulan berbeda dari penerima; bagaimanapun, hanya satu hubungan ke peladen surat akan dibuka:

    message1 = (
        "Subject here",
        "Here is the message",
        "from@example.com",
        ["first@example.com", "other@example.com"],
    )
    message2 = (
        "Another Subject",
        "Here is another message",
        "from@example.com",
        ["second@test.com"],
    )
    send_mass_mail((message1, message2), fail_silently=False)

Nilai kembalian akan berupa angka dari pesan terkirim berhasil.

Deprecated since version 6.0: Passing `fail_silently` and later parameters as positional arguments is deprecated.

### `send_mass_mail()` x `send_mail()`

The main difference between `send_mass_mail()` and `send_mail()` is that `send_mail()` opens a connection to the mail server each time it's executed, while `send_mass_mail()` uses a single connection for all of its messages. This makes `send_mass_mail()` slightly more efficient.

## `mail_admins()`

mail_admins(subject, message, *, fail_silently=False, connection=None, html_message=None)

`django.core.mail.mail_admins()` adalah jalan pintas untuk mengirim sebuah surel pada admin situs, seperti ditentukan dalam pengaturan `ADMINS`.

`mail_admins()` mengawali subyek dengan nilai dari pengaturan `EMAIL_SUBJECT_PREFIX`, yaitu `"[Django] "` secara awalan.

Kepala "From:" dari surel akan berupa nilai dari pengaturan `SERVER_EMAIL`.

Metode ini ada untuk kenyamanan dan kesiapan.

Jika `html_message` disediakan, surel dihasilkan akan berupa surel multipart/alternative dengan `message` seperti jenis isi text/plain dan `html_message` seperti jenis isi text/html.

Deprecated since version 6.0: Passing `fail_silently` and later parameters as positional arguments is deprecated.

## `mail_managers()`

mail_managers(subject, message, *, fail_silently=False, connection=None, html_message=None)

`django.core.mail.mail_managers()` seperti `mail_admins()`, kecuali itu mengirim sebuah surel ke pengelola situs, seperti ditentukan dalam pengaturan `MANAGERS`.

Deprecated since version 6.0: Passing `fail_silently` and later parameters as positional arguments is deprecated.

## Contoh

Ini mengirim surel tunggal kepada john@example.com dan jane@example.com, dengan keduanya mereka muncul dalam "To:":

    send_mail(
        "Subject",
        "Message.",
        "from@example.com",
        ["john@example.com", "jane@example.com"],
    )

This sends a message to `john@example.com` and `jane@example.com`, with them both receiving a separate email:

    datatuple = (
        ("Subject", "Message.", "from@example.com", ["john@example.com"]),
        ("Subject", "Message.", "from@example.com", ["jane@example.com"]),
    )
    send_mass_mail(datatuple)

## Mencegah penyuntikan kepala

Header injection adalah memanfaatkan keamanan dimana seorang penyerang memasukkan kepala surel tambahan untuk mengendalikan "To:" dan "From:" dalam pesan-pesan surel yang tulisan-tulisan anda dibangkitkan.

The Django email functions outlined above all protect against header injection by forbidding newlines in header values. If any `subject`, `from_email` or `recipient_list` contains a newline (in either Unix, Windows or Mac style), the email function (e.g. `send_mail()`) will raise `ValueError` and, hence, will not send the email. It's your responsibility to validate all data before passing it to the email functions.

If a `message` contains headers at the start of the string, the headers will be printed as the first bit of the email message.

Here's an example view that takes a `subject`, `message` and `from_email` from the request's POST data, sends that to `admin@example.com` and redirects to "/contact/thanks/" when it's done:

    from django.core.mail import send_mail
    from django.http import HttpResponse, HttpResponseRedirect

    def send_email(request):
        subject = request.POST.get("subject", "")
        message = request.POST.get("message", "")
        from_email = request.POST.get("from_email", "")
        if subject and message and from_email:
            try:
                send_mail(subject, message, from_email, ["admin@example.com"])
            except ValueError:
                return HttpResponse("Invalid header found.")
            return HttpResponseRedirect("/contact/thanks/")
        else:
            # In reality we'd use a form class
            # to get proper validation errors.
            return HttpResponse("Make sure all fields are entered and valid.")

Changed in Django 6.0:

Older versions raised `django.core.mail.BadHeaderError` for some invalid headers. This has been replaced with `ValueError`.

## Kelas `EmailMessage`

Django's `send_mail()` and `send_mass_mail()` functions are actually thin wrappers that make use of the `EmailMessage` class.

Not all features of the `EmailMessage` class are available through the `send_mail()` and related wrapper functions. If you wish to use advanced features, such as BCC'ed recipients, file attachments, or multi-part email, you'll need to create `EmailMessage` instances directly.

Catatan

This is a design feature. `send_mail()` and related functions were originally the only interface Django provided. However, the list of parameters they accepted was slowly growing over time. It made sense to move to a more object-oriented design for email messages and retain the original functions only for backwards compatibility.

`EmailMessage` is responsible for creating the email message itself. The email backend is then responsible for sending the email.

For convenience, `EmailMessage` provides a `send()` method for sending a single email. If you need to send multiple messages, the email backend API provides an alternative.

### Obyek `EmailMessage`

class EmailMessage

  The `EmailMessage` class is initialized with the following parameters. All parameters are optional and can be set at any time prior to calling the `send()` method.

  The first four parameters can be passed as positional or keyword arguments, but must be in the given order if positional arguments are used:

  - `subject`: Pokok baris dari surel.

  - `body`: Teks badan. Ini harus berupa pesan teks polos.

  - `from_email`: The sender's address. Both `fred@example.com` and `"Fred" <fred@example.com>` forms are legal. If omitted, the `DEFAULT_FROM_EMAIL` setting is used.

  - `to`: Sebuah list atau tuple dari alamat-alamat penerima.

  The following parameters must be given as keyword arguments if used:

  - `cc`: Sebuah list atau tuple dari alamat-alamat penerima digunakan dalam kepala "Cc" ketika mengirim surel.

  - `bcc`: Sebuah list atau tuple dari alamat-alamat digunakan dalam kepala "Bcc" ketika mengirim surel.

  - `reply_to`: Sebuah list atau tuple dari alamat-alamat penerima dalam kepala "Reply-To" ketika mengirim surel.

  - `attachments`: A list of attachments to put on the message. Each can be an instance of `MIMEPart` or `EmailAttachment`, or a tuple with attributes `(filename, content, mimetype)`.

    Changed in Django 5.2:

    Support for `EmailAttachment` items of `attachments` was added.

    Changed in Django 6.0:

    Support for `MIMEPart` objects in the `attachments` list was added.

    Deprecated since version 6.0: Support for Python's legacy `MIMEBase` objects in `attachments` is deprecated. Use `MIMEPart` instead.

  - `header`: Sebuah dictionary dari kepala tambahan untuk menaruh pesan. Kunci-kunci adalah nama kepala, nilai-nilai adalah nilai-nilai kepala. Itu terserah pada pemanggil untuk memastikan nama=nama dan nilai-nilai dalam bentuk benar untuk pesan surel. Atribut sesuai adalah `extra_headers`.

  - `connection`: An email backend instance. Use this parameter if you are sending the `EmailMessage` via `send()` and you want to use the same connection for multiple messages. If omitted, a new connection is created when `send()` is called. This parameter is ignored when using send_messages().

  Deprecated since version 6.0: Passing all except the first four parameters as positional arguments is deprecated.

  Sebagai contoh:

      from django.core.mail import EmailMessage

      email = EmailMessage(
          subject="Hello",
          body="Body goes here",
          from_email="from@example.com",
          to=["to1@example.com", "to2@example.com"],
          bcc=["bcc@example.com"],
          reply_to=["another@example.com"],
          headers={"Message-ID": "foo"},
      )

  Kelas mempunyai cara berikut:

  send(fail_silently=False)

    Sends the message. If a connection was specified when the email was constructed, that connection will be used. Otherwise, an instance of the default backend will be instantiated and used. If the keyword argument `fail_silently` is `True`, exceptions raised while sending the message will be quashed. An empty list of recipients will not raise an exception. It will return `1` if the message was sent successfully, otherwise `0`.

  message(policy=email.policy.default)

    Constructs and returns a Python `email.message.EmailMessage` object representing the message to be sent.

    The keyword argument `policy` allows specifying the set of rules for updating and serializing the representation of the message. It must be an `email.policy.Policy` object. Defaults to `email.policy.default`. In certain cases you may want to use `SMTP`, `SMTPUTF8` or a custom policy. For example, `django.core.mail.backends.smtp.EmailBackend` uses the `SMTP` policy to ensure `\r\n` line endings as required by the SMTP protocol.

    If you ever need to extend Django's `EmailMessage` class, you'll probably want to override this method to put the content you want into the Python EmailMessage object.

    Changed in Django 6.0:

    The `policy` keyword argument was added and the return type was updated to an instance of `EmailMessage`.

  recipients()

    Returns a list of all the recipients of the message, whether they're recorded in the `to`, `cc` or `bcc` attributes. This is another method you might need to override when subclassing, because the SMTP server needs to be told the full list of recipients when the message is sent. If you add another way to specify recipients in your class, they need to be returned from this method as well.

  attach(filename, content, mimetype)
  attach(mimepart)

    Creates a new attachment and adds it to the message. There are two ways to call `attach()`:

    - You can pass it three arguments: `filename`, `content` and `mimetype`. `filename` is the name of the file attachment as it will appear in the email, `content` is the data that will be contained inside the attachment and `mimetype` is the optional MIME type for the attachment. If you omit `mimetype`, the MIME content type will be guessed from the filename of the attachment.

      Sebagai contoh:

          message.attach("design.png", img_data, "image/png")

      If you specify a `mimetype` of message/rfc822, `content` can be a `django.core.mail.EmailMessage` or Python's `email.message.EmailMessage` or `email.message.Message`.

      For a `mimetype` starting with text/, content is expected to be a string. Binary data will be decoded using UTF-8, and if that fails, the MIME type will be changed to application/octet-stream and the data will be attached unchanged.

    - Or for attachments requiring additional headers or parameters, you can pass `attach()` a single Python `MIMEPart` object. This will be attached directly to the resulting message. For example, to attach an inline image with a Content-ID:

          cid = email.utils.make_msgid()
          inline_image = email.message.MIMEPart()
          inline_image.set_content(
              image_data_bytes,
              maintype="image",
              subtype="png",
              disposition="inline",
              cid=f"<{cid}>",
          )
          message.attach(inline_image)
          message.attach_alternative(f'… <img src="cid:${cid}"> …', "text/html")

      Python's `email.contentmanager.set_content()` documentation describes the supported arguments for `MIMEPart.set_content()`.

      Changed in Django 6.0:

      Support for `MIMEPart` attachments was added.

      Deprecated since version 6.0: Support for `email.mime.base.MIMEBase` attachments is deprecated. Use `MIMEPart` instead.

  attach_file(path, mimetype=None)

    Creates a new attachment using a file from your filesystem. Call it with the path of the file to attach and, optionally, the MIME type to use for the attachment. If the MIME type is omitted, it will be guessed from the filename. You can use it like this:

        message.attach_file("/images/weather_map.png")

    For MIME types starting with text/, binary data is handled as in `attach()`.

class EmailAttachment
  New in Django 5.2.

  A named tuple to store attachments to an email.

  The named tuple has the following indexes:

  - `filename`

  - `content`

  - `mimetype`

### Mengirim pilihan lain jenis isi

#### Sending multiple content versions

It can be useful to include multiple versions of the content in an email; the classic example is to send both text and HTML versions of a message. With Django's email library, you can do this using the `EmailMultiAlternatives` class.

class EmailMultiAlternatives

  A subclass of `EmailMessage` that allows additional versions of the message body in the email via the `attach_alternative()` method. This directly inherits all methods (including the class initialization) from `EmailMessage`.

  alternatives

    A list of `EmailAlternative` named tuples. This is particularly useful in tests:

        self.assertEqual(len(msg.alternatives), 1)
        self.assertEqual(msg.alternatives[0].content, html_content)
        self.assertEqual(msg.alternatives[0].mimetype, "text/html")

    Alternatives should only be added using the `attach_alternative()` method, or passed to the constructor.

    Changed in Django 5.2:

    In older versions, `alternatives` was a list of regular tuples, as opposed to `EmailAlternative` named tuples.

  attach_alternative(content, mimetype)

    Attach an alternative representation of the message body in the email.

    For example, to send a text and HTML combination, you could write:

        from django.core.mail import EmailMultiAlternatives

        subject = "hello"
        from_email = "from@example.com"
        to = "to@example.com"
        text_content = "This is an important message."
        html_content = "<p>This is an <strong>important</strong> message.</p>"
        msg = EmailMultiAlternatives(subject, text_content, from_email, [to])
        msg.attach_alternative(html_content, "text/html")
        msg.send()

  body_contains(text)
    New in Django 5.2.

    Returns a boolean indicating whether the provided `text` is contained in the email `body` and in all attached MIME type `text/*` alternatives.

    This can be useful when testing emails. For example:

        def test_contains_email_content(self):
            subject = "Hello World"
            from_email = "from@example.com"
            to = "to@example.com"
            msg = EmailMultiAlternatives(subject, "I am content.", from_email, [to])
            msg.attach_alternative("<p>I am content.</p>", "text/html")

            self.assertIs(msg.body_contains("I am content"), True)
            self.assertIs(msg.body_contains("<p>I am content.</p>"), False)

class EmailAlternative
  New in Django 5.2.

  A named tuple to store alternative versions of email content.

  The named tuple has the following indexes:

  - `content`

  - `mimetype`

#### Updating the default content type

By default, the MIME type of the `body` parameter in an `EmailMessage` is `"text/plain"`. It is good practice to leave this alone, because it guarantees that any recipient will be able to read the email, regardless of their mail client. However, if you are confident that your recipients can handle an alternative content type, you can use the `content_subtype` attribute on the `EmailMessage` class to change the main content type. The major type will always be `"text"`, but you can change the subtype. For example:

    msg = EmailMessage(subject, html_content, from_email, [to])
    msg.content_subtype = "html"  # Main content is now text/html
    msg.send()

## Backend email

Pengiriman sebenarnya dari sebuah surel ditangani oleh backend email.

Kelas backend surel mempunyai metode-metode berikut:

- `open()` instantiates a long-lived email-sending connection.

- `close()` menutup hubungan mengirim-surel saat ini.

- `send_messages(email_messages)` sends a list of `EmailMessage` objects. If the connection is not open, this call will implicitly open the connection, and close the connection afterward. If the connection is already open, it will be left open after mail has been sent.

Itu dapat juga digunakan sebagai pengelola konteks, yang akan otomatis memanggil `open()` dan `close()` sesuai kebutuhan:

    from django.core import mail

    with mail.get_connection() as connection:
        mail.EmailMessage(
            subject1,
            body1,
            from1,
            [to1],
            connection=connection,
        ).send()
        mail.EmailMessage(
            subject2,
            body2,
            from2,
            [to2],
            connection=connection,
        ).send()

### Mengambil sebuah instance dari sebuah backend surel.

The `get_connection()` function in `django.core.mail` returns an instance of the email backend that you can use.

get_connection(backend=None, *, fail_silently=False, **kwargs)

Secara awalan, sebuah panggilan pada `get_connection()` akan mengembalikan sebuah instance dari backend surel ditentukan dalam `EMAIL_BACKEND`. Jika anda menentukan argumen `backend`, sebuah instance dari backend itu akan diinstasiasikan.

The keyword-only `fail_silently` argument controls how the backend should handle errors. If `fail_silently` is True, exceptions during the email sending process will be silently ignored.

All other keyword arguments are passed directly to the constructor of the email backend.

Django dikirim dengan beberapa backend pengiriman surel. Dengan pengecualian dari backend SMTP (yaitu awalan), backend ini hanya berguna selama percobaan dan pengembangan. Jika anda mempunyai persyaratan mengirim surel khusus, anda dapat write your own email backend.

Deprecated since version 6.0: Passing `fail_silently` as positional argument is deprecated.

#### Backend SMTP

class backends.smtp.EmailBackend(host=None, port=None, username=None, password=None, use_tls=None, fail_silently=False, use_ssl=None, timeout=None, ssl_keyfile=None, ssl_certfile=None, **kwargs)

  Ini adalah backend awalan. Surel akan dikirim melalui peladen SMTP.

  Nilai untuk setiap argumen diambil dari pencocokan pengaturan jika argumen adalah `None`:

  - `host`: `EMAIL_HOST`

  - `port`: `EMAIL_PORT`

  - `username`: `EMAIL_HOST_USER`

  - `password`: `EMAIL_HOST_PASSWORD`

  - `use_tls`: `EMAIL_USE_TLS`

  - `use_ssl`: `EMAIL_USE_SSL`

  - `timeout`: `EMAIL_TIMEOUT`

  - `ssl_keyfile`: `EMAIL_SSL_KEYFILE`

  - `ssl_certfile`: `EMAIL_SSL_CERTFILE`

  Backend SMTP adalah konfigurasi awalan diwarisi oleh Django. Jika anda ingin menentukan itu secara jelas, taruh berikut dalam pengaturan anda:

      EMAIL_BACKEND = "django.core.mail.backends.smtp.EmailBackend"

  If unspecified, the default `timeout` will be the one provided by `socket.getdefaulttimeout()`, which defaults to `None` (no timeout).

#### Backend konsol

Daripada mengirim keluar surel asli backend konsol hanya menulis surel yang akan dikirim ke keluaran standar. Secara awalan, backend konsol menulis ke `stdout`. Anda dapat menggunakan obyek aliran-seperti berbeda dengan menyediakan argumen katakunci `stream` ketika membangun hubungan.

Untuk menentukan backend ini, taruh berikut dalam pengaturan anda:

    EMAIL_BACKEND = "django.core.mail.backends.console.EmailBackend"

Backend ini tidak diperuntukkan untuk penggunaan dalam produksi -- itu disediakan sebagai kenyamanan yang dapat digunakan selama pengembangan.

#### Backend berkas

The file backend writes emails to a file. A new file is created for each new session that is opened on this backend. The directory to which the files are written is either taken from the `EMAIL_FILE_PATH` setting or from the `file_path` keyword when creating a connection with `get_connection()`.

Untuk menentukan backend ini, taruh berikut dalam pengaturan anda:

    EMAIL_BACKEND = "django.core.mail.backends.filebased.EmailBackend"
    EMAIL_FILE_PATH = "/tmp/app-messages"  # change this to a proper location

Backend ini tidak diperuntukkan untuk penggunaan dalam produksi -- itu disediakan sebagai kenyamanan yang dapat digunakan selama pengembangan.

#### backend di-memory

The `'locmem'` backend stores messages in a special attribute of the `django.core.mail` module. The `outbox` attribute is created when the first message is sent. It's a list with an `EmailMessage` instance for each message that would be sent.

Untuk menentukan backend ini, taruh berikut dalam pengaturan anda:

    EMAIL_BACKEND = "django.core.mail.backends.locmem.EmailBackend"

Backend ini tidak dimaksudkan untuk digunakan dalam produksi -- itu disediakan sebagai kenyamanan yang dapat digunakan selama pengembangan dan percobaan.

Django's test runner automatically uses this backend for testing.

#### Backend tiruan

Ketika nama menganjurkan backend tiruan tidak melakukan apapun dengan pesan-pesan anda. Untuk menentukan backend ini, taruh berikut dalam pengaturan anda:

    EMAIL_BACKEND = "django.core.mail.backends.dummy.EmailBackend"

Backend ini tidak diperuntukkan untuk penggunaan dalam produksi -- itu disediakan sebagai kenyamanan yang dapat digunakan selama pengembangan.

There are community-maintained solutions too!

Django has a vibrant ecosystem. There are email backends highlighted on the Community Ecosystem page. The Django Packages Email grid has even more options for you!

### Menentukan penyesuaian backend surel

Jika anda butuh merubah bagaimana surel dikirim anda dapat menulis backend surel anda sendiri. Pengaturan `EMAIL_BACKEND` dalam berkas pengaturan anda adalah kemudian Pythn mengimpor jalur untuk kelas backend anda.

Custom email backends should subclass `BaseEmailBackend` that is located in the `django.core.mail.backends.base` module. A custom email backend must implement the `send_messages(email_messages)` method. This method receives a list of `EmailMessage` instances and returns the number of successfully delivered messages. If your backend has any concept of a persistent session or connection, you should also implement the `open()` and `close()` methods. Refer to `smtp.EmailBackend` for a reference implementation.

### Mengirim banyak surel

Membangun dan menutup hubungan SMTP (atau hubungan jaringan lain, untuk masalah itu) adalah sebuah pengolahan yang mahal. Jika anda mempunyai banyak surel untuk dikirim, itu masuk akal menggunakan kembali hubungan SMTP, daripada membuat dan manghancurkan hubungan setiap kali anda ingin mengirim surel.

Ada dua cara memberitahu sebuah backend surel untuk menggunakan kembali sebuah hubungan.

Firstly, you can use the `send_messages()` method on a connection. This takes a list of `EmailMessage` (or subclass) instances, and sends them all using that single connection. As a consequence, any `connection` set on an individual message is ignored.

For example, if you have a function called `get_notification_email()` that returns a list of `EmailMessage` objects representing some periodic email you wish to send out, you could send these emails using a single call to `send_messages()`:

    from django.core import mail

    connection = mail.get_connection()  # Use default email connection
    messages = get_notification_email()
    connection.send_messages(messages)

Dalam contoh ini, panggilan pada `send_messages()` membuka hubungan pada backend, mengirim daftar pesan-pesan, dan kemudian menutup hubungan kembali.

Pendekatan kedua adalah menggunakan metode `open()` dan `close()` pada backend surel untuk secara manual mengendalikan hubungan. `send_messages()` tidak akan secara manual membuka atau menutup hubungan jika itu sudah terbuka, jadi jika anda membuka secara munual hubungan, anda dapat mengendalikan ketika itu tertutup. Sebagai contoh:

    from django.core import mail

    connection = mail.get_connection()

    # Manually open the connection
    connection.open()

    # Construct an email message that uses the connection
    email1 = mail.EmailMessage(
        "Hello",
        "Body goes here",
        "from@example.com",
        ["to1@example.com"],
        connection=connection,
    )
    email1.send()  # Send the email

    # Construct two more messages
    email2 = mail.EmailMessage(
        "Hello",
        "Body goes here",
        "from@example.com",
        ["to2@example.com"],
    )
    email3 = mail.EmailMessage(
        "Hello",
        "Body goes here",
        "from@example.com",
        ["to3@example.com"],
    )

    # Send the two emails in a single call -
    connection.send_messages([email2, email3])
    # The connection was already open so send_messages() doesn't close it.
    # We need to manually close the connection.
    connection.close()

## Konfigurasi surel untuk pengembangan

Ada saatnya ketika anda tidak ingn Django mengirim surel sama sekali. Sebagai contoh, selagi mengembangkan sebuah situs jaringan, anda mungkin tidak ingin mengirim ribuan surel -- tetapi anda mungkin ingin mensahkan surel akan dikirim ke orang benar dibawah suasana yang benar, dan surel itu akan mengandung isi benar.

The easiest way to configure email for local development is to use the console email backend. This backend redirects all email to `stdout`, allowing you to inspect the content of mail.

Backend surel file dapat berguna selama pengembangan -- backend ini membuang isi dari setiap hubungan SMTP ke sebuah berkas yang dapat diperiksa pada waktu luang anda.

Another approach is to use a "dumb" SMTP server that receives the emails locally and displays them to the terminal, but does not actually send anything. The aiosmtpd package provides a way to accomplish this:

    python -m pip install "aiosmtpd >= 1.4.5"

    python -m aiosmtpd -n -l localhost:8025

This command will start a minimal SMTP server listening on port 8025 of localhost. This server prints to standard output all email headers and the email body. You then only need to set the `EMAIL_HOST` and `EMAIL_PORT` accordingly. For a more detailed discussion of SMTP server options, see the documentation of the aiosmtpd module.

For information about unit-testing the sending of emails in your application, see the Layanan surel section of the testing documentation.