Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29
Hello all,
I have my postfix mail server running mm 2.1.26 installed via apt on Ubuntu 18.04. I wish to upgrade to 2.1.29 but it’s not in the official repos.
I tried installing from source, after first running mailman-config to gather the configure parameters (thanks Lindsay!). It installed no sweat BUT failed to start afterwards. It kept complaining of a pid file being unreadable.
So I started over (restored snapshot) and then tried adding a ppa apt source which contains 2.1.29:
https://launchpad.net/~mailman-administrivia/+archive/ubuntu/ppa
Installed with an IO error over a lock file purported to be from one of my lists but otherwise started ok. But sending an email produced an error complaining:
The mail system
list@localhost: Command died with status 2: "/var/lib/mailman/mail/mailman post list". Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group "daemon", but the system's mail server executed the mail script as group "list". Try tweaking the mail server to run the script as group "daemon", or re-run configure, providing the command line option `--with-mail-gid=list'.
So that gid is what I used when I tried from source.
Does anyone have any ideas? Thanks.
--
Fabian S.
OpenPGP:
0xA1250C2112D2D0E53E5BD964BBB5B16CFB701CD7
Quick link to shared public key: https://keys.mailvelope.com/pks/lookup?op=get&search=0xBBB5B16CFB701CD7
On 5/21/19 5:20 PM, Fabian Aldo Santiago wrote:
Hello all,
I have my postfix mail server running mm 2.1.26 installed via apt on Ubuntu 18.04. I wish to upgrade to 2.1.29 but it’s not in the official repos.
I tried installing from source, after first running mailman-config to gather the configure parameters (thanks Lindsay!). It installed no sweat BUT failed to start afterwards. It kept complaining of a pid file being unreadable.
Did you look at https://wiki.list.org/x/17891606?
What was the exact complaint. It's probably easy to fix.
So I started over (restored snapshot) and then tried adding a ppa apt source which contains 2.1.29:
https://launchpad.net/~mailman-administrivia/+archive/ubuntu/ppa
Installed with an IO error over a lock file purported to be from one of my lists but otherwise started ok. But sending an email produced an error complaining:
The mail system
list@localhost: Command died with status 2: "/var/lib/mailman/mail/mailman post list". Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group "daemon", but the system's mail server executed the mail script as group "list". Try tweaking the mail server to run the script as group "daemon", or re-run configure, providing the command line option `--with-mail-gid=list'.
This is a group mismatch in the /var/lib/mailman/mail/mailman wrapper. See https://wiki.list.org/x/4030645 for more on group mismatch.
This may be an issue with the ppa which is maintained by @jimpop who reads this list and may chime in.
However, Postfix is running the wrapper as group 'list' because 'list'
is the owner of Mailman's data/aliases.db file. You can change this by
chown daemon data/aliases.db
but you need to ensure that that file is
still group 'list' and group writable for Mailman to be able to update
it as lists are added/deleted.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 5/22/19 11:42 AM, Mark Sapiro wrote:
Did you look at https://wiki.list.org/x/17891606?
What was the exact complaint. It's probably easy to fix.
Thank you Mark for this reference. I did not look at it. I also didn't record the error. i needed this server / list back up asap so i snapshot'ed the server 1st just in case and when i encountered the issue(s), i only had limited time to resolve or restore so i didn't spend too much time troubleshooting it. but i will try this as referenced in your link when i can afford more possible downtime and if the error reappears i will capture it.
This is a group mismatch in the /var/lib/mailman/mail/mailman wrapper. See https://wiki.list.org/x/4030645 for more on group mismatch.
This may be an issue with the ppa which is maintained by @jimpop who reads this list and may chime in.
However, Postfix is running the wrapper as group 'list' because 'list' is the owner of Mailman's data/aliases.db file. You can change this by
chown daemon data/aliases.db
but you need to ensure that that file is still group 'list' and group writable for Mailman to be able to update it as lists are added/deleted.
Thanks for this heads up. i should also mention adding the ppa to my apt sources fails on gpg signing key import. i had to do it manually, searching for the key on ubuntu's keyserver.
thanks for the help.
--
Fabian S.
OpenPGP:
0xA1250C2112D2D0E53E5BD964BBB5B16CFB701CD7
also, that wiki page you sent me mention an error with missing dnspython and it states to run this:
"sudo apt-get install python-dnspython"
but that claims it's already installed, yet the error occurs. what i found you want to install is the package "python-dev".
--
Fabian S.
OpenPGP:
0xA1250C2112D2D0E53E5BD964BBB5B16CFB701CD7
On 5/23/19 9:04 AM, Fabian A. Santiago wrote:
On 5/22/19 11:42 AM, Mark Sapiro wrote:
Did you look at https://wiki.list.org/x/17891606?
What was the exact complaint. It's probably easy to fix.
Thank you Mark for this reference. I did not look at it. I also didn't record the error. i needed this server / list back up asap so i snapshot'ed the server 1st just in case and when i encountered the issue(s), i only had limited time to resolve or restore so i didn't spend too much time troubleshooting it. but i will try this as referenced in your link when i can afford more possible downtime and if the error reappears i will capture it.
ok, the issue occurred again with the same error. the complaint is (from systemctl status ... -l):
May 23 09:44:40 mail systemd[1]: mailman.service: Can't open PID file /var/run/mailman/mailman.
journalctl -xe reports:
May 23 09:46:02 mail CRON[18652]: pam_unix(cron:session): session closed for user sogo May 23 09:46:10 mail systemd[1]: mailman.service: Start operation timed out. Terminating. May 23 09:46:10 mail systemd[1]: mailman.service: Failed with result 'timeout'. May 23 09:46:10 mail systemd[1]: Failed to start Mailman Master Queue Runner. -- Subject: Unit mailman.service has failed
there is no pid file present in that location. am i wrong in assuming that gets created when the service starts?
the dir permissions in that path are:
root@mail:/var/run/mailman# ls -la total 0 drwxr-xr-x 2 list list 40 May 23 09:41 . drwxr-xr-x 38 root root 1260 May 23 09:06 ..
mm seems to start if i run "mailmanctl start", but not as the service.
i probably prefer to troubleshoot this issue and correct it rather than use the ppa via apt. what say you? Thanks.
--
Fabian S.
OpenPGP:
0xA1250C2112D2D0E53E5BD964BBB5B16CFB701CD7
On 5/23/19 7:02 AM, Fabian A. Santiago wrote:
ok, the issue occurred again with the same error. the complaint is (from systemctl status ... -l):
May 23 09:44:40 mail systemd[1]: mailman.service: Can't open PID file /var/run/mailman/mailman.
journalctl -xe reports:
May 23 09:46:02 mail CRON[18652]: pam_unix(cron:session): session closed for user sogo May 23 09:46:10 mail systemd[1]: mailman.service: Start operation timed out. Terminating. May 23 09:46:10 mail systemd[1]: mailman.service: Failed with result 'timeout'. May 23 09:46:10 mail systemd[1]: Failed to start Mailman Master Queue Runner. -- Subject: Unit mailman.service has failed
there is no pid file present in that location. am i wrong in assuming that gets created when the service starts?
the dir permissions in that path are:
root@mail:/var/run/mailman# ls -la total 0 drwxr-xr-x 2 list list 40 May 23 09:41 . drwxr-xr-x 38 root root 1260 May 23 09:06 ..
It's hard to say without seeing the contents of your mailman.service
file (or if it is generated by systemd-sysv-generator, the
/etc/init.d/mailman file), but chmod g+w /var/run/mailman
may help.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Service file:
[Unit] Description=Mailman Master Queue Runner After=network.target
[Service] Type=forking PIDFile=/var/run/mailman/mailman.pid ExecStart=/usr/lib/mailman/bin/mailmanctl -s start ExecStop=/usr/lib/mailman/bin/mailmanctl stop ExecReload=/usr/lib/mailman/bin/mailmanctl restart Restart=always RestartSec=3s RestartPreventExitStatus=1
[Install] WantedBy=multi-user.target Alias=mailman-qrunner.service
No joy on the chmod. Same error. Thanks.
On Thu, May 23, 2019, at 10:17 AM, Mark Sapiro wrote:
On 5/23/19 7:02 AM, Fabian A. Santiago wrote:
ok, the issue occurred again with the same error. the complaint is (from systemctl status ... -l):
May 23 09:44:40 mail systemd[1]: mailman.service: Can't open PID file /var/run/mailman/mailman.
journalctl -xe reports:
May 23 09:46:02 mail CRON[18652]: pam_unix(cron:session): session closed for user sogo May 23 09:46:10 mail systemd[1]: mailman.service: Start operation timed out. Terminating. May 23 09:46:10 mail systemd[1]: mailman.service: Failed with result 'timeout'. May 23 09:46:10 mail systemd[1]: Failed to start Mailman Master Queue Runner. -- Subject: Unit mailman.service has failed
there is no pid file present in that location. am i wrong in assuming that gets created when the service starts?
the dir permissions in that path are:
root@mail:/var/run/mailman# ls -la total 0 drwxr-xr-x 2 list list 40 May 23 09:41 . drwxr-xr-x 38 root root 1260 May 23 09:06 ..
It's hard to say without seeing the contents of your mailman.service file (or if it is generated by systemd-sysv-generator, the /etc/init.d/mailman file), but
chmod g+w /var/run/mailman
may help.-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/fsantiago%40gjb-online...
--
Fabian S.
OpenPGP:
0xA1250C2112D2D0E53E5BD964BBB5B16CFB701CD7
Quick link to shared public key: https://keys.mailvelope.com/pks/lookup?op=get&search=0xBBB5B16CFB701CD7
On 5/23/19 8:07 AM, Fabian Aldo Santiago wrote:
Service file:
[Unit] Description=Mailman Master Queue Runner After=network.target
[Service] Type=forking PIDFile=/var/run/mailman/mailman.pid
You could try
PIDFile=/var/lib/mailman/data/master-qrunner.pid
which is where mailmanctl actually stores the PID.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Ok making progress. Service started now but the www UI reports:
Bug in Mailman version 2.1.29
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs or the web server logs.
The web logs (nginx) contain:
2019/05/23 11:38:24 [error] 1174#1174: *2517 FastCGI sent in stderr: "PORT: 53836 REQUEST_SCHEME: https REQUEST_METHOD: GET HTTP_HOST: lists.<server>.com PATH_INFO: / CONTENT_TYPE: SERVER_PROTOCOL: HTTP/1.1 QUERY_STRING: LOGNAME: www-data REQUEST_URI: /cgi-bin/mailman/listinfo/ USER: www-data DOCUMENT_ROOT: /usr/lib" while reading response header from upstream, client: 2600:1001:b02c:d912:1501:38eb:b353:2f89, server: lists.<server>.com, request: "GET /cgi-bin/mailman/listinfo/ HTTP/1.1", upstream: "fastcgi://unix:/var/run/fcgiwrap.socket:", host: "lists.<server>.com"
Feels like another permission issue. But unsure where to go looking. Thanks.
On Thu, May 23, 2019, at 11:31 AM, Mark Sapiro wrote:
On 5/23/19 8:07 AM, Fabian Aldo Santiago wrote:
Service file:
[Unit] Description=Mailman Master Queue Runner After=network.target
[Service] Type=forking PIDFile=/var/run/mailman/mailman.pid
You could try
PIDFile=/var/lib/mailman/data/master-qrunner.pid
which is where mailmanctl actually stores the PID.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/fsantiago%40gjb-online...
--
Fabian S.
OpenPGP:
0xA1250C2112D2D0E53E5BD964BBB5B16CFB701CD7
Quick link to shared public key: https://keys.mailvelope.com/pks/lookup?op=get&search=0xBBB5B16CFB701CD7
On 5/23/19 8:50 AM, Fabian Aldo Santiago wrote:
Ok making progress. Service started now but the www UI reports:
Bug in Mailman version 2.1.29
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs or the web server logs.
What's in Mailman's error log?
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 5/23/19 12:11 PM, Mark Sapiro wrote:
On 5/23/19 8:50 AM, Fabian Aldo Santiago wrote:
Ok making progress. Service started now but the www UI reports:
Bug in Mailman version 2.1.29
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs or the web server logs.
What's in Mailman's error log?
nothing.
--
Fabian S.
OpenPGP:
0xA1250C2112D2D0E53E5BD964BBB5B16CFB701CD7
On 5/23/19 1:29 PM, Fabian A. Santiago wrote:
On 5/23/19 12:11 PM, Mark Sapiro wrote:
On 5/23/19 8:50 AM, Fabian Aldo Santiago wrote:
Ok making progress. Service started now but the www UI reports:
Bug in Mailman version 2.1.29
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs or the web server logs.
What's in Mailman's error log?
nothing.
all cgi-bin files owned by root:list. just an fyi. but private archives folder owned by www-data. i'm unsure if this is correct.
--
Fabian S.
OpenPGP:
0xA1250C2112D2D0E53E5BD964BBB5B16CFB701CD7
On 5/23/19 10:41 AM, Fabian A. Santiago wrote:
On 5/23/19 1:29 PM, Fabian A. Santiago wrote:
On 5/23/19 12:11 PM, Mark Sapiro wrote:
What's in Mailman's error log?
nothing.
It probably is permissions on the logs and others. Have you run
check_perms. If not run check_perms -f
as root. Don't worry about
symlinks, they don't matter.
If that doesn't fix it and you still don't get the error log messages, edit (not sure of path, but I think) /usr/lib/mailman/scripts/driver and at line 33 change STEALTH_MODE = 1 to STEALTH_MODE = 0 and you'll get the error info in your browser.
all cgi-bin files owned by root:list. just an fyi. but private archives folder owned by www-data. i'm unsure if this is correct.
Yes, that's correct.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
It probably is permissions on the logs and others. Have you run check_perms. If not run
check_perms -f
as root. Don't worry about symlinks, they don't matter.
that did it, finally! check_perms -f. thanks for your help. finally on 2.1.29 now. all seems to be working now.
--
Fabian S.
OpenPGP:
0xA1250C2112D2D0E53E5BD964BBB5B16CFB701CD7
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On Wed, 2019-05-22 at 08:42 -0700, Mark Sapiro wrote: +AD4 On 5/21/19 5:20 PM, Fabian Aldo Santiago wrote: +AD4 +AD4 +AD4 +AD4 So I started over (restored snapshot) and then tried adding a ppa apt source which contains 2.1.29: +AD4 +AD4 +AD4 +AD4 https://launchpad.net/+AH4-mailman-administrivia/+-archive/ubuntu/ppa +AD4 +AD4 +AD4 +AD4 Installed with an IO error over a lock file purported to be from one of my lists but otherwise started ok. But sending an email produced an error complaining: +AD4 +AD4 +AD4 +AD4 The mail system +AD4 +AD4 +AD4 +AD4 +ADw-list+AEA-localhost+AD4: Command died with status 2: +ACI-/var/lib/mailman/mail/mailman +AD4 +AD4 post list+ACI. Command output: Group mismatch error. Mailman expected the +AD4 +AD4 mail wrapper script to be executed as group +ACI-daemon+ACI, but the system's mail +AD4 +AD4 server executed the mail script as group +ACI-list+ACI. Try tweaking the mail +AD4 +AD4 server to run the script as group +ACI-daemon+ACI, or re-run configure, providing +AD4 +AD4 the command line option +AGA---with-mail-gid+AD0-list'. +AD4 +AD4 +AD4 This is a group mismatch in the /var/lib/mailman/mail/mailman wrapper. +AD4 See +ADw-https://wiki.list.org/x/4030645+AD4 for more on group mismatch. +AD4 +AD4 This may be an issue with the ppa which is maintained by +AEA-jimpop who +AD4 reads this list and may chime in. +AD4 +AD4 However, Postfix is running the wrapper as group 'list' because 'list' +AD4 is the owner of Mailman's data/aliases.db file. You can change this by +AD4 +AGA-chown daemon data/aliases.db+AGA but you need to ensure that that file is +AD4 still group 'list' and group writable for Mailman to be able to update +AD4 it as lists are added/deleted.
New PPAs were released a few hours ago that address this userid mis- match problem.
- -Jim P.
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEECPbAhaBWEfiXj/kxdRlcPb+1fkUFAlz5UeEACgkQdRlcPb+1 fkViMxAAj4QFzarrGlqciYloc9KaGC3V5sGIYo7njEBbpygWdqoVmERmmBMFhPko myv8l7fmVP7JOVeO6bnqc1GJ4vYmBqnNwywPBgg3kVKX0PlEiQYO5DEDUA3GFQ6a K3oLf4PxR6xvTsegLDmDtHVwtFMWoLJ/K2AsFhnZE9qsCQ1Fi7g/QkTdLuUVtzgN rp2pOjsHG7aUOeFUKIUOO+zmHxfGONLg3HMHDAhVrIEaXjbZze9vTaxxTUHEeI1W /bSATTEnhpPUW+fKuP3f6Jp2OePrt4uMIBQgFs8/5RO3Q8cSPQBQzoy/zeCL5HUk djLd2sGZOUKdcrVRUQHtwCHmQ/iwB2Xc1xzu05kUljmzNfcWkbDusm0yyO2yen0C clugcCsfxhssK6tKigwjBHPtEiLG57Jl0QQqFHEzRip2HzVAJUnkDDEHrsEv9g2y wgU+Y2BDVPiT+WbWyrNkbgv0cN72FB1xEB6eaB0SIwHZjvLpHKRzdeGXScAntxxM EXdxQ3bP7VDo//fo/2H1dTPLMJzsdCxqIMfErt06DY/RLUhA8mHGPk88VSE17arN IS5SUxKZnoy58DTtq5+nyosK4stWtsZxNT8t7W4bh9PZ3KXYJTjWNFYPOK5qHp8b CG8+1rKKEGjy6GgW5N/D8TR3XMqLWGmUb5HDrG/G5WeL5fr3L40= =VTyA -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On Thu, 2019-05-23 at 09:04 -0400, Fabian A. Santiago wrote: +AD4 +AD4 Thanks for this heads up. i should also mention adding the ppa to my apt +AD4 sources fails on gpg signing key import. i had to do it manually, +AD4 searching for the key on ubuntu's keyserver.
Can you provide some more details on this, please. Was this possibly due to you not being able to follow the default PPA instructions of using +ACI-add-apt-repository+ACI?
I just update the Mailman PPA to include this text above the area that details how to add a PPA to an Ubuntu system.
The details below are automatically provided by Launchpad and not edible by Mailman Administrators. One important bit that is missing below is that the command line program +ACI-add-apt-repository+ACI is available in the stock Ubuntu package +ACI-software-properties-common+ACI which may need to be installed on your system.
hth.
- -Jim P. -----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEECPbAhaBWEfiXj/kxdRlcPb+1fkUFAlz5VWAACgkQdRlcPb+1 fkWqsw//RNCXQJ0BX/3SaNuNtdc+EFRjvbAYWrnGAIAs0ObdwfJnoI9QwSNI3BDt owdiovTqyAe7lnmHYSCIIr01h7BGh1Y2N4cQztzYZOR+oS6ECjyYLHXq1CV57cBz dcpJv2nYTRiPYdsRgxEMYrsoBR1MjykNOOMI6Ts5Pl8rhJI7KbMqa9zyc3avNkTV ATPk4Fo33N1+AiVKadjTIJOssrK/obkYt8EDFDv4IabGb40UlwScq3Z+eHl1BBOM TDcRfbbodF8kN0JgyWRnOSdpZ9vAgXjDDyzdZbHOOkaN8RhoPh63sggzB6ROnO8O xjP0rrcTr+2zVy4KAguDMj+7S30EBgj3jjIRtt+lEAlSo1vQ6EzQnRLYbtLmf43I 9OO+CCAdMwnlX1HDNZWlsNnkD5qOKDULjgnMv5+ZEawQbqoEH18UJklu1pYcQLUo Qc9B1G3ignISVyvz334x0GZ5rvUmiNKQT4OsI6e1mfCRqTXKQFvRIRVs7YazA2S0 pFeyhj5I5ViiLlNzz7T2wmvz1k/E2ikmgu3shYTFgFGgJRsczG8o3rVui4kdJW9q mbH7Lo8P3elMGL7VjfC7ERspqO7I+II56PnEkOpiOXMxEwkn9wwdhDj4k6c8QUn4 wauVGLKC2yxbLjC96cuW+TWF/Kfe3pGBpipTM4YUoAbANgf3MHQ= =dPzb -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On Thu, 2019-05-23 at 09:40 -0400, Fabian A. Santiago wrote: +AD4 also, that wiki page you sent me mention an error with missing dnspython +AD4 and it states to run this: +AD4 +AD4 +ACI-sudo apt-get install python-dnspython+ACI +AD4 +AD4 but that claims it's already installed, yet the error occurs. what i +AD4 found you want to install is the package +ACI-python-dev+ACI. +AD4
python-dev should only be necessary if you are building Mailman from source. If you are installing from PPA/apt/rpm/dpkg/etc you should only need python-dnspython
- -Jim P. -----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEECPbAhaBWEfiXj/kxdRlcPb+1fkUFAlz5WZwACgkQdRlcPb+1 fkWrRg/9FQhOdtAP0yPAxmu8cTZp9LZUOlL33pRx4oT+okhjDP+G+XwvDvlt3Ta6 isA20JDIsN5HV0G1Kw1nA5/JHo4qCep8SIHFzQmlJ6izIg5bji7ygDiwCjjxf9zw CE/99Aen1N9I5FxW10Hynr7C8pD34Q5KpMqnev6IxpkvOsN4rbTkSCHtbZ4havko qSLM4GxMtoulJj5fe+WUUqlp60BpLh85qCg12RRufrL9IS+2i/LTkqAHNKBGqQPj ld1x6Qou5AmP7QR4XXVp4BDsbgNQjxq0KJaLnDYTVy9Uijq2PExDCo5K9ddPmFoI 0uqaveIDrHauY79ihb6dQJxvqty/ZoompG3bL460nhxWsJFyY1nPoMvpfjsQvBmI 87vduCqyIbhhfBarXhSkSwIFjLjwLMRVrfr+mvfe7obJD4kPavPaIRo4kj8lzYJ+ NsBAx9sAYDgYGSNAg74dB8pbHXwMi83hVfkACcybnZIQPZyOXg1iZcbwAFMpf2sL HSCpDf5P2YKXQKba2+aMIPNgvc5aXLx/yrqN60Gv5ra58uEIadtf+wTriX28u99u pql0FFeTqCgT5YYj3raWemHlB/Ipjf0JgMzSe7iYXF2tVUJfTKlFzEfw1YKqT32I vISThv44+h+swZ08ysnEZd0VZtPesF8UnITLFjL9jC5blDhdEwU= =MZKl -----END PGP SIGNATURE-----
participants (4)
-
Fabian A. Santiago
-
Fabian Aldo Santiago
-
Jim Popovitch
-
Mark Sapiro