mirror of
https://github.com/coddingtonbear/django-mailbox.git
synced 2026-07-09 22:38:19 +02:00
Updating documentation.
This commit is contained in:
parent
a3b1e12b25
commit
4e83ae8eb3
7 changed files with 258 additions and 49 deletions
|
|
@ -3,7 +3,8 @@ Getting incoming mail
|
|||
=====================
|
||||
|
||||
If you are utilizing one of the polling methods above,
|
||||
you will need to periodically poll the mailbox for messages using one of the below methods.
|
||||
you will need to periodically poll the mailbox for messages using one of the
|
||||
below methods.
|
||||
If you are receiving mail directly from a mailserver via a pipe
|
||||
-- using the ``processincomingmessage`` management command --
|
||||
you need not concern yourself with this section.
|
||||
|
|
@ -23,8 +24,9 @@ and select the 'Get new mail' option.
|
|||
Using a cron job
|
||||
----------------
|
||||
|
||||
You can easily consume incoming mail by running the management command named ``getmail``
|
||||
(optionally with an argument of the name of the mailbox you'd like to get the mail for).::
|
||||
You can easily consume incoming mail by running the management command named
|
||||
``getmail`` (optionally with an argument of the name of the mailbox you'd like
|
||||
to get the mail for).::
|
||||
|
||||
python manage.py getmail
|
||||
|
||||
|
|
@ -34,15 +36,18 @@ You can easily consume incoming mail by running the management command named ``g
|
|||
Receiving mail directly from Exim4 or Postfix via a pipe
|
||||
--------------------------------------------------------
|
||||
|
||||
Django Mailbox's ``processincomingmessage`` management command accepts, via ``stdin``, incoming messages.
|
||||
You can configure Postfix or Exim4 to pipe incoming mail to this management command
|
||||
to import messages directly without polling.
|
||||
Django Mailbox's ``processincomingmessage`` management command accepts, via
|
||||
``stdin``, incoming messages.
|
||||
You can configure Postfix or Exim4 to pipe incoming mail to this management
|
||||
command to import messages directly without polling.
|
||||
|
||||
You need not configure mailbox settings when piping-in messages,
|
||||
mailbox entries will be automatically created matching the e-mail address to which incoming messages are sent,
|
||||
mailbox entries will be automatically created matching the e-mail address to
|
||||
which incoming messages are sent,
|
||||
but if you would like to specify the mailbox name,
|
||||
you may provide a single argument to the ``processincmingmessage`` command
|
||||
specifying the name of the mailbox you would like it to use (and, if neccessary, create).
|
||||
specifying the name of the mailbox you would like it to use
|
||||
(and, if necessary, create).
|
||||
|
||||
Receiving Mail from Exim4
|
||||
.........................
|
||||
|
|
@ -57,11 +62,14 @@ start by adding a new router configuration to your Exim4 configuration like::
|
|||
transport = send_to_django_mailbox
|
||||
local_parts = emailusernameone : emailusernametwo
|
||||
|
||||
Make sure that the e-mail addresses you would like handled by Django Mailbox are not handled by another router;
|
||||
Make sure that the e-mail addresses you would like handled by Django Mailbox
|
||||
are not handled by another router;
|
||||
you may need to disable some existing routers.
|
||||
|
||||
Change the contents of ``local_parts`` to match a colon-delimited list of usernames for which you would like to receive mail.
|
||||
For example, if one of the e-mail addresses targeted at this machine is ``jane@example.com``,
|
||||
Change the contents of ``local_parts`` to match a colon-delimited list of
|
||||
usernames for which you would like to receive mail.
|
||||
For example, if one of the e-mail addresses targeted at this machine is
|
||||
``jane@example.com``,
|
||||
the contents of ``local_parts`` would be, simply ``jane``.
|
||||
|
||||
Next, a new transport configuration to your Exim4 configuration::
|
||||
|
|
@ -74,18 +82,23 @@ Next, a new transport configuration to your Exim4 configuration::
|
|||
return_path_add
|
||||
delivery_date_add
|
||||
|
||||
Like your router configuration, transport configuration should be altered to match your environment.
|
||||
First, modify the ``command`` setting such that it points at the proper python executable
|
||||
(if you're using a virtual environment, you'll want to direct that at the python executable in your virtual environment)
|
||||
Like your router configuration, transport configuration should be altered to
|
||||
match your environment.
|
||||
First, modify the ``command`` setting such that it points at the proper
|
||||
python executable
|
||||
(if you're using a virtual environment, you'll want to direct that at the
|
||||
python executable in your virtual environment)
|
||||
and project ``manage.py`` script.
|
||||
Additionally, you'll need to set ``user`` and ``group`` such that
|
||||
they match a reasonable user and group (on Ubuntu, ``www-data`` suffices for both).
|
||||
they match a reasonable user and group
|
||||
(on Ubuntu, ``www-data`` suffices for both).
|
||||
|
||||
Receiving mail from Postfix
|
||||
...........................
|
||||
|
||||
Although I have not personally tried using Postfix for this,
|
||||
Postfix is capable of delivering new mail to a script using ``pipe``.
|
||||
Please consult the `Postfix documentation for pipe here <http://www.postfix.org/pipe.8.html>`_.
|
||||
Please consult the
|
||||
`Postfix documentation for pipe here <http://www.postfix.org/pipe.8.html>`_.
|
||||
You may want to consult the above Exim4 configuration for tips.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue