===========
EmailFilter
===========
Description
===========
Module provides proxying emails from external addresses to local ones according to ``django.contrib.User`` emails
Installation
============
1. Install emailfilter to your project's environment. If your env should be activated by hand, then create script (``mail_route.sh``) like this::
#!/bin/sh
export PYTHONPATH=/path/to/settings_dir/:/path/to/project/
echo "$(cat)" | /path/to/env/bin/python /path/to/env/bin/mail_route.py >> /path/to/logs/mail_route.log 2>&1
2. Add new pipe to ``mail_route.py`` script in postfix (by default it should be placed in ``/etc/postfix/master.cf``)::
mailproxy unix - n n - - pipe
flags=FR user=user_that_runs_uwsgi_or_project argv=/path/to/mail_route.sh
${nexthop} ${user}
3. Then this transport should be used to process mails.
For example you want to process mails to ``domain.com`` and you are using cdb storage for postfix.
Add this to ``/etc/postfix/transport``::
domain.com mailproxy:
Then update cdb map::
postmap cdb:/etc/postfix/transport
4. now you should create ``/path/where/you/place/mail_route_settings/mail_route_settings.py``::
PROJECT_BASE_DIR = '/path/where/project/settings/can/be/imported/'
DJANGO_SETTINGS_MODULE = 'project.settings'
PROCESS_OUTGOING_EMAILS = False
SELF_ADDRESS = 'proxy@kavahq.com'
Settings
========
Some django settings are available for configuration:
* ``EMAIL_HOST``, ``EMAIL_PORT`` — host and port used to "forward" emails
* ``EMAIL_SERVER_DOMAINS`` — list of domains that should be checked for mail forwarding. Example::
EMAIL_SERVER_DOMAINS = ['@42cc.co', '@42coffeecups.com', '@khavr.com']
Not Django settings in mail_route_settings.py file:
* ``SELF_ADDRESS`` — email address of mail_rote. For example if you forwar all emails from somewhwere
to mail_route by bcc`ingthem then you should set ``SELF_ADDRESS`` to bcc address and it will be ignored
when forwarding address(es) is determined
* ``PROJECT_BASE_DIR`` — this directory will be added to PYTHONPATH
* ``DJANGO_SETTINGS_MODULE`` — env variable with same name will be set to value of this setting
* ``LOG_PATH`` — where logs should be saved
EmailFilter
===========
Description
===========
Module provides proxying emails from external addresses to local ones according to ``django.contrib.User`` emails
Installation
============
1. Install emailfilter to your project's environment. If your env should be activated by hand, then create script (``mail_route.sh``) like this::
#!/bin/sh
export PYTHONPATH=/path/to/settings_dir/:/path/to/project/
echo "$(cat)" | /path/to/env/bin/python /path/to/env/bin/mail_route.py >> /path/to/logs/mail_route.log 2>&1
2. Add new pipe to ``mail_route.py`` script in postfix (by default it should be placed in ``/etc/postfix/master.cf``)::
mailproxy unix - n n - - pipe
flags=FR user=user_that_runs_uwsgi_or_project argv=/path/to/mail_route.sh
${nexthop} ${user}
3. Then this transport should be used to process mails.
For example you want to process mails to ``domain.com`` and you are using cdb storage for postfix.
Add this to ``/etc/postfix/transport``::
domain.com mailproxy:
Then update cdb map::
postmap cdb:/etc/postfix/transport
4. now you should create ``/path/where/you/place/mail_route_settings/mail_route_settings.py``::
PROJECT_BASE_DIR = '/path/where/project/settings/can/be/imported/'
DJANGO_SETTINGS_MODULE = 'project.settings'
PROCESS_OUTGOING_EMAILS = False
SELF_ADDRESS = 'proxy@kavahq.com'
Settings
========
Some django settings are available for configuration:
* ``EMAIL_HOST``, ``EMAIL_PORT`` — host and port used to "forward" emails
* ``EMAIL_SERVER_DOMAINS`` — list of domains that should be checked for mail forwarding. Example::
EMAIL_SERVER_DOMAINS = ['@42cc.co', '@42coffeecups.com', '@khavr.com']
Not Django settings in mail_route_settings.py file:
* ``SELF_ADDRESS`` — email address of mail_rote. For example if you forwar all emails from somewhwere
to mail_route by bcc`ingthem then you should set ``SELF_ADDRESS`` to bcc address and it will be ignored
when forwarding address(es) is determined
* ``PROJECT_BASE_DIR`` — this directory will be added to PYTHONPATH
* ``DJANGO_SETTINGS_MODULE`` — env variable with same name will be set to value of this setting
* ``LOG_PATH`` — where logs should be saved
Metadata
Release files for email-filter 0.2.12
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| email-filter-0.2.12.tar.gz | 9.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| email-filter-0.2.12.linux-x86_64.tar.gz | Details |
Total release size: 30.2 kB
Release files / email-filter-0.2.12.tar.gz
| Download URL | email-filter-0.2.12.tar.gz |
|---|---|
| Size | 9.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8d135b8f7a663eee48b7e77465f7b9be9c3c4925dbd8e2040083c2f13c181943
|
|
BLAKE2b-256 checksum How to use checksums |
4ce73d4c1fc61fe484e2c734ec336546f1910a6565d6782b97ba4cdcdd1c9b79
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / email-filter-0.2.12.linux-x86_64.tar.gz
| Download URL | email-filter-0.2.12.linux-x86_64.tar.gz |
|---|---|
| Size | 20.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2dbca0d1d8b150262ec7f8b84ff2f9676a8c14008adf5c578e14d976d3d1796d
|
|
BLAKE2b-256 checksum How to use checksums |
ca5891c10000bbbd72f0f2efbc725059ed4c5cbf27847667007573f15b0c5082
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for email-filter 0.2.12
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.