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

[MM3-users] Re: Apple Mail encoding again

by Rainer Herbst

Dear all, my first post was to optimistic - the user tested some other combinations and when he tries to send a signed HTML mail, the server again refuses to accept it with "Diagnostic-Code: smtp; 501 Message has defects". The user suggested that the problem is caused by a line containing only "-- " somewhere in the text, but I can not confirm this. Please find enclosed the refused mail (anonymized). Regards Rainer On Mi, 20 Apr 2022 10:51:38 +0200 Rainer Herbst <rainer.herbst(a)aip.de> wrote: > Dear all, > > as the original poster, I have asked the user to send a test mail >through our mailman3 system (docker image > maxking/mailman-core:0.4.2) and the mail passed. > > The user is now on Apple Mail 16, maybe that does the trick. Please >find enclosed the anonymizied mail source. > > Best regards and thanks for caring even if the problems seems to >affect only a small number of users! > Rainer > > On Fr, 15 Apr 2022 09:03:41 -0700 > Mark Sapiro <mark(a)msapiro.net> wrote: >> On 4/14/22 21:33, Stephen J. Turnbull wrote: >>> >>> Whether we *want* to do that depends on how much trouble that causes >>> for our main constituency (list and site admins), and whether we can >>> provide discoverable documentation of the problem. My take is that >>> this seems to be an extremely rare problem, and at least some MUAs >>>are >>> able to read the message, so we should let it through. >> >>First, we are not silently dropping this message. We are rejecting it >>at LMTP time so the sender should be notified. >> >> Then the broader question is should we accept all messages with >>defects, almost all of which are spam, or only certain defects and >>which ones. >> >> I note that Apple has now released Mail 16 so maybe they've fixed >>this. My macs are still on Big Sur, so I can't test this. >> >> >> -- >> 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/ >> > > Viele Grüße > > Rainer Herbst > Leiter IT-Service > Phone: +49 331 7499-257 > e-mail: rainer.herbst(a)aip.de > https://www.aip.de > > ----------------------------------------------------------------------------------------------- > Leibniz-Institut für Astrophysik Potsdam (AIP) > An der Sternwarte 16, 14482 Potsdam > > Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach > Stiftung bürgerlichen Rechts > Stiftungsverzeichnis Brandenburg: 26 742-00/7026 > ----------------------------------------------------------------------------------------------- Viele Grüße Rainer Herbst Leiter IT-Service Phone: +49 331 7499-257 e-mail: rainer.herbst(a)aip.de https://www.aip.de ----------------------------------------------------------------------------------------------- Leibniz-Institut für Astrophysik Potsdam (AIP) An der Sternwarte 16, 14482 Potsdam Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach Stiftung bürgerlichen Rechts Stiftungsverzeichnis Brandenburg: 26 742-00/7026 -----------------------------------------------------------------------------------------------

4 years, 3 months

[MM3-users] Re: Change the default value for the General Archive Policy

by Markus Grandpré

Dear Mr Sapiro, many thanks for your reply. When I create a mailing list without an archive, I’ve noticed that the default value under "Settings > Archiving > Archive policy" is always set to "Public archives". I was wondering if it's possible to change the default to "Do not archive this list" instead. Additionally, in an earlier email, you mentioned that a more convenient way to set default values would be introduced in an upcoming version. Could you please let me know the current status of that development? Many thanks in advance. Best regards, Markus Am 6/23/25 um 19:53 schrieb Mark Sapiro: > On 6/23/25 08:03, Markus Grandpré wrote: >> Dear list, >> >> currently, when I create a new mailing list with MM3 the value for "Archive policy" is always set to "Public >> archives". I'd like to change the default value for "Archive policy" to "Do not archive this list". How can I do this? >> In Debian 12 I find in </usr/lib/python3/dist-packages/postorius/forms/list_forms.py>: > ... >> but have no idea how to change the settings here. Your help is very appreciated. > Are you creating the list in Postorius. If so, you have a choice for list style. Currently those choices are: > ``` > Announce only mailing list style. > Ordinary discussion mailing list style. > Discussion mailing list style with private archives. > ``` > There is currently no style for a list without archives, but you can implement one. See the thread at https:// > lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/Q6QVDWCY… for hints on how to > do this with a plugin. > > Alternatively, you can do it with a patch like: > ``` > --- a/src/mailman/styles/default.py > +++ b/src/mailman/styles/default.py > @@ -18,6 +18,7 @@ > """Application of list styles to new and existing lists.""" > > from mailman.core.i18n import _ > +from mailman.interfaces.archiver import ArchivePolicy > from mailman.interfaces.styles import IStyle > from mailman.styles.base import ( > Announcement, > @@ -91,3 +92,25 @@ class PrivateDefaultStyle( > Private.apply(self, mailing_list) > Discussion.apply(self, mailing_list) > Moderation.apply(self, mailing_list) > + > + > +@public > +@implementer(IStyle) > +class PublicNoArchiveStyle( > + > + Identity, BasicOperation, Bounces, Public, Discussion, Moderation): > + > + """The legacy default style with no archives.""" > + > + name = 'legacy-default-no-archive' > + description = _('Ordinary discussion mailing list style with no archive.') > + > + def apply(self, mailing_list): > + """See `IStyle`.""" > + Identity.apply(self, mailing_list) > + BasicOperation.apply(self, mailing_list) > + Bounces.apply(self, mailing_list) > + Public.apply(self, mailing_list) > + Discussion.apply(self, mailing_list) > + Moderation.apply(self, mailing_list) > + mailing_list.archive_policy = ArchivePolicy.never > ``` > If you are creating lists from the command line `mailman create`, there is a --style-name option to specify the style. > -- Markus Grandpré Universität Konstanz Kommunikations-, Informations- und Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur Sachgebiet Diensteadministration Tel: ++49 7531 88 4342

1 year, 1 month

[MM3-users] Re: hyperkitty failed to create a thread

by Danil Smirnov

Hi guys, I've updated my containers (though can't confirm for sure the fix is in there; but I see that the 'latest' tag of 'mailman-web' has been rebuilt in the last night). Could you advise how to rebuild the failing threads please? I've done index update with 'django-admin update_index' command but it seems irrelevant to the issue, I still have all those messages separated: https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/2019/2/ Thank you very much! Danil сб, 16 февр. 2019 г. в 18:46, Abhilash Raj <maxking(a)asynchronous.in>: > > > On Thu, Feb 14, 2019, at 11:51 AM, Danil Smirnov wrote: > > Thank you very much for the quick fix, Mark and Abhilash! > > > > Abhilash, could you include the fix into the "latest" version of > > mailman-web container please? > > They are nightly builds, if the fix was merged and the CI went through, > they should > already be in there. > > > > > Btw I wasn't able to find a changelog of Mailman docker images anywhere > and > > 'Releases' page in Github is quite outdated too... Is there any other > > place I should check? > > I have admittedly been too busy to write release notes, but the recent > releases > have seen not too much changes other than version bumps for the included > Mailman packages. > > > > > Danil > > > > вт, 12 февр. 2019 г., 4:06 Mark Sapiro <mark(a)msapiro.net>: > > > > > On 2/11/19 9:47 AM, Danil Smirnov wrote: > > > > > > > > What could be a reason of HyperKitty failing to create a thread from > > > > chained emails? > > > > > > > > For example, see "RECENTLY ACTIVE DISCUSSIONS" on page > > > > https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/ > > > > > > > > "Openvpn and Network mapping" discussion displayed as five threads > > > instead > > > > of only one... > > > > > > > > Any ideas how to improve HyperKitty ability to detect threaded > messages? > > > > > > > > > Thanks for the report. > > > > > > The MR at <https://gitlab.com/mailman/hyperkitty/merge_requests/125> > > > will fix this. > > > > > > -- > > > 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/ > > > > -- > thanks, > Abhilash Raj (maxking) >

7 years, 6 months

[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

[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, 3 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/

8 years, 10 months

[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

[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, 5 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, 6 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, 4 months

Search results for query "sapiro"