Search results for "Postorius" - Mailman-users

Race condition when mass subscribing same email addresses to two lists?

by Alan So

We are testing the latest Mailman core 3.3.5 and Postorius 1.3.6. My colleagues reported that some email addresses cannot subscribe to the lists when two of them are using mass subscribe feature to add email addresses to the list. Then I try whether I can repeat the same issue. I did this: 1) Create two lists with default setting 2) Prepare a list of 1000 fresh email addresses not added to the system before 3) Mass subscribe both lists of these 1000 email addresses around the same time with all three Pre (confirm, approved, verified) checked There are quite a lot of similar errors in mailman.log. Did not study the code yet. Which part is causing the issue? SQLAlchemy 1.3.24 psycopg2-binary 2.8.6 [2021-10-28 08:38:30 +0000] [20141] [ERROR] Error handling request /3.1/members Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.6/site-packages/gunicorn/workers/sync.py", line 136, in handle self.handle_request(listener, req, client, addr) File "/opt/mailman/venv/lib/python3.6/site-packages/gunicorn/workers/sync.py", line 179, in handle_request respiter = self.wsgi(environ, resp.start_response) File "/opt/mailman/venv/lib/python3.6/site-packages/mailman/database/transaction.py", line 51, in wrapper config.db.commit() File "/opt/mailman/venv/lib/python3.6/site-packages/mailman/database/base.py", line 52, in commit self.store.commit() File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/session.py", line 1046, in commit self.transaction.commit() File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/session.py", line 502, in commit self._assert_active(prepared_ok=True) File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/session.py", line 296, in _assert_active code="7s2a", sqlalchemy.exc.InvalidRequestError: This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first issue Session.rollback(). Original exception was: (raised as a result of Query-invoked autoflush; consider using a session.no_autoflush block if this flush is occurring prematurely) (psycopg2.errors.UniqueViolation) duplicate key value violates unique constraint "ix_address_email" DETAIL: Key (email)=(testemail999(a)example.com) already exists.

4 years, 4 months

Initial success: Mailman 3.3 integrated with Zimbra 8.8

by Morris Jones

I have a very old existing mail server running Zimbra 6 with a mailman 2.1 instance alongside. I needed to rebuild my mail server for some compelling reasons (the old server used outdated TLS protocol, I could no longer compile clamav, nothing could really be updated). The final straw was a lack of support for my old commercial SSL certificates. I patched in a letsencrypt certificate to get through the past six months. I'm in the process of commissioning a new mail server using an 8GB Linode, Ubuntu 18, Zimbra 8.8, and Mailman 3.3. A couple of days ago I had my first successful list creation, with user confirmation working by email. I have django running with uwsgi, and am using Zimbra's installed nginx proxy to reverse proxy http traffic to Postorius and Hyperkitty. Nginx is doing the SSL layer. The mailman core mta hooks are all done using Zimbra's "local configuration" technique. In theory I should be able to do Zimbra upgrades with a minimum of hassle. I've written up a "case history" of how it came together. I have a .rst file in a gitlab project here: https://gitlab.com/MojoLA/mailman3.3-zimbra-8.8-integration I suppose this is a crazy project, but it's worthwhile to me. (Mark, thank's so much for integrating the virtual domain maps. It took me about three days to recognize that they were the solution to bounced mails to list-owner@...) Now I can spend some time migrating my email accounts (only four) from the old server to the new one, and move a dozen or so mailing lists to the new mailman3 instance. I'll have to get accustomed to a new way to manage the mail lists, and already really like what I've seen. Thank you. :) Best regards, Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

5 years, 3 months

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

by Abhilash Raj

On Thu, Sep 30, 2021, at 2:20 AM, Odhiambo Washington wrote: > On Thu, Sep 30, 2021 at 1:59 AM Abhilash Raj <maxking(a)asynchronous.in> > wrote: > >> >> >> > On Sep 29, 2021, at 2:34 PM, Odhiambo Washington <odhiambo(a)gmail.com> >> wrote: >> > >> > On Wed, Sep 29, 2021 at 8:31 PM Mark Sapiro <mark(a)msapiro.net> wrote: >> > >> >> On 9/29/21 9:50 AM, Odhiambo Washington wrote: >> >>> 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: >> >> ... >> >>> 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 >> >> >> >> >> >> You are using mod_wsgi and not proxying at all, so this is not relevant >> >> in your case. >> >> >> >> Are you actually seeing this issue? If so, it might be related to >> >> >> >> >> https://docs.mailman3.org/en/latest/faq.html#the-domain-name-displayed-in-h… >> >> >> > >> > My issue is related to this, but the documentation referred to is not for >> > the faint-hearted! >> > I can't make head or tails of it. >> >> Click on “Domain” in Postorius from the top bar, which should take you to >> the Domains page. >> >> For your domain (in the “Mail Host” column), see the corresponding “Web >> Host” column, it should look something like: >> >> lists.mailman3.org (lists.mailman3.org) >> (Edit) >> SITE_ID = 1 >> > > Mine looks different, slightly. But there is no example.com at all. > > [image: Abhilash.png] > > > >> >> on a new-ish version of Postorius. >> > > I have the newest versions of everything, having installed only yesterday. > > >> >> If it doesn’t show the right values and instead shows “example.com” for >> you, click on the “Edit” link, which will take >> you to a page that will allow you to edit both the values. >> > > It shows the right values, but with "SITE_ID = 2". In my settings_local.py > I have SITE_ID = 1. > I suppose the example.com is the one tied to SITE_ID = 1 and that is what I > have in my settings_local.py. That is most likely what is happening. > Should I edit my settings_local.py? Yes, please update it to have SITE_ID = 2 to correspond to the site you want and restart. > > I am still confused. > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", egrep -v '^$|^.*#' :-) > _______________________________________________ > 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)

4 years, 5 months

Re: Strange password problem

by Eggert Ehmke

There may be broken entries in my config. In web/logs/uwsgi-error.log I get: Unknown command: 'qcluster' when the entry in uwsgi.ini is: *attach-daemon* *=* python3 /opt/mailman/venv/lib/python3.9/site-packages/ mailman_web/manage.py qcluster When I change that line to: *attach-daemon* *=* python3 ./manage.py qcluster I get: python3: can't open file '//./manage.py': [Errno 2] No such file or directory This may be unrelated to the password problem, but this line runs every minute in the cron job. Am Donnerstag, 22. Juni 2023, 11:50:57 CEST schrieb Odhiambo Washington: > On Thu, Jun 22, 2023 at 12:34 PM Eggert Ehmke via Mailman-users < > mailman-users(a)mailman3.org> wrote: > > > > This happened several times recently with Postorius Version 1.3.8: > > -I try to log in as admin > > -rejected because of wrong password (password is stored in browser) > > -used forgotten password function > > -reset password to the stored value from browser > > -login works now. Works also when logged out/in again > > -however, the next day this behaviour repeats. > > > > > > > > Any hints? > > > > 1. You have a bug in the browser cache. Try a different browser. > 2. You can check also mailmanweb logs for clues?? > > -- > 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] > _______________________________________________ > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message > /BWAVUEMHI56YI7FHTDULIZNIKIAM7324/ > > This message sent to eggert(a)eehmke.de ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 years, 8 months

Re: nginx configuration on a multitasking server

by David Newman

On 12/22/21 8:50 PM, Mark Sapiro wrote: > On 12/22/21 7:54 PM, David Newman wrote: >> On 12/22/21 7:29 PM, Mark Sapiro wrote: >> >>> This looks like a uwsgi issue as discussed at >>> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >>> although that's with apache and not nginx so it may not be. >> >> If I'm reading the thread correctly, it's Apache workarounds to an >> underlying Debian issue, so I agree it may not apply with nginx. > > > I think you're correct that it doesn't apply to nginx, but the symptom > is not the same. It is not a Debian issue per se. It is an Apache change > that got installed with a Debian update, but the underlying issue is > with Apache. See > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > >> There are 260 files named 'urls.py' under /opt/mailman, mostly for >> socialaccount stuff. >> >> Where does that change go? All files? Or just this one: >> >> /opt/mailman/venv/lib/python3.9/site-packages/postorius/urls.py > > > Not that one. The one whose content looks like > https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py. It > is probably in the same directory as your Django settings. On my system that file lives here: /opt/mailman/venv/lib/python3.9/site-packages/mailman_web/urls.py But the error persists after this addition and restarting MM3 and mailmanweb and nginx: url(r'^mailman/', include('postorius.urls')), There is this 404 error in uwsgi.log: [pid: 73356|app: 0|req: 3/3] 127.0.0.1 () {48 vars in 1544 bytes} [Wed Dec 22 21:13:48 2021] GET /mailman/admindb/listname => generated 5328 bytes in 14 msecs (HTTP/1.0 404) 6 headers in 197 bytes (1 switches on core 0) If this is a uwsgi issue, is there something else to tweak with that? Thanks dn > >

4 years, 2 months

Re: sqlite3 Database "read only" error on mailman_sync job

by Abhilash Raj

On Thu, Sep 5, 2019, at 1:49 PM, Ugnius wrote: > > Thank You. This is very valuable information. According documentation I understood that "runserver" should run on some internal port and uwsgi just works like proxy connects to the same as runserver port and serves content to apachi. Because when I was playing with the setup without "runserver" Web interface didn't work. > Yes, I have stopped "runserver" and page still works fine. :) This didn't solve me database RO issue, but this information was important. Thank You. I am thinking what to do now... Maybe to recreate database (make initiation once again). It could take 2-3 hours. I did not noticed option to export/import lists setting. Or to try find solution how to make sqlite3 multiple > writable. I think your problem about locked database might be solved. Like I mentioned, it is possible that those two running server could be stepping over each other toes. After removing the "runserver" process, I think you shouldn't fall into anymore of those locking issues. FWIW, it is also highly recommended to not use sqlite for any production use cases. Either postgres or mysql is preferred. > SQLite version 3.16.2 2017-01-06 16:32:41 > Enter ".help" for usage hints. > > BR > Ugnius > > On 5 Sep 2019, at 23:31, Abhilash Raj <maxking(a)asynchronous.in> wrote: >> On Thu, Sep 5, 2019, at 1:15 PM, Ugnius wrote: >>> >>> I do not know... In the setup example settings was something like process number = 2. But I understand at least 1 uwsgi and 1 run server should run? >> >> No, only uwsgi needs to run. It is fine if there are two of those, since it probably forks to have 2 worker process. There shouldn't be any "python manage.py runserver" processes running at all, it is meant only for testing purposes. >> >> The doc mentions that it is "development" server[1][2]. >> >> [1]: # Run the Django's "development" server at localhost:8000 >> [2]: http://docs.mailman3.org/en/latest/prodsetup.html#setting-up-django-project >> >> Perhaps it should be more descriptive about what does it mean. >> >>> >>> On 5 Sep 2019, at 23:08, Abhilash Raj <maxking(a)asynchronous.in> wrote: >>>> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>> >>>> This fishy, why do you have both uwsgi and "python manage.py runserver" running? >>>> >>>> You only need one of those, since they both do the exact same thing. Please remove >>>> whatever is running the "python manage.py runserver" part and only use uwsgi. >>>> >>>> On Thu, Sep 5, 2019, at 1:02 PM, Ugnius S wrote: >>>>> Thank You, Abhilash, to helping. I have checked the processes, but also I have read, that sqlite3 can run in multi writing mode. >>>>> May mailman processes are next: >>>>> >>>>> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>>> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>>> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>>> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>>> 6643 ? S 0:00 /usr/bin/python3 /usr/bin/master -C /opt/home/mailman.cfg >>>>> 659 ? S 0:46 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=in:0:1 >>>>> 6660 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=nntp:0:1 >>>>> 6661 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=digest:0:1 >>>>> 6662 ? S 0:48 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=pipeline:0:1 >>>>> 6663 ? S 0:44 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=archive:0:1 >>>>> 6664 ? S 0:41 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=command:0:1 >>>>> 6665 ? S 0:01 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=retry:0:1 >>>>> 6666 ? S 0:45 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=virgin:0:1 >>>>> 6667 ? Sl 0:16 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=lmtp:0:1 >>>>> 6668 ? Sl 1:30 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=rest:0:1 >>>>> 6669 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=bounces:0:1 >>>>> 6670 ? S 0:49 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=out:0:1 >>>>> >>>>> Looks like there are no double. Nothing more is running. >>>>> >>>>> 2019-09-05, kt, 03:16 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>>>>> __ >>>>>> On Wed, Sep 4, 2019, at 2:05 PM, Ugnius S wrote: >>>>>>> >>>>>>> I have installed using documentation. My linux distribution version has no full package available. I have installed step by step: >>>>>>> $ sudo pip3 install mailman >>>>>>> $ sudo pip3 install postorius >>>>>>> $ sudo pip3 install hyperkitty >>>>>>> $ sudo pip3 install mailman-hyperkitty >>>>>>> And of course all mandatory components... Everything without errors, I can drop db files and I can download mailman-suite again and start from empty page again. But it will not guarantee that DB will not become READ ONLY again. Here should be logic. No developing support here? >>>>>> >>>>>> Could you be running two separate processes such that the database is locked by one and so other finds it as READ Only? When you find a read only database, can you check if it is open in some other process? >>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> 2019-09-03, an, 19:36 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>>>>>>> >>>>>>>> >>>>>>>> On Sun, Sep 1, 2019, at 3:22 AM,ugniusviln(a)gmail.com wrote: >>>>>>>> > Hi. All the project installation is under the same user / path and >>>>>>>> > it works. Archiving working as well, (just one remark: no matter what >>>>>>>> > to set in postorius, hyperkitty shows list as public) >>>>>>>> > I have found work around - it is possible to change list as private in >>>>>>>> > "admin" page. >>>>>>>> > I started to get issues with runjobs after I have created couple of >>>>>>>> > new lists with "no archive" option. >>>>>>>> >>>>>>>> How did you install all these components. It seems there the installation is broken in weird ways. >>>>>>>> >>>>>>>> > >>>>>>>> > If as owner user from project home I run: >>>>>>>> > >>>>>>>> > django-admin mailman_sync >>>>>>>> > >>>>>>>> > Traceback (most recent call last): >>>>>>>> > File >>>>>>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/utils.py", >>>>>>>> > line 84, in _execute >>>>>>>> > return self.cursor.execute(sql, params) >>>>>>>> > File >>>>>>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py", >>>>>>>> > line 383, in execute >>>>>>>> > return Database.Cursor.execute(self, query, params) >>>>>>>> > sqlite3.OperationalError: attempt to write a readonly database >>>>>>>> > >>>>>>>> > "django-admin runjob sync_mailman " - makes read only errors as well. >>>>>>>> > "django-admin runjob new_lists_from_mailman" >>>>>>>> > django.db.utils.OperationalError: attempt to write a readonly database >>>>>>>> > END TRACEBACK >>>>>>>> > >>>>>>>> > I did not find information how to fix this. It was worked without errors >>>>>>>> > before. >>>>>>>> > I noticed, that if I stop mailman, "django-admin mailman_sync" starts >>>>>>>> > to work. >>>>>>>> > If I start "mailman start", then "django-admin mailman_sync" failing >>>>>>>> > again. >>>>>>>> > I did not check other jobs, but I think what is related to database, >>>>>>>> > will get errors. >>>>>>>> > Seems mailman locking the database. It is not a file permissions issue. >>>>>>>> > Mailman db location is: /project_directory/var/data/mailman.db >>>>>>>> > >>>>>>>> > if to rename /project_directory/var/data/mailman.db to something, >>>>>>>> > mailman creates database file size 0, django-admin runjobs start >>>>>>>> > working, but of course postorius stops working. I did it for testing. >>>>>>>> > I have returned this database file back, postorius started to work >>>>>>>> > again, but django-admin runjobs does not work, error: "database read >>>>>>>> > only". >>>>>>>> > Please help me how to fix this issue. >>>>>>>> > _______________________________________________ >>>>>>>> > 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) >>>>>> >>>>>> -- >>>>>> thanks, >>>>>> Abhilash Raj (maxking) >>>>>> >>>>>> >>>> >>>> -- >>>> thanks, >>>> Abhilash Raj (maxking) >>>> >>>> >> >> -- >> thanks, >> Abhilash Raj (maxking) >> >> -- thanks, Abhilash Raj (maxking)

6 years, 6 months

Re: mailman addmember/syncmember commands print undecoded UTF-8 [ADD] or [DEL] mail addresses in its messages like "[ADD] =?utf-8?q?John_=....."

by Wikinaut

Not a single mail was sent - I am migrating (and newly setting up from textfiles) the mailman3 suite, installed fresh from the scratch in (venv) in /opt/mailman. I noticed that after having used a mix of addmember and also syncmember, one (or yesterday about 100 entries) of 500 had the MIME-coding. Then I used a script to remove users with the "=?UTF...." begin. In postorius users the user was gone and also in the lists where this user was in. def delete_users(): url = f"{API_URL}/users" r = requests.get(f'{url}', auth = AUTH) r.raise_for_status() users = r.json()['entries'] for user in users: dn = user.get('display_name') if type(dn) == type("string") and dn.startswith("="): print (dn) self_link = user.get('self_link') requests.delete(self_link, auth=AUTH) def main(): delete_users() After a new add/syncmember, that spooky entry was up again! Then I used mailman delmembers --fromall --no-goodbye-msg --no-admin-notify -m <this@address>: Then after a new add/syncmember, that entry was gone and the correct entry was shown. That means, that somewhere some remains were stored somewhere. I also have a another issue, where I cannot get rid of a test display_name like "1111 [äöo]" <myemailaddress> for my own user entry (this issue has not yet been filed, as I do not want to flood you here; the "=?utf.." issue seems to be a more apparent problem). At the moment, none of the ~500 users have "utf" searchable, which is some good news. Perhaps to mention: I noticed the utf-problems when I used Ctrl-C during heavy script actions while add/syncing the lists which I needed to stop. while testing. Perhaps this caused an inconsistent database state??? and that present issue was a consequence of my harsh break?

7 months

Re: [Mailman-Developers] Mailman 3.1 beta coming soon

by Barry Warsaw

Thanks for doing the testing Florian. Btw I fixed the venv problem. It was actually a bug in one of the dependencies. I have another small branch to land before spinning the beta but I think the MySQL docker image on ci is having some problems. I can't double check ATM. Sent from my digital lollipop. > On Dec 3, 2016, at 15:22, Florian Fuchs <f(a)florianfuchs.com> wrote: > >> On Fri, Dec 02, 2016 at 11:07:24AM -0500, Barry Warsaw wrote: >> Hello Mailman 3 users and developers! >> >> It's been a long slog but I think we are finally ready to begin the release >> process for Mailman 3.1. I am pretty happy about the state of the Core, and >> Florian is going to do some more integration testing with HyperKitty and >> Postorius. We still have a few issues and a merge proposal or two to address, > > I did some manual integration testing today > (core+mailmanclient+postorius) which looked fine so far. I didn't get > to test HyperKitty and the bundler though, so any help testing those > would be very much appreciated. I will have some more time tomorrow. > > I did all of my testing locally, which has some limitations. So I > started setting up a more realistic environment on one of my dev > machines. But I'm not done yet. Will report back when I'm done... ;-) > >> but I am planning to spin a beta of Core this weekend to facilitate testing. > > I think it's OK to put out a separate beta of the core, because the > version pulled from pypi will still be 3.0 if I'm not terribly mistaken. > > For the real 3.1 we should probably do a coordinated release of all > components, once everything's tested a little more thoroughly. > > Cheers > Florian

9 years, 3 months

Re: invalid parameter response of the rest-api

by Stephen J. Turnbull

gioklr71(a)gmail.com writes: > Dear Jacob did you make any progress on this issue? I've exactly > the same problem.... Is Jacob's problem really exactly the same as yours? Please compare your error message to Jacob's: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Jacob Sievert writes: > Since a few days we get an error response from our automated membership > script. > > We use the following code to control the membership for some lists: > ``` > def mailinglist_manage(list_address, members): This looks like it should work. > Since Tuesday without any update performed by us we get the following > error from the script when it's running: *Something* changed. It would likely help if one of you can figure out what. > line 339, in subscribe > response, content = self._connection.call('members', data) > File > "/root/.local/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", Either mailmanclient is now marshalling the URL and data incorrectly (which is hard to believe, it's hard to imagine this simple call is causing an error without causing both Postorius and HyperKitty to break too), or the REST protocol has changed for that resource, and the resource accessed by the URL that is constructed by self._connection.call() is not the member roster. This also seems unlikely. Your installation seems very old. From the next version of Mailman, we will not target Python 3.6 (that is, we have dropped it from the automated test pipeline), so regressions may occur. I know of at least one that occurs in old versions of core if you upgrade Python from < 3.8 to >= 3.8. Your Mailman installation also seems quite old: the code that the frame above says is on line 339 is on line 491 in git head. Are you sure you haven't applied a batch of security updates or the like that might affect any of Python, mailmanclient, or Mailman core?

3 years, 5 months

Re: Confirmation emails aren't sent to users.

by Stephen J. Turnbull

Ibiam Chihurumnaya via Mailman-users writes: > Mark Sapiro wrote: > > > OK, this is Django. The default EMAIL_BACKEND from > > mailman_web/settings/base.py is > > django.core.mail.backends.smtp.EmailBackend and unless you've changed > > that or added overrides various other defaults are > > EMAIL_HOST = "localhost" > > EMAIL_PORT = 25 > > EMAIL_HOST_USER = "" > > EMAIL_HOST_PASSWORD = "" > > EMAIL_USE_TLS = False > > EMAIL_USE_SSL = False > > EMAIL_SSL_CERTFILE = None > > EMAIL_SSL_KEYFILE = None > > Are those appropriate? Do you have an outgoing MTA listening on > > localhost:25? What's in it's logs? > > I don't have any of those set, didn't realize I needed to have them > set, the docs didn't make it obvious too. Those defaults *are* set in the mailman_web settings files. You can override them in /etc/mailman3/settings.py, but often you don't need to. > I also didn't notice them in schema.cfg in mailman. This is for Django, whose configuration is in /etc/mailman3/settings.py, with defaults set in the mailmanweb package in your venv's site-package in the files in .../mailman_web/settings/. > smtp_port is currently set to 25, and I do have an outgoing MTA > listening on localhost:25. If Mailman can distribute posts that way, Django should be able to send mail with the default settings. > Nothing shows up in the MTA logs about this particular email. Not sure what to say about that. I'm not sure Postorius or Django log outgoing mail messages but I think they use the mailmanweb.log file by default if they log mail at all. (This is separate from the MTA logs which should record any connections from localhost and mail submitted.) -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

3 weeks, 5 days

Mailman-users search results for query "Postorius"