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

[MM3-users] Re: [ERROR] Error handling request List archivers

by Shashikanth Komandoor

Thank you Mark for guiding me to the benefit of putting the list and so I have added the list. Along with the [archiver.hyperkitty], [mta] and [database], few lines of my mailman.cfg look like below: *[webservice]workers = 4timeout = 900* The above block of webservice is added yesterday for testing or trail as I am getting the above issue. And there is no line that is calling *gunicorn* in my mailman.cfg. Apart from that I tried to locate and see the content of the gunicorn.cfg file as below : *(venv3) [root@lsmgr mailman]# cat /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg[gunicorn]# All the options that can be put here are available at# http://docs.gunicorn.org/en/stable/settings.html#settings <http://docs.gunicorn.org/en/stable/settings.html#settings># No of seconds to wait before killing the worker processes.graceful_timeout = 30* Please confirm the time I have to change is *graceful_timeout *in *gunicorn.cfg* and if I have changed how do I restart the *gunicorn*. I have never used or never known about this *gunicorn* but still running the service in production. Please help me and also suggest if I could provide you any more data from giving resolution. <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_5710631741815235215_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Thu, Jul 23, 2020 at 3:47 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/22/20 9:13 AM, Shashikanth Komandoor wrote: > > > Never mind please I am sending to you only instead of group as I am > sending you the production content along with the mail. > > I don't see anything there that can't be posted to the > mailman-users(a)mailman3.org list. If your concern is revealing the > support-tnvc.lsmgr.nic.in list id, just replace it with <list-id> or > list.example.com or similar. > > Messages sent to me personally rather than the list suffer many > problems. They are my absolute last priority, and I am only one person, > the collective knowledge of the list is greater. Also, at times I am off > line for several days or longer. > > Finally, there is no opportunity for other members of the community to > benefit from an off-list exchange. > > > When I am trying to browse one of my lists, I am getting "[ERROR] > > Error handling request /3.1/lists/support-tnvc.lsmgr.nic.in/archivers > > <http://support-tnvc.lsmgr.nic.in/archivers>" in the mailman.log and the > > full error message is in attachment. > > Try increasing your gunicorn worker timeout from the default 30 seconds. > I.e., add > > timeout = 90 > > to your gunicorn.cfg and restart gunicorn. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > -- Thanks & Regards, Shashi Kanth.K 9052671936 <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>

6 years, 2 months

[MM3-users] Re: Pb with archive display

by Pierre Malard

Thanks Mark, Effectively we had a problem with the value of « api_key » which were in pseudo value. I fixed that with the value of « MAILMAN_ARCHIVER_KEY ». Unfortunately we still don't have any archives... Here are the logs retrieved from the mailman.log logs: May 05 15:59:42 2022 (579075) Exception in the HyperKitty archiver: {"error": "character with byte sequence 0xe2 0x80 0x99 in encoding \"UTF8\" has no equivalent in encoding \"LATIN1\"\n"} raise ValueError(result.text) ValueError: {"error": "character with byte sequence 0xe2 0x80 0x99 in encoding \"UTF8\" has no equivalent in encoding \"LATIN1\"\n"} And in mailman-web.log: WARNING 2022-05-05 13:58:52,996 579167 hyperkitty.views.mailman Could not archive the email with message-id '<C7E61653-D399-466A-BEC3-CE61D567E870(a)teledetection.fr>': character with byte sequence 0xe2 0x80 0x99 in encoding "UTF8" has no equivalent in encoding "LATIN1" Is it a way? I don't understand the message about LATIN1. It seems to me that UTF-8 was the encoding retained in Mailman. > Le 4 mai 2022 à 15:39, Mark Sapiro <mark(a)msapiro.net> a écrit : > > On 5/4/22 05:45, Pierre Malard via Mailman-users wrote: >> On the other hand Mailman3 does not seem to take into account the display of the archives. The contributions are indeed in the directory "/var/lib/mailman3/archives/hyperkitty/spool" but HyperKitty does not take them into account when displayed on the Web interface. >> Is this normal? > > No. The messages are in /var/lib/mailman3/archives/hyperkitty/spool because delivery to HyperKitty failed. There should be messages in Mailman's var/logs/mailman about the failures. > > The setting for api_key in mailman-hyperkitty.cfg must match the setting for MAILMAN_ARCHIVER_KEY in your Django settings. Also, the setting for base_url in mailman-hyperkitty.cfg must be good. If you append `/api` to that url, the result should return a page of documentation of HyperKitty's REST API. > > Also see this thread https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > -- > 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/ -- Pierre Malard «Le courage, c'est de chercher la vérité et de la dire, c'est de ne pas subir la loi du mensonge triomphant qui passe et de ne pas faire écho de notre âme, de notre bouche et de nos mains aux applaudissements imbéciles et aux huées fanatiques.» Jean Jaures - "Discours de jeunesse" - 1903 ("`-/")_.-'"``-._ . . `; -._ )-;-,_`) (v_,)' _ )`-.\ ``-' _.- _..-_/ / ((.' ((,.-' ((,/ πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

4 years, 5 months

[MM3-users] Re: Upgrade path

by David Krantz

Hi. Getting back to this... Some log of what I'm doing. * First git fetch; git pull on all parts. Started new envs to simplify rollback etc. * activate the new 3.5 venv. ( I run the commands one at a time, but this is more compact in text form:) > cd git/mailman; python setup.py build; python setup.py install > cd ../mailman-hyperkitty; python setup.py build; python setup.py install > deactivate activate 2.7 venv, then > cd ../mailmanclient; python setup.py build; python setup.py install > cd ../django-mailman3; python setup.py build; python setup.py install > cd ../postorius; python setup.py build; python setup.py install > cd ../hyperkitty; python setup.py build; python setup.py install So far no errors. Just warnings. Backups: * deployment directory (as user with rw in directory) > tar -cvzf backup.tgz deployment_directory * postgres databases (as user with postgres-priv) > pg_dump maiman | gzip -9 > mailman.bak.gz > pg_dump mailmanweb | gzip -9 > mailmanweb.bak.gz Create new .wsgi-file based on mailman-suite (I used the kludge in the script to get the python path correct) Change apache2.conf to point to new venv and new wsgi-version Updated the mailman3wrapper.sh I use for init to start the service. I could not get hyperkitty interface to run so I deactivated it and set mailman as index instead. It complains that a column is missing, but I cannot get the migrate script to run so I decided that I do not need the archiver as I currently don't use it. So I will have to get back to this and either remove the archiver completely or get it to run. So the line with ^$ in urls.py now is url(r'^$', RedirectView.as_view(url=reverse_lazy('list_index'))), instead, and the line "hyperkitty," is commented in the django application list. cheers. // David On Tue, Aug 8, 2017 at 6:48 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 08/08/2017 04:42 AM, David Krantz wrote: >> >> What is the rekommended way to upgrade to the newest version? (newest >> _usable_ version, of course)? Is it docker-only with a migration from >> the current solution to a docker based? If so, any ideas or pointers >> on how to go about this? > > > You may find this wiki article helpful <https://wiki.list.org/x/17891998>. > > I started with bundler on both this (lists.mailman3.org) and the > mail.python.org installs, but have been updating from the heads of the > various gitlab branches since very early on. > > At the moment, these installations are somewhat ahead of the 3.1 > release, but I am not updating as the latest core has dropped Python 3.4 > support, and I haven't yet installed Python 3.5 or 3.6 on these (Ubuntu > 14.04) servers. (I will probably install 3.6 from source at some point.) > > Please feel free to ask here if you have more specific questions. > > -- > 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/

9 years

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

by Krinetzki, Stephan

Hi Mark, >That's a misleading message. It's been improved by https://gitlab.com/mailman/mailman/-/merge_requests/1362, however usually the underlying issue is inability to access a header or footer template when decorating the message. This in turn is most likely >caused by some template(s) in Mailman's var/templates/ directory being owned by `root` or some other non-mailman user and not readable by the Mailman user which in turn most likely results from running `mailman import21` as root. You are my hero! After "patching" the outgoing.py file with the error messages I got Aug 06 09:52:51 2025 (443278) Cannot connect to SMTP server 127.0.0.1 on port 25: HTTPSConnectionPool(host='lists.example.com', port=443): Max retries exceeded with url: /postorius/api/templates/list/hpc-admintreffen-info.lists.example.com/list:member:regular:footer (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1006)'))) And was shocked. Why is there an SSL Certificate Error? Why can't python requests verify the certificate? So I googled a bit and found, that we can fix this be editing the cacert.pem of certifi. I did, but the error was still there. So I checked my https VHost (Apache btw) and there was a wrong chain in it. Oof. An error, that a browser does not see, but any ssl client. I fixed it and boom - everything works again. Thank you again and thank you Stephen for trying to resolve the problem 😊 -- Stephan Krinetzki IT Center Gruppe: Anwendungsbetrieb und Cloud Abteilung: Systeme und Betrieb RWTH Aachen University Seffenter Weg 23 52074 Aachen Tel: +49 241 80-24866 Fax: +49 241 80-22134 krinetzki(a)itc.rwth-aachen.de www.itc.rwth-aachen.de Social Media Kanäle des IT Centers: https://blog.rwth-aachen.de/itc/ https://www.facebook.com/itcenterrwth https://www.linkedin.com/company/itcenterrwth https://twitter.com/ITCenterRWTH https://www.youtube.com/channel/UCKKDJJukeRwO0LP-ac8x8rQ -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, August 5, 2025 6:19 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Held messages not delivered after approval On 8/5/25 02:06, Krinetzki, Stephan wrote: > Aug 05 10:21:05 2025 (217986) Cannot connect to SMTP server localhost > on port 25 > > The last error is a very often in the mailman.log: That's a misleading message. It's been improved by https://gitlab.com/mailman/mailman/-/merge_requests/1362, however usually the underlying issue is inability to access a header or footer template when decorating the message. This in turn is most likely caused by some template(s) in Mailman's var/templates/ directory being owned by `root` or some other non-mailman user and not readable by the Mailman user which in turn most likely results from running `mailman import21` as root. Bottom line - check that all sub-directories and files in Mailman's var/templates/ directory are searchable and readable by the Mailman user. -- 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 krinetzki(a)itc.rwth-aachen.de

1 year, 2 months

[MM3-users] Re: Mailman web Stopped working after upgrade

by David Krantz

But now that it is working the order of the mailing lists on the index page are in random order again. When it worked initially they seemed sorted by name. Whey I follow the link "see all lists" the order is correct, though. Annoying. BR // David On Tue, Mar 3, 2020 at 10:26 PM David Krantz <gazorg(a)gmail.com> wrote: > > Hi, > > I tried psycopg2-binary and a few other rehashes of that. Now I got it > working by downloading the source for psycopg2 manually and building > it myself, then I installed it into my venv like any other self-built > package. https://pypi.org/project/psycopg2/#files > > I run mod_wsgi in Apache so I thought it should be enough to restart > Apache. I am quite convinced that I did that (and for that matter > restart the machine at a few points). But I might have been sloppy and > reversed the order in the end when I got it running, this process is a > bit to manual. I will use another solution when I rebuild the server > one day. The problem with rebuilding the server is that I'd have to > install a MTA with all its modules, milters, setups and what not, and > mailman. To just reinstall on a fresh machine would be easy, the trick > is that I want to rebuild some things in a better way which will take > me some time. E.g. using a separate wsgi service and a more modern > spam filter than Spamassassin. Otherwise it is easy. But my situation > now is a bit short on time so if I can postpone that a bit I will. > > Thanks. > // David > > // David > > On Tue, Mar 3, 2020 at 10:02 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > > On 3/3/20 12:33 PM, David Krantz wrote: > > > > > > I think that this might be due to some kind of python misfeature where > > > compiled code behaves slightly differently to interpreted code, that > > > might explain the delay in it working initially before breaking. I > > > have no idea of how to solve this. I have tried to uninstall and > > > reinstlall psycopg2 in different versions without any luck. > > > > You need to activate your virtualenv and do > > > > pip install psycopg2-binary > > > > it must be psycopg2-binary, not just psycopg2. It's probably best to do > > > > pip uninstall psycopg2 > > > > first. > > > > As far as it working for a while, did you restart your wsgi service > > (gunicorn, uwsgi, ??) after upgrading? > > > > -- > > 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/

6 years, 7 months

[MM3-users] Re: Pck files stuck in out queue

by Lieuallen, Thomas Otis

I ended up emailing the list. That email got stuck as well. So, I removed their template – and the message went through. So, that appears to have been the problem. But, not sure why. Thank you Tom Lieuallen From: Lieuallen, Thomas Otis via Mailman-users <mailman-users(a)mailman3.org> Date: Thursday, February 6, 2025 at 3:25 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Pck files stuck in out queue [This email originated from outside of OSU. Use caution with links and attachments.] Mark, There were no apparent permissions problems on templates. I was getting the ‘Cannot connect to SMTP server’ message in mailman.log. I did end up applying the patch to decorate.py and messages went through. I’ve since removed the patch, as I’m still looking for an answer and might as well let it queue up again. The only thing that is making me ponder at the moment is that the list owners setup a template for list:member:regular:footer in postorius. It appears that each list has a copy of that file. The modifications I see in postorius are not in their …/templates/list/<listname>/en/list:member:regular:footer.txt file. Are their modifications stored somewhere else and causing the problem? Thx Tom Lieuallen From: Mark Sapiro <mark(a)msapiro.net> Date: Thursday, February 6, 2025 at 2:22 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Pck files stuck in out queue [This email originated from outside of OSU. Use caution with links and attachments.] On 2/6/25 12:42, Lieuallen, Thomas Otis via Mailman-users wrote: > Running Mailman 3.3.10 > > I have 11x pck files stuck in my out queue. There tends to always be a .bak file as well. If I run ‘ls -l’, the files are continually updated and rotated through, just as fast as I can look. Are old ones being delivered and new ones added or the same ones just being renamed? I suspect the latter and I suspect the issue in that case is probably due to the OUT runner trying to access a template file like list:member:{regular|generic}:{header|footer}.txt and not having permission. See the last two posts in the thread at https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…><https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> > I believe they’re all for one list. When I use ‘strings’ on one to get a hint of what’s inside, I see the list members at the bottom (recipients). One of them consistently has ‘!’ before their email address. Not sure if that’s a clue. Just no other reason to suspect that, though. The files are python pickles and `strings` shows lots of stuff. The ! may be something in the pickle that's not part of the email address. The way to examine these files is with the `mailman qfile` command. -- 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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…><https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…><https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to lieualth(a)oregonstate.edu _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to lieualth(a)oregonstate.edu

1 year, 8 months

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Odhiambo Washington

On Tue, 28 Jul 2020 at 06:50, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/27/20 4:29 AM, Odhiambo Washington wrote: > > On Mon, 27 Jul 2020 at 02:49, Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> Is there an empty /opt/mailman/mm/__init__.py file? > >> > > > > No. > > > There has to be one. Create it and then Django will be able to import > your settings. > > See the first line after > > Create directories: > ... > and files: > > at > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience#line-69 > > > I don't know why I didn't see that initially :-) > > Yes. However, that also means the /opt/mailman should be owned by > mailman3, > > right? So I wasn't quite mistaken. > > > It doesn't matter what user actually `owns` this directory and its > subordinates as long as the Mailman user, mailman3 in your case, can > read and write there. Of course, making everything owned by the Mailman > user is the easiest way to ensure this. > True. > > Note also that any commands in /opt/mailman/mm/bin need to be run as the > Mailman user and not root. Running them as root can create things owned > by root the can't be read by the Mailman user. > So, now I remember why I had to chown -R mailman3 /opt/mailman Then now it seems like I have been doing things incorrectly, because I have been doing a lot of operations as root by simply: cd /opt/mailman/mm virtualenv venv source venv/bin/activate Looks like the correct way is to start with su - mailman3 > > PS: There is the issue with qcluster, which doesn't seem to have been > > documented in details from your "experience". > > I see the configuration file and the init script, but not how to install > > it, or whether the procedure already installed it. > > > qcluster is part of Django. If you have this > > # > # Asynchronous tasks > # > Q_CLUSTER = { > 'timeout': 300, > 'save_limit': 100, > 'orm': 'default', > } > > or similar uncommented in your Django settings, and also 'django_q' in > your INSTALLED_APPS, it's there and all you need to do is run > > /opt/mailman/mm/bin/django-admin qcluster > > to run it, but it should be run as a service via init or ?? > I have run it from supervisord. It has forked 30 processes and refuses to kill them when I stop supervisord. I will look for options around it. Answering my own question I asked earlier, I have found "django-admin help --commands" to answer it. PS: Did you by any chance find time to look into the issue about wsgi.py that you had mentioned - the one that has me stuck using it?? Thanks again. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 2 months

[MM3-users] Re: Enable delivery

by Hirayama, Pat

No, I was obfuscating the addresses of the user and listname. And it was the trailing dot/period that was the problem. Sorry about that -- copy/pasting from the emailed report rather than typing the address myself. Now that I have the commands and order, I will look closer at some of those lists when additional reports come in. Thank you! -p > -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > Sent: Tuesday, December 10, 2024 1:41 PM > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Re: Enable delivery > > CAUTION: This email originated from outside of the organization. Do not click > links or open attachments unless you recognize the sender and know the > content is safe. > > > On 12/10/24 10:43, Hirayama, Pat wrote: > > Apologies, I should've said my "Mailman 3" server, not listserv. > > > > MTA logs do not show messages being sent to the member(s) in question, > even though other members are being sent messages. Nothing out of the > mailman server, and nothing received by our outbound Postfix MTAs. > > > > As for the CLI commands, I keep getting Attribute Error when I try them, like: > > > > /opt/mailman # mailman shell -l listname(a)mailman.tld > > Welcome to the GNU Mailman shell > > Use commit() to commit changes. > > Use abort() to discard changes since the last commit. > > Exit with ctrl+D does an implicit commit() but exit() does not. > > The variable 'm' is the listname(a)mailman.tld mailing list > >>>> from mailman.core.constants import system_preferences > >>>> mbr = m.members.get_member('user(a)domain.com.') > >>>> print(mbr.delivery_status) > > Traceback (most recent call last): > > File "<console>", line 1, in <module> > > AttributeError: 'NoneType' object has no attribute 'delivery_status' > > > Are you literally typing > > mbr = m.members.get_member('user(a)domain.com.') > > That needs to be an actual list member's email without a trailing > period. The fact that mbr is None means whatever you provided is not a > member of the listname(a)mailman.tld list. > > Curious that the member(s) in question are not amongst the recipients > delivered to the MTA even though > > >> when I run: > >> > >> mailman members --nomail any listname@listserv > >> > >> Nothing is returned. > > This should only happen if the members are digest members (are they) or > are directly addressed in To: or Cc: of the post. > > -- > 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://urldefense.com/v3/__https://lists.mailman3.org/mailman3/lists/mail > man- > users.mailman3.org/__;!!GuAItXPztq0!kBv3nt9E96ao_7FvkLnOsm_R9OWol1 > U4Lk0bnfCxTPiRuYdCv4jHRpx11tT3vx2cyFNW8ByfZlsvtwg$ > Archived at: > https://urldefense.com/v3/__https://lists.mailman3.org/archives/list/mailma > n- > users(a)mailman3.org/message/ET7NTZVDLCY6RBXHUIYRVTYQQX6SQ3KI/__; > !!GuAItXPztq0!kBv3nt9E96ao_7FvkLnOsm_R9OWol1U4Lk0bnfCxTPiRuYdCv4 > jHRpx11tT3vx2cyFNW8ByfwPhcXNc$ > > This message sent to phirayam(a)fredhutch.org

1 year, 10 months

[MM3-users] Re: Subscription request cannot be moderated: 404 Not Found

by Eric Broens

Hi Mark, Unfortunately the provided options didn't work out either: Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the ************* mailing list >>> ISubscriptionManager(m).confirm('4d6b4b11266c7332684c5a492eb3f92c531f761b') Traceback (most recent call last): File "<console>", line 1, in <module> File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.py", line 578, in confirm workflow.restore() File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", line 142, in restore raise LookupError(self.token) LookupError: 4d6b4b11266c7332684c5a492eb3f92c531f761b I noticed that the mail address was also listed as a non-member. After deleting it there, I could not accept the subscription either. Next, I have rejected the subscription and added it using the mass subscription option in the WebUI. I'll monitor if such cases will happen again. Thanks,Eric On Saturday, January 16, 2021, 06:05:19 PM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 1/16/21 7:49 AM, Eric Broens via Mailman-users wrote: > Hi Mark, > I can't find any log entry which indicate a problem with this subscription request. > The _request table does not contain a request for the specific mailinglist, but I am not sure if subscription requests are included in this table. It is unclear and confusing, but the requests are not in the _request table. See <https://gitlab.com/mailman/mailman/-/issues/768#note_415536043>. So this is normal. > The token is found in the pended table: > > +-----+------------------------------------------+---------------------+ > | id | token | expiration_date | > +-----+------------------------------------------+---------------------+ > | 115 | 4d6b4b11266c7332684c5a492eb3f92c531f761b | 2031-01-04 16:17:38 | > +-----+------------------------------------------+---------------------+ > > These are the relevant entries in the pendedkeyvalue table: > +------+--------------+-------------------------------------+-----------+ > | id | key | value | pended_id | > +------+--------------+-------------------------------------+-----------+ > | 1130 | type | subscription | 115 | > | 1131 | list_id | "********************" | 115 | > | 1132 | email | "***********************@*********" | 115 | > | 1133 | display_name | "" | 115 | > | 1134 | when | "2021-01-06T16:17:38" | 115 | > | 1135 | token_owner | "moderator" | 115 | > +------+--------------+-------------------------------------+-----------+ > > Can I workaround this problem for this specific subscriber by adding entries in the _request table, and if so what do I need to add? Adding to the _request table won't help. Try confirming by emailing listname-confirm+4d6b4b11266c7332684c5a492eb3f92c531f761b(a)list.domain You could also try confirming via mailman shell mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> ISubscriptionManager(m).confirm('4d6b4b11266c7332684c5a492eb3f92c531f761b') Traceback (most recent call last): File "<console>", line 1, in <module> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/app/subscriptions.py", line 570, in confirm raise LookupError LookupError In my case, I get the LookupError because the token doesn't exist, but I think it should work for you. -- 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/

5 years, 9 months

[MM3-users]Re: [Mailman-Announce] New Mailman 3 users list

by Barry Warsaw

On Apr 05, 2016, at 12:13 PM, Mark Sapiro wrote: >I'm happy to announce a new list for Mailman 3 users and others >interested in Mailman 3. Thanks Mark, this is *awesome*. -Barry

10 years, 6 months

Search results for query "sapiro"