Skip to Content.
Sympa Menu

en - Re: [sympa-users] sympa, exim4, debian

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Paul Menzel <address@concealed>
  • To: Czakó Krisztián <address@concealed>
  • Cc: address@concealed
  • Subject: Re: [sympa-users] sympa, exim4, debian
  • Date: Thu, 21 Jul 2011 18:03:33 +0200

Dear Krisztian


Am Freitag, den 25.01.2008, 13:39 +0100 schrieb Krisztián Czakó:

> Where should I contribute config examples?
>
> Here're some exim4 config additions to make it work with sympa without
> alias management.

thank you again for your configuration examples [1].

> It automatically detects sympa lists (just "open" ones), manages the
> -owner, -request, etc. addresses, bounces, etc.
> I use it on a Debian Etch system with "split config" debconf settings
> with exim4-daemon-heavy.
>
> Simple untar the attached file to /etc/exim4 and it will work. Note that
> it uses the Debian exim4 split configuration method. You must select
> "split config" in debconf to use it.
>
> The configuration is based on the exim4 mailman configuration examples.
>
> If you find any bug or missing feature, please let me know!
> The detection of the open state of a list must be fine tuned, I know.

I have a question regarding exactly how Exim can figure if a list’s
state is open or not. In your example the corresponding part is the
following.

require_files = SYMPA_HOME/expl/$local_part/config
condition = ${if
eqi{${lookup{status}lsearch{SYMPA_HOME/expl/$local_part/config}}}{open}{yes}{no}}
user = sympa

This does not work for me when I want to use recipient verification [2].
The problem is for recipient verification Exim is not run as user `root`
but as user `exim4` and therefore cannot read the content of
`SYMPA_HOME` which can only be read by the user or the group `sympa`.

$ ls -l /var/lib/
[…]
drwxrwx--x 6 sympa sympa 4096 2009-01-17 18:15 sympa
[…]
$ sudo ls -l /var/lib/sympa
total 16
drwxr-x--- 6 sympa sympa 4096 2009-01-26 13:44 expl
drwxrwxr-x 3 sympa sympa 4096 2009-01-17 22:31 static_content
drwxrwx--x 4 sympa sympa 4096 2009-02-01 12:12 wwsarchive
drwxrwx--x 2 sympa sympa 4096 2008-10-19 21:13 x509-user-certs
$ sudo ls -l /var/lib/sympa/expl
drwxr-x--- 6 sympa sympa 4096 2009-01-29 00:00 domain.org
$ sudo ls -l /var/lib/sympa/expl/domain.org
drwxr-x--- 4 sympa sympa 4096 2009-01-29 08:43 list
$ sudo ls -l /var/lib/sympa/expl/domain.org/list/config
-rw-r----- 1 sympa sympa 942 2009-01-29 08:30
/var/lib/sympa/expl/domain.org/list/configl

(The `user = sympa` line seems to do something different and seems to be
only important for the transports further on [3].)

So my question is how did you solve that? Did you turn recipient
verification off? Did you add the user `exim4` to the group `sympa`? I
am still holding off of using the brute-force method suggested to me in
[4].


Thanks,

Paul


[1] http://www.sympa.org/faq/exim (last line)
[2]
http://lists.alioth.debian.org/pipermail/pkg-exim4-users/2011-April/001915.html
[3] http://www.exim.org/exim-html-current/doc/html/spec_html/ch15.html
[4]
http://lists.alioth.debian.org/pipermail/pkg-exim4-users/2011-April/001916.html

Attachment: signature.asc
Description: This is a digitally signed message part



  • Re: [sympa-users] sympa, exim4, debian, Paul Menzel, 07/21/2011

Archive powered by MHonArc 2.6.19+.

Top of Page