Search results for "Postorius" - Mailman-users

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

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]

1 year, 11 months

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

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

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, 1 month

Re: Importing Mailman 2 Lists apart from Django

by Mark Sapiro

On 4/30/20 7:59 AM, 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? import21 requires only Mailman core. > 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? The only current archive import we support is `django-admin hyperkitty_import` which imports archive .mbox files into HyperKitty. The prototype archiver is just a maildir format collection of messages. Converting an mbox file to a maildir is trivial. from mailbox import Maildir, mbox mb = mbox('/path/to/mbox', create=False) md = Maildir('/path/to/maildir', create=True) for msg in mb: md.add(msg) > We are getting ready to start working on a custom forum application for > Mailman 3 (called Empathy) and I am would like to import some mailman 2 > archives into the development server to work with. First you have to decide how Empathy will store messages. Look at <https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/management/c…>. This is how HyperKitty gets messages from a mbox and adds them to its database. It's actually fairly simple - a lot of the code is handling exceptions due to defective messages. Presumably Empathy will have a method for adding a message to the archive, so importing is just getting messages from the mbox and using Empathy's method 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

5 years, 6 months

Re: unique key violation because of case sensitivity of email address

by Mark Sapiro

On 6/15/24 11:47, Jörg Schulz wrote: > After updating to the most recent version of mailman-web, the migrations > script issued an error: > > > Apply all migrations: account, admin, auth, contenttypes, > django_mailman3, django_q, hyperkitty, postorius, sessions, sites, > socialaccount > mailman-web | Running migrations: > mailman-web | Traceback (most recent call last): > mailman-web | File > "/usr/lib/python3.12/site-packages/django/db/backends/utils.py", line > 89, in _execute > mailman-web | return self.cursor.execute(sql, params) > mailman-web | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > mailman-web | psycopg2.errors.UniqueViolation: duplicate key value > violates unique constraint > "account_emailaddress_user_id_email_987c8728_uniq" > mailman-web | DETAIL: Key (user_id, email)=(27, > John.Doe(a)mynicedomain.de) already exists. > mailman-web |(...) Presumably you upgraded django-allauth to a version >=0.62. Beginnin then, email addresses were no longer stored case-sensitively and the migration was dealing with that. There were other issues when addresses were store case sensitively. See https://github.com/pennersr/django-allauth/issues/3019 > Digging into the db, I found the duplicate to result from a duplicate > entry using john.doe(a)mynicedomain.de > > > Obviously, the process that originally created the entry, took case > sensitivity literally which doesn't seem to be the case any longer for > the migration script. > > I fixed this by removing one of the duplicates hoping no further errors > will come up.... > > > What would have been the better approach? Removing one of the duplicates is the solution, and beginning with django-allauth>=0.62, duplicates should no longer occur. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

Re: using SSH/TLS with external MTA

by Roland Giesler

On 2024/07/28 15:42, Roland Giesler via Mailman-users wrote: > > On 2024/07/28 15:26, Roland Giesler via Mailman-users wrote: >> On 2024/07/28 00:39, Mark Sapiro wrote: >>> On 7/27/24 15:16, Roland Giesler via Mailman-users wrote: >>>> >>>> The server runs power-mailinabox, which uses Postfix indeed. All my >>>> mail, and quite a few others' mail is sent from the using SMTP-Auth >>>> on port 465. Actually, this message is sent via that server too. >>>> So it's clear to me that MM3 is not authenticating for some reason. >>> >>> What do you see in Mailman's smtp.log and in the mail.log on the >>> mail server? >> >> The smtp log is in syslog... > > I also see this in /var/log/mailman3/web/mailman-web.log The /etc/mailman3/mailman3-web.py file contains inter alia these lines: # Set default domain for email addresses. EMAILNAME = 'fast.za.net' # If you enable internal authentication, this is the address that the emails # will appear to be coming from. Make sure you set a valid domain name, # otherwise the emails may get rejected. # https://docs.djangoproject.com/en/1.8/ref/settings/#default-from-email # DEFAULT_FROM_EMAIL = "mailing-lists(a)you-domain.org" DEFAULT_FROM_EMAIL = 'postorius@{}'.format(EMAILNAME) # If you enable email reporting for error messages, this is where those emails # will appear to be coming from. Make sure you set a valid domain name, # otherwise the emails may get rejected. # https://docs.djangoproject.com/en/1.8/ref/settings/#std:setting-SERVER_EMAIL # SERVER_EMAIL = 'root(a)your-domain.org' SERVER_EMAIL = 'root@{}'.format(EMAILNAME) fast.za.net was giesler.za.net before, so I changed it.

1 year, 3 months

Mailman-users search results for query "Postorius"