anchor.diff:  TemplateMail
   ~~~~~~~~~~~~
   
  -Is a low level interface for buid emails using templates. It allows statically define email classes for posterior
  +This is a low level interface for buiding emails using templates. It allows to statically define email classes for posterior
   usage:
   
   [source,python]
  
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: User guide
  ----------
  
  As I have mentioned previously, _djmail_ works as a middleware.
  
  - It saves emails using django orm and track its status. If an exception is raised during sending,
    it marks the email as *failed* and stores the exception traceback for posterior analysis.
  - Exposes usefull commands and methods for retring to send failed messages.
  - Handles priority, with ability to delay sending of messages with lowest priorty 
    to periodic task (with cron or celery).
  
  To get djmail working on your project, you should configure it:
  
  .Example initial development configuration:
  [source,python]
  