en - Re: [sympa-users] Sympa Install

Subject: The mailing list for listmasters using Sympa

List archive

Re: [sympa-users] Sympa Install

From: "True, James Scott" <address@concealed>
To: David Verdin <address@concealed>
Cc: "address@concealed" <address@concealed>
Subject: Re: [sympa-users] Sympa Install
Date: Thu, 28 Jan 2021 16:42:43 +0000

David,

We have had a lot of success thanks to your help. We are going to migrated our prod environment soon.

Just wanted to ask another question to fine tune our process. At what point are local logins (user and passwords) migrated? We don’t see passwords when we dump subscribers.

Thank You,

Jim True
Campus Communications Infrastructure
Indiana University

address@concealed
812-855-7519 (Office)

On Oct 21, 2020, at 5:01 AM, David Verdin <address@concealed> wrote:
Hi James,

I said move the list directory. After the list was closed; In that situation, the subscribers list has been dumped to the file system inside the list directory. That way, you don't have to bother moving any data from teh database.

You also move the archives directory for that list.

HOWEVER

You're moving from 6.1.11 to 6.2.52, that means that several parameters in the list configuration have changed. For example, the list owners and editors are no longer stored in the config file but in the database. the archives parameters have been refit too.

Consequently, you need to run an upgrade process to make it work.

So after you have moved the directory, you run sympa.pl --upgrade --from 6.1.11 --to 6.2.25 and everything should be fine. Don't forget to reopen the list afterwards.

Now, if you plan to move the whole lists on a new server, that's a different story. Closing/opening all the lists can't be done by script : ou can do it only by the web, manually. So it seems unlikely you'll be able to do the previous process.

Then you'll need to export the part of the database you'll need.

Here is an example of synchronization operations to move the filesystem of a server (run on the new server through SSK to the old server). We run it frequently to have all the data in place and up to date for the day we switch servers.
#!/bin/sh +e

#### Warning, rsync gotcha : 
### source with a "/" at the end : synchronize only content of the source directory to the destination
### source without "/" at the end : synchronize source directory AND its content.
### If some rsync commands contain trailing / and other don't is therefore not an error. It's on purpose. Don't touch.

# build ssh line

# get ssh host

date |xargs echo "rsync domain.tld list data"
rsync --exclude-from /usr/local/migration/excludes -a --delete -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/list_data/domain.tld/ /var/lib/sympa/list_data/domain.tld

date |xargs echo "rsync domain.tld list archives"
rsync --exclude-from /usr/local/migration/excludes -a --delete -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/address@concealed /var/lib/sympa/archives

date |xargs echo "rsync domain.tld bounces"
rsync --exclude-from /usr/local/migration/excludes -a --delete -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/address@concealed /usr/local/sympa/bounce

date |xargs echo "rsync domain.tld pictures"
rsync --exclude-from /usr/local/migration/excludes -a --delete -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/address@concealed /usr/local/sympa/static_content/pictures

date |xargs echo "rsync domain.tld dkim keys"
rsync -a -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/var/lib/ssl/dkim_private_keys/cru.fr.private_dkim.pem /usr/local/sympa/etc/dkim_private_key.pem
rsync -a -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/var/lib/ssl/dkim_public_keys/cru.fr.public_key /usr/local/sympa/etc/dkim_public_key
    

# data_sources
date |xargs echo "rsync domain.tld domain specific data_sources"
rsync --exclude-from /usr/local/migration/excludes -a --delete -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/etc/domain.tld/data_sources /usr/local/sympa/etc/domain.tld
# custom_actions
date |xargs echo "rsync domain.tld domain specific custom_actions"
rsync --exclude-from /usr/local/migration/excludes -a --delete -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/etc/domain.tld/custom_actions /usr/local/sympa/etc/domain.tld
# custom_conditions
date |xargs echo "rsync domain.tld domain specific custom_conditions"
rsync --exclude-from /usr/local/migration/excludes -a --delete -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/etc/domain.tld/custom_conditions /usr/local/sympa/etc/domain.tld
# topics.conf
date |xargs echo "rsync domain.tld domain specific topics.conf"
rsync --exclude-from /usr/local/migration/excludes -a --delete -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/etc/domain.tld/topics.conf /usr/local/sympa/etc/domain.tld
# mail_tt2
date |xargs echo "rsync domain.tld domain specific mail_tt2"
rsync --exclude-from /usr/local/migration/excludes -a --delete -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/etc/domain.tld/mail_tt2 /usr/local/sympa/etc/domain.tld
# csv
date |xargs echo "rsync domain.tld domain specific csv"
rsync --exclude-from /usr/local/migration/excludes -a --delete -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/etc/domain.tld/csv /usr/local/sympa/etc/domain.tld
# families
date |xargs echo "rsync domain.tld domain specific families"
rsync --exclude-from /usr/local/migration/excludes -a --delete -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/etc/domain.tld/families /usr/local/sympa/etc/domain.tld
# scenari
date |xargs echo "rsync domain.tld domain specific scenari"
rsync --exclude-from /usr/local/migration/excludes -a --delete -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/etc/domain.tld/scenari /usr/local/sympa/etc/domain.tld
# create_list_templates
date |xargs echo "rsync domain.tld domain specific create_list_templates"
rsync --exclude-from /usr/local/migration/excludes -a --delete -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/etc/domain.tld/create_list_templates /usr/local/sympa/etc/domain.tld
# edit_list.conf
date |xargs echo "rsync domain.tld domain specific edit_list.conf"
rsync --exclude-from /usr/local/migration/excludes -a --delete -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/etc/domain.tld/edit_list.conf /usr/local/sympa/etc/domain.tld
# create_list.conf
date |xargs echo "rsync domain.tld domain specific create_list.conf"
rsync --exclude-from /usr/local/migration/excludes -a --delete -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/etc/domain.tld/create_list.conf /usr/local/sympa/etc/domain.tld

# auth
date |xargs echo "rsync domain.tld spool auth"
rsync --exclude '*~' -a --delete -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/address@concealed* /var/spool/sympa/auth
    
# digest
date |xargs echo "rsync domain.tld spool digest"
rsync --exclude '*~' -a --delete -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/address@concealed /var/spool/sympa/digest
    
# moderation
date |xargs echo "rsync domain.tld spool moderation"
rsync --exclude '*~' -a --delete -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/address@concealed* /var/spool/sympa/moderation
    
# subscribe
date |xargs echo "rsync domain.tld spool subscribe"
rsync --exclude '*~' -a --delete -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/address@concealed* /var/spool/sympa/subscribe
    
# task
date |xargs echo "rsync domain.tld spool task"
rsync --exclude '*~' -a --delete -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/address@concealed /var/spool/sympa/task
    
# topic
date |xargs echo "rsync domain.tld spool topic"
rsync --exclude '*~' -a --delete -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/address@concealed.* /var/spool/sympa/topic
    
# viewmail
date |xargs echo "rsync domain.tld spool viewmail"
[ -d /var/spool/sympa/viewmail/bounce ] || mkdir /var/spool/sympa/viewmail/bounce
[ -d /var/spool/sympa/viewmail/mod ] || mkdir /var/spool/sympa/viewmail/mod
chown -R sympa:sympa /var/spool/sympa/viewmail
rsync --exclude '*~' -a --delete -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/address@concealed /var/spool/sympa/viewmail/mod
rsync --exclude '*~' -a --delete -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/address@concealed /var/spool/sympa/viewmail/bounce
    

# X509 certificates
date |xargs echo "rsync domain.tld X509 certificates"
rsync --exclude-from /usr/local/migration/excludes -a -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/list_data/X509-user-certs /var/lib/sympa/list_data

# TT2 plugins
date |xargs echo "rsync domain.tld TT2 Plugins"
rsync --exclude-from /usr/local/migration/excludes -a -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/bin/Sympa/Template/Plugin/ /usr/local/sympa/bin/Sympa/Template/Plugin/

# data_sources
date |xargs echo "rsync global data_sources"
rsync --exclude-from /usr/local/migration/excludes -a -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/etc/data_sources /usr/local/sympa/etc
# custom_actions
date |xargs echo "rsync global custom_actions"
rsync --exclude-from /usr/local/migration/excludes -a -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/etc/custom_actions /usr/local/sympa/etc
# custom_conditions
date |xargs echo "rsync global custom_conditions"
rsync --exclude-from /usr/local/migration/excludes -a -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/etc/custom_conditions /usr/local/sympa/etc
# topics.conf
date |xargs echo "rsync global topics.conf"
rsync --exclude-from /usr/local/migration/excludes -a -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/etc/topics.conf /usr/local/sympa/etc
# mail_tt2
date |xargs echo "rsync global mail_tt2"
rsync --exclude-from /usr/local/migration/excludes -a -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/etc/mail_tt2 /usr/local/sympa/etc
# scenari
date |xargs echo "rsync global scenari"
rsync --exclude-from /usr/local/migration/excludes -a -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/etc/scenari /usr/local/sympa/etc
# create_list_templates
date |xargs echo "rsync global create_list_templates"
rsync --exclude-from /usr/local/migration/excludes -a -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/etc/create_list_templates /usr/local/sympa/etc
# ldap_alias_entry.tt2
date |xargs echo "rsync global ldap_alias_entry.tt2"
rsync --exclude-from /usr/local/migration/excludes -a -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/etc/ldap_alias_entry.tt2 /usr/local/sympa/etc
# ldap_alias_manager.conf
date |xargs echo "rsync global ldap_alias_manager.conf"
rsync --exclude-from /usr/local/migration/excludes -a -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/etc/ldap_alias_manager.conf /usr/local/sympa/etc
# create_list.conf
date |xargs echo "rsync global create_list.conf"
rsync --exclude-from /usr/local/migration/excludes -a -e "ssh -l allowed_ssh_user -o UserKnownHostsFile=/path/to/known_hosts -i /path/to/ssh/key" origin.server.tld:/usr/local/sympa/etc/create_list.conf /usr/local/sympa/etc
An here are the operations on the database:

I don't put all oerations, just an example of mysql dump that we run to retrieve the data we need:
ssh -l migration -o UserKnownHostsFile=/path/to/know_hosts -i /path/to/ssh/key origin.server.tld mysqldump sympa --single-transaction --force --tables user_table --user sympa -pold-server-password --complete-insert --extended-insert=FALSE --replace \> \/var\/tmp\/sql-dump\/\/user_table.sql
What's nice with this dump is taht you create a single query for each record. So if one of them fails, you still carry on inserting the rest.

Afterwards, we run a set of finalization operations:
root@ix1-pv-u16-Universalistessympa-04:/usr/local/migration# cat sympa_finalize.sh 
#!/bin/sh +e
date |xargs echo "upgrade Sympa"
/usr/local/sympa/bin/sympa.pl --upgrade --from 6.1.11 --to 6.2.52
date |xargs echo "upgrade Sympa"
/usr/local/sympa/bin/sympa.pl --reload_list_config
date |xargs echo "Sympa health check"
/usr/local/sympa/bin/sympa.pl --health_check
date |xargs echo "reboot Sympa"
service sympa restart
service wwsympa restart
service sympasoap restart
date |xargs echo "generate alias file"
/usr/local/sympa/bin/sympa.pl --make_alias_file
date |xargs echo "move aliases to final location"
mv $(ls -1t  /var/spool/sympa/tmp/sympa_aliases.* | head -1) /etc/mail/sympa_transport
date |xargs echo "run postmap"
postmap /etc/mail/sympa_transport
Best regards,

David

On 20/10/2020 22:37, True, James Scott wrote:

David,

Have you had success with this? When you say move the list, you are including data in the database correct? Did you export the data from the database for just the one list and then import it into the new database?

Has anyone had any experience with migrating lists one by one to a new upgrade list environment? We are moving from Sympa 6.1.1 on RHEL6 to Sympa 6.2.52 on CentOS 7. We would like to migrate some individual list first as a pilot. Any thoughts?

Thanks for any suggestions,

Jim True
Campus Communications Infrastructure
Indiana University

address@concealed
812-855-7519 (Office)

On Oct 5, 2020, at 6:38 AM, David Verdin <address@concealed> wrote:

From a server to another server, the simplest is to close the list, move the list (and archive) irectory to the other server, then reopen the list. It should be enough to retrieve all data. Regards, David On 02/10/2020 18:16, Pinson, Brian wrote: Is there a simple way to move lists from one sympa system to another?

-----Original Message-----
From: address@concealed <address@concealed> On Behalf Of Pinson, Brian
Sent: Thursday, October 1, 2020 9:53 AM
To: Stefan Hornburg (Racke) <address@concealed>; address@concealed
Subject: RE: [sympa-users] Sympa Install

Figured I'd ask 😃 I have sent it over to our AD team.

-----Original Message-----
From: Stefan Hornburg (Racke) <address@concealed>
Sent: Thursday, October 1, 2020 9:24 AM
To: Pinson, Brian <address@concealed>; address@concealed
Subject: Re: [sympa-users] Sympa Install

On 10/1/20 4:20 PM, Pinson, Brian wrote:

Thank you for sharing! Can you or someone explain the this part? Specifically the last part with all the numbers.

    get_dn_by_email_filter
(&(objectcategory=person)(mail=[sender])(!(userAccountControl:1.2.840.
113556.1.4.803:=2)))

Sorry I can't .. this filter was provided by the client so I simply pasted it into the auth.conf.

As I said, the actual configuration might differ between AD installations. Ask your AD admins for the correct string.

Regards
         Racke

-----Original Message-----
From: address@concealed
<address@concealed> On Behalf Of Stefan Hornburg
(Racke)
Sent: Thursday, October 1, 2020 9:15 AM
To: address@concealed
Subject: Re: [sympa-users] Sympa Install

On 10/1/20 4:02 PM, Pinson, Brian wrote:

I was able to get it figured out. There was a typo in my sympa.conf file… Thanks to everyone that helped!

Does anyone have any pointers on getting sympa to work against AD
with LDAP? The documentation I saw on sympa’s site didn’t go into
much detail. I found the auth.conf file but how does work? I made the changes and it still seems to be using the local authentication method.

https://urldefense.com/v3/__https://sympa-community.github.io/manual/
customize/ldap-auth.html__;!!H8mHWRdzp34!r5XltFUOlox0-bl-ucftpd4r2cE_
4Bz2jp83g7Kw4zL9_zWySHC15v1MEQajZoQ$

I suppose the actual configuration depends on your local setup.

Here is a real life example from one of my clients (redacted for privacy):

--- snip ---
ldap
    regexp .*
    host ldap.linuxia.de:636
    bind_dn address@concealed
    bind_password nevairbe
    timeout 20
    suffix dc=linuxia,dc=de
    get_dn_by_uid_filter (uid=[sender])
    get_dn_by_email_filter (&(objectcategory=person)(mail=[sender])(!(userAccountControl:1.2.840.113556.1.4.803:=2)))
    email_attribute mail
    scope sub
    use_ssl 1
    ca_file /etc/ssl/linuxia-chain.pem
    ca_verify required

user_table
  regexp .*
--- snap ---

The blank line between the two entries is mandatory.

Regards
         Racke

*From:* address@concealed
<address@concealed> *On Behalf Of *Colas Nahaboo
*Sent:* Thursday, October 1, 2020 2:38 AM
*To:* Stefan Hornburg (Racke) <address@concealed>
*Cc:* address@concealed
*Subject:* Re: [sympa-users] Sympa Install

ATTENTION: This email originated from a sender outside of MCW. Use caution when clicking on links or opening attachments.

---------------------------------------------------------------------
-
--------------------------------------------------

Well, I guess the RPM package can work. It is just that before using
the Debian package of Sympa (that I used apache, mysql, postfix), I
have been installing from source, and looking at the amount of manual
work left once the RPM package was installed, I thought that it did not save much compared to installing by hand, so why bother (and adding one more dependency, aka potential for failure)?

Out of curiosity, I will try to use the Debian package on Ubuntu however, before resorting to installing by hand.

On Thu, 1 Oct 2020 at 08:39, Stefan Hornburg (Racke) <address@concealed <mailto:address@concealed>> wrote:

    On 9/30/20 11:57 PM, Colas Nahaboo wrote:
    > Just a warning on the linux distribution packages I tried 2 months ago:
    >
    > * Ubuntu doesn't work (archiving doesn't work) and has not been maintained for 2 years.
    > * Debian works nicely, and updates sympa versions.
    > * RHEL is not useful. It just copies files, but do not attempt to really install things (no database setup, no
    > integration with the mail system, ...) and I don't think it will be of any use for upgrading.
    >

    Thanks for your valuable input. I can improve the Debian packages, but the other ones are out
    of my scope.

    I have a client with Sympa installed on CentOS 7 from RPM. Last upgrade was fine there.

    Regards
      Racke

    >
    >
    > On Wed, 30 Sep 2020 at 23:02, Pinson, Brian <address@concealed <mailto:address@concealed> <mailto:address@concealed
    <mailto:address@concealed>>> wrote:
    >
    > Thank you! That helped. Final stretch here... so I go to the webpage and I'm getting:
    >
    > Forbidden
    >
    > You don't have permission to access /sympa on this server.
    >
    >
    > Anything come to mind with this?
    >
    > -----Original Message-----
    > From: address@concealed <mailto:address@concealed>
    <mailto:address@concealed <mailto:address@concealed>>
    > <address@concealed <mailto:address@concealed>
    <mailto:address@concealed <mailto:address@concealed>>> On Behalf Of Stefan
    Hornburg
    > (Racke)
    > Sent: Wednesday, September 30, 2020 2:12 PM
    > To: address@concealed <mailto:address@concealed> <mailto:address@concealed
    <mailto:address@concealed>>
    > Subject: Re: [sympa-users] Sympa Install
    >
    > On 9/30/20 9:08 PM, Pinson, Brian wrote:
    > > I'm getting stuck with configuring the sendmail part.
    > > (https://urldefense.com/v3/__https://sympa-community.github.io/manual/install/configure-mail-serve__;!!H8mHWRdzp34!r5XltFUOlox0-bl-ucftpd4r2cE_4Bz2jp83g7Kw4zL9_zWySHC15v1MlBjKTtM$
    <https://urldefense.com/v3/__https:/sympa-community.github.io/manual/install/configure-mail-serve__;!!H8mHWRdzp34!s0RhBNoCKz8XH3jbRbv0tJ0QY8cvIgMuqNkNZKQ9M12pXKIegLsrpCQUYz8vvO8$>
    > > r-sendmail.html)
    > >
    > > Particularly the alias part. What is the "$SENDMAIL_ALIAS" thing it's talking about?
    >
    > These variables are explained here: https://urldefense.com/v3/__https://sympa-community.github.io/manual/layout.html__;!!H8mHWRdzp34!r5XltFUOlox0-bl-ucftpd4r2cE_4Bz2jp83g7Kw4zL9_zWySHC15v1M5cM1KAw$
    <https://urldefense.com/v3/__https:/sympa-community.github.io/manual/layout.html__;!!H8mHWRdzp34!s0RhBNoCKz8XH3jbRbv0tJ0QY8cvIgMuqNkNZKQ9M12pXKIegLsrpCQUEeWgc8E$>.
    >
    > Regards
    >    Racke
    >
    > >
    > > -----Original Message-----
    > > From: address@concealed <mailto:address@concealed>
    <mailto:address@concealed <mailto:address@concealed>>
    > > <address@concealed <mailto:address@concealed>
    <mailto:address@concealed <mailto:address@concealed>>> On Behalf Of Stefan
    Hornburg
    > > (Racke)
    > > Sent: Wednesday, September 30, 2020 10:52 AM
    > > To: address@concealed <mailto:address@concealed>
    <mailto:address@concealed <mailto:address@concealed>>
    > > Subject: Re: [sympa-users] Sympa Install
    > >
    > > On 9/30/20 5:48 PM, Pinson, Brian wrote:
    > >> Wish me luck! Going to try the RPM.
    > >>
    > >
    > > Let us know how it goes ... maybe you can suggest improvements to the documentation if you find it unclear or
    > missing useful information.
    > >
    > > Good luck
    > >
    > > Racke
    > >
    > >> -----Original Message-----
    > >> From: address@concealed <mailto:address@concealed>
    <mailto:address@concealed <mailto:address@concealed>>
    > >> <address@concealed <mailto:address@concealed>
    <mailto:address@concealed <mailto:address@concealed>>> On Behalf Of David Verdin
    > >> Sent: Wednesday, September 30, 2020 10:25 AM
    > >> To: address@concealed <mailto:address@concealed>
    <mailto:address@concealed <mailto:address@concealed>>
    > >> Subject: Re: [sympa-users] Sympa Install
    > >>
    > >> Another point of attention: The distribution has no impact on Sympa
    > >> administration. Around 45 % of installs are under Redhat (or Fedora,
    > >> centos, etc.), 45 % under Debian (or Ubuntu and the like) and most of
    > >> the 10% remaining are FreeBSD.
    > >>
    > >> The only impact of distribution is which Sympa version is packaged.
    > >>
    > >> About it, Soji maintains the RPM, so RedHat can always have the
    > >> latest version packaged, but you need to set up the dedicated
    > >> repository. I don't know how it works for Debian if you want the
    > >> latest version packaged. It seems that current version in Debian is
    > >> something like
    > >> 6.2.40 which is good enough.
    > >>
    > >> Personally, I always install from sources, so I don't care and use
    > >> Ubuntu servers.
    > >>
    > >> Cheers!
    > >>
    > >> David
    > >>
    > >> On 30/09/2020 17:14, Pinson, Brian wrote:
    > >>> We are generally a RHEL or OEL shop. But, from what I've discovered is Debian seems to be the go-to option. Is
    > the Sympa documentation accurate for the Debian install? I haven't found that their documentation is the best.
    > >>>
    > >>> Thank you so much for you input. We are trying to move away from
    > >>> Mailman and Sympa seems promising if I could just get it installed!
    > >>> 😃
    > >
    > >>>>>
    > >>> -----Original Message-----
    > >>> From: address@concealed <mailto:address@concealed>
    <mailto:address@concealed <mailto:address@concealed>>
    > >>> <address@concealed <mailto:address@concealed>
    <mailto:address@concealed <mailto:address@concealed>>> On Behalf Of Stefan
    Hornburg
    > >>> (Racke)
    > >>> Sent: Wednesday, September 30, 2020 10:12 AM
    > >>> To: address@concealed <mailto:address@concealed>
    <mailto:address@concealed <mailto:address@concealed>>
    > >>> Subject: Re: [sympa-users] Sympa Install
    > >>>
    > >>> On 9/30/20 4:54 PM, Pinson, Brian wrote:
    > >>>> I'm starting from scratch. I'm basically just wanting to feel out what the community recommends. We have one
    > system running Ubuntu but it just doesn't seem to be working right. We have to reset our passwords almost everyday
    > right now. I would just rather rebuild as I think something was installed incorrectly the first time.
    > >>>>
    > >>> The community has several opinions and different infrastructure concerns, so there is no general
    recommendation.
    > >>>
    > >>> Here is the list of what I prefer:
    > >>>
    > >>> Distribution: Debian
    > >>> Web server: Nginx (faster and more consistent than Apache)
    > >>> Database: PostgreSQL (more mature and less surprises than MySQL /
    > >>> MariaDB) Mail server: Exim (but Postfix is fine too)
    > >>>
    > >>> Regards
    > >>> Racke
    > >>>
    > >>>
    > >>>> -----Original Message-----
    > >>>> From: address@concealed <mailto:address@concealed>
    <mailto:address@concealed <mailto:address@concealed>>
    > >>>> <address@concealed <mailto:address@concealed>
    <mailto:address@concealed <mailto:address@concealed>>> On Behalf Of Stefan
    > >>>> Hornburg
    > >>>> (Racke)
    > >>>> Sent: Wednesday, September 30, 2020 9:52 AM
    > >>>> To: address@concealed <mailto:address@concealed>
    <mailto:address@concealed <mailto:address@concealed>>
    > >>>> Subject: Re: [sympa-users] Sympa Install
    > >>>>
    > >>>> On 9/30/20 4:42 PM, Pinson, Brian wrote:
    > >>>>> Good Morning all,
    > >>>>>
    > >>>>> Is there anyone out there that has a good step-by-step
    > >>>>> installation for Sympa? All the ones that I have tried are either incomplete or just don't work.
    > >>>>>
    > >>>>>
    > >>>>>
    > >>>>> Any guidance is greatly appreciated!
    > >>>> Hello Brian,
    > >>>>
    > >>>> it depends on a couple of things:
    > >>>>
    > >>>> How do you install it? From sources?
    > >>>> Which distribution is installed on your server?
    > >>>>
    > >>>> Database?
    > >>>> MTA?
    > >>>> Web server?
    > >>>>
    > >>>> Regards
    > >>>> Racke
    > >>>>
    > >>>>
    > >>>> --
    > >>>> Ecommerce and Linux consulting + Perl and web application programming.
    > >>>> Debian and Sympa administration. Provisioning with Ansible.
    > >>>>
    > >>>>
    > >>>
    > >>> --
    > >>> Ecommerce and Linux consulting + Perl and web application programming.
    > >>> Debian and Sympa administration. Provisioning with Ansible.
    > >>>
    > >
    > >
    > > --
    > > Ecommerce and Linux consulting + Perl and web application programming.
    > > Debian and Sympa administration. Provisioning with Ansible.
    > >
    >
    >
    > --
    > Ecommerce and Linux consulting + Perl and web application programming.
    > Debian and Sympa administration. Provisioning with Ansible.
    >
    >
    >
    > --
    > Colas Nahaboo - https://urldefense.com/v3/__https://colas.nahaboo.net__;!!H8mHWRdzp34!r5XltFUOlox0-bl-ucftpd4r2cE_4Bz2jp83g7Kw4zL9_zWySHC15v1MVKZ9gsg$
    <https://urldefense.com/v3/__https:/colas.nahaboo.net__;!!H8mHWRdzp34!s0RhBNoCKz8XH3jbRbv0tJ0QY8cvIgMuqNkNZKQ9M12pXKIegLsrpCQUinnjIWM$>
    <https://urldefense.com/v3/__http://colas.nahaboo.net__;!!H8mHWRdzp34
!r5XltFUOlox0-bl-ucftpd4r2cE_4Bz2jp83g7Kw4zL9_zWySHC15v1MV7FAwPo$
    <https://urldefense.com/v3/__http:/colas.nahaboo.net__;!!H8mHWRdzp34!
s 0RhBNoCKz8XH3jbRbv0tJ0QY8cvIgMuqNkNZKQ9M12pXKIegLsrpCQUj-puZPU$>>

    --
    Ecommerce and Linux consulting + Perl and web application programming.
    Debian and Sympa administration. Provisioning with Ansible.

--

Colas Nahaboo -
https://urldefense.com/v3/__https://colas.nahaboo.net__;!!H8mHWRdzp34
!r5XltFUOlox0-bl-ucftpd4r2cE_4Bz2jp83g7Kw4zL9_zWySHC15v1MVKZ9gsg$
<https://urldefense.com/v3/__http:/colas.nahaboo.net__;!!H8mHWRdzp34!
s 0RhBNoCKz8XH3jbRbv0tJ0QY8cvIgMuqNkNZKQ9M12pXKIegLsrpCQUj-puZPU$>

--
Ecommerce and Linux consulting + Perl and web application programming.
Debian and Sympa administration. Provisioning with Ansible.

--
Ecommerce and Linux consulting + Perl and web application programming.
Debian and Sympa administration. Provisioning with Ansible.

-- "Mieux vaut viser la perfection et la rater que viser la médiocrité et l'atteindre." - Francis Blanche David Verdin Chef de Projet Collaboratif Département PROduits NUMériques Direction des Services Applicatifs RENATER - Rennes

-- 
"Mieux vaut viser la perfection et la rater que viser la médiocrité et l'atteindre."
- Francis Blanche

David Verdin
Chef de Projet Collaboratif
Département PROduits NUMériques
Direction des Services Applicatifs
RENATER - Rennes

Re: [sympa-users] Sympa Install, True, James Scott, 01/28/2021

List archive

Re: [sympa-users] Sympa Install