Search results for "Postorius" - Mailman-users

Re: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 1/2/23 03:54, Onyeibo Oku wrote: > > I pulled the plugs on uwsgi and installed Gunicorn. Gunicorn gave more > mileage but something is still not right. When I visit the mailmanweb > home with a browser, I see the following: > > "Server Error. An error occurred while processing your request." > > Mailmanweb and mailman3 services are running. I perused the log file > at /opt/mailman/web/logs/mailmanweb.log and found the following: > > > raise MailmanConnectionError( > mailmanclient.restbase.connection.MailmanConnectionError: ('Could not > connect to Mailman API: ', > 'ConnectionError(MaxRetryError("HTTPConnectionPool(host=\'localhost\', > port=8001): Max retries exceeded with url: > /3.1/lists?advertised=true&count=0&page=1 (Caused by > NewConnectionError(\'<urllib3.connection.HTTPConnection object at > 0x7f7f4b128c40>: Failed to establish a new connection: [Errno 111] > 0x7f7f4b128c40>Connection refused\'))"))') Postorius is unable to connect to Mailman core's REST API. Are your settings for accessing Mailman's REST API correct? E.g., does MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' match $ mailman info ... REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass Note the 3.1/ in REST root url is not included in MAILMAN_REST_API_URL. What do you get from, e.g. curl -urestadmin:restpass http://localhost:8001/3.1/lists It should return JSON with information about your lists. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

Circumstances in which a subscriber is added to Pending Confirmation list

by David Owen

Hi I wondered if anybody would be able to assist me in my understanding of the Pending Confirmation list, please. In our Mailman mailing list, our Member Policy settings for both Subscription Policy and Un-subscription Policy are set to Open. Therefore we don't require subscribers to confirm their subscription after they submit a request to join our mailing list. Despite this, a number of subscribers seem to be arriving in the Pending Confirmation (Subscriptions pending user confirmation) list. Others correctly arrive in the Members list, as we would expect. All subscription requests are made by the subscriber sending an email to our "join" email address with the subject "subscribe". I've looked at the settings carefully and can't seem to see any that may cause the above behaviour at any time (although I may have missed something of course). Therefore, does anybody know the circumstances in which subscribers to an open mailing list may somehow arrive in the Pending Confirmation list? If I could understand the cause(s) I could then consider ways to manage it or prevent it from happening. Our Mailman installation is hosted centrally in a large organisation so we while we can alter our mailing list's settings in Postorious, we can't alter the source code or similar, so we don't have great room for manoeuvre. Our Postorius version is 1.3.6. Thanks and regards David

2 years, 1 month

Re: redirecting -bounces replies

by Mark Sapiro

On 6/25/25 10:53, Hirayama, Pat wrote: > Thanks, Mark. > > I (finally) started working on this ... and in trying to implement your suggestion — ran into a problem, I think. > > The current postfix_vmap has entries like: > > list-bounces(a)lists.domain.info lmtp:[mailman-core]:24 This looks very strange. It should be something like ``` list-bounces(a)lists.domain.info list-bounces(a)alias.domain ``` where alias.domain is the configured alias domain for the mail host lists.domain.info. > So, when I try adding entries to a separate vmap file, like: > > list-bounces(a)lists.domain.info lmtp:[mailman-core]:24, user(a)gmail.com > > It only goes through normal bounce processing. > > If I do: > > list-bounces(a)lists.domain.info user(a)gmail.com, lmtp:[mailman-core]:24 > > Then it goes to the gmail address, and no bounce processing happens. The issue here is the value `lmtp:[mailman-core]:24` is completely wrong. It should be an email address with a syntactically valid domain name. The domain name isn't a real domain. It is only a name exposed to Postorius in the postfix_vmap and postfix_lmtp files. What do you have configured for the alias domain for the lists.domain.info domain? See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… If you have this properly configured, adding user(a)gmail.com in either order in postfix_vmap should work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

Re: changing the main template for subscriptions and more

by Andreas Barth

* Jens Günther (jens.guenther(a)posteo.de) [210621 17:05]: > Hey there, > > in Mailman2 there was a simple link in the moderation-emails, with > which I was able to open directly the "held-messages". I know how to > manually integrate such a link with the variables of mailman (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) > But: > > How can I change the template for all the lists (respectively > maildomains/webdomains) so that I don't have to do this manually for > all lists? I searched a bit for the corresponding template, but > didn't find it. At the end it only says the following: I'm using this patch (however, german-only) Andi diff --git a/src/mailman/templates/de/list:admin:action:post.txt b/src/mailman/templates/de/list:admin:action:post.txt index bc76a54c4..85cdd9376 100644 --- a/src/mailman/templates/de/list:admin:action:post.txt +++ b/src/mailman/templates/de/list:admin:action:post.txt @@ -9,5 +9,6 @@ Die Nachricht wurde aus folgenden Gründen zurückgehalten: $reasons -Besuchen Sie die Administrations-Seiten, um die Nachricht +Besuchen Sie die Administrations-Seiten, um die Nachricht anzunehmen oder abzulehnen. +https://$domain/mailman3/postorius/lists/$list_id/held_messages diff --git a/src/mailman/templates/de/list:admin:action:subscribe.txt b/src/mailman/templates/de/list:admin:action:subscribe.txt index 88427c8d0..ba77aa3ce 100644 --- a/src/mailman/templates/de/list:admin:action:subscribe.txt +++ b/src/mailman/templates/de/list:admin:action:subscribe.txt @@ -3,3 +3,7 @@ die Mailingliste nötig: Für: $member Liste: $listname + +Besuchen Sie die Administrations-Seiten, um die Anmeldung +anzunehmen oder abzulehnen. +https://$domain/mailman3/postorius/lists/$list_id/subscription_requests diff --git a/src/mailman/templates/de/list:admin:action:unsubscribe.txt b/src/mailman/templates/de/list:admin:action:unsubscribe.txt index c794355e8..0bace3950 100644 --- a/src/mailman/templates/de/list:admin:action:unsubscribe.txt +++ b/src/mailman/templates/de/list:admin:action:unsubscribe.txt @@ -3,3 +3,7 @@ der Mailingliste nötig: Für: $member Liste: $listname + +Besuchen Sie die Administrations-Seiten, um die Abmeldung +anzunehmen oder abzulehnen. +https://$domain/mailman3/postorius/lists/$list_id/subscription_requests diff --git a/src/mailman/templates/de/list:user:notice:welcome.txt b/src/mailman/templates/de/list:user:notice:welcome.txt index 3efc32bd1..974d8e465 100644 --- a/src/mailman/templates/de/list:user:notice:welcome.txt +++ b/src/mailman/templates/de/list:user:notice:welcome.txt @@ -1,16 +1,18 @@ Willkommen auf der Mailingliste "$display_name"! -Um an diese Liste zu schreiben, senden Sie eine E-Mail an: - +E-Mails an die Adresse $listname +werden an alle Teilnehmer verteilt. -Sie können Einstellungen vornehmen, indem Sie eine E-Mail an +Auf der Webseite https://$domain/ können Sie Ihre Einstellungen verwalten. +Wer dies möchte, kann sich dort registrieren - bitte mit der E-Mail-Adresse, +die auf der Mailingliste eingetragen ist. Nach dem Einloggen ist auch +möglich, die Empfangsadresse für die Mailinglisten zu ändern, oder +zusätzliche Sendeadressen einzurichten. +Sie können auch Einstellungen vornehmen, indem Sie eine E-Mail an $request_email - mit dem Wort 'help' (ohne Anführungszeichen) im Betreff oder im Inhalt -senden, Sie erhalten dann eine automatisierte Antwort mit weiteren -Instruktionen. Sie werden Ihr Passwort benötigen, um Änderungen an Ihren -Einstellungen vorzunehmen, aber aus Sicherheitsgründen wird dieses hier -nicht angegeben. Sollten Sie Ihr Passwort vergessen haben, nutzen Sie bitte -die 'Passwort vergessen'-Funktion auf der Login-Seite. +senden. Sie erhalten dann eine automatisierte Antwort mit weiteren +Instruktionen. Um Änderungen bei den Einstellungen vorzunehmen, wird das auf +https://$domain/ vereinbarte Passwort benötigt.

5 years

Re: Template Ignored?

by Stephen Daniel

That pulls a 404 error. Thanks for the hint. I will investigate. On Thu, Feb 17, 2022 at 11:49 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/17/22 08:04, Stephen Daniel wrote: > > Mailman3 people -- > > > > I created a new list, and used postorius to create a template for " > > list:user:notice:welcome". I then used the mass subscription feature to > > add myself to the list, having checked "pre-confirmed", "pre-approved", > and > > "pre-verified". > > > > I received a welcome message that appears to be the default welcome > > message. It certainly wasn't what I put into my template. > > > > Any suggestions on how I get mailman to use my template? Things I might > be > > doing wrong? > > > What is your setting for POSTORIUS_TEMPLATE_BASE_URL? If you create a > full URL by appending > `/api/templates/list/list.example.com/list:user:notice:welcome` > <http://list.example.com/list:user:notice:welcome> to that > where `list.example.com` is the actual list_id of your list, and go to > that URL, what do you get? > > -- > 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/ >

4 years, 4 months

Re: Is there a way of recording bounce messages?

by Mark Sapiro

On 9/26/23 11:29, Mohsen Masoudfar wrote: > > I'm dealing with the same issue. Upon reviewing the logs, I've noticed a significant number of bounced emails for a particular mailing list. Gmail users have reported not receiving emails. > I haven't been able to locate the "munge from" information. My current setup is using Mailman 3.1.1. I read it has been introduced in 3.2. DMARC mitigations were introduced in Mailman 3.1.0. They should be available in 3.1.1. They were first exposed in Postorius 1.1.0. Where are you looking for DMARC mitigations? > The Question is what to do with Mailman 3.1.1, if the upgrade is not an option. > > I get in the logs messages like below with several Queue-ids: > > Sep 25 09:03:55 localhost postfix/smtpd[26692]: 147583E927: client=a14-93.smtp-out.amazonses.com[54.240.14.93] > Sep 25 09:03:55 localhost postfix/cleanup[26696]: 147583E927: message-id=<0100018acb94b326-fdf39193-144e-4fdc-8faf-0d3df54eb4ee-000000(a)email.amazonses.com> > Sep 25 09:03:55 localhost postfix/qmgr[1298]: 147583E927: from=<>, size=24934, nrcpt=1 (queue active) > Sep 25 09:03:55 localhost postfix/lmtp[26697]: 147583E927: to=<listname-bounces@servername>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.03, delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (250 Ok) > Sep 25 09:03:55 localhost postfix/qmgr[1298]: 147583E927: removed This only says that some Amazon MTA has relayed a bounce to Mailman. It says nothing about why the message bounced. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

Re: How to create user accounts and mail addresses through CURL instead of Site Administration ?

by Shashikanth Komandoor

Thank you Mark for you response in time. On Tue, Aug 11, 2020 at 9:40 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/10/20 11:18 AM, Shashikanth Komandoor wrote: > > I am currently automating a few things using the CURL commands but > only > > postorius related as of now. Now I have a requirement. > > > > I need to create a lot many users and their mapping email ids through > > Site Administration almost daily. But it is becoming to do the same > through > > Graphical Interface. > > > > So, I just want to know the CURL commands that can be used to create > the > > user accounts and email ids mapped to user accounts. > > The accounts you are talking about are Django accounts. You cannot > create these via CURL to the Mailman core REST API. > > You might find > <https://www.django-rest-framework.org/tutorial/quickstart/> of interest. > > -- > 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/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years, 11 months

Re: Moderation not working?

by Mark Sapiro

On 11/24/20 12:30 PM, peter(a)chubb.wattle.id.au wrote: > > Hi Folks, > Running a shiny new instance of mailman3, as per the Debian package > (version 3.2.2) but the moderation doesn't seem to work. WE got > hit by a heap of spammers overnight, even though the 'hold for > moderation' bit is set for non-members (and now for members too). If the action for member posts was accept ot default processing at the time, perhaps the spam spoofed a member address in one of From:, Reply-To:, Sender: or the envelope sender, > Emails seem just to get straight through. Even now with both member and non-member actions set to hold? > Any advice on how to debug this? Would upgrading to a later version > using pip help? An upgrade probably won't help. This should work in your version. For one of the mail's, check all 4 addresses, From:, Reply-To:, Sender: and the envelope sender (available in the MTA logs). Note that Reply-To: and/or Sender: may have been modified by the list. Then see if any of those addresses matches a member or a non-member and what the specific moderation action is for that address. Also check the list's accept_these_nonmembers which is probably not exposed in your version of Postorius but which you can see via `mailman shell`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

Re: Add an extra option for "Delivery status" for users?

by Stephen J. Turnbull

Mark Sapiro writes: > On 11/19/25 12:50 PM, Thomas Ward via Mailman-users wrote: > > We have a unique case where we have a user we want to disable for mail > > receiving, etc. for the reason "Disabled by IT Security Team" but I > > don't even know if it's possible to add a delivery status that is that > > custom. > At a minimum, you would need to add that choice to the > DeliveryStatus(Enum) in mailman/interfaces/member.py and the choice and > its description to the DELIVERY_STATUS_CHOICES tuples in > postorius/forms/fields.py. I don't know offhand if that would be > sufficient, or if more would be required. In postorius/views/user.py, you also need to add it to `UserPreferencesView,delivery_status_disabled_fields`. Otherwise users will be able to reenable from a security disable. In Mailman core, it's not absolutely necessary, but I think you should handle it the same as `by_moderator` in mailman/commands/cli_members.py, mailman/commands/cli_addmembers.py, and mailman/commands/cli_syncmembers.py. The mention of `by_moderator` in mailman/utilities/importer.py is irrelevant since the new `by_security` (or whatever you call it) doesn't exist in Mailman 2. In mailmanclient, you *may* want to update docstrings in mailmanclient/asynclient.py and mailmanclient/restobjects/mailinglist.py. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

7 months, 3 weeks

Re: sqlite3 Database "read only" error on mailman_sync job

by Ugnius

Thank You. This is very valuable information. According documentation I understood that "runserver" should run on some internal port and uwsgi just works like proxy connects to the same as runserver port and serves content to apachi. Because when I was playing with the setup without "runserver" Web interface didn't work. Yes, I have stopped "runserver" and page still works fine. :) This didn't solve me database RO issue, but this information was important. Thank You. I am thinking what to do now... Maybe to recreate database (make initiation once again). It could take 2-3 hours. I did not noticed option to export/import lists setting. Or to try find solution how to make sqlite3 multiple writable. SQLite version 3.16.2 2017-01-06 16:32:41 Enter ".help" for usage hints. BR Ugnius > On 5 Sep 2019, at 23:31, Abhilash Raj <maxking(a)asynchronous.in> wrote: > >> On Thu, Sep 5, 2019, at 1:15 PM, Ugnius wrote: >> >> I do not know... In the setup example settings was something like process number = 2. But I understand at least 1 uwsgi and 1 run server should run? > > No, only uwsgi needs to run. It is fine if there are two of those, since it probably forks to have 2 worker process. There shouldn't be any "python manage.py runserver" processes running at all, it is meant only for testing purposes. > > The doc mentions that it is "development" server[1][2]. > > [1]: # Run the Django's "development" server at localhost:8000 > [2]: http://docs.mailman3.org/en/latest/prodsetup.html#setting-up-django-project > > Perhaps it should be more descriptive about what does it mean. > >> >>> On 5 Sep 2019, at 23:08, Abhilash Raj <maxking(a)asynchronous.in> wrote: >>> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>> >>> This fishy, why do you have both uwsgi and "python manage.py runserver" running? >>> >>> You only need one of those, since they both do the exact same thing. Please remove >>> whatever is running the "python manage.py runserver" part and only use uwsgi. >>> >>>> On Thu, Sep 5, 2019, at 1:02 PM, Ugnius S wrote: >>>> Thank You, Abhilash, to helping. I have checked the processes, but also I have read, that sqlite3 can run in multi writing mode. >>>> May mailman processes are next: >>>> >>>> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>> 6643 ? S 0:00 /usr/bin/python3 /usr/bin/master -C /opt/home/mailman.cfg >>>> 659 ? S 0:46 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=in:0:1 >>>> 6660 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=nntp:0:1 >>>> 6661 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=digest:0:1 >>>> 6662 ? S 0:48 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=pipeline:0:1 >>>> 6663 ? S 0:44 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=archive:0:1 >>>> 6664 ? S 0:41 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=command:0:1 >>>> 6665 ? S 0:01 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=retry:0:1 >>>> 6666 ? S 0:45 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=virgin:0:1 >>>> 6667 ? Sl 0:16 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=lmtp:0:1 >>>> 6668 ? Sl 1:30 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=rest:0:1 >>>> 6669 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=bounces:0:1 >>>> 6670 ? S 0:49 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=out:0:1 >>>> >>>> Looks like there are no double. Nothing more is running. >>>> >>>> 2019-09-05, kt, 03:16 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>>> >>>>> On Wed, Sep 4, 2019, at 2:05 PM, Ugnius S wrote: >>>>> >>>>> I have installed using documentation. My linux distribution version has no full package available. I have installed step by step: >>>>> $ sudo pip3 install mailman >>>>> $ sudo pip3 install postorius >>>>> $ sudo pip3 install hyperkitty >>>>> $ sudo pip3 install mailman-hyperkitty >>>>> And of course all mandatory components... Everything without errors, I can drop db files and I can download mailman-suite again and start from empty page again. But it will not guarantee that DB will not become READ ONLY again. Here should be logic. No developing support here? >>>> >>>> Could you be running two separate processes such that the database is locked by one and so other finds it as READ Only? When you find a read only database, can you check if it is open in some other process? >>>> >>>>> >>>>> >>>>> >>>>> 2019-09-03, an, 19:36 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>>>> >>>>> >>>>> On Sun, Sep 1, 2019, at 3:22 AM,ugniusviln(a)gmail.com wrote: >>>>> > Hi. All the project installation is under the same user / path and >>>>> > it works. Archiving working as well, (just one remark: no matter what >>>>> > to set in postorius, hyperkitty shows list as public) >>>>> > I have found work around - it is possible to change list as private in >>>>> > "admin" page. >>>>> > I started to get issues with runjobs after I have created couple of >>>>> > new lists with "no archive" option. >>>>> >>>>> How did you install all these components. It seems there the installation is broken in weird ways. >>>>> >>>>> > >>>>> > If as owner user from project home I run: >>>>> > >>>>> > django-admin mailman_sync >>>>> > >>>>> > Traceback (most recent call last): >>>>> > File >>>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/utils.py", >>>>> > line 84, in _execute >>>>> > return self.cursor.execute(sql, params) >>>>> > File >>>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py", >>>>> > line 383, in execute >>>>> > return Database.Cursor.execute(self, query, params) >>>>> > sqlite3.OperationalError: attempt to write a readonly database >>>>> > >>>>> > "django-admin runjob sync_mailman " - makes read only errors as well. >>>>> > "django-admin runjob new_lists_from_mailman" >>>>> > django.db.utils.OperationalError: attempt to write a readonly database >>>>> > END TRACEBACK >>>>> > >>>>> > I did not find information how to fix this. It was worked without errors >>>>> > before. >>>>> > I noticed, that if I stop mailman, "django-admin mailman_sync" starts >>>>> > to work. >>>>> > If I start "mailman start", then "django-admin mailman_sync" failing >>>>> > again. >>>>> > I did not check other jobs, but I think what is related to database, >>>>> > will get errors. >>>>> > Seems mailman locking the database. It is not a file permissions issue. >>>>> > Mailman db location is: /project_directory/var/data/mailman.db >>>>> > >>>>> > if to rename /project_directory/var/data/mailman.db to something, >>>>> > mailman creates database file size 0, django-admin runjobs start >>>>> > working, but of course postorius stops working. I did it for testing. >>>>> > I have returned this database file back, postorius started to work >>>>> > again, but django-admin runjobs does not work, error: "database read >>>>> > only". >>>>> > Please help me how to fix this issue. >>>>> > _______________________________________________ >>>>> > 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) >>>> >>>> -- >>>> thanks, >>>> Abhilash Raj (maxking) >>>> >>>> >>> >>> -- >>> thanks, >>> Abhilash Raj (maxking) >>> >>> > > -- > thanks, > Abhilash Raj (maxking) > >

6 years, 10 months

Mailman-users search results for query "Postorius"