Search results for "Postorius" - Mailman-users

Re: Internal Server Error, Need 2 values to unpack in for loop; got 1

by Elias Rudberg

After some more digging into this I found a way to reproduce it using a much simpler URL, like the following (but with the real name instead of example.org) https://example.org/mailman3/postorius/lists/?items=x The error comes when Django is trying to process the template django-mailman3/django_mailman3/templates/django_mailman3/paginator/pagination.html which contains two for-loops of the following kind: {% for key, value in request.GET.items %} [... doing something with key and value here ...] {% endfor %} It seems like Django then gets confused by the different "items" variables involved, I think the value from the "?items=x" part of the request URL gets used instead of the "request.GET.items" (both are called "items" but they contain different things. I don't know if the for-loops in that template could be done differently to avoid this. There is something similar at https://github.com/django/django/blob/main/django/views/templates/technical… where the corresponding for-loop looks like this instead: {% for k, v in request_GET_items %} [...] {% endfor %} So there they write "request_GET_items" instead of "request.GET.items" for some reason. I don't know if doing it like that is possible in case of the mailman template, just mentioning it because it looks like it could be another way to achieve the same thing. I wrote a question about this in the Django forum also, here: https://forum.djangoproject.com/t/getting-error-need-2-values-to-unpack-in-… Hoping for an answer there to help figure out if this should be seen as a bug in Django or not. / Elias

1 year, 3 months

Re: Migrating mailman3 to latest ubuntu lts

by Mark Sapiro

On 12/18/23 6:24 AM, Helio Loureiro wrote: > Hi, > > Indeed it was the configuration. It was placed into > /etc/mailman3/mailman-web.py. After a I changed to > /etc/mailman3/settings.py a few things advanced a little bit more. > > I had to figure out how to fix mysqlclient installation since there isn't a > mention about it and the simple "pip install mysqclient" was breaking with > pkg-config issues. But it did work at the end. > > Now I can see further messages on mailman3-web than before. > > (venv) mailman@new-server ~ (v3.3.9)> mailman-web migrate > System check identified some issues: > > WARNINGS: > account.EmailAddress: (models.W036) MariaDB does not support unique > constraints with conditions. > HINT: A constraint won't be created. Silence this warning if you don't care > about it. > account.EmailAddress: (models.W043) MariaDB does not support indexes on > expressions. > HINT: An index won't be created. Silence this warning if you don't care > about it. > Operations to perform: > Apply all migrations: account, admin, auth, contenttypes, > django_mailman3, django_q, hyperkitty, postorius, sessions, sites, > socialaccount > Running migrations: > Applying account.0004_alter_emailaddress_drop_unique_email...Traceback > (most recent call last): I'm not sure why there would be an issue with this migration, but there is a possible compatibility issue depending on how you installed things. django-mailman3<=1.3.11 is not compatible with django-allauth>=0.58. In your venv, try ``` pip install django-allauth\<0.58 ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

Re: Turn off social logins?

by tlhackque

I am one who uses Mailman to support a closed community. Social logins are NOT a good thing there. Besides encouraging spam signups (social media accounts are easy to get - just ask the spammers), they tie your site to the privacy and other policies of the providers. This includes that when they authenticate, they also track users and sites. Monetizing the data. Many people find this objectionable. And not auditable. When I tried to use MM3, turning off social logins was one of the first things I tried to configure. It wasn't easy. First I commented out too much, then too little. The resulting errors were opaque. I hope things have improved - at present I keep an eye on MM3, but it's not usable for me at this time. So I may be somewhat behind the times. The admin interface could use an authentication control panel - per site, and per-list. Click to enable/disable the social (password, 2-factor, and other plugin) providers. On the whole, MM3 is far to painful to set up - editing hierarchies of config files assumes a technical person runs the list. Frequently, people who want lists aren't. [X} login with Google [x] login with passwords [x] login with GitHub is comprehensible - the implications may not be, but better to explain policies than how to edit a config file written in a foreign language. There's a big difference between "installing" (that can assume some technical knowledge) and "configuring" (that should not). The former has to do with where you put files, how updates and time-driven events are enabled. The latter is how one expresses one's site policies/preferences. Package managers and MaxKing's containers are "good enough" for installing. "configuring" by config files and extensive wiki searches is not. The persistent echos of issues I raised and appear on the list from others are in the same vein. Cut and paste is not scalable for bulk subscribing thousands of users. Neither is API performance. Or "resent confirmation codes". or... I recognize that replacing a mature technology is hard. MM3 has a lot of potential. It's just not there, for me, yet. On 12-Feb-19 11:11, Stephen J. Turnbull wrote: > Note: I've changed the order of sentences from Torge's post to fit my > responses. > > Torge Riedel writes: > > > I do agree, same here on my side. Lot's of my users are very > > "sensitive" to social media and don't want see them here. > > This is the first I've heard of this. Obviously it's fairly > widespread; *please* speak up if anyone have similar issues that we > haven't addressed. AFAIK all of the currently active Mailman > developers believe that social auth is a GoodThang[tm], so we're > unlikely to DTRT as you see it without your help. > > > I need to migrate from mailman2 to mailman3 and was wondering why > > social accounts are enabled by default > > By default Mailman 3 is social media: you have a profile, you can be > searched in the indicies of the archives, and so on. The large auth > providers provide more secure authentication, and a lot of convenience > for users who have such accounts already. They also take some > administrative burden off the list and site managers when people lose > their passwords and forget what their subscription address is, and > similar scenarios. Clearly, these are not universally-valued > features, but I think that they justify the current defaults. > > > and are difficult to disable. > > They're easy enough to disable (easy to recognize and just add a hash > character in front), since you have to edit settings_local.py to > install anyway. If you're using a packaged version and the package > configuration utility doesn't handle it, there's nothing we can do > about it. The distro will have to deal with that. > > It should be better documented, I imagine (haven't checked yet). > > > I propose something like an additional setting listing the enabled > > social accounts. > > Do you mean in the Postorius administration interface? If so, do you > want it by-site, by-domain, or by-list? ("You" is everybody who wants > to disable social auth, not just Torge!) > > If you mean in settings_local.py, I suggested something similar > earlier. It's not obvious it would be easy to do (sometimes these > things are order-dependent, though that's bad practice). > > > And if the admin is setting this to an empty value in the > > settings_local.py everything is disabled > > Because the settings are a Python module, this is the way > settings_local.py works anyway. That's why Mark suggested editing > INSTALLED_APPS. > _______________________________________________ > 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/ -- This communication may not represent my employer's views, if any, on the matters discussed.

6 years, 9 months

Messages disappearing into hole??

by Ruth Ivimey-Cook

Folks, I have been trying to set up a mailing list that is mostly for message distribution, so there is a single sender of messages and multiple receivers, but the receivers are moderated. I wouldn't mind receiver messages being explicitly rejected but that's not an issue for now. I looked around the interface and decided to set up the sender as a non-member, as that appeared to permit them to be "special" and outside of the normal access rules for the list. Before I did that I could send a message from this sender and that would be sent to me as list owner for moderation, so both incoming (from my mailserver) and outgoing (to it) can be completed. However, with a non-member who is auto-accepted the message is passed from my mailserver to mailman and then disappears. I cannot find anything in the logs to indicate what happened next. I have tried setting the default non-member policy to both 'hold' and 'default' with no change in that behaviour. The logs for the mailserver show the message being sent to mailman; mailman's "smtp.log" shows an LMTP message being received ok, and then nothing. Any ideas how to find out what is going on? I can share config if that helps but not sure what would be useful. As a side-issue, at one point I added a regex matching the sender address to the acceptable members list, but find that I cannot now delete it (using postorius): If I delete the field and Save, it returns on page refresh. Regards, Ruth -- Software Manager & Engineer Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

5 years, 2 months

[Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/accounts/XXXXX/login/

by Stephen J. Turnbull

Odhiambo Washington writes: > Where XXXXX from the subject implies github|fedora|openid|gitlab, etc, I > edited my settings.py and removed those references to socialaccount auth > providers, except google: It's clear enough: Internal Server Error: /mailman3/accounts/gitlab/login/ DoesNotExist at /accounts/gitlab/login/ SocialApp matching query does not exist. Mailman is doing the right thing here: it assumes the remote user knows what they're doing, tries the auth provider, and discovers it doesn't exist, so it reports an error. Mailman is not responsible for the query; some third party is. You're dealing with the Internet -- we can't help you with what third parties do. The one possible link to Mailman is that somehow mailman-web is offering social auth using those providers to users. When you log out of Postorius/ HyperKitty, then try to log back in, does the application offer login through any social auth other than Google? If so, that may be the problem, but I don't know how that can happen: the social auth offered is based on querying the providers installed by settings.py. And the person initiating the login would presumably be your user, who I would imagine would complain if they were trying to use social auth and it failed for them. Perhaps it's a user's browser cache. If mailman-web doesn't offer social auth, it's something else. The reverse DNS lookup says it's coming from REMOTE_ADDR = '185.191.171.20' which is "20.bl.bot.semrush.com", where semrush is an SEO company. The "bot" part is suggestive of an automated attack, but who knows. Steve

4 years, 1 month

Re: moving lists to another server

by Odhiambo Washington

On Mon, Nov 20, 2023 at 7:56 AM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Odhiambo Washington writes: > > > The idea is to (if possible) not change anything at all. I will be > > serving the list using the original domain. > > Fine. I just didn't want to assume anything. > > > I am hoping that should not be necessary. > > It's not. That's one of the major things that MM3 does that MM2 does > not: handle multiple domains properly. > > > I actually had thought it wouldn't be complex doing this until I > > sat down and said wait - there is a DB involved :) > > > 3. (If the DB engines are different) Dump both databases in text > > > format (ie, scripts of SQL commands). Check to see how they > > > differ. > > > > > > > The DB is MySQL. My running setup uses MariaDB. I am not getting what > you > > mean here by how they differ. > > You didn't say that before. I tend to assume PostgreSQL because > that's what I use. > > I don't know if MySQL and MariaDB have different features that have > different syntax, etc. That's what you're looking for. Any commands > that are *not SQL* used to configure the database engine itself (for > example the utf8mb4 parameter which MySQL has but PostgreSQL does not, > does MariaDB need it?) Also any non-standard SQL stuff (mostly around > varchar/text types I think). > I use the utf8mb4 character set as default, unless something wants a different one. MySQL and MariaDB are almost similar. I have encountered very few significant differences since I switched to MariaDB. > 4. Adapt the foreign database to its new environment with search and > > > replace. > > > > If going with what I have mentioned above, is this step still > > necessary? > > Isn't one installation using 'mailman' and 'mailmanweb' databases, > while the other only 'mailman'? You'll need to deal with that at > least I suppose. > This is true. However, I was hoping that I could merge the two foreign DBs into one. I am yet to test it though. > > > 5. (Optional if your name is "Daredevil") Create a new Mailman suite > > > install using your current configs, preferably in a new VM or set > > > of containers. > > > > I was thinking about this as one way of testing the situation, much > > as it is quite involving. > > Fred Brooks famously put it this way: "Build one to throw away. You > will anyway. The only question is whether you deliver the first > version to the customer." ;-) > I had to Google who he was :-) > Suppose I just do: > > 1. Create the new list on my server using the inherited domain and > > configure it appropriately, > > 2. Configure Django to handle the different domains (there is something > > that I am yet to understand here around SITE_ID when you have multiple > > sites!) > > You just add them in the Django admin page. Problems come in when you > delete the original example.com placeholder domain. I think you > probably need to add SITE_ID=0 to settings.py so the Django figures > out the site from the HTTP header rather than just assuming it's the > same Postorius site for all lists. > In my case, I did not delete the original example.com. I finally get to use SITE_ID=0. I suppose that it should be accompanied by FILTER_VHOST=True > > 3. Extract the users from the list and subscribe them afresh (I can > > shoot an email to let them know the ML had to be moved so they can > > set their preferences again) > > 4. Import the archives of the list > > I should more or less achieve the migration, no? > > I think that should work. > I am going to try this method. It looks safer for me. > > What about setting up on /opt/mailman2 a complete replica of the > > list? That'd be the real "Daredevil" :) > > This will also work, I'm sure. But we'd be embarrassed after going to > the trouble of making Mailman 3 handle multiple domains. Also you'd > need separate instances of Mailman running, with their own > /etc/mailman3-1 and /etc/mailman3-2, and more important you'd double > the RSS and VM requirements by running two instances. > I also will need to have extra macros, routers, and transports for Exim. This method is untenable as it complicates life. -- 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]

2 years

Re: Member Issue Discovered

by Brian Carpenter

On 10/23/20 11:19 AM, Mark Sapiro wrote: > Here's a thought. For Affinity/Empathy at least, how about using Mailman > core's user as the Affinity registered user. I.e., if someone's first > interaction is to register with Affinity, have that registration create > a core user to keep the Affinity registration data. This core user > already accommodates a display_name and password and email address(es). > > If the person already is a core user when registering for Affinity, just > update the core user as needed, probably only a password reset or just > setting it if it is currently None. > > Then you don't have the issue of another, separate registration for > Affinity. > > This would be more difficult for Postorius/Hyperkitty because those > users are Django users, but that isn't an issue for Affinity. > > -- 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/ How would a person already be a core user outside of a registration with Affinity? Via a list subscription or the import21 script? I do agree overall that we can more easily address some/all of these issues more easily and quicker due to not being tied to Django. I hope to get all of this address in our Nov development cycle. I do want to apologize for my tone Mark. I was wrong in the way I communicated. > -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

Confirmation emails to Users has wrong domain name (example.com!)

by Odhiambo Washington

1. Confirmation emails to Users has wrong domain name (example.com!) <https://docs.mailman3.org/en/latest/faq.html#id1> <https://docs.mailman3.org/en/latest/faq.html#confirmation-emails-to-users-h…> This happens when your reverse (SSL) proxy isn’t setting up the correct headers when proxying requests. Fix this by setting the right proxy_set_header directives: # For Nginx. location / { proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Host $host; proxy_pass http://localhost:8000/; } Appropriate headers for different web servers needs to be set if something other the How is this supposed to be mitigated in Apache when using WSGI? My config: WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman user=mailman group=mailman WSGIPythonHome "/usr/local" WSGIProcessGroup hyperkitty <VirtualHost *:443> ServerName lists.doma.ain ServerAdmin odhiambo(a)gmail.com SSLEngine on SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL SSLCertificateFile "/usr/local/etc/letsencrypt/live/lists.doma.ain/cert.pem" SSLCertificateKeyFile "/usr/local/etc/letsencrypt/live/lists.doma.ain/privkey.pem" SSLCertificateChainFile "/usr/local/etc/letsencrypt/live/lists.doma.ain/chain.pem" CustomLog /var/log/mm3-lists-access.log combined ErrorLog /var/log/mm3-lists-error.log LogLevel info Alias /favicon.ico /usr/local/mailman/static/hyperkitty/favicon.ico Alias /static /usr/local/mailman/static <Directory "/usr/local/mailman/static"> Order Allow,Deny Require all granted Allow from all </Directory> WSGIScriptAlias /mailman3 /usr/local/mailman/etc/wsgi.py process-group=hyperkitty WSGIScriptAlias /hyperkitty /usr/local/mailman/etc/wsgi.py process-group=hyperkitty WSGIScriptAlias /postorius /usr/local/mailman/etc/wsgi.py process-group=hyperkitty WSGIScriptAlias /archives /usr/local/mailman/etc/wsgi.py process-group=hyperkitty <Directory "/usr/local/mailman/"> <Files wsgi.py> Require all granted </Files> WSGIProcessGroup mailman-web </Directory> </VirtualHost> -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

4 years, 1 month

Re: rDNS issue? Helo name contains an IP address (HELO was [127.0.0.1]) and not is valid

by Stephen J. Turnbull

Kyriakos Terzopoulos writes: > No more mail being marked as spam. However I face a (hopefully) new > problem now. When I mass subscribe the users, they get an initial > invitation email. However after replying I get this in the exim > logs, the subsequent mails do not arrive and the users are not > verified at all: > > 2023-10-25 13:36:41 1qvbFh-001kcb-Ig <= myname(a)myproject.eu > H=localhost (webmail.myproject.eu) [127.0.0.1] P=esmtpa > A=dovecot_login: myname(a)myproject.eu S=1726 > id=32091a0e12cc23fa988380639a4c44a6@ myproject.eu > 2023-10-25 13:36:41 1qvbFh-001kcb-Ig == partners(a)myproject.eu > <partners-confirm+6df62cd0f805b2b66b21a43a42ec8ee77487e8ad(a)myproject.eu> > R=mailman3_router T=mailman3_transport defer (-54): > retry time not reached for any host for ' myproject.eu' It looks like 'myname' has replied to the invitation, and was received by this MTA (is it Mailman's MTA?). Then delivery to Mailman was deferred because delivery to ' myproject.eu' has failed, and Exim is queueing them for future delivery, until the next retry time. Try using 'runq' then checking the log to see why mail is failing in the first place. I do not understand why there are spaces before the host name in these lines: > id=32091a0e12cc23fa988380639a4c44a6@ myproject.eu > retry time not reached for any host for ' myproject.eu' The first never happens in my Exim instance. (I have no instances of "retry time not reached" at all in my logs.) That suggests a misconfiguration, in Exim, in Mailman, or Postorius. You should check the mailman3_router and the mailman3_transport first because they're easier. Steve

2 years, 1 month

LookupError: unknown encoding: _iso-2022-jp$esc

by Thor Atle Rustad

This happens when I open a page of Held Messages containing an offending message. I get Server Error (500) in Postorius. Here is the mailman.log: Sep 07 15:25:39 2018 (32) REST request handler error: Traceback (most recent call last): File "/usr/local/lib/python3.6/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/usr/local/lib/python3.6/site-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/local/lib/python3.6/site-packages/mailman/rest/wsgiapp.py", line 214, in __call__ return super().__call__(environ, start_response) File "/usr/local/lib/python3.6/site-packages/falcon/api.py", line 244, in __call__ responder(req, resp, **params) File "/usr/local/lib/python3.6/site-packages/mailman/rest/post_moderation.py", line 160, in on_get resource = self._make_collection(request) File "/usr/local/lib/python3.6/site-packages/mailman/rest/helpers.py", line 159, in _make_collection for resource in collection] File "/usr/local/lib/python3.6/site-packages/mailman/rest/helpers.py", line 159, in <listcomp> for resource in collection] File "/usr/local/lib/python3.6/site-packages/mailman/rest/post_moderation.py", line 150, in _resource_as_dict resource = self._make_resource(request.id) File "/usr/local/lib/python3.6/site-packages/mailman/rest/post_moderation.py", line 77, in _make_resource resource['msg'] = msg.as_string() File "/usr/local/lib/python3.6/site-packages/mailman/email/message.py", line 54, in as_string value = email.message.Message.as_string(self) File "/usr/local/lib/python3.6/email/message.py", line 158, in as_string g.flatten(self, unixfrom=unixfrom) File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten self._write(msg) File "/usr/local/lib/python3.6/email/generator.py", line 181, in _write self._dispatch(msg) File "/usr/local/lib/python3.6/email/generator.py", line 214, in _dispatch meth(msg) File "/usr/local/lib/python3.6/email/generator.py", line 243, in _handle_text msg.set_payload(payload, charset) File "/usr/local/lib/python3.6/email/message.py", line 315, in set_payload payload = payload.encode(charset.output_charset) LookupError: unknown encoding: _iso-2022-jp$esc

7 years, 2 months

Mailman-users search results for query "Postorius"