-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add documentation for Exim integration #57
Comments
For reference, this is the exim setup we use:
From what I understand of what sympa needs this should cover all the addresses also covered for example in https://sympa-community.github.io/manual/install/configure-mail-server-opensmtpd.html Please note that the user exim runs as will need read access to different parts of the exim data tree for this to work, we achieved this by adding the user exim runs as to the sympa group. |
Hello. |
Just one point: The manual page says that |
@ikedas Thanks, I'm going to test that out. |
A complication is that the following no longer works in Exim 4.96:
because Exim is paranoid about passing "tainted" values into shell commands. The solution is to use "dsearch" directory lookups to match ${local_part} against existing lists on the system. This populates an untainted variable $local_part_data. Here is the configuration that I am successfully using with Exim 4.96 (which should also work with older versions of Exim):
|
${domain} is also tainted. I don't have to worry about that as I only have a single domain to play with, lists.cam.ac.uk |
@dpc22 thanks for the update. Exim 4.94 is also affected. |
Tainting was first introduced in 4.94. The following still worked in 4.95:
but was broken by the following change in 4.96:
as I discovered (the hard way!) on upgrading to 4.96 earlier this week:
|
PR #90 has been merged. Thank you for infomation! |
This is missing and causing a 404: https://sympa-community.github.io/manual/install/configure-mail-server-exim.md.
The text was updated successfully, but these errors were encountered: