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

[MM3-users] KeyError: 'get_requests_count' after an upgrade

by Guillermo Hernandez (Oldno7)

I've just upgrade mailman 3 installation following Mr. Sapiro advice: did a pip install --upgrade django-mailman3 hyperkitty mailman mailmanclient mailman-hyperkitty postorius I did a "python3 manage.py migrate" after, too. And all seemed to run well. All the lists showed in postorius via web, but when I try to accesss into one of them the browser shows an error. In the log you can see: *-*-*-*-*-*-* Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'get_requests_count' ... (And after all the traceback lines) AttributeError: 'MailingList' object has no attribute 'get_requests_count' *-*-*-*-*-*-*-* The lists seem to be distributing messeages well.. but I cannot acces via web administration (django/postorius) Can anyone point me in the right direction to solve this, please?

5 years, 8 months

[MM3-users] Re: PGP - S/MIME signed messages

by Stephen J. Turnbull

Mark Sapiro writes: > On 7/28/25 13:29, Peter Adebahr via Mailman-users wrote: > > we are receiving a few PGP-signed posts as a S/MIME attachment. Some > > final recipients check these, and as mailman3 does not munge them - the > > original mail is signed, not mailman3's final posts - those get rejected. Besides Mark's suggestions, technically, PGP-signed and S/MIME are two different protocols. If you try to verify one with software expecting the other, it will fail. This seems unlikely (there would be reports of direct mail failing verification), but if Mark's suggestions don't help, you could verify that all the users are on the same page as to what signature protocols are being used. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 year, 2 months

[MM3-users] Re: Triaging message non-receipt

by Eric Abrahamsen

On 07/13/18 12:56 PM, Mark Sapiro wrote: > On July 13, 2018 12:11:13 PM PDT, Eric Abrahamsen <eric(a)ericabrahamsen.net> wrote: > >>All messages are correctly archived in hyperkitty. smtp.log always >>shows >>"for 5 recips", even for the messages that the two users aren't >>getting. >>These two users only ever miss messages sent by the other. >> > .... >> >>Is there any way to get a better sense of where things are going wrong? >>Turn up the logging verbosity? Send test messages? Get more >>diagnostics? > > > Mailman has delivered the messages to the outgoing MTA and can't tell > you any more. Mailman 3 bounce processing is broken. > > Look in the MTA logs for more. Okay, I'll see what postfix has to tell me. I appreciate the tip on bounce processing. Thanks, Eric

8 years, 3 months

[MM3-users] Re: Can disabled users enable themself?

by Stephen J. Turnbull

Mark Sapiro writes: > On 7/6/26 6:33 AM, Flo via Mailman-users wrote: > > > > How can I find these settings in Postorius? There is only a user's > > language and a list's language. > > > You have to be logged in as the user. Then you can go to > https://example.com/mailman3/accounts/mailmansettings/ and see Global > Mailman preferences, Address-based preferences and List-based preferences. To be precise, the list owner can see (and I believe set) the *user's* *subscription* preference. They can't see the global and address preferences. Do you know if the superuser can access and mutate the latter? I couldn't figure it out from a quick look at the templates. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

3 months, 1 week

[MM3-users] Re: How to Increase outgoing mail volume for Mailman 3

by Mark Dadgar

On Nov 10, 2020, at 1:18 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> >> The downside to this is that you lose automated bounce processing, of course. > > > You don't lose bounce processing. It just becomes a bit less reliable. > The VERPed envelope sender says exactly what address the message was > sent to. Without this information, Mailman (actually flufl.bounce > <https://fluflbounce.readthedocs.io/en/latest/README.html>) has to parse > the returned bounce message to determine the bouncing address. There are > many MTAs that do not send RFC 1894 compliant DSNs and we have several > heuristic recognizers to try to parse these, but they can fail. Brian specified: verp_personalized_deliveries: no Doesn’t that default back to regular mass delivery, as opposed to individualized VERPed envelopes, which mandates individual deliveries? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 11 months

[MM3-users] Re: Time Zone Issue in Postorius

by Henrik Rasmussen

> -----Oprindelig meddelelse----- > Fra: Mark Sapiro <mark(a)msapiro.net> > Sendt: 8. februar 2022 07:48 > Til: mailman-users(a)mailman3.org > Emne: [MM3-users] Re: Time Zone Issue in Postorius > > It should be TIME_ZONE = 'UTC' > > Times passed from Mailman core are naive times, I.e. they don't have > time zone info, but they are in UTC. Thus for Django to get the correct > time with time zone you need USE_TZ = True (without that, Django will > throw an exception about naive times) and the TIME_ZONE to apply is UTC. As https://stackoverflow.com/questions/29311354/how-to-set-the-timezone-in-dja… seems to say otherwise ("You can use TIME_ZONE = 'Europe/Istanbul'"), to make sure, am I right to understand it as for Mailman, Danish time should be stated as "TIME_ZONE = 'UTC+1' " with use of "USE_TZ = True"? /Henrik Rasmussen

4 years, 8 months

[MM3-users] Re: mailman-full question

by Dave McGuire

On 9/25/22 13:34, Mark Sapiro wrote: >> - to configure the db in venv i would use mailman-web migrate - this >> works fine - but mailman-full install does not seem to include >> mailman-web >> or mailman3-web - the mailman info cmd works fine - do i need to >> also install mailman-web? i had thought the mailman-full included all >> components > > I'm not sure what it's called in the Debian/Ubuntu mailman-full package, > but the `mailman-web` command installed by `pip install mailman-web` is > the Django admin command, possibly called `django-admin` or `manage.py` > in the mailman-full package. In my (old) Ubuntu package installation, which I got locked into before I realized how awful that was going to be, mailman-web should be symlinked to /usr/share/mailman3-web/manage.py but isn't. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

4 years

[MM3-users] Re: Do i need a mailman-hyperkitty.cfg file?

by Bill Oliver

On Mon, 2024-10-28 at 21:08 -0700, Mark Sapiro wrote: > [ > [snip] > es. See the last part of the section at > https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail… > > where it says in part `And, create the > /etc/mailman3/mailman-hyperkitty.cfg file containing these settings: > ...` > > > I found a template here: > > > > https://gitlab.com/mailman/mailman-hyperkitty/blob/master/mailman- > > hyperkitty.cfg > > > > > > Do I need to copy and paste that in my installation? > > > It, or something as mentioned in the above doc needs to be at the > location defined in the `configuration:` setting in the > `[archiver.hyperkitty]` section of mailman.cfg > > -- Hah! If it were a snake it woulda bit me. I can't believe I scanned right over it. Thanks! billo

1 year, 11 months

[MM3-users] Re: Apache+mod_wsgi issue

by Guillermo Hernandez (Oldno7)

El 26/12/22 a las 23:57, Mark Sapiro escribió: > ... >> I don't want to put more noise in the list. But I'm confused because >> I always updated via pip the apache mod_wsgi thinking is was needed >> for my configuration. If it is not, I will stop updating it. > > Based on the above you ARE using Apache mod_wsgi and if you are still > also running uwsgi as > > /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini & > > that is unnecessary. It clarifies a pair of things. Thanks a lot. I'll try deactivating that in one of my servers (the "quieter" one) and see how it goes. Again, thanks for your kind support. -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

3 years, 9 months

[MM3-users] Re: Can't subscribe on new site/domain

by Flo

On 10/10/25 17:46, Mark Sapiro wrote: > On 10/10/25 1:37 AM, Flo via Mailman-users wrote: >> >> The difference I am talking about is that lists.example1.com/ >> postorius/ lists shows only its mailing lists while >> lists.example2.com/postorius/ lists shows all mailing lists on the >> server (ie. also mailing lists of example1.com) > > What is your Postorius version? Whether Postorius displays all lists or > only those matching the current host is controlled by the FILTER_VHOST > setting. There was an issue with this prior to Postorius 1.3.3. See > https://gitlab.com/mailman/postorius/-/issues/394 > Postorius Version 1.3.13, /usr/share/mailman3-web/settings.py: FILTER_VHOST = True , however, this is set for the whole server and not for single domains/sites, right? In my case mail_host is the same as web_host so I shouldn't be touched by that problem anyway. Flo

1 year

Search results for query "sapiro"