Search results for "Postorius" - Mailman-users

Re: Migrating users from MM2 to MM3 on a new server?

by Mark Sapiro

On 11/25/24 9:31 AM, jkoral(a)luc.edu wrote: > Is there a way to copy users from the old MM2 server to a new MM3 server? Also, will it copy their password as well? The `mailman import21` command imports am MM 2.1 config.pck to a MM 3 list. Passwords are not imported. MM 3 does not use a list member's password. The web management UI (Postorius) and web archiver (HyperKitty) are Django applications and the user has to sign up for a Django account via the web UI. This account is then connected to the users list memberships via the user's email address. 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

1 year, 9 months

Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 6/12/19 2:54 AM, Michael Sage wrote: > Hi, > I came across this really useful guide (posted to the list earlier). It has all gone really well and mailman 3 is installed. However, I have an issue, when I go to login using Postorius, I get the login page when I enter my credentials the page appears to hang and eventually goes to a Error 500 page. This totally hangs all of the mailman 3 web interface (but not apache). I then have to reboot the server to even get back to the login page. This seems like something I've seen reported before, but I can't find it now. Is anything logged in the various Mailman, Django, Apache logs? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

Re: Twitter OAuth2

by Odhiambo Washington

On Fri, Dec 30, 2022 at 7:51 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/30/22 03:12, Odhiambo Washington wrote: > > On Thu, Dec 29, 2022 at 10:08 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> Try adding lists.kictanet.or.ke to Chosen sites along with > >> mm3-lists.kictanet.or.ke > > > > > > Even with that added, still same error. > > > Did you run `django-admin migrate` after uncommenting > 'allauth.socialaccount.providers.twitter', in your settings? > I always do whenever I change anything in settings. (venv) [mailman@gw ~/mm]$ /opt/mailman/mm/bin/django-admin migrate Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. (venv) [mailman@gw ~/mm]$ -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 8 months

Re: Uncaught runner exception: 'str' object has no attribute 'decode'

by Henrik Rasmussen

> The bottom line is at this point, <https://bugs.python.org/issue27321> > no longer affects Postorius, but it still affects message delivery. I > have opened <https://gitlab.com/mailman/mailman/issues/406> about > defending against that and also the UnicodeEncodeError you included in > your OP. Is there some kind of workaround, I can give my users or something that the list admins can do as a workaround? > > No. 'bin/mailman queue' is the Mailman 3 command. The Mailman 2 command > is 'bin/show_qfiles'. I much be in the wrong place because when I do a 'docker exec -it mailman-core bash' and do a 'mailman --help' I don't see a 'queue' argument. The only bin/mailman I have inside the mailman-core container is /usr/local/bin/mailman, which is the same command.

8 years, 11 months

Attachement processings questions

by Lars Schimmer

Hello, I got some questions about attachements in MM3 mailinglists and HyperKitty. Hard to find any real documentation about this in the huge load of links out there. Short: Debian Stretch system with MailMan 3.2.1-1 packages (Postorius 1.2.4, HyperKitty 1.2.2). In a mailinglist it seems some mails are not forwarded to a member, but is listed in archive in hyperkitty. That mail did include a PDF attachement, but HyperKitty does not list any attachement. All I found was "convert HTML to plaintext", but does this setting remove attachements? Is there any generel documentation about attachement processing in MM3? I would like this mailinglist to accept mails with attachements, send it to the members and archvie the attachments in HyperKitty, to. Any idea where to look? Thank you so far. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

6 years, 7 months

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

1 month, 3 weeks

Re: Verification Failed Error

by brian＠emwd.com

> In postorius(a)host.name.com, please change the host.name.com to match the > MM3_DOMAINS or whatever it is called in your MACROS. > Remember, it has to be a VALID hostname that you will be using for Mailman3 > lists. That, coupled with the IPs 172.19.199.x being in relay_from_hosts > should let the address to pass verification with Exim. The problem turned out to be not using a valid email account to send out admin related emails coupled with: verify = sender I did have a valid domain setup in the macros file and I had the mailman only IPs listed in the relay_from _hosts setting however that was not enough to get past the verification error. Once I commented out verify = sender, then the error message went away. I will be getting a valid mailbox setup today for posterius(a)host.name.com today so I can turn the above setting back on. Brian

7 years, 8 months

Re: Changing Mailman's "from" domain - redux

by Mark Sapiro

On 5/23/19 5:33 AM, roger(a)reasonal.com wrote: > (this is a posting directly into this web ui as mails to this list just vanish without a trace) Most of us have no problem posting by email. Can you provide more info. Even a time stamp would enable looking at the mail.log on mailman3.org. > Anyone? Anyone? With reference to the original mail here https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > It seems that the "From" domain field is set by Postorius, but I can't find anything in its documentation on how to change it. It is set in core. See my reply to the original mail (just sent) at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

Re: Upgrading from 3.1 to 3.2

by Mark Sapiro

On 07/17/2018 07:29 PM, Joe Steeve wrote: > > I have a 3.1 installation. I want to upgrade to 3.2. > > Has anyone attempted this? Any gotchas I need to be aware of? Yes. The gotcha is the web UI (postorius, hyperkitty, django-mailman3 and thus the WSGI process under which Django runs is Python 2.7 in Mailman 3.1 and associates and Python 3.5+ in Mailman 3.2 and associates. This migration can be tricky depending on your exact configuration. The most difficult situation I encountered was on a server that also supported MoinMoin which is a Python 2.7 WSGI process. Thus I needed both Python 2.7 and Python 3 WSGI support. I wound up leaving the Python 2.7 mod_wsgi in Apache and proxying the Mailman 3 URLs to gunicorn for Python 3 support. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 1 month

Re: Automatic migration from Mailman 2.1 (Debian buster) to Mailman 3 (Debian bookworm)

by Mark Sapiro

On 5/25/24 11:49 AM, Marc SCHAEFER wrote: > > This. Sorry, I mixed From: with Subject: and the content: > > Date: Sat, 25 May 2024 13:37:29 -0000 > From: postorius(a)lists2.alphanet.ch > To: schaefer@XXX > Subject: [example.com] Please Confirm Your E-mail Address > > Hello from example.com! > > You're receiving this e-mail because user Schaefer-XXX has given your e-mail > +address to register an account on example.com. > > To confirm this is correct, go to [ ... ] > > Thank you for using example.com! > example.com > > I guess it's the same SITE_ID setting in Django's DB: Yes, that's what it is. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

Mailman-users search results for query "Postorius"