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

[MM3-users] Re: [External Email] Re: Mailman2 CLI commands for Mailman3

by Dave Hall

Mark, Thank you for your reply. This will help greatly in adapting to this new (to me) version. -Dave -- Dave Hall Binghamton University kdhall(a)binghamton.edu 607-760-2328 (Cell) 607-777-4641 (Office) On Wed, Oct 5, 2022 at 12:00 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/5/22 07:53, Dave Hall via Mailman-users wrote: > > Hello. > > > > Sorry if this is an old topic. I'm in the process of migrating from 2.1 > to > > 3.2. In my use case one of the advantages of Mailman 2.1 vs services > like > > Google Groups has been the ability to manage lists from the command line. > > Things like using sync_members to update the list for a committee when > the > > membership of the committee is updated one a year, or like using > > find_members and remove_members to remove a user from all mailing lists > > when they leave the organization. Even the ability to script mailing > list > > creation. > > > > So far I haven't found these commands in Mailman3. I hope there is a > plan > > to add these soon. > > They are there. In MM 3, the command line commands are all subcommands > of the `mailman` command. See `mailman --help` where you will see > subcommands including `syncmembers`, `findmember` and `delmembers`. Note > that prior to 3.3.2 there were no `addmembers`, `delmembers` and > `syncmembers` subcommands, but there were `modes` of the `mailman > members` command that would accomplish these functions. > > -- > 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/ >

2 years, 11 months

[MM3-users] Re: Importing config and archives only partially succeeded?

by Mark Sapiro

On 12/13/20 7:11 AM, Eric Broens via Mailman-users wrote: > Hi Mark, > 1.Regarding the repeated access of /archives/api/mailman/urls seems to be related to mailman not being able to open port 25. > This is weird because other mails have been distributed. > The mailman log shows:Dec 12 22:16:48 2020 (1471) ACCEPT: < message id > > Dec 12 22:16:52 2020 (1474) Cannot connect to SMTP server localhost on port 25 That message is in response to a socket.error exception in attempted delivery. It is logged only once until there is a successful delivery, but the message keeps being retried. > webserver logs:<host > - - [12/Dec/2020:22:16:50 +0100] "GET /archives/api/mailman/urls ?mlist=...&key=*** HTTP/1.1" 200 64 "-" "python-requests/2.25.0" > <host > - - [12/Dec/2020:22:16:52 +0100] "GET /archives/api/mailman/urls?mlist=...&msgid=< message id >&key=*** HTTP/1.1" 200 105 "-" "python-requests/2.25.0" > This last entry is repeated forever (until I stop the mailserver for a few minutes, but later on this happens again for other mails too). Those GETs are part of normal message processing. As I said, they result from core handlers asking HyperKitty for the URL at which the message will be archived so they can add that URL to the Archived-At: header and maybe to a message header or footer. Presumably the one that keeps repeating is the one message/message-id that is throwing the socket.error and being continuously retried. I would stop Mailman and move that one .pck or .bak file out of Mailman's var/queue/out/ directory and then start mailman. You can then examine the queue entry with `mailman qfile` and maybe see what the issue is. > 2..Regarding the mails on the archive page, for most of the lists it is solved now. So probably one of the periodic jobs fixed that.The mailinglist which showed 0 participants 0 subscribers, does show now 0 participants 66 discussions.I have checked the member tables, and the members for this mailinglist are included there. OK. > 3.What I notice now too is that the hourly runjobs tasks don't seem to finish.I would have to check what they exactly do. Can I somehow activate logging for these? > mailman 300042 300016 1 08:00 ? 00:09:18 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 302158 302149 2 09:00 ? 00:09:10 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 304513 304506 2 10:00 ? 00:09:38 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 308631 308620 3 11:00 ? 00:09:29 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 312847 312832 3 12:00 ? 00:09:15 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 317343 317332 4 13:00 ? 00:09:20 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 320079 320072 7 14:00 ? 00:09:08 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 322618 322610 13 15:00 ? 00:08:54 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 325205 325198 84 16:00 ? 00:06:56 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settings /opt/mailman/venv/bin/django-admin runjobs --list will show you what the jobs are. The hourly jobs are new_lists_from_mailman, thread_starting_email and update_index. The one running long is almost certainly update_index. I would stop running the hourly jobs until you have successfully updated the search index for all lists. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Mail configuration

by Bill Christensen

Though not a perfect solution, setting an SPF in your DNS will help. Enter something along the lines of: v=spf1 include: mailServerDomainName.com ip4:<old_IP_Address> ip4:<new_IP_address> ~all (obviously, change the generic entries to real values, and use IP6 addresses if appropriate. ) On Tue, Mar 27, 2018 at 6:34 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 03/27/2018 03:43 PM, Stephen J. Turnbull wrote: > > > > My feeling is that you want to ask on Postfix channels, since I don't > > see a good reason to involve Mailman itself in what is really a task > > for the MTA. Mailman was deliberately designed to not know anything > > about outgoing mail except a host and port to send to. > > > Which brings up the point I've been meaning to post for days but it > keeps slipping off the back burner and falling on the floor. > > I can think of a couple of ways to hack the code in Mailman 2.1 to > select a different outgoing MTA by list. It can also be done in Mailman > 3 by having separate MTA configs per list, but I can't give you a recipe > off hand. > > But, the way I would do this is what you are presumably doing anyway. > That is have separate Mailman installations on the old and new server. > Then you can move the lists incrementally and gradually. Then all you > need is a transport map in Postfix on the old server to route mail to > the new server for the already moved lists, and then finally update DNS > after all the lists are moved. > > > -- > 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, 1 month

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Odhiambo Washington

On Mon, Jan 23, 2023 at 11:48 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/23/23 12:17, Odhiambo Washington wrote: > > On Mon, Jan 23, 2023, 23:09 Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> It's actually trying to create fulltext_index, so clearly it's not > >> looking at the fulltext_index that you are. If you are following > >> https://docs.mailman3.org/en/latest/install/virtualenv.html you > probably > >> need to specify the path in /etc/mailman3/settings.py as in, e.g. > >> ``` > >> HAYSTACK_CONNECTIONS['default']['PATH'] = > >> '/opt/mailman/mm/var/fulltext_index' > >> > > > > Doesn't this follow the same rules of getting the settings.py from > gitlab? > > > I don't understand. Can you be more specific? > > Note that when following > https://docs.mailman3.org/en/latest/install/virtualenv.html you create > /etc/mailman3/settings.py and it contains > ``` > from mailman_web.settings.base import * > from mailman_web.settings.mailman import * > ``` > to establish a base set of settings that can be augmented or overridden > in /etc/mailman3/settings.py. mailman_web.settings.mailman in turn contains > ``` > HAYSTACK_CONNECTIONS = { > 'default': { > 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', > 'PATH': "fulltext_index", > ``` > which is a relative path for fulltext_index and may need to be set to an > absolute path. > Mi Mark, I have read this page - https://docs.mailman3.org/en/latest/install/virtualenv.html and further - https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-config - without clicking any external links. I still don't see the HAYSTACK_CONNECTIONS in the settings.py included on that page. I am missing something obvious, no? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 7 months

[MM3-users] Re: Mailman3 without Hyperkitty in docker

by Abhilash Raj

On February 27, 2019 11:53:34 PM PST, Danil Smirnov <danil(a)smirnov.la> wrote: >Hi Mark, > >Actually all this stuff happens inside the container after it's started >and >initialized without errors. I didn't amend the image anyhow. > >Also I have the configuration based on docker-compose.yaml provided in >the >repository which works just fine for mailman-web image. > >The very same config with postorius image (+ UWSGI_STATIC_MAP param) >fails >with 500 error... > >Now answering your questions: > >ср, 27 февр. 2019 г., 22:56 Mark Sapiro <mark(a)msapiro.net>: > >> do you have django-q in INSTALLED_APPS in your Django settings and >what >> is set for Q_CLUSTER? >> > >I've checked settings.py inside the container and I haven't found any >of >the mentioned configurations there. > >Does the manage.py that's being run here point to the right >settings.py? >> > >No clue. > >Also I wonder why we have some Hyperkitty-related cronjobs in non-HK >configured image? > >https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web… Because I am a dum dum ;-) Will work on removing those crons and stuff. Would be nice if you opened an issue on Github so that I don't forget. >Danil > > > >> -- >> 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/ >> >_______________________________________________ >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/ -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

6 years, 6 months

[MM3-users] Re: nginx configuration on a multitasking server

by David Newman

On 12/22/21 8:50 PM, Mark Sapiro wrote: > On 12/22/21 7:54 PM, David Newman wrote: >> On 12/22/21 7:29 PM, Mark Sapiro wrote: >> >>> This looks like a uwsgi issue as discussed at >>> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >>> although that's with apache and not nginx so it may not be. >> >> If I'm reading the thread correctly, it's Apache workarounds to an >> underlying Debian issue, so I agree it may not apply with nginx. > > > I think you're correct that it doesn't apply to nginx, but the symptom > is not the same. It is not a Debian issue per se. It is an Apache change > that got installed with a Debian update, but the underlying issue is > with Apache. See > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > >> There are 260 files named 'urls.py' under /opt/mailman, mostly for >> socialaccount stuff. >> >> Where does that change go? All files? Or just this one: >> >> /opt/mailman/venv/lib/python3.9/site-packages/postorius/urls.py > > > Not that one. The one whose content looks like > https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py. It > is probably in the same directory as your Django settings. On my system that file lives here: /opt/mailman/venv/lib/python3.9/site-packages/mailman_web/urls.py But the error persists after this addition and restarting MM3 and mailmanweb and nginx: url(r'^mailman/', include('postorius.urls')), There is this 404 error in uwsgi.log: [pid: 73356|app: 0|req: 3/3] 127.0.0.1 () {48 vars in 1544 bytes} [Wed Dec 22 21:13:48 2021] GET /mailman/admindb/listname => generated 5328 bytes in 14 msecs (HTTP/1.0 404) 6 headers in 197 bytes (1 switches on core 0) If this is a uwsgi issue, is there something else to tweak with that? Thanks dn > >

3 years, 8 months

[MM3-users] Re: Weird response to postings after subscriptions and accounts

by Mark Sapiro

On 9/16/19 9:22 PM, Paul Arenson wrote: > In my test of the two forms of signup, I am getting these unexpected results. Is it my settings or is something weird within the program itself? > > 1) https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > > 2) Choose "You can also subscribe without creating an account. If you wish to do so, please use the form below" > > 3) Then I have to approve it. They get "Welcome to the "Discuss" mailing list! To post to this list, send your email to: discuss(a)list.tokyoprogressive.org You have to approve it or the user has to confirm her email address? Maybe you have to approve it because the lists Subscription Policy is Moderate. > 4) But I have to approve it.I assume this is because they do not yet have a real account. And they should be listed as a NON MEMBER? No. They will be a member, they just will not have a Django account that they can log in to. > 5) But even when they sign up here: https://list.tokyoprogressive.org/accounts/signup/?next=%2Fpostorius%2Flist… they get an email from my provider (NOT MY LIST????) as follows: > > "Hello from mailman3.emwd.com! You're receiving this e-mail because user iCloud has given yours as an e-mail address to connect their account. > To confirm this is correct, go to https://list.tokyoprogressive.org/accounts/confirm-email/MTE3:1iA44k:E7w7xh… Thank you from mailman3.emwd.com! mailman3.emwd.com" Because when you create a Django account, you have to confirm your email address. > 6) And this is where it gets weird. If they send from their email program and get the welcome (Welcome to the "Discuss" mailing list! > To post to this list, send your email to: discuss(a)list.tokyoprogressive.org You can unsubscribe or make adjustments to your options via email by > sending a message to....... I then get a notice: > > "Your mail to 'discuss(a)list.tokyoprogressive.org' with the subject test notice Is being held until the list moderator can review it for approval. The message is being held because: The message is not from a list member" What is Message Acceptance -> Default action to take when a member posts to the list ? You get the notice or the user gets the notice? > 7) While if they send FROM THE interface it goes through. > > 8) What I am confused about. > > Signing up for an account should make them a member, right? Subscribing should make them a non member, no? Signing up for an account is just signing up for a Django account. You can sign up for an account and log in and then subscribe to the list. Subscribing makes one a member whether or not you subscribe from a logged in account or subscribe without creating an account. > But here it seems that both make them a non member. If an address which is not a member posts to the list, that address becomes a non-member. This is the only way other than being explicitly added by an admin that an address becomes a non-member. > And worse, someone with an account sending from the Interface has their message get through while the same person sending from an email program has me get a notice that a non member is trying to post. If by sending from the interface, you mean posting via hyperkitty, the user must have an account and be logged in to do that. Your "same person" may have multiple entities within Mailman, possibly subtly different email addresses, one of which is a member and one of which isn't. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: Recommended way to backup a mailman3 instance

by Abhilash Raj

On Mon, Apr 13, 2020, at 9:40 AM, Mark Sapiro wrote: > On 4/13/20 3:22 AM, Andrew Hodgson wrote: > > > > I was working round my own backup strategy a few weeks ago as I discussed earlier on this list. One thing I found when the directory structure that Mailman Core uses is that the lists directories do not get re-created when Mailman Core starts if they don't already exist. Is this something that should happen, and when would those directories get created? Every other directory did get re-created. > > > > In my case I was moving from a Dockerised installation to one using venvs, and as the directories from the Docker installation were empty as there hadn't been any postings for a few days, I didn't transfer those over. I created the list directories myself and everything carried on. > > > These var/lists/<list-id>/ directories hold the digest.mmdf files which > are mailboxes containing the messages for the next digest. A list post > will be added to the digest.mmdf file which will be created if > necessary, but if the var/lists/<list-id>/ directory doesn't exist, the > create will fail. > > Thus, the var/lists/<list-id>/ directories need to exist. Normally, they > are created when the list is created so they need to be part of a backup. If they are empty, perhaps the digest creation process should just re-create them instead of failing to create/send digests? We don't really need the directory structure to exist. > > -- > 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, Abhilash Raj (maxking)

5 years, 4 months

[MM3-users] Re: Issue converting table charset to utf8mb4 on mysql

by Helio Loureiro

Ok. Thanks for the clarification. Just a heads up: something went wrong. Very wrong. I had to revert the database to the last backup. But not on mailman3. It was on mailman3web. Apparently things got really bad after I converted tables django_q_ormq and hyperkitty_sender. After that hyperkitty got into cyclical crashes. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Sun, 24 Mar 2024 at 01:24, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/23/24 12:14, Helio Loureiro wrote: > > > So the question is whether it is possible to change the types in this > table. > > > > MariaDB [mailman3]> desc pendedkeyvalue; > > +-----------+----------------+------+-----+---------+----------------+ > > | Field | Type | Null | Key | Default | Extra | > > +-----------+----------------+------+-----+---------+----------------+ > > | id | int(11) | NO | PRI | NULL | auto_increment | > > | key | varchar(255) | YES | MUL | NULL | | > > | value | varchar(20000) | YES | MUL | NULL | | > > | pended_id | int(11) | YES | MUL | NULL | | > > +-----------+----------------+------+-----+---------+----------------+ > > 4 rows in set (0.001 sec) > > > > key and value are varchar. Can any of them be changed to text instead? > > Perhaps even both? > > > I wouldn't bother. The keys and values in the pendedkeyvalue table > should all be OK as latin1. That's why that table wasn't included in the > migration at > > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/database/alemb… > > -- > 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 helio(a)loureiro.eng.br >

1 year, 5 months

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

Hi Mark, Any suggestions over my earlier email? I am waiting for your reply. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Oct 27, 2020 at 1:16 PM Shashikanth Komandoor < shashikanth.komandoor(a)gmail.com> wrote: > Hi Mark, > > Thank you for your help. I have traced the versions of > different components of mailman 3. I am downloading through GIT LAB because > I need to modify the code according to my organization's requirements like > to add SMS notifications when a mail is waiting for pending approval and so. > > With your help, I have found out the commits I am using in my > environment. I got them using the way you suggested "git log". That may be > helpful for you to help dummies like me. > > *### Mailman Core Version ###* > > *commit 437cb49ffc29ef8960ef26d18bd883ed5aa61ded* > *Merge: 98cf97b 0bca998* > *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* > *Date: Thu Oct 15 14:02:36 2020 -0700* > > * Merge branch 'template' into 'master'* > > * Clarify the posting instruction in the list welcome message.* > > * See merge request mailman/mailman!723* > > *### django-mailman3 Version ###* > > *commit d9e675e5cc1b966f9cd02b2e492649972f8ddc40* > *Merge: ea2b33a c091e43* > *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* > *Date: Thu Oct 15 00:40:51 2020 +0000* > > * Merge branch 'fix-ci' into 'master'* > > * Use GHCR for the CI image* > > * See merge request mailman/django-mailman3!108* > > *### Hyperkitty Version ###* > > *commit 36f43466763c2686cf4d69c982ea64b956c30939* > *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* > *Date: Mon Oct 5 04:54:44 2020 +0000* > > * Use GH registry to pull CI image.* > > *### Mailmanclient Version ###* > > *commit aaa529808e2d61899f90509da4ea802a70d2c8ff* > *Merge: ff39dd8 8670751* > *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* > *Date: Thu Oct 15 01:09:32 2020 +0000* > > * Merge branch 'fix-ci' into 'master'* > > * Use GHCR for the CI image* > > * See merge request mailman/mailmanclient!130* > > *### Mailman Hyperkitty Version ###* > > *commit 87db8b03cc4ceba8ef8eafedeaaf11f99f2e50e0* > *Merge: 35ff801 04deff5* > *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* > *Date: Fri Jun 19 18:15:57 2020 +0000* > > * Merge branch 'fix_25' into 'master'* > > * Add a test for the presence of surrogates in the stringified message.* > > * Closes #25* > > * See merge request mailman/mailman-hyperkitty!7* > > *### Mailman-suite Version ###* > > *commit 3b8780f26d544cb333970eae43ccffc7e34314aa* > *Merge: 74e7927 4463b31* > *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* > *Date: Sat May 30 00:32:40 2020 +0000* > > * Merge branch 'doc_mb4' into 'master'* > > * Added comment about OPTIONS = {'charset': 'utf8mb4'} to settings.py.* > > * See merge request mailman/mailman-suite!8* > > *### Postorius Version ###* > > *commit 02e3183c3cd9e069d8d886426b76b08504ea5e1e* > *Merge: 61242d2 321310c* > *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* > *Date: Thu Oct 15 00:43:14 2020 +0000* > > * Merge branch 'fix-ci' into 'master'* > > * Use the GHCR registry for CI image.* > > * See merge request mailman/postorius!549* > > I have removed only mailmanclient and re-cloned it from gitlab and > ran the python setup.py develop command. But still the same error. > > Is there anything else I can do to get rid of that error. > > Thanks in advance. > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > <#m_6854939421424022049_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > On Tue, Oct 27, 2020 at 6:56 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 10/26/20 6:10 PM, Shashikanth Komandoor wrote: >> > >> > How to find out the versions of the each and every component >> > of the mailman 3 like mailman core, mailmancilent, postorius, >> > hyperikitty, mailman-hyperkitty, django-mailman3, mailman-suite and so, >> > after installation? >> >> >> cd to the directory in which you cloned the gitlab project for the >> component and do `git log` >> >> >> > If I am running an old mailmanclient or older version of any >> > other mailman component, please suggest how to upgrade either one or >> > multiple components based on the requirement. Is there any link that >> > would help me to upgrade ? >> > >> > I have used the >> > link https://docs.mailman3.org/en/latest/devsetup.html to install the >> > mailman 3 components. I expected that the procedure followed in this >> > link would install the latest versions of the mailman 3 components. >> > Please correct me if I am wrong. Is there any latest version >> > compatibility table ? >> >> >> If you installed each of mailman, mailmanclient, django-mailman3, >> postorius and hyperkitty according to instructions like >> >> $ cd ~/mailman >> $ git clone https://gitlab.com/mailman/mailmanclient.git >> >> Then set up mailmanclient: >> >> $ cd mailmanclient >> $ python setup.py develop >> $ cd .. >> >> from that document, you should have the latest version. If that is the >> case, `git log` in the mailmanclient directory should begin like >> >> commit aaa529808e2d61899f90509da4ea802a70d2c8ff (HEAD -> master, >> origin/master, origin/HEAD) >> Merge: ff39dd8 8670751 >> Author: Abhilash Raj <maxking(a)asynchronous.in> >> Date: Thu Oct 15 01:09:32 2020 +0000 >> >> Merge branch 'fix-ci' into 'master' >> >> Use GHCR for the CI image >> >> See merge request mailman/mailmanclient!130 >> >> commit 8670751caff689733751ef323ef521c4a3fa1237 >> Author: Abhilash Raj <raj.abhilash1(a)gmail.com> >> Date: Wed Oct 14 17:36:58 2020 -0700 >> >> Use GHCR for the CI image >> >> commit ff39dd8f03a820f442f2251553c444370df3b914 >> Merge: 80ebed4 76d44e1 >> Author: Abhilash Raj <maxking(a)asynchronous.in> >> Date: Fri Aug 7 19:35:05 2020 +0000 >> >> Merge branch 'invite' into 'master' >> >> Add support for inviting an email address to join a list. >> >> See merge request mailman/mailmanclient!129 >> >> or if you did this before Oct 15, maybe it starts with >> commit ff39dd8f03a820f442f2251553c444370df3b914 >> >> The particular commit you need for your issue is >> >> commit 86eb0da3cdb48e253b0d36138ab7cf91259a7583 >> Merge: c8dcb1e 28d1c3a >> Author: Abhilash Raj <maxking(a)asynchronous.in> >> Date: Sat May 16 08:02:21 2020 +0000 >> >> Merge branch 'held-count' into 'master' >> >> Add a new get_held_count() API to get a count of held messages. >> >> See merge request mailman/mailmanclient!122 >> >> >> >> Note that unless you intend to do actual development of Mailman 3, you >> should be following >> <https://docs.mailman3.org/en/latest/install/virtualenv.html> rather >> than <https://docs.mailman3.org/en/latest/devsetup.html>. >> >> -- >> 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 > > > > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 10 months

Search results for query "sapiro"