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

[MM3-users] Re: How can i suppress sending moderation mail to all owners?

by Markus Grandpré

Thank you for you instant response. Best, Markus Am 8/11/25 um 12:46 schrieb Mark Sapiro: > On August 11, 2025 9:48:00 AM GMT, "Markus Grandpré" <markus.grandpre(a)uni-konstanz.de> wrote: >> >> How can I configure the list settings the way that emails intended for moderators are delivered only to them, and not to the owners/administrators of the list? > > You can't. You could modify code to do this either unconditionally or per list, but there is currently no configuration to do this. > L > -- Markus Grandpré (he/him) Universität Konstanz Kommunikations-, Informations- und Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur Sachgebiet Diensteadministration 78457 Konstanz Tel: +49 7531 88-4342D

4 weeks, 1 day

[MM3-users] Re: uncaught bounce messages

by David Bremner

Mark Sapiro <mark(a)msapiro.net> writes: > > Thank you. I tested that DSN with current flufl.bounce and it is > recognized as a temp failure for the reported address and that in turn > should just be ignored by Mailman's bounce runner and not reported as > unrecognized. > > What version of Mailman core is this and what version of flufl.bounce? > Sorry, meant to reply on list with the rest of the details, but got distracted by making dinner. So it sounds like the problem is old versions of flufl.bounce. This particular machine is running debian oldstable, so things are a bit out of date. mailman-core is 3.2.1 and flufl.bounce is 3.0. I'll look into upgrading at least flufl.bounce. thanks for your help, David

3 years, 10 months

[MM3-users] Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by David Newman

On 1/14/22 8:18 PM, Mark Sapiro wrote: >> https://${domain}/mailman3/lists/${short_listname}.${domain}/ > > FYI, ${short_listname}.${domain} is the same as ${list_id} Good to know. Thanks. > Also, ${domain} as the web site address may not be appropriate. For > example, on this list $domain is `mailman3.org`, but the base URL for > Postorius is `https://lists.mailman3.org/mailman3` and > `https://mailman3.org/mailman3` doesn't work. There is no replacement > for the web domain if it's different from the email domain for the same > reason that there are no web URLs in the default templates. Is there a variable for the base Postorius URL? Something like: https://${baseVarName}/lists/${list_id} Thanks dn

3 years, 7 months

[MM3-users] Re: mailman-web compress - Invalid template socialaccount/login_cancelled.html

by Odhiambo Washington

On Sat, Oct 28, 2023 at 9:46 PM Mark Sapiro <mark(a)msapiro.net> wrote: > This is definitely an issue with django_allauth 0.58. See > https://github.com/pennersr/django-allauth/issues/3503 and > https://github.com/pennersr/django-allauth/pull/3504 Thank you for following up on the fix. Consequent upon this django-allauth issue and the previous issue with psycopg2, how likely is it that new MM3 installations will suffer the effects? I am asking because I am doing my tests on a relatively vanilla system and just following the official documentation sin any deviations. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 10 months

[MM3-users] Re: Table 'mailmansuite.django_q_ormq' doesn't exist ("Delete this thread" -> 'HTTP-500 -> NoneType' object has no attribute 'all')

by Simon Liebold

Am 30.05.2017 um 02:06 schrieb Mark Sapiro: > Do you have django_q in INSTALLED_APPLICATIONS in your Django config and > do you have > > # > # Asynchronous tasks > # > Q_CLUSTER = { > 'timeout': 300, > 'save_limit': 100, > 'orm': 'default', > } > > in your Django config and are you running > > django-admin qcluster > > at startup? > > See > <https://mail.python.org/pipermail/mailman-developers/2017-May/026064.html>. Thanks Mark. After adding django_q, running python manage.py migrate and starting the runners it now works nicely: Successfully deleted 2 messages. Simon

8 years, 3 months

[MM3-users] Re: Postorius password resets

by Andrew Hodgson

Mark Sapiro wrote: >On 10/14/20 11:11 AM, Andrew Hodgson wrote: >> I am having an issue with our system where password resets are giving the users an email with a http://localhost:8000 URL. I have made sure settings in settings_local.py (and even settings.py) are as follows: >> >> POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.hodgsonfamily.org' >This is not relevant. Does it need resetting back to http://localhost:8000? >> However emails are still coming through with the wrong URL. >I'm not sure offhand, but it's either domains in Postorius or sites in the django admin UI. I've checked both and cannot see any errors (I just have the one site lists.hodgsonfamily.org) and nothing is empty which seems as though it needs filling in. Thanks. Andrew.

4 years, 10 months

[MM3-users] Re: How to identify the exact reason behind the shunting of the mails ?

by Shashikanth Komandoor

Dear Mark, FYI, I observed this issue with the postfix that receives the mails from the previous MTA and hands it over to the mailman. But I fixed at postfix by upgrading it to the version postfix 3. But still Mailman is not able to understand Hindi (Indian local language) in which language the display names of the email ids are there. So, now what to do at Mailman so that it can also understand local languages or any work around or other alternate solutions for these sort of cases. On Fri, Jun 18, 2021 at 4:04 PM Shashikanth Komandoor < shashikanth.komandoor(a)gmail.com> wrote: > Thank you Mark for your immediate response. > > The below are the tracebacks I could find in the mailman log. > > > > > > > > > > > > > > > > > *Jun 17 19:04:08 2021 (8642) Uncaught runner exception: sequence item 0: > expected str instance, Header foundJun 17 19:04:08 2021 (8642) Traceback > (most recent call last): File > "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, in > _one_iteration self._process_one_file(msg, msgdata) File > "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, in > _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File > "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line 37, in > _dispose process(mlist, msg, msgdata, pipeline) File > "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line 50, in > process handler.process(mlist, msg, msgdata) File > "/var/lib/mailman/mailman/src/mailman/handlers/avoid_duplicates.py", line > 59, in process addrs = getaddresses(msg.get_all(header, [])) File > "/usr/lib64/python3.6/email/utils.py", line 112, in getaddresses all = > COMMASPACE.join(fieldvalues)TypeError: sequence item 0: expected str > instance, Header foundJun 17 19:04:08 2021 (8642) SHUNTING: > 1623936848.367641+4753f8127953071ddcabfe828ebe72fcf04d0ae2* > > In the shunt file, I see something like this as below in CC while To is > good: > > > > > > > > > *Cc: > =?unknown-8bit?q?=22Support_Zimbra=22_=3Csupport-zimbra=40nic=2Ein=3E=2C?= =?unknown-8bit?b?ICLgpLbgpLDgpKYg4KSu4KS+4KSl4KWB4KSwIC0gU2hhcmFkIE1hdGh1ciIgPHN1cHBvcnQtdmFqcmFAc3VwcG9ydGdvdi5pbj4s?= =?unknown-8bit?b?ICLgpLDgpL7gpJzgpYfgpLYg4KS44KS/4KSC4KS5IC0gUmFqZXNoIFNpbmdoIiA8cmFqc0BuaWMuaW4+LA==?= =?unknown-8bit?b?ICJTYWJ5YXNhY2hpIENob3VkaHVyeSIgPHNhYnlhQG5pYy5pbj4sIG1haWxhZG1pbkBuaWMuaW4s?= =?unknown-8bit?b?ICJNUklUVU5KQVkgS1VNQVIiIDxta0BuaWMuaW4+LCAiQmhyaWd1IEt1bWFyIiA8YmhyaWd1QG5pYy5pbj4s?= =?unknown-8bit?b?ICJPbSBQcmFrYXNoIiA8b3AubmhxQG5pYy5pbj4sICJIYXJpaGFyYW4gTSIgPGhhcmloYXJhbi5tQGdvdi5pbj4s?= =?unknown-8bit?b?ICJQaGlzaGluZyBQaGlzaGluZyIgPHBoaXNoaW5nQG5pYy5pbj4sICJpbmNpZGVudCIgPGluY2lkZW50QG5pYy5pbj4s?= =?unknown-8bit?b?ICJNYW5hdiBSYWtoZWphIiA8bWFuYXYucmFraGVqYUBuaWMuaW4+?=* > > Also, I came to know that two of the recipients in CC block have their > mail ID display name in their local language. While I am not sure, I doubt > if it could be the issue of getting shunted. > > Please confirm and suggest any solution. > > > > On Thu, Jun 17, 2021 at 8:48 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 6/17/21 6:56 AM, Shashikanth Komandoor wrote: >> > >> > Is there any chance to find out the reason for shunting of the >> > mails through any means ? >> > >> >> >> Look in Mailman's var/logs/mailman.log for the tracebacks associated >> with the shunted messages. >> >> -- >> 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, 2 months

[MM3-users] Re: Upgrade

by Darren Smith

Further debugging - using the python3.6 from the virtual environment where mailman is running, it looks like it is trying to use utf-8: >>> import locale >>> import codecs >>> print(locale.getpreferredencoding()) UTF-8 >>> print(codecs.lookup(locale.getpreferredencoding()).name) utf-8 >>> Thoughts? On Mon, Apr 16, 2018 at 11:29 AM, Darren Smith <silas.crutherton(a)gmail.com> wrote: > By the way, in reading the URL in the error, I attempted to set the LANG > and LC_ALL to en_US.utf8 (as was found in the error) but it still does not > work. > > > > On Mon, Apr 16, 2018 at 11:26 AM, Darren Smith <silas.crutherton(a)gmail.com > > wrote: > >> Nice...spoke too soon. >> >> Mailman info works, but when attempting to start mailman I'm now getting >> this: >> >> Traceback (most recent call last): >> File "/opt/mailman3/conda/bin/mailman", line 11, in <module> >> sys.exit(main()) >> File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", >> line 722, in __call__ >> return self.main(*args, **kwargs) >> File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", >> line 676, in main >> _verify_python3_env() >> File "/opt/mailman3/conda/lib/python3.6/site-packages/click/_unicodefun.py", >> line 118, in _verify_python3_env >> 'for mitigation steps.' + extra) >> RuntimeError: Click will abort further execution because Python 3 was >> configured to use ASCII as encoding for the environment. Consult >> http://click.pocoo.org/python3/for mitigation steps. >> >> This system lists a couple of UTF-8 supporting locales that >> you can pick from. The following suitable locales where >> discovered: aa_DJ.utf8, aa_ER.utf8, aa_ET.utf8, (followed by a bijillion >> others) >> >> -Darren >> >> On Mon, Apr 16, 2018 at 11:25 AM, Darren Smith < >> silas.crutherton(a)gmail.com> wrote: >> >>> Boy howdy did that work... >>> >>> Thanks! >>> >>> >>> On Mon, Apr 16, 2018 at 11:22 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >>> >>>> On 04/16/2018 10:12 AM, Darren Smith wrote: >>>> >>>> > "/opt/mailman3/conda/lib/python3.6/site-packages/sqlalchemy/ >>>> engine/strategies.py", >>>> > line 160, in create >>>> > engineclass.__name__)) >>>> > TypeError: Invalid argument(s) 'pool_pre_ping' sent to >>>> create_engine(), >>>> > using configuration PGDialect_psycopg2/QueuePool/Engine. Please >>>> check that >>>> > the keyword arguments are appropriate for this combination of >>>> components." >>>> > >>>> > Anyone able to point me where to go to look for a solution for this? >>>> >>>> >>>> You need to update SQLAlchemy to >= 1.2 for this, but there is another >>>> issue that requires at least 1.2.3 (current is 1.2.6) >>>> >>>> >>>> -- >>>> 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, 4 months

[MM3-users] Re: cc'd e-mail addresses rewritten with @invalid.domain

by Williams, Peter B

Hi Mark, Thanks for the help with this! Other list members will also see the e-mail as coming from user(a)invalid.domain<mailto:user@invalid.domain>. I will continue testing the other scenarios and will reply back as soon as possible. Thanks again for the help with this and have a nice day! Peter On Mon, Sep 21, 2020 at 9:00 PM Mark Sapiro <mark(a)msapiro.net> wrote: On 9/21/20 10:49 AM, peterbw(a)gmail.com<mailto:peterbw@gmail.com> wrote: > Hi, > > We've recently noticed an issue where users who are cc'd in a message where a mailing list is also within the cc list are getting rewritten a user(a)invalid.domain. > > This issue looks like it may be related to Outlook and how user names are displayed specifically. Here is an example: > > To: test_user(a)gmail.com<mailto:test_user@gmail.com> > cc: listserv(a)lists.test.org<mailto:listserv@lists.test.org>; Williams, Peter; > > "Williams, Peter" maps to a user e-mail in the Outlook Global Address book. When the message is sent the list will send the message with the first name and last name separated, for example the message will appear: > > to: test_user(a)gmail.com<mailto:test_user@gmail.com> > cc: listserv(a)lists.test.org<mailto:listserv@lists.test.org>, Williams(a)invalid.domain, Peter(a)invalid.domain Because apparently Outlook is sending the message with the literal > Cc: listserv(a)lists.test.org<mailto:listserv@lists.test.org>; Williams, Peter; instead of something like > Cc: listserv(a)lists.test.org<mailto:listserv@lists.test.org>, "Williams, Peter" <peters_real_address(a)example.com<mailto:peters_real_address@example.com>> Then some MTA in the chain is seeing the unqualified addresses Williams and Peter and appending its own local domain. > This only seems to happen with users who are cc'd who are also members of the list that is being cc'd. For example in the scenario above my e-mail that is cc'd is also a member of listserv(a)lists.test.org<mailto:listserv@lists.test.org>. In this case, where do you see this? i.e., do other list members see it in the message they receive from the list? I don't know why that would be. I'm certain that Mailman is not involved in this and the Williams(a)invalid.domain and Peter(a)invalid.domain addresses are in the Cc: as received by Mailman. > This issue does not occur if the user e-mail address is listed before the mailing list in the cc field. So for example, if the cc in the scenario above contained Williams, Peter; listserv(a)lists.test.org<mailto:listserv@lists.test.org>; it would route properly. Again, I think this is Outlook. What's in the Cc: of the mail that test_user(a)gmail.com<mailto:test_user@gmail.com> receives directly? What happens if you send mail in this way with To: test_user(a)gmail.com<mailto:test_user@gmail.com> cc: other_user(a)gmail.com<mailto:other_user@gmail.com>; Williams, Peter; Again, what's in the Cc: of the mail that test_user(a)gmail.com<mailto:test_user@gmail.com> and other_user(a)gmail.com<mailto:other_user@gmail.com> receive? Also, please see <https://wiki.list.org/DOC/Mailman%20is%20not%20Listserv>. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@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<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 11 months

[MM3-users] Re: Configuring the List-Archive and Archived-At headers

by Ralph Seichter

* Mark Sapiro: > It has nothing to do with the ssl certificate. In retrospect, that possibility seems unlikely indeed. Note to self: Don't write to public mailing lists at 01:43 local time... ;-) > What that means is the lists.example.com domain must first be known to > Django at <https://lists.example.com/admin/sites/site/ Ah, that's what I was missing, thank you. The headers in my test installation are now generated with the correct URLs. Could I suggest extending the documentation regarding web hosts? https://mailman.readthedocs.io/en/latest/src/mailman/model/docs/domains.html briefly mentions "Domains are how Mailman interacts with email host names and web host names", but as far as I can tell that's pretty much it. -Ralph

6 years, 5 months

Search results for query "sapiro"