Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Incoming command emails (i.e. listname-leave) routed to list itself

by Mark Sapiro

On 04/20/2017 05:37 PM, Mark Lindsay wrote: > > I'm new to Mailman 3 and Mailman in general, but I've got it up and > running, and my external app is communicating quite well with the > administrative REST API. Cool. > Here's the only problem I haven't been able to figure out: > > Say I have a list called "potato." List members can post to the list by > emailing potato(a)lists.mydomain.org. This works fine. However, incoming mail > for command addresses (e.g. potato-leave(a)lists.mydomain.org) is routed to > the list too. The command email gets sent out to all members, as if the > user who wanted to unsubscribe had just written to potato(a)lists.mydomain.org. > This is also the case with the potato-request(a)lists.mydomain.org address. > > I am using exim4 on Ubuntu. I followed the instructions here: > http://mailman.readthedocs.io/en/release-3.0/src/mailman/docs/MTA.html. The > only change I had to make to the exim4 config files in the readthedocs > instructions was in this line: > > MM3_LISTCHK=MM3_HOME/lists/${local_part}@${domain} > > I had to change it to: > > MM3_LISTCHK=MM3_HOME/lists/${local_part}.${domain} > > That is how the subdirectories are named in my lists directory. e.g. > potato.lists.mydomain.org. If I use the exact MM3_LISTCHK value from > readthedocs, I get 550 Unrouteable bounces. OK. That document needs updating. Also, the '-admin' local_part_suffix should not be there, but that's not related to your issue. '-admin' is from MM 2.1 and isn't used in MM 3. > Here are some baffling lines from /var/log/exim4/mainlog from the incoming > potato-leave(a)lists.mydomain.org email: > > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r DKIM: d=nervous-org.20150623. > gappssmtp.com s=20150623 c=relaxed/relaxed a=rsa-sha256 [verification > succeeded] > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r <= redacted(a)nervous.org H= > mail-qk0-f170.google.com [209.85.220.170] P=esmtp S=2466 id= > CABPy5zyQtJHXtCgrN37GHCUOjuo3J=DO_j0ZD03zm8gk+4shww(a)mail.gmail.com > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r => potato(a)lists.mydomain.org < > potato-leave(a)lists.mydomain.org> R=mailman3_router T=mailman3_transport > H=localhost [127.0.0.1] C="250 Ok" > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r Completed > > Why does it say `potato(a)lists.mydomain.org <potato-leave(a)lists.mydomain.org >> `? That's the key question. The transport is supposed to just relay the message to Mailman via LMTP to MM3_LMTP_PORT, but it appears to be rewriting the envelope recipient from potato-leave(a)lists.mydomain.org to potato(a)lists.mydomain.org. I suspect the router is somehow stripping local_part_suffix from the recipient address, but why, I don't know. > I think this is actually an exim4 problem, so if the solution is to just > switch to postfix, then I will definitely do that. But I'm just asking in > case someone had a similar issue with exim4 and was able to work through it. We want to make MM 3 work with Exim as an MTA. Unfortunately, I have not used Exim as an MTA in a long time and not with Mailman 3 at all, so I may not be much help. I think the person who set up Exim is on this list and may reply. If not, I'll try to research this further. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 6 months

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/23/20 11:19 AM, Mark Sapiro wrote: > Here's a thought. For Affinity/Empathy at least, how about using Mailman > core's user as the Affinity registered user. I.e., if someone's first > interaction is to register with Affinity, have that registration create > a core user to keep the Affinity registration data. This core user > already accommodates a display_name and password and email address(es). > > If the person already is a core user when registering for Affinity, just > update the core user as needed, probably only a password reset or just > setting it if it is currently None. > > Then you don't have the issue of another, separate registration for > Affinity. > > This would be more difficult for Postorius/Hyperkitty because those > users are Django users, but that isn't an issue for Affinity. > > -- 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/ How would a person already be a core user outside of a registration with Affinity? Via a list subscription or the import21 script? I do agree overall that we can more easily address some/all of these issues more easily and quicker due to not being tied to Django. I hope to get all of this address in our Nov development cycle. I do want to apologize for my tone Mark. I was wrong in the way I communicated. > -- Brian Carpenter Harmonylists.com Emwd.com

5 years

[MM3-users] Re: Question about whitlisting a domain for specific mailing list

by Odhiambo Washington

So the MTA option that doesn't involve any regex is better than no? On Thu, Mar 30, 2023, 20:17 Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/30/23 08:55, Zaheer Abbas wrote: > > Hi All, > > > > I need to whitelist a domain for a specific mailing list on your > platform. > > Only *(a)example.com email addresses should be allowed to post messages to > > this list. > > > > Could you please provide me with documentation or instructions on how to > > achieve this? I have already searched the knowledge base and user manuals > > without success. > > > In Postorius Header filters add a filter with Header = from, pattern = > ^.*(a)(?!example\.com(\W|$)) and Action as desired. That pattern will > match anything in a From: header which contains an @ followed by > anything other than example.com and a non-alphanumeric or the end of > string. I.e., things that won't match are for example > > xxx(a)example.com > xxx(a)example.com> > xxx(a)example.com yyy > > Things that will match are for example > > xxx(a)other.domain > xxx(a)example.comp > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com >

2 years, 7 months

[MM3-users] Re: UnpicklingError on mailman lists command

by Bryan Loniewski

Okay, that helped identify possible culprits. Three of our lists are hitting/over the max BLOB length (65,535 bytes) for accept_these_nonmembers. I executed this SQL command for each of the BLOB cols you referenced and only accept_these_nonmembers is borked: MySQL [mailman]> SELECT list_name, OCTET_LENGTH(accept_these_nonmembers) as howManyBytes from mailinglist where OCTET_LENGTH(accept_these_nonmembers) > 64000; +---------------+--------------+ | list_name | howManyBytes | +---------------+--------------+ | <snip> | 65535 | | <snip> | 65535 | | <snip> | 65535 | +---------------+--------------+ 3 rows in set (0.01 sec) So, putting aside *why* these lists are so large wrt that column, can or should I alter the col type(s) to MEDIUMBLOB? If yes, would that remain on suite upgrades? If no, is there a better alternative? Or some recommendation in between? ________________________ Bryan Loniewski Rutgers University OIT:EAS:Messaging and Collaboration Services System Administrator ________________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, August 3, 2021 12:15 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: UnpicklingError on mailman lists command On 8/2/21 7:35 PM, Bryan Loniewski wrote: > $ /opt/mailman/mm/bin/mailman version > GNU Mailman 3.3.2 (Tom Sawyer) > > So, I'm running > 3.2. Any other advice on debugging the truncated data? The traceback indicates sqlalchemy is unpickling data whose type is PickleType. The only mailinglist columns which are PickleType are the legacy *these_nonmembers and topics. You could try invoking mysql on Mailman's database and doing SELECT list_name, accept_these_nonmembers, hold_these_nonmembers, reject_these_nonmembers, discard_these_nonmembers, topics FROM mailinglist; and look for the longest values to possibly identify the problem list and attribute. -- 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://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

4 years, 2 months

[MM3-users] Re: Social signup?

by Duane Raymond

Wow - thanks for the redirection on where to patch it and the first-cut code. I'll look into this in 2 weeks when I am able to focus on it. Cheers, Duane On Wed, 15 Mar 2023 at 16:18, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/15/23 05:08, Duane Raymond wrote: > > > > I'll jump over to the developers list when I start this (I'm about to > > travel for a week to run an annual event in Oxford - so the far removed > > from programming)...but which chatGPT suggested so far was > > > > 1. Extending postorius/signups.html with a loop to get the configured > > social login providers PLUS adding a csrf_token field to the form > > 2. Modifying postorius/views.py (which doesn't seem to exist but > there > > is a postorius/views folder) - so perhaps this is views/urls.py > > > This is not what you want to do for this. The changes need to be in > django-mailman3, not postorius. I have attached a patch which might work > for you. I think it is good, but some of the wording is stuff that may > not be appropriate. See what you think. > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to duane(a)fairsay.com >

2 years, 7 months

[MM3-users] Re: Held messages not delivered after approval

by Mark Sapiro

On 7/31/25 04:29, Stephan Krinetzki wrote: > > /opt/mailman/var/queue/out: > total 2868 > drwxrwx--- 2 mailman mailman 4096 Jul 31 13:26 . > drwxr-xr-x 14 mailman mailman 165 Jun 27 2024 .. > -rw-rw---- 1 mailman mailman 221708 Jul 30 13:16 1753874180.0845337+0cc7849043859a79dc3678a0d8b63c1c66df0c66.pck.tmp > -rw-rw---- 1 mailman mailman 733425 Jul 31 00:00 1753912841.8847518+da55f8789ae41b75d19a02b595e3fd6d45983ade.pck.tmp These indicate a problem of some sort. .pck.tmp files should only exist for a fraction of a second. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/core/switchboa… What does `mailman qfile report for these? Are they the missing messages? > -rw-rw---- 1 mailman mailman 17758 Jul 31 13:26 1753961185.0481033+6adf966467266567275f1146f5054c95e4365c13.pck > -rw-rw---- 1 mailman mailman 31122 Jul 31 13:26 1753961185.1064982+b1f502e2af56b9b11680135c6de5fcc5285d967e.bak > -rw-rw---- 1 mailman mailman 12945 Jul 31 13:26 1753961185.1562705+a88534cfa9b03012c248ac00cbb54f4fc08c8dcc.pck > -rw-rw---- 1 mailman mailman 1407634 Jul 31 13:26 1753961185.2598634+96e501d7aa8e72fbb9f9a5c953d48fc2c7db2bc7.pck > -rw-rw---- 1 mailman mailman 17570 Jul 31 13:26 1753961185.3654013+d693065f2b9a2338f887d3ac9c0669c957131100.pck > -rw-rw---- 1 mailman mailman 60624 Jul 31 13:26 1753961185.4132354+8998ee9eb9a8a99faf1fcf045d604e669f5d0c9e.pck > -rw-rw---- 1 mailman mailman 7361 Jul 31 13:26 1753961185.413462+50dcef9bb178f54ecb2d4707ccfe02773f92336c.pck > -rw-rw---- 1 mailman mailman 84848 Jul 31 13:26 1753961185.4464717+17836b8875aa6643f7e5fb0744e72940ce5603c6.pck > -rw-rw---- 1 mailman mailman 18003 Jul 31 13:26 1753961185.4929028+17e9c78a2721cbc344124c6e04a129217ea6c794.pck > -rw-rw---- 1 mailman mailman 66982 Jul 31 13:26 1753961185.5228019+4ef59e61c6a79dd4cdee6d1110fb0582fcfafb6c.pck > -rw-rw---- 1 mailman mailman 221723 Jul 31 13:26 1753961185.5756643+6de90ae99b3d528ce5234b78a287e19f7b6686fc.pck Also, this is a lot of outgoing messages to be queued. Are you sending periodic digests at this time? If you normally see a lot of messages in the out queue, you might consider setting it's `instances` to 2 or 4. E.g., ``` [runner.out] instances: 4 ``` in mailman.cfg > /opt/mailman/var/queue/shunt: > total 3304 > drwxrwx--- 2 mailman mailman 4096 Jul 31 11:44 . > drwxr-xr-x 14 mailman mailman 165 Jun 27 2024 .. > -rw-rw---- 1 mailman mailman 451 Jul 31 00:00 1753912822.2651796+28eceef7e18eb70393377b88dc7117af8f9362a0.pck > -rw-rw---- 1 mailman mailman 490 Jul 31 00:00 1753912838.4197352+ea531cf0262c1faa58b1679b907fee92bc16822c.pck > -rw-rw---- 1 mailman mailman 1407870 Jul 31 00:00 1753912841.9177196+ccea15bdefce3a54301281c8eddf86e8230244a6.pck > -rw-rw---- 1 mailman mailman 86108 Jul 31 00:00 1753912841.9197443+7dcef4febc71e44c6d9309a24a08b08753e1ff42.pck > -rw-rw---- 1 mailman mailman 1407668 Jul 31 00:00 1753912841.9849963+a3f1869b750060c97262ece38737480d91652828.pck > -rw-rw---- 1 mailman mailman 38992 Jul 31 00:01 1753912860.5167956+940584c4f361cbd8c29e390b2f60590558effe40.pck > -rw-rw---- 1 mailman mailman 440 Jul 31 00:01 1753912860.6972685+635c065bac8dff5f9d562275d707001d773b84c1.pck > -rw-rw---- 1 mailman mailman 445 Jul 31 00:01 1753912868.7903054+befa066f254d7a3529a8555a6c942a554715d837.pck > -rw-rw---- 1 mailman mailman 33494 Jul 31 00:01 1753912878.7562895+82b724fd93260ab9a2bb49709d3a42a2f32f2c80.pck > -rw-rw---- 1 mailman mailman 217073 Jul 31 00:01 1753912878.9337828+de73a65d9c6febfa80275853921f4b53fd1d9e2a.pck > -rw-rw---- 1 mailman mailman 85888 Jul 31 00:02 1753912950.303359+8a87bce0be63ac1df8493c6b1ad6ae154fcedba7.pck > -rw-rw---- 1 mailman mailman 50244 Jul 31 00:02 1753912950.4970112+d44d493912bb3024547b8a5112f86f035dcb352f.pck > -rw-rw---- 1 mailman mailman 12887 Jul 31 00:02 1753912970.038427+31bcbd7fb2ebdf81f6de24b7283b50bcda6ded21.pck.tmp > -rw-rw---- 1 mailman mailman 443 Jul 31 11:44 1753955094.900898+67bc76525412da66a7c76363f65f583989716305.pck > > /opt/mailman/var/queue/virgin: > total 32 > drwxrwx--- 2 mailman mailman 81 Jul 31 13:17 . > drwxr-xr-x 14 mailman mailman 165 Jun 27 2024 .. > -rw-rw---- 1 mailman mailman 32013 Jan 11 2025 1736550035.6163204+472f81ece5e45a2651a4499bef418f611b43c619.pck.tmp > > Nothing special there (shunt should be checked, but not in correlation with my mail). Actually those .pck.tmp files indicate some issue. > I have one list which archives the mail. In the archive there is the mail, but it doesn't get deliverd Which says the pipeline to_archive handler is adding the message to the archive queue and the archive runner is handling it, so presumably the pipeline to_outgoing handler is adding the message to the out queue, so the issue is in the outging runner. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months

[MM3-users] Re: Message-Footer after migrating to Mailman3

by Mark Sapiro

On 5/24/21 10:43 AM, christopher.claus(a)tgcamberg1848.de wrote: > > I found the file > [code] > /usr/lib/python3.8/site-packages/mailman/templates/de/list:member:generic:footer.txt > [/code] > which includes the old footer: > [code] > _______________________________________________ > $display_name Mailingliste -- $listname > Zur Abmeldung von dieser Mailingliste senden Sie eine Nachricht an ${short_listname}-leave@${domain} > [/code] > > but no configuration item to disable this behaviour. That is the default footer template that's part of the Mailman distribution. That template is overridden by those in Mailman's var/templates/ directory. Mailmnan's import21 process created footers template in var/templates/lists/<LIST_ID>/list:member:regular:footer.txt and var/templates/lists/<LIST_ID>/list:member:digest:footer.txt > I created a new template list:member:regular:footer for the list to override the footer. But the old footer is still used where did you put it? > in detail: the resulting message sent to all subcribers of the list contains only the footer and the content sent to the list is an attachement of that "footer-message". This is the basic reason why I want to change it. > > In the logfiles I found an error and a warning: > [code] > ERROR 2021-05-24 16:22:22,895 1648 django.security.DisallowedHost Invalid HTTP_HOST header: 'tgc_mailman_web:8000'. The domain name provided is not valid according to RFC 1034/1035. > WARNING 2021-05-24 16:22:22,896 1648 django.request Bad Request: /postorius/api/templates/list/homepage.gruppe.tgcamberg1848.de/list:member:regular:footer > [/code] It appears you created the new template with Postorius, but there is an issue for Postorius templates. Possibly your Django setting for POSTORIUS_TEMPLATE_BASE_URL needs to be adjusted. > Obviously I have a problem with the hostname. I set > [code] > POSTORIUS_TEMPLATE_BASE_URL=http://tgc_mailman_web:8000 > [/code] > where tgc_mailman_web is my container name. This URL ist stored in the DB-table "template" for the name=list:member:regular:footer. A call to my fqdn or to localhost > [code] > wget http://localhost:8000/postorius/api/templates/list/homepage.gruppe.tgcamber… > [/code] > will return the footer itself - this works fine. Therefore, should i set POSTORIUS_TEMPLATE_BASE_URL to http://localhost:8000? If that works, yes. > I think, resolving this issue will use the newly configured footer. But I started with the intention to remove alle footers due to the attachement situation described above. > > Does anybody have an idea how to change the configuration of my list? Are these problems probably related to the import? Currently we are using more then 25 lists with a lot of users. Manually recreating all lists is not possible an could only be a test for a single list. The issue you are seeing has only to do with the fact that the footer is non-empty. It is not related to footer content. It is because you are posting other than text/plain messages and the MUAs you are viewing the mail with are confused by the footer being a separate MIME part. See the FAQ article at https://wiki.list.org/x/4030707 for discussion of this issue in MM 2.1 which is also relevant to MM 3. To disable adding footers entirely, sitewide, create an empty file, readable by Mailman at Mailman's ``` var/templates/site/de/list:member:generic:footer.txt ``` More about templates and search rules is at templates/de/list:member:generic:footer.txt and https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: update_index

by Darren Smith

Holy cow I think that's exactly what the problem is. I will give that a try and let you know what happens! On Tue, Apr 3, 2018 at 10:50 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/03/2018 09:02 AM, Darren Smith wrote: > > Hello, > > > > If I'm reading the docs correctly, when we run manage.py update_index, it > > should be an incremental index of new emails that have been added since > the > > last time update_index was run - can anyone confirm that this is the > > expected behavior? Or is there another command line option that I am > > missing? > > > There are two ways to run update_index. > > Hyperkitty's update_index is incremental and is run by > > manage.py runjob update_index > > Running > > manage.py update_index > > runs haystack's update_index which with no options does a full update. Run > > manage.py update_index --help > > to see the options. The incremental 'manage.py runjob update_index' > should be run every minute by 'manage.py runjobs minutely' assuming cron > is running the periodic Django jobs, so running either update_index job > manually shouldn't be necessary > > > ... > > So...can anyone help with how to get the update_index to do only emails > > added since the last time the update_index was run? > > > manage.py runjob update_index > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

7 years, 6 months

[MM3-users] Re: digests are created but not sent out

by "Jörg M. Schulz"

start fails when I use # The default language for this server. default_language: en [language.en] charset: utf-8 enabled: yes when I comment out the lines above, mailman starts. > Am 09.01.2019 um 20:53 schrieb Jörg M. Schulz <js(a)jslz.de>: > > and: When I put the stanza >>> [language.en] > into the mailman.cfg, the service doesn’t restart: > … > PermissionError: [Errno 13] Permission denied: '//var/templates' > > somehow the template path gets lost by defining this section. Possibly, somewhere the path to the .en / language templates must be set. How, where? > > > >> Am 09.01.2019 um 20:50 schrieb Mark Sapiro <mark(a)msapiro.net <mailto:mark@msapiro.net>>: >> >> Mark Sapiro wrote: >>> >>> You can change this for English by putting >>> >>> [language.en] >>> charset: utf-8 >>> >>> in your mailman.cfg. This works because us-ascii is a proper subset of >>> utf-8. >> >> >> I forgot to mention that there is a potential downside to the above. Because of the way the Python email library treats UTF-8 message bodies, list messages with UTF-8 bodies are sent with the body base64 encoded. This may or may not be an issue depending on whether you look at raw messages or perhaps grep mailboxes looking for things. >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> >

6 years, 9 months

[MM3-users] Re: Request for help with configuring "from" headers in mailman3 list

by Stephen Daniel

That worked! I apologize for needing to ask for help on this. I am very appreciative of how quickly and accurately my issues were resolved. On Thu, Jan 6, 2022 at 5:23 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/6/22 12:52 PM, Stephen Daniel wrote: > > > > Sendgrid requires that the "From:" address on any email reference an > > authenticated domain. > > > > In the old mailman2 implementation, emails sent by mailman are listed as > > > > From: <human name via LISTNAME> LISTNAME(a)LISTDOMAIN.org > > > > Reply-to: <human name> sender(a)senderdomain.com (the original email's > sender) > > > > Sendgrid would be happy with this, because LISTDOMAIN.org is a > > validated domain. > > > > However, in my mailman3 implementation, the From: header lists the > original > > email's sender. Sendgrid rejects this because the original email's > > sender's address is not one of the validated domains. > > > > How do I configure mailman3 to generate headers in the same style as the > > old mailman2 implementation? > > > In the list's Settings -> DMARC mitigations, set DMARC mitigation action > to Rrplace 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, 9 months

Search results for query "sapiro"