Search results for "Postorius" - Mailman-users

Website 404 error

by Stephen J. Turnbull

peter(a)pi4cc.nl writes: > I'm running Debian 12 with the latest version and installed > mailman3 via apt install-mailman3-full. Assuming you have done no configuration "by hand", this is almost certainly a Debian issue. You should report it to them. > When I first access the website domain.nl/mailman3, it's redirected > to domain.nl/mailman/postorius/lists/, resulting in a 404 error The initial redirect is done by your webserver, not by Mailman. I have no good idea why the result changes if you do it twice.[1] In Apache, this is likely in a file in /etc/apache2/sites-available/. In nginx, similarly /etc/nginx/sites-available/. The file's name is likely to be either something like "debian-default.conf" or "mailman3.conf" for either of those popular webservers. Footnotes: [1] The only thing I can think of is that in one case you accessed domain.nl/mailman3, and in the other domain.nl/mailman3/ (difference is the trailing "/"), and there are separate redirects for the two URLs for some reason. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

8 months, 3 weeks

Re: Editing templates from settings

by Abhilash Raj

On Tue, Sep 3, 2019, at 9:18 PM, paul(a)arenson.org wrote: > Hello again. > > Gradually coming along thanks to the help of other members. > > One thing I want to do is edit my headers or footers to have key info > about my site. But it seems even if I skip spaces, when a message is > received the spaces disappear. Likewise, is there any way to add basic > formatting like BOLD? > > For example, if I make a footer like this... > > Skipping a space here > __/__/__/__/__/_/__/__/__/__/ > Our List > _/__/__/__/__/_/__/__/__/__/ > Skipping a space here > > > ...the centering disappears, as do the > skipped spaces, meaning the message after a header or before a footer > looks cluttered, > > Is there a fix? Not yet, there is an open issue about it[1]. [1]: https://gitlab.com/mailman/postorius/issues/301 > > Thank you. > _______________________________________________ > 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)

6 years, 8 months

Re: Weird response to postings after subscriptions and accounts

by Mark Sapiro

On 9/17/19 6:39 PM, paul(a)arenson.org wrote: > > A) Thoughts before summarizing tests. > 1) I had originally thought of making archives only for subscribers to give them the benefit of posting from the archives directly and being able to find stuff more like a forum (email is always hard to follow). Anyone logged in to an account can post from Hyperkitty. Their post is treated the same as if they posted by email. > 2) But in retrospect it seems people can get an idea what the list is about from free access. So that is now what I have. OK > 3) On the other hand, it is a bit confusing that a non member can post from the archives without realizing that they need to register, with my settings I can moderate and decide if I want to add him or her to the list based on whether that is spam or not. So ok. A non-member is a non-member. A post from a non-member is handled according to "Default action to take when a non-member posts to the list" unless that non-member has a Moderation action other than List Default. > B) THE TESTS > I was testing too many variables so, to simplify things, I made my settings as follows > > 1) Subscription—> Confirm > > 2) Message Acceptance—> Default processing (so only members may post) > > 3) Testing Procesure > I added people three ways—> To do that I created 3 unique addresses to see if they can send and receive by email. > > > 3a) subscribe without creating an account—from here (bottom) https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > > 3b) Subscription / Unsubscription from same page, navigate to Login and again navigate to signup > Comment 1: Confusing because even after creating an account, they are not subscribed to the list. Maybe it makes sense if a person has many lists, but I only have this one. It does not say clearly that one has to subscribe after creating an account. I understand it's not totally explicit, but it says "To subscribe or unsubscribe from this list, please log in first. If you have not previously logged in, you may need to set up an account with the appropriate email address." To me the implication is once you have created an account, you have to come back, log in and subscribe. What do you want it to say? > Comment 2: The other thing is that it does not show my domain but that of mailman3.emwd.com <http://mailman3.emwd.com/>. Talk to Brian (emwd) > 3c) Mass Subscribe by me. Which is what I intend for my 600 users from another list company. > Comment This worked fine. > > > C) Summary > 1) I have been thinking of having an account as a good way to get users used to using the archives as a way to confirm current and past topics (as opposed to keeping track by email. But it seems I need to tell them to BOTH subscribe AND create an account. Am I thinking about it the wrong way? That's correct. They need an account and they need to subscribe that account to the list. > 2) When a person wants to unsubscribe, they go to discuss-request(a)list.tokyoprogressive.org <mailto:discuss-request@list.tokyoprogressive.org> with subject bline help. > > a) Isn’t there a better way to unsubscribe by email? email to discuss-leave(a)list.tokyoprogressive.org (or discuss-unsubscribe(a)list.tokyoprogressive.org) Or you can login, go to https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… and click the big red unsubscribe button. > b) And how about a way to remove their account itself? Log in and click the dropdown at the upper right, select Account and click the Delete Account tab or go directly to https://list.tokyoprogressive.org/user-profile/ and click the Delete Account tab or go directly to https://list.tokyoprogressive.org/user-profile/delete -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

Re: Change Member's Address

by Stephen J. Turnbull

Dennis Putnam via Mailman-users writes: > I can't seem to confirm the superuser's email address. Find the address in both the account_emailaddresses table and the addresses table. I'm interested to see the full record for both (you can obscure the email and display_name for this purpose). This is in the interest of figuring out why you are inflooping in the confirmation process. Confirmation you can do with a single SQL update. Find the address in the account_emailaddresses table and update the verified attribute to t. I think that's enough to allow you to log in. If not you should do the same for that address in the addresses table. However, in the addresses table you need to fill the verified field with a timestamp. Not sure how that works in SQL, try copying the value of the registered field. I don't know why you're inflooping though. It's possible that you're verified in one table but not the other, confusing Postorius. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

3 months, 3 weeks

Re: REST API authorization failed

by Mark Sapiro

On 1/8/22 10:40 AM, Axel Rau wrote: > Hi all, > > I’m going to do a mailman2->3 migration in a FreeBSD jail. > I installed mailman3 in an venv from pypi, along with nginx, uwsgi and exim. > The above error happens when I try to open the base url of my server with a browser > (is redirected to postorius/lists/) > (no errors on admin/ and hyperkitty urls) > > Same passwords and users in mailman.cfg: > > [webservice] > hostname: localhost > port: 8001 > use_https: no > admin_user: restadmin > admin_pass: ??? > > and in settings.py: > > MAILMAN_REST_API_URL = 'http://localhost:8001' > MAILMAN_REST_API_USER = 'restadmin' > MAILMAN_REST_API_PASS = ??? > > Its a long password, created as secret key by manage.py Is the password unquoted in mailman.cfg as admin_pass: ??? and quoted in settings.py as MAILMAN_REST_API_PASS = '???' Does the `mailman info` command report what you think for REST credentials? To you get an appropriate JSON response from wget -O- --user restadmin --password ??? http://localhost:8001/3.1/lists -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

mm3 floods syslog

by Wolfgang Bock

Dear friends, I got another problem: mailman floods my syslog. I deleted a domain/webdomain (further mentioned as deleted.org) in postorius, django web. No entries are now in /var/lib/mailman3/data/postfix_domains or postfix_lmtp or /var/lib/mailman3/lists. Here an extract of my syslog (anonymized): Oct 31 10:49:02 myserver mailman3[1284]: Oct 31 10:49:02 2021 (1284) Certificate did not match expected hostname: localhost. Certificate: {'subject': ((('commonName', 'deleteted.org'),),), 'issuer': ((('countryName', 'US'),), (('or ganizationName', "Let's Encrypt"),), (('commonName', 'R3'),)), 'version': 3, 'serialNumber': '0326A733CA7B16D13C830EE707EA614E25F9', 'notBefore': 'Oct 30 20:21:08 2021 GMT', 'notAfter': 'Jan 28 20:21:07 2022 GMT', 'subjectAltName': (('DN S', 'deleteted.org'), ('DNS', 'lists.deleteted.org'), ('DNS', 'mail.deleteted.org'), ('DNS', 'ns.deleteted.org'), ('DNS', 'www.deleteted.org')), 'OCSP': ('http://r3.o.lencr.org',), 'caIssuers': ('http:/ /r3.i.lencr.org/',)} This appears nonstop. I now stopped the cronjob fort he moment: "[ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.minutely /usr/share/mailman3-web/manage.py runjobs minutely" and others Does mailman or django store any information about domains in another place/file. If yes, how this can be deleted?? Thanks for your reply in advance. Regards Wolfgang

4 years, 6 months

Re: mailman3-web language preference and translation settings

by Mark Sapiro

On 12/6/23 15:54, Nils wrote: > Thanks for your help, Mark. I've already tried that and it gave me this > message: > > # sudo -u www-data python3 /usr/bin/django-admin compilemessages > --pythonpath /usr/share/mailman3-web --settings settings > CommandError: This script should be run from the Django Git checkout or > your project or app tree, or with the settings module specified. > > I'm working on ubuntu and I don't have (venv)$ The other commands (migrate, collectstatic and compress) worked fine. Kind regards I don't know why this fails like that, particularly since the same thing works for migrate, collectstatic and compress. The only thing I can think of is you may need to cd to the directory containing django/ django_mailman3/ postorius/ and /hyperkitty before doing the above. This may be something like /usr/lib/python3.x/site-packages. If that doesn't work, since I think you are using the Debian/Ubuntu package, I suggest you try Debian for help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

Re: Can't subscribe on new site/domain

by Mark Sapiro

On 10/9/25 5:02 AM, Flo via Mailman-users wrote: > Hi, > > I added a new site in Django: lists.example.com > > Usually I click on 'view site' and I can add a Domain in Postorios. In > this case I get an error message and I need to add a Domain in Django. > Then I can go to 'view site'. > > I can create a mailing list there. However when I send an email to be > subscribed, I get the following in mailman.log (and nothing else happens): > > > Oct 09 13:46:24 2025 (110452) deque: do_confirm_verify > Traceback (most recent call last): ... > File "/usr/lib/python3/dist-packages/mailman/model/domain.py", line > 177, in __getitem__ > raise KeyError(mail_host) > KeyError: 'lists.example.com' It appears you don't have a domain in Mailman core with mail_host = 'lists.example.com'. Do you see one in Postorius' domains view? If not, perhaps you need to add it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 3 weeks

Re: Importing Mailman 2 Lists apart from Django

by Andrew Hodgson

Brian Carpenter wrote: >Hello Mailman Users, >Are there instructions on importing a Mailman 2 list into a Mailman 3 core installation only? Does the import21 script not need Django/Postorius/Hyperkitty? >It seems Django is required to import archives I guess because of the use of Hyperkitty. How about importing archives without having a Django installation? Is that what the prototype archiver for? Its an interesting question, my understanding on this is that Mailman Core and Hyperkitty are separate projects and so if you are building a replacement to Hyperkitty you would need to deal with how messages get posted to it (currently Mailman sends messages to Hyperkitty when they get posted) and also how archives can be imported. I may be wrong on this but if you were creating a new archiver you would need to factor this in, you also would have the choice to use the current schema that Hyperkitty uses or your own database schema elsewhere. If you use the Hyperkitty schema I guess you could continue to use it's import process, but that may limit your design decisions for the software you are writing. Andrew.

6 years

Re: Issues encountered while upgrading to 3.3.7

by Mark Sapiro

On 12/5/22 10:02, Odhiambo Washington wrote: > On Mon, Dec 5, 2022 at 8:54 PM Mark Sapiro <mark(a)msapiro.net> wrote: >> >> Thus, putting >> ``` >> DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' >> ``` >> in your settings will maintain compatibility with pre 3.2 versions and >> existing tables and this is the correct thing to do. >> > > Thank you very much for the clarification. Also note that for the past year or so, the files postorius/example_project/settings.py:, mailman_web/settings/base.py, hyperkitty/example_project/settings.py and mailman-suite/mailman-suite_project/settings.py have all contained DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' and if you follow https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… you will import mailman_web/settings/base.py and pick this up from mailman-web 0.0.6 and both https://wiki.list.org/x/17892066 and https://wiki.list.org/x/17891998 suggest that your settings.py should be a copy of the mailman-suite settings.py file but with DEBUG = False, the implication being that when that file changes, yours should too. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

Mailman-users search results for query "Postorius"