anchor.diff:  email.send("to@example.com", {"template": "context"})
   ----
   
  -If you want obtain django native Email instance:
  +Also you can obtain a native django email instance from TemplateMail instance:
   
   [source, python]
   ----
   # Create a instance
   template_email = SomeTemplateEmail()
   
  -# Or obtain a native django email object
  +# obtain a native django email object
   email = template_email.make_email_object("to@example.com",
                                            {"template": "context"})
   email.send()
  
positive.code: email = mails.some_email(user, {"template": "context"})
  ----
  
  Magic builder is really magic, and if your user has lang field, magic builder uses it to setup a correct user language
  for render email in user locale.
  
  NOTE: Also, you can specify a custom "lang" on context for same purpose.
  
  Settings
  --------
  
  djmail exposes some additional settings for costumize a great part of default behavior.
  
  - *DJMAIL_REAL_BACKEND* +
    Indicates to djmail which a real email backend use for deliver email messages. +
    Default: `django.core.mail.backends.console.EmailBackend`
  - *DJMAIL_MAX_RETRY_NUMBER* +
    Set a default maximum retry number for deliver failed messages. +
    Default: 3
  - *DJMAIL_BODY_TEMPLATE_PROTOTYPE* +
    Prototype for make body template path. +
    Default: `emails/{name}-body-{type}.{ext}`
  - *DJMAIL_SUBJECT_TEMPLATE_PROTOTYPE* +
    Prototype for make subject template path. +
  
negative.code: MagicMailBuilder
  ~~~~~~~~~~~~~~~~
  
  This is a more powerful way for building email messages from templates. Behind the scenes, it uses
  `TemplateMail` implementation but exposes a dynamic api that allows building of subclasses on demand.
  
  .Example that represents the same behavior as previous example using dynamic api of `MagicMailBuilder`
  [source,python]
  