Originally during the sending of email there is a check to not send out
email from an unaothorized address. There you can set only exact email
addresses.
With this modification you are able to send out any address within a
specified domain. This is the reverse methodology to the catchall
function, you can use this to catch everything and send everything in a
domain, usable for a project management/ERP software.
To enable this you need to set "@domain.com" as sender address alias
just like you set up a cacthall functionality.
Signed-off-by: Csaba Tóth <csaba.toth@i3rendszerhaz.hu>
* Initial commit for LDAP sync process.
* Fixed unit tests.
* Added doc and run ldapsync tests on travis.
* Removed server address.
* Force bytes when calling ldap methods.
* Fixed tests compat with python2.
* Do not force bytes here.
* Force bytes.
* Force bytes for attribute names too.
* Disable bytes mode in PY2.
* Handle account removals.
* Fixed unit tests.
* Limit sync to simple users.
* Fixed unit test.
* Fixed unit test.
The DKIM key is base64 encoded, meaning it can end with "=" signs
Split on "=" and check if you have 2 'parts' (key and value) will fail in these cases.
By using split("=",1) we make sure we only slit on the first occurence of the "=" sign
### Problem
Currently, if I have a domain `bla.com` that is an alias of `blub.com` and John has user account as `john@blub.com`, then will not be able to send e-mails as `john@bla.com` because the system will not recognize / communicate to Postfix that `john@bla.com` is the same as `john@blub.com` and hence Postfix will reject this attempt.
### Proposed Solution
When calculating the allowed SASL usernames for an email address, also include aliases from aliased domains in the result of the query. (This will also work for the primary username, since that is added as “internal” alias to that table as well.)
### Caveats
I only tested the proposed query with PostgreSQL.
Csaba Tóth