Skip to Content.
Sympa Menu

en - Re: [en@sympa] Migration to a new server and version

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Benjamin Renard <address@concealed>
  • To: address@concealed
  • Subject: Re: [en@sympa] Migration to a new server and version
  • Date: Wed, 31 Jul 2024 17:17:35 +0200

Sympa has a cache for the member list, and its operation is well explained in the documentation:

https://www.sympa.community/manual/customize/data-sources.html#cache-management

By default, the cache is set to expire after 1 hour. This means that if Sympa needs to access the member list and the cached content is more than an hour old, it will automatically update the cache.


Le 31/07/2024 à 15:16, Saadallah Itani a écrit :
Thank you Benjamin for the valuable info.

Regarding SQL Query part, can Sympa
Provide a cron query to update list on daily basis or hourly basis from dynamoc mailing lists? Just like what the current perl script is doing @cron level?

Thanks

Regards,
Saad
Ext. 2229

Sent from my iPhone

On 31 Jul 2024, at 4:10 PM, Benjamin Renard <address@concealed> wrote:



Hello,

A SQL data source (see include_sql_query parameter) should be a more advantageous solution to replace your Perl script [1]. Regarding incoming and outgoing emails via Office 365, I think you will need a local SMTP server (such as postfix) to act as a relay with sympa. For outgoing emails, you will need to set up Office 365 as a relayhost and provide SMTP connection information. Here's an example of how you could configure this in Postfix:

/etc/postfix/main.cf :
relayhost = [smtp.office365.com]:587
smtp_tls_security_level = encrypt
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_sasl_security_options = noanonymous

/etc/postfix/sasl_passwd :
[smtp.office365.com]:587    address@concealed:your_password

Note: Remember to run the command "postmap /etc/postfix/sasl_passwd" after making any changes to this file for the changes to take effect.

As for migrating without downtime and smoothly, it may not be simple with such a large version gap if you want to keep your archives of the lists. However, it should be possible to minimize this by setting up a new server alongside the old one and preparing a gradual version upgrade on it.

Regards,

[1] https://www.sympa.community/manual/customize/data-sources.html

Le 31/07/2024 à 14:31, Saadallah Itani a écrit :
Anyone?

Regards,
Saad

Sent from my iPhone

On 10 Jun 2024, at 11:45 PM, Saadallah Itani <address@concealed> wrote:

Dears,

We are running an old version of sympa/on old Rhel OS. Plan is to migrate the mailing lists to new OS and new Version.
Question is that some of the lists are dynamic through oracle db gets populated by a customzied perl script that fills Sympa mysql db in the Src column and another thing is that we use exim to send email to an Smpt servers which we need to decomission soon.
What is the best practice to migrate without heavy downtime and smoothly? And does new versions of Sympa connects to office365 instead of non-auth local smtp servers without problems?
Does new version supports dynamic list poplualtion without doing a script. Those are my concerns I hope someone can address.

Current sympa version is: 6.1.17

Thank you


Regards,
Saad
Ext. 2229

Sent from my iPhone
-- 
Benjamin Renard                  -                   Easter-eggs
44-46 rue de l'Ouest  -  75014 Paris   -   France -  Métro Gaité
Phone: +33 (0) 1 43 35 00 37   -  mailto:address@concealed
-- 
Benjamin Renard                  -                   Easter-eggs
44-46 rue de l'Ouest  -  75014 Paris   -   France -  Métro Gaité
Phone: +33 (0) 1 43 35 00 37   -  mailto:address@concealed



Archive powered by MHonArc 2.6.19+.

Top of Page