Jan Johansson wrote: > I have been asked to set up a Exim/Sympa server, but for political reasons, > they do not want custom routers/transports, but rather to utilize the sympa > generated, sendmail-style alias file. > > Can it be utilized within exim in an easy way? (In all cases, the effective > user should be "sympa:sympa"?
AFAIK, the 'challenge' if you are restricted to only the *system* alias file comes about if the server hosts more than one (mail) domain. Otherwise, all-else-being-equal, it should JFW. NB: *someone* will ordinarily need 'root' privs to get those entries into the system-alias file and/or alter them if/as/when lists change. If that is part of the 'political reasons' then custom routers that use a file/table you control and can grant the exim daemon runner access to is 'safer'. Once the router/transports are installed & tested, no further access to exim's config is needed as you set up/tear-down lists. Bill (Using Ecartis, with very similar issues, on virtual-hosting MX). > > The sympa aliasmanager creates a list as below with entries for all lists. > > ## This aliases file is dedicated to Sympa Mailing List Manager > ## You should edit your sendmail.mc or sendmail.cf file to declare it > #------------------------------ testlist: list alias created 23 okt 2006 > testlist: "| /home/sympa/bin/queue testlist @lists.skyddsrummet.net" > testlist-request: "| /home/sympa/bin/queue > [EMAIL PROTECTED]" > testlist-editor: "| /home/sympa/bin/queue > [EMAIL PROTECTED]" > # testlist -subscribe: "| /home/sympa/bin/queue > [EMAIL PROTECTED]" > testlist-unsubscribe: "| /home/sympa/bin/queue > [EMAIL PROTECTED]" > testlist-owner: "| /home/sympa/bin/bouncequeue > [EMAIL PROTECTED]" > -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/
