Search results for "2021" - Mailman-users

Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Sat, May 15, 2021 at 1:04 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 2:52 PM, Odhiambo Washington wrote: > > > > Do I need to install sassc in the base OS or in the virtualenv? > > Have you checked `which sassc` to see if you don't already have it. It > doesn't matter whether it's in the base OS or the virtualenv. Things > running in the virtualenv can still access the base OS, just not vice > versa. > I install sassc, because sass installation always failed - after some upgrade. <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> I remember posting about it in 2020 or 2019 :) root@gw:/usr/home/wash # which sassc /usr/local/bin/sassc -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 1 month

Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Fri, May 14, 2021 at 2:41 PM Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > > On Wed, Feb 3, 2021 at 5:00 AM Abhilash Raj <maxking(a)asynchronous.in> > wrote: > >> Hey Everyone, >> >> I am pleased to announce new stable releases for Mailman Core, Postorius, >> Hyperkitty. >> >> These include both new features and bug fixes. Complete change log for >> each components: >> >> Mailman Core 3.3.3: >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… >> Postorius 1.3.4 >> https://docs.mailman3.org/projects/postorius/en/latest/news.html >> Hyperkitty 1.3.4 : >> https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html >> >> Minimum supported Python version is 3.6. >> >> You can install them using: >> >> $ pip install --upgrade postorius hyperkitty mailman >> > > I don't know if this is necessary, but I used to do it with another update > method documented by Mark. > After running the upgrade script (from that method) I would run these too: > > /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput > --verbosity 0 > /opt/mailman/mm/bin/django-admin compress > /opt/mailman/mm/bin/django-admin compilemessages > /opt/mailman/mm/bin/django-admin migrate > > Now I did run them and got an error and I wonder if I should be worried: > > > (venv) [mailman3@gw ~]$ /opt/mailman/mm/bin/django-admin compress > CommandError: *An error occurred during rendering > /opt/mailman/mm/venv/lib/python3.7/site-packages/django_allauth-0.42.0-py3.7.egg/allauth/templates/account/password_reset.html: > /bin/sh: sass: Permission denied* > Compressing... (venv) [mailman3@gw ~]$ > It actually turns out to be a show-stopper: ERROR 2021-05-14 11:48:12,691 7086 django.request Internal Server Error: /mm3/accounts/login/ Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/core/handlers/base.py", line 145, in _get_response response = self.process_exception_by_middleware(e, request) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/core/handlers/base.py", line 143, in _get_response response = response.render() File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/response.py", line 105, in render self.content = self.rendered_content File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/response.py", line 83, in rendered_content return template.render(context, self._request) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/base.py", line 171, in render return self._render(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/base.py", line 936, in render bit = node.render_annotated(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/base.py", line 903, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/loader_tags.py", line 150, in render return compiled_parent._render(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/base.py", line 936, in render bit = node.render_annotated(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/base.py", line 903, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/loader_tags.py", line 150, in render return compiled_parent._render(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/base.py", line 936, in render bit = node.render_annotated(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/base.py", line 903, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_compressor-2.4-py3.7.egg/compressor/templatetags/compress.py", line 143, in render return self.render_compressed(context, self.kind, self.mode, forced=forced) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_compressor-2.4-py3.7.egg/compressor/templatetags/compress.py", line 97, in render_compressed return self.render_offline(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_compressor-2.4-py3.7.egg/compressor/templatetags/compress.py", line 82, in render_offline 'is the original content:\n\n%s' % (key, original_content)) compressor.exceptions.OfflineGenerationError: You have offline compression enabled but key "fa788b08b65fd318d68cfc5afebc18acd3exxxxxx54d863572ad1754f368" is missing from offline manifest. You may need to run "python manage.py compress". Here is the original content: <link rel="stylesheet" href="/static/hyperkitty/libs/fonts/icomoon/icomoon.css" type="text/css" media="all" /> <link rel="stylesheet" href="/static/hyperkitty/libs/fonts/droid/droid.css" type="text/css" media="all" /> <link rel="stylesheet" href="/static/django-mailman3/css/main.css" /> <link rel="stylesheet" type="text/x-scss" media="all" href="/static/hyperkitty/sass/hyperkitty.scss" /> -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 1 month

Re: Header Filter madness

by Mark Sapiro

On January 11, 2021 5:50:04 PM MST, Brian Carpenter <brian_carpenter(a)emwd.com> wrote: >I have a client whose header filters seemed to have stop working. No >matter what I try, it seems none of their header filters are being >applied. Other lists on the same server that use header filters, are >working fine. This particular header is the subject header. I can >duplicate their problem but only with their list. If I create the exact > >same header on a test list using the exact same subject line, the >header >filter does its job (moderate). Just not with this one list. Is the poster's moderation action or the list's moderation action set to accept? Moderation action accept (rather than default processing) will bypass header filters an many other rules. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

4 years, 5 months

Re: Sad news - Brian Carpenter

by Odhiambo Washington

On Wed, May 12, 2021 at 10:45 PM <smorytko(a)gmail.com> wrote: > > https://www.tributearchive.com/obituaries/21066847/Brian-Keith-Carpenter/wa… > > I mentioned some "unfortunate circumstances" in a recent post. An inquiry > from Mark Sapiro prompted me to do a search and I sadly found this. > > Brian's company managed our list and on 4/22 we became aware that he was > hospitalized with Covid. > I have known Brian for many years mainly from the Mailman lists and he was a great resource. For a while now I have been meaning to check on the HOWTO he was writing for installing Mailm3 on Debian and yesterday I actually wanted to check on it. What a sad turn of events. May his soul rest in peace. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 1 month

Attachments in digests mails

by Eric Broens

Hi, subscribers that prefer to receive digests, are receiving attachments as encoded characters in the message body. This makes digests almost unreadable, see an extract of an example below. Is there a way to make sure the attachments are send as attachments in the digest mails? Message: 2 Date: Thu, 11 Mar 2021 23:09:29 +0100 From: *********** <*********(a)**********.**> Subject: [Planoccult] (2589) Daniel and 3 others - negative To: Planoccult <*********@******** <mailto:*********@ls.vvs.be> > Message-ID: <wcieubkwujbuvtoyrqhg@kqqa> Content-Type: multipart/mixed; boundary="=-bcRfVuQTUIVzQDmITHPG" --=-bcRfVuQTUIVzQDmITHPG Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Dear all, please find attached negative reports of 4 recent observations, including (= 2589) Daniel. I could not afford to skip such important asteroid to me (-; = despite very low probability of positive result. Best regards, --=-bcRfVuQTUIVzQDmITHPG Content-Type: image/png; name=2021_03_09_Blazewicz_2589_Daniel.png Content-Id: <cfaaa58faf30919364d7dcee7cb4cc20221c8dc4> Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=2021_03_09_Blazewicz_2589_Daniel.png iVBORw0KGgoAAAANSUhEUgAAAsAAAAGtCAYAAAAYrcL2AAAACXBIWXMAAA7EAAAOxAGVKw4bAAAg AElEQVR4nOzd6XcUR54v/C+SEEJIgDAgCbAQICFAIPbFdntvu9sX6HbbfoZn+tyZ7vu84N/o239G M/fcOefOnJnmtunpBbXtdhuvDRgwuwCxiR2BhHYJbaV6XuAqqopcIjMjMiMyv59zfIwqqzIjMyMi fxkZETntw9/+Jg0iIiIiooQoijoBRERERERhYgBMRERERIlSEnUCZDp/6T5ee+01X7/94osvsHZV Thanks, Eric

4 years, 3 months

Re: SMTPSenderRefused - howto enable STARTTLS for local mail drop

by Stefan Bauer

Need to bring this up again. Django now sends with STARTTLS, but mailman itself, does still only drop mails in cleartext. Dec 6 11:47:33 al01 postfix/lmtp[7598]: A6422600510: to=<remote-party@remote>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.01, delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (250 Ok) Dec 6 11:47:33 al01 postfix/qmgr[29156]: A6422600510: removed Dec 6 11:47:35 al01 postfix/smtpd[8092]: disconnect from localhost[::1] ehlo=1 mail=2 rcpt=2 data=2 commands=7 No starttls=1 at all :( Does the above settings work for anyone? etc/mailman3/mailman.cfg [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: localhost smtp_port: 25 smtp_user: smtp_pass: smtp_verify_hostname: false smtp_verify_cert: false smtp_secure_mode: starttls Am Mi., 10. Nov. 2021 um 09:46 Uhr schrieb Stephen J. Turnbull < stephenjturnbull(a)gmail.com>: > Stefan Bauer writes: > > > thank you for your time. Thats it :) Works now. > > Love to hear it! > > Steve > >

3 years, 7 months

Re: Showing sender as ... via ... list

by Wolfgang Bock

Dear Mark, many thanks. Works! Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Samstag, 6. November 2021 16:28 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: Showing sender as ... via ... list On 11/6/21 4:40 AM, Wolfgang Bock via Mailman-users wrote: > > Here is my question: > > What do I have to configure to get my lists to show the sender like in > this > list: Wolfgang Bock via Mailman-users mailman-users(a)mailman3.org In Postorius go to Settings->DMARC Mitigations and set DMARC mitigation action to Replace From with list address and DMARC Mitigate unconditionally to Yes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 7 months

Re: Mailman notify generating emails for request that aren't visible.

by Mark Sapiro

On 10/31/21 10:42 PM, Simon Coggins wrote: > Looking at the code in gitlab it looks like it wasn’t merged until 1.3.6: > > https://gitlab.com/mailman/postorius/-/blob/1.3.6/src/postorius/urls.py#L53 > > But it’s not in 1.3.5: > > https://gitlab.com/mailman/postorius/-/blob/1.3.5/src/postorius/urls.py#L49 Yes, I was mistaken. That code was merged on 14 Feb 2021 and is not in Postorius 1.3.4 which was released on 2 Feb. It should have been in 1.3.5 and I don't know why it is not at https://gitlab.com/mailman/postorius/-/blob/1.3.5/src/postorius/urls.py#L49, but that is moot in any case. > Thats ok, I’m going to 1.3.6 in a few days so that should solve my issue. OK -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

Re: [EXTERNAL] Re: Database deadlock when trying to delete a member.

by Simon Coggins

Thanks I’ll give that a try. Also in my tracing of the code I noticed https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/interfaces/dat… it starts with a single quote and ends with triple quotes so the single quote is never terminated. -Simon From: Mark Sapiro <mark(a)msapiro.net> Date: Wednesday, 24 March 2021 at 4:10 am To: "mailman-users(a)mailman3.org" <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: [EXTERNAL] Re: Database deadlock when trying to delete a member. On 3/22/21 9:53 PM, Simon Coggins wrote: > Ok after bit tracking I’ve worked out that the bouncer is dangling transactions when it’s sending warning messages. When https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…<https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…> is called and it get to update last_warn_sent it does the following in the DB: > > 2021-03-23 14:42:50.622 AEST [11693] LOG: statement: UPDATE member SET last_warning_sent='2021-03-23T04:42:50.622015'::timestamp, total_warnings_sent=1 WHERE member.id = 169331 > > But it never COMMITs this transaction. So all write operations are now hung waiting for the transction to be closed as the member record has been modified. As a test I added config.db.commit() after https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…<https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…> and restarted. And my mailman syncmembers worked perfectly and I didn’t have any hangs it correctly removed everyone it should have. In the database logs I can see the COMMIT. > > I’m pretty sure this is not the right spot for a config.db.commit() but hopefully this helps point to what might be going wrong. Thank you for all the research on this. It is extremely helpful. Instead of adding a commit after line 277 please try adding the @transactional decorator to the send_warnings_and_remove method at line 210 @transactional @dbconnection def send_warnings_and_remove(self, store): I think that is the proper fix. Let us know if that works. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org>

4 years, 3 months

Re: at the finish line of mailman3 docker, but can't sign in.

by Abhilash Raj

On Sun, Aug 1, 2021, at 1:52 PM, John Covici wrote: > I am finding some missing documentation in the section on configuring > mailman-web, it refers to a file > https://asynchronous.in/docker-mailman/web/ which does not exist. Try https://asynchronous.in/docker-mailman/web.html Can you point me where you saw the original URL so I can update it? > > > On Sat, 31 Jul 2021 21:21:24 -0400, > John Covici wrote: > > > > OK, thanks a lot -- if anyone here can help with proper config for > > those, that would be great. I do have a web server, but its apache > > rather than mginx and I am not sure how to properly translate. Also, > > doing a separate container for an mta which would just talk to > > mailman would get around the sendmail situation I have, although > > there may be a decent way to do that as well. I guess the hard part > > is to tie the multiple containers together. > > > > > > On Sat, 31 Jul 2021 17:56:15 -0400, > > Abhilash Raj wrote: > > > > > > > > > > > > On Sat, Jul 31, 2021, at 3:56 AM, John Covici wrote: > > > > I have a couple of questions about the container, if its OK. > > > > > > Sure it is :) > > > > > > > > > > > First, it says to run you create the directory > > > > /opt/mailman/mailman-core and /opt/mailman/mailman-web and then do the > > > > git clone. What directory should the git clone be in? > > > > > > You can do clone anywhere you can run commands from. There aren't any files in the repository that you'd be directly using. You'll just be relying on the docker-compose.yaml file from the repo (or one of the other compose files if you choose to use a different database) unless you are going to build the container images on your own instead of using the published ones. > > > > > > I just do it in my home directory of the user I am running commands as. /opt/mailman could be a good option too. > > > > > > > A couple of more questions -- is there a way to install the web server > > > > and the mta in the container, this way I could make the whole thing > > > > be independent of my host configs? > > > > > > You probably don’t want to install mta and webserver in the Mailman containers, you want to add separate containers for them and make Mailman containers talk to them. This will let you keep the container for each component separate and it is just easier to manager. > > > > > > You would need to add appropriate containers for webserver and mta in the docker-compose.yaml file and figure out the configuration on how to tie them to Mailman. The Mailman container images repo doesn’t provide such a configuration, but there are folks in the channel who have done it and you should be able to find them in this list’s archives. > > > > > > > > > > > On Fri, 30 Jul 2021 16:04:48 -0400, > > > > bob B wrote: > > > > > > > > > > is this the info you need for the container version > > > > > > > > > > [root@..... docker-mailman]# docker ps > > > > > CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES > > > > > 30af82ac9315 maxking/mailman-web:0.3 "docker-entrypoint.s…" 2 hours ago Up 2 hours 127.0.0.1:8000->8000/tcp, 127.0.0.1:8080->8080/tcp mailman-web > > > > > cd01a99cf908 maxking/mailman-core:0.3 "docker-entrypoint.s…" 2 hours ago Up 2 hours 127.0.0.1:8001->8001/tcp, 127.0.0.1:8024->8024/tcp mailman-core > > > > > 77fe89ced9e8 postgres:9.6-alpine "docker-entrypoint.s…" 2 hours ago Up 2 hours 5432/tcp dockermailman_database_1 > > > > > > > > > > > > > > > for smtp host > > > > > ------------ > > > > > cat /opt/mailman/web/settings_local.py > > > > > #allowed_hosts = ['127.0.0.1', 'localhost','HOST.DOMAIN.org'] > > > > > #ALLOWED_HOSTS = ['127.0.0.1', 'localhost','HOST.DOMAIN.org'] > > > > > ALLOWED_HOSTS = ['*'] > > > > > DEBUG = True > > > > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > > > > > EMAIL_HOST = 'smtp.example.com' > > > > > EMAIL_PORT = 25 > > > > > --------------------------- > > > > > cat /opt/mailman/core/mailman-extra.cfg > > > > > # mailman-extra.cfg > > > > > > > > > > [mta] > > > > > incoming: mailman.mta.postfix.LMTP > > > > > outgoing: mailman.mta.deliver.deliver > > > > > # mailman-core hostname or IP from the Postfix server > > > > > lmtp_host: localhost > > > > > lmtp_port: 8024 > > > > > # Postfix server's hostname or IP from mailman-core > > > > > smtp_host: smtp.example.com > > > > > smtp_port: 25 > > > > > configuration: /etc/postfix-mailman.cfg > > > > > [mailman] > > > > > # This address is the "site owner" address. Certain messages which must be > > > > > # delivered to a human, but which can't be delivered to a list owner (e.g. a > > > > > # bounce from a list owner), will be sent to this address. It should point to > > > > > # a human. > > > > > site_owner: my_real_email_is_in_the_file.com > > > > > __________________________________ > > > > > > > > > > My docker most machine /etc/postfix/main.cf has > > > > > > > > > > transport_maps = > > > > > regexp:/opt/mailman/core/var/data/postfix_lmtp > > > > > local_recipient_maps = > > > > > regexp:/opt/mailman/core/var/data/postfix_lmtp > > > > > relay_domains = > > > > > regexp:/opt/mailman/core/var/data/postfix_domains > > > > > > > > > > > > > > > # Support the default VERP delimiter. > > > > > recipient_delimiter = + > > > > > unknown_local_recipient_reject_code = 550 > > > > > owner_request_special = no > > > > > > > > > > ------------------------------ > > > > > > > > > > > > > > > > > > > > is that correct? I leave them set to smtp.example.com because the will send out via the docker host machine, and so i ONLY have my actual outbound server listed in /etc/postfix/main.cf on the docker host machine, or do i need to replace smtp.example.com with our outbound server? > > > > > > > > > > > > > > > Also, If I want to blow away everything away (databse etcc) and rebuild it... what are those steps? > > > > > _______________________________________________ > > > > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > > > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > > > > > > > > > > -- > > > > Your life is like a penny. You're going to lose it. The question is: > > > > How do > > > > you spend it? > > > > > > > > John Covici wb2una > > > > covici(a)ccs.covici.com > > > > _______________________________________________ > > > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > > > > > > > > > > -- > > > thanks, > > > Abhilash Raj (maxking) > > > > > > > -- > > Your life is like a penny. You're going to lose it. The question is: > > How do > > you spend it? > > > > John Covici wb2una > > covici(a)ccs.covici.com > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > -- > Your life is like a penny. You're going to lose it. The question is: > How do > you spend it? > > John Covici wb2una > covici(a)ccs.covici.com > -- thanks, Abhilash Raj (maxking)

3 years, 11 months

Mailman-users search results for query "2021"