Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: MM3 + Postfix + Dovecot + PostfixAdmin

by Mark Sapiro

On 8/8/19 10:14 PM, Stephen J. Turnbull wrote: > maztec(a)gmail.com writes: > > > Issue: Postfix LMTP does not pass messages onto MM3:LMTP. > > I don't understand why this is a Mailman problem. Seems like Postfix > user lists would be a better venue to get expert help with this. > Among other things, our most responsive Postfix guy is out of cell > coverage for now. I have a window of availability - and it's longer than I thought because my second of three back-country trips has been canceled :( > I would post this To: the relevant Postfix list, Cc: this list, and > set Reply-To and Mail-Followups-To to the Postfix list to get > everybody who can contribute on the same page. I don't have much to add to what Steve has said except our recommended config includes transport_maps = hash:/path-to-mailman/var/data/postfix_lmtp in Postfix main.cf. This should contain (per your log message) things like ListName-confirm(a)ListServer.TLD lmtp:[127.0.0.1]:8024 to tell Postfix to deliver that address via lmtp to port 8024 on the local host. Dovecot should not be involved. There is something in your config that trumps this and delivers via lmtp to Dovecot for mailman3:[127.0.0.1]:8024. Does your transport_maps look like the above or perhaps like ListName-confirm(a)ListServer.TLD mailman3:[127.0.0.1]:8024 If so, I don't know where mailman3 instead of lmtp: comes from. Also, even if it is lmtp: I don't know that Dovecot can deliver via lmtp. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: starting gunicorn per mailman.log yet gunicorn not installed

by Mark Sapiro

On 6/26/23 1:15 AM, Odhiambo Washington wrote: > On Mon, Jun 26, 2023 at 9:29 AM Stephen J. Turnbull < > turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > >> Yes, it makes sense. Mailman 3 core is basically an application which >> manages a webserver that provides the REST API, a database of domains, >> users, and lists, an LMTP server for incoming posts and an SMTP client >> for outgoing distribution. Mailman uses gunicorn to provide the >> webserver. >> >> Installation of gunicorn is handled as a package dependency, so you >> probably wouldn't notice unless you were watching the installation >> process very carefully. >> > > It doesn't make sense, IMHO, because as the OP says, > 1. his ExecStart is: > ExecStart=/opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini" *and > not* > ExecStart=/opt/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf > mailman_web.wsgi:application. > > 2. He has not knowingly created any gunicorn.conf > > Why would Gunicorn be Exec-ing itself? :-) As Steve says, Mailman core uses Gunicorn to manage it's REST API. This has nothing to do with whatever WSGI server (uWSGI, Gunicorn, Apache mod_wsgi, ...) is used to support the Django applications (django-mailman3, hyperkitty and postorius). I.e., there is always a Gunicorn instance configured and started by Mailman core, regardless of whatever WSGI server supports Django or even if one isn't running Django at all. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: Unable to update templates

by Mark Sapiro

On 5/27/25 18:54, Mark wrote: > > However when I update the template, the databases are updated correctly > but the Welcome message is still sent with the old template content. > > mailman.templates > mailmanweb.postorius_emailtemplate > > Additionally, if I delete the template and create a new one the old > content still gets sent. > > I cannot find where this content is written or is being cached. The content is stored in the mailmanweb.postorius_emailtemplate table. As far as Mailman core and Postorius are concerned, that's the only place. I'm guessing, but my guess is it's cached in your wsgi server. I.e., upon initial creation an entry is made in the mailman.template table with a uri like https://example.com/mailman3/api/templates/list/list.example.com/list:user:… and when Mailman core wants the template, it gets that uri which I'm guessing is then cached in the wsgi server. Then, if the content is changed, the GET returns the old cached value instead of getting the new value from Postorius. If the template is deleted, the mailman.template table entry is deleted and at that point Mailman core will get the template from the file system following it's normal search rules, but if the template is recreated in Postorius, a new table entry is made with the same uri which may still get a cached template from the wsgi server. If this is correct, restarting mailman-web or whatever controls the wsgi server should fix it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 4 weeks

[MM3-users] Re: Hyperkitty import from mailman2

by Mark Sapiro

> > Now I wanted to try import from mailman2 mbox, so i did: > > python2 manage.py hyperkitty_import --settings settings --ignore-mtime > -v 3 --since 2010-01-01 -l test(a)list.domain.com /tmp/test.mbox > > It shows that it have sucessfully imported all emails and I can see them > from database (sqlite3), but I cannot see them from GUI (hyperkitty). > Only thing I can see is this inactive "test" list. > > I have tried that I create list before importing, still same result. I have done this several times for several different lists and it has always worked with no problems. I have always created the list first. I do not use any of the options other than -l. My settings location is built in to the django admin script I run. So what I run is equivalent to python2 manage.py hyperkitty_import --settings .. -l .. mbox Do you have cron set up to run the periodic django tasks as in @hourly python2 manage.py runjobs --settings settings hourly @daily python2 manage.py runjobs --settings settings daily @weekly python2 manage.py runjobs --settings settings weekly @monthly python2 manage.py runjobs --settings settings monthly @yearly python2 manage.py runjobs --settings settings yearly 0,15,30,45 * * * * python2 manage.py runjobs --settings settings quarter_hourly * * * * * python2 manage.py runjobs --settings settings minutely If not, did you run python2 manage.py update_index --settings settings after the hyperkitty_import? I'm actually not sure any of this will help since it should only affect the search index, not the message display. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 2 months

[MM3-users] Re: User settings triggers error

by Mark Sapiro

On 6/18/20 3:33 PM, Mark Dadgar wrote: > > Any thoughts on how to salvage ~20 years of list archives? The archives shouldn't be an issue. I don't think they are involved in the corruption, but anyway, hopefully you still have the archive mbox you imported. Then for the messages since then, you should be able to get a mbox from hyperkitty with something like https://example.com/hyperkitty/list/listname@example.com/export/arbitrary-n… with the obvious substitutions and appropriate start and end dates. The list is trickier. If you are going to start over with a clean install, and if you have a config.pck that you imported from MM 2.1, I suggest the following: Use the `mailman members` command to get a list of all members. Then depending on how much work you want to do, also get separate lists of plaintext and mime digest members and members with delivery disabled. Then on the new install, import the config.pck with `mailman import21` and import the archive mboxes with hyperkitty_import. Run `mailman members --sync` with the full current membership list, and record the [ADD]s. Then you can match the [ADD]s against the plain and mime digest members and those with delivery disabled and set their options. That's a lot to do, but it should get you close. On the other hand, if you can wait, we might be able to figure out how to fix this, and it's even possible the underlying issue isn't database corruption. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Moderator Approval Subscription template

by Mark Sapiro

On 2/8/21 5:55 PM, Brian Carpenter wrote: > Hey all, > > I am seeing a strange issue with the Moderator Approval Subscription > template. > > 1. First problem is that this template by default does not include a URL > to the list admin page of said mailing list. Mailman 2's notifications did. Mailman 2 was monolithic. Mailman 3 is Modular. Core, which sends this notice, doesn't know if you even have a web admin UI, much less how to access it. It has been suggested that we add a config setting for the web base URL and if that is set, include URLs in these messages and we may eventually do that, but in the mean time > 2. Problem 1 can be solved by editing the template and adding the List > Owner (admin) url to moderate the subscription. This is what you need to do. > However in the case of > long URLs, the URL is getting cut-off in Thunderbird. Not sure about > other email clients. That is an issue because the expanded template is filled and wrapped at column 70 with mailman.utilities.string.wrap(). However, you can avoid wrapping the URL by preceding it in the template with a space. Something like > Your authorization is required for a mailing list subscription request > approval: > > For: $member > List: $listname > > Visit > > https://list.redeacted.org/admin/list/oligodendroglioma.list.redacted.org > > to act on this request. Lines beginning with spaces aren't wrapped. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: FILTER_VHOST = True doesn't work fine with alias_domain

by Mark Sapiro

On 2/17/22 15:15, Élodie BOSSIER via Mailman-users wrote: > Hello, > > My mailman3 installation is now functional, but the config "FILTER_VHOST > = True" doesn't work fine when I define "alias_domain" for the 2 > domains. I need to define that because I need to get "postfix_vmap" file. > > As you can see, list from others domains are visible on this URL : > https://ml.franceserv.fr/postorius/lists/ > > I would like https://ml.franceserv.fr/postorius/lists/ and > https://ml.viticreation.fr/postorius/lists/ with their own lists. There are issues with FILTER_VHOST due to the fact that mailing lists do not have a web host attribute. This means when you go to HyperKitty or Postorius when FILTER_VHOST is True, we look up the domain record for the web host you are visiting and show you all the lists whose mail host matches the mail host for the web host domain. This has nothing to do with alias domains. What that means is if all your domains records have a unique mail host, FILTER_VHOST will work as you expect, but if multiple domains have the same mail host FILTER_VHOST will show you the lists for the current web host plus all those with a matching mail host. I.e. if in your case, the ml.franceserv.fr domain and the ml.viticreation.fr domain have the same mail host, FILTER_VHOST won't separate them. If they have different mail hosts FILTER_VHOST will separate them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: Mailman issues after re-boot

by Mark Sapiro

On 10/4/23 05:09, paulrubin37(a)gmail.com wrote: > Ok first I tried the force reinstall, that changed nothing. > > (venv) mailman@mail:~> pip install --force-reinstall psycopg2-binary\<2.9 > Collecting psycopg2-binary<2.9 > Using cached psycopg2_binary-2.8.6-cp311-cp311-linux_x86_64.whl You are forcing the version to be <2.9 which is why your venvs have 2.8.6. Note you are installing a cached version. That may be why it's broken. You could try ``` pip install --no-cache-dir --force-reinstall psycopg2-binary\<2.9 ``` or as I note below, if your Django is >=3.1 ``` pip install --no-cache-dir -U psycopg2-binary ``` ... > Here is what is in the file that is failing, If I read this right I need to check every single sub import. > > 50 > 51 from psycopg2._psycopg import ( # noqa > 52 BINARY, NUMBER, STRING, DATETIME, ROWID, > 53 > 54 Binary, Date, Time, Timestamp, > 55 DateFromTicks, TimeFromTicks, TimestampFromTicks, > 56 > 57 Error, Warning, DataError, DatabaseError, ProgrammingError, IntegrityError, > 58 InterfaceError, InternalError, NotSupportedError, OperationalError, > 59 > 60 _connect, apilevel, threadsafety, paramstyle, > 61 __version__, __libpq_version__, > 62 ) > 63 This is way too much detail. This psycopg2-binary is broken. You can't successfully import psycopg2 from it. You need to get a working psycopg2 installed rather than trying to fix your broken one. What is your Django version? The only reason for pinning psycopg2-binary<2.9 is for Django<3.1. See https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail…. If your Django is >=3.1 try in your venv ``` pip install -U psycopg2-binary ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Mark Sapiro

On 11/4/21 12:58 PM, Simon Coggins wrote: > > Please file an issue for this at > https://gitlab.com/mailman/mailman/-/issues<https://gitlab.com/mailman/mailman/-/issues> and I will try to find a > better solution. Your approach of munging Message-IDs will create other > issues. Consider a post to a list with direct CC to userx. userx > replies-all to the message received directly. the In-Reply-To of this > reply is the unmunged Message-ID which will affect threading in the > archives and other recipient's MUAs. I realize this is preferable to > losing the message, but I hope we can do better. > > > Yeah it’s not a great solution but it’s the quickest I could come up with that works “for us”. 99% of our lists are announcement lists only with minimal replies so while this will break some. I’m hoping it will give us enough time to wait out a proper fix. I’ve created a new issue #955 with as much detail as I think you’ll need. Let me know if you need any more. Thanks for filing the issue. I'll work on a solution. My current thinking is to add a `count` column to the message table, set the count to 1 when initially adding a message-id, increment the count when adding an existing message-id, decrement the count when deleting a message-id and only delete the entry and message when the count reaches 0. -- 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-users] Re: Getting connection timed out

by Mark Sapiro

On 5/22/21 11:29 AM, blackout69 wrote: > Hello everybody, > > for a couple of days I have been seeing several lines calling these on > /var/log/mail.log > > May 22 18:22:57 glugct postfix/qmgr[21205]: 0ACE641C1B: > from=<lug-bounces(a)catania.linux.it>, size=3698, nrcpt=9 (queue active) > May 22 18:23:06 glugct postfix/qmgr[27175]: 0ACE641C1B: > from=<lug-bounces(a)catania.linux.it>, size=3698, nrcpt=9 (queue active) > May 22 18:23:36 glugct postfix/smtp[27177]: 0ACE641C1B: > to=<myaddress(a)simail.it>, relay=none, delay=55152, > delays=55122/0.07/30/0, dsn=4.4.1, status=deferred (connect to > mail.simail.it[217.27.113.30]:25: Connection timed out) ... > But always on a single email address.What could it depend on?Probable > that the mail.simail.it server is blacklisted? It's probably not blacklisting. It's not getting that far. Your `glugct` is attempting to connect to port 25 at mail.simail.it and the connect is not being answered. Normal blacklisting will not occur until after the remote MTA answers the connect and determines the IP of the caller. And in any case, if it is some kind of blacklisting it is your `glugct` server that is blacklisted by mail.simail.it. I just did the following ``` $ telnet mail.simail.it 25 Trying 217.27.113.30... Connected to mail.simail.it. Escape character is '^]'. 220 mail.simail.it ESMTP ready. quit 221 mail.simail.it closing connection Connection closed by foreign host. ``` so it did answer my connect. In any case, this is not a Mailman issue. It is between Postfix on your server and the remote server at mail.simail.it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

Search results for query "sapiro"