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

[MM3-users] Re: config incoming email in my domain cpanel

by Mark Sapiro

On 08/03/2017 01:22 PM, Rafael Mora wrote: > El jue., 3 ago. 2017 a las 15:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: >> >> You need to forward port 25 for SMTP mail delivery and if you want the >> web UI (Postorius and HyperKitty) accessible from the outside, port 80 >> for http and/or port 443 for https >> < >> https://www.iana.org/assignments/service-names-port-numbers/service-names-p… >>> . >> > > I mean for incoming mail redirected from my hostgator hosting, because when > I suscribe an email address MM3 sends a confirmation email, so I have to > reply to be suscribed to the list. As I said, for mail delivery you need to forward port 25 to the Mailman server. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 7 months

[MM3-users] Re: Reason for Shunting

by Mark Sapiro

On 2/9/21 2:57 PM, Brian Carpenter wrote: > > On 2/9/21 5:25 PM, Mark Sapiro wrote: >> On 2/9/21 2:03 PM, Brian Carpenter wrote: >>> Is there a way to determine why a message keeps ending up in the shunt >>> queue? >>> >> >> Look in mailman.log for the `SHUNTING` message and the traceback that >> immediately preceeds it. > > > Thanks Mark. The reason was: > > Feb 09 16:40:11 2021 (2614) Uncaught runner exception: Multiple rows > were found for one_or_none() > > sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for > one_or_none() > > Feb 09 16:40:11 2021 (2614) SHUNTING: > 1612906811.2642436+cd8e97a66b6d0c2b73c2adde71a4914108c3e673 > > I have no idea what that means. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> and <https://gitlab.com/mailman/mailman/-/issues/657> -- 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: MM2 -> MM3 Migration

by Mark Sapiro

On 12/29/22 23:17, Odhiambo Washington wrote: > On Thu, Dec 29, 2022 at 10:39 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> The default without the since= option is to import only those messages >> from the mbox which are newer than the newest message in the existing >> archive which is exactly what you want. >> > > So I ended up using this and I can see the list metrics indicating that the > last post was on 29Dec22, but > I don't seem to be able to see those posts in the archives. If Postorius list metrics show the last post was 29 Dec, that was a post to the MM3 list and if it was archived, then running hyperkitty_import without a since= option will not import any messages older than that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: Clearing webserver cache - Nginx

by Mark Sapiro

On 8/6/24 09:33, Odhiambo Washington via Mailman-users wrote: > On Tue, Aug 6, 2024 at 7:18 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 8/6/24 00:24, Odhiambo Washington via Mailman-users wrote: >>> >>> In any case, here is my virtualhost config: >> >> It looks OK. >> >> I suggest you run >> >> mailman-web collectstatic --clear >> mailman-web compress >> > > Done. > > However, I still see the errors in Nginx logs: > ``` > root@eu:~# tail -f /var/log/nginx/mm3-lists_error.log > 2024/08/06 18:52:54 [error] 37221#37221: *53355 open() > "/opt/mailman/mm/static/CACHE/css/output.158acc288604.css" failed (2: No > such file or directory), ... Is this with only one browser? It's a long shot, but clearing browser cache might work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: Documentation for transferiering a list between mm3 and mm3

by Mark Sapiro

On 2/26/21 11:03 AM, Morris Jones wrote: > On 2/26/2021 10:55 AM, Mark Sapiro wrote: >> Brian is correct. Essentially, you would need to run database queries to >> get all the relevant data from the database and then add it to the >> database of the new instance. A tool could be created to do the export >> and import, but it doesn't currently exist unless some user has >> developed one and not reported it. > > Would it be unreasonable to do a database dump on the old instance and a > restore on the new one? The question is transferring a `list`. I took that to mean transferring one of multiple lists to another installation which may also have other lists. -- 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: MM3 generates long lines?

by Mark Sapiro

On 6/23/21 7:10 AM, Andreas Barth wrote: > * Mark Sapiro (mark(a)msapiro.net) [210623 15:34]: >> We would need to see the email itself in order to begin to >> understand if this is a Mailman issue or some issue withe the mail >> as received by Mailman. >> >> Assuming the prototype archiver is enabled, you should be able to >> find the messages in Mailman's var/archives/prototype/LIST/new/ >> directory. > > One question, in order to ease debugging, can I forcefully activate > the prototype archiver from the global configuration, or do I need to > do that on a per-list basis? You need [archiver.prototype] enable: yes in mailman.cfg. I'm not sure if that's enough for existing lists. You may need to activate the archiver per list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Link in the top-left corner of Hyperkitty

by Mark Sapiro

On 5/8/20 8:06 AM, Seth Seeger wrote: > On May 8, 2020, at 10:58 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > >> You have to edit the display name for the domain in the Django web admin >> Sites section. > > Huh. I had it properly set for the domain that is active, but it wasn’t taking affect. I changed it for the (old) test site, and it changed it. So the name that is showing doesn’t match the domain name that I was changing it for. It should show the display name corresponding to the domain name that matches the domain in the URL that you go to. If this doesn't seem correct, perhaps there is some issue with the way you are proxying in your web server. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: How to fix: [Django] ERROR (EXTERNAL IP)

by Mark Sapiro

On 10/31/24 21:18, Jigme Datse wrote: > On Thu, 31 Oct 2024 20:07:00 -0700 > Mark Sapiro <mark(a)msapiro.net> wrote: > >> What's in Django's logs? >> > > Attached logs (I hope that works). A couple are currently empty? I suspect the django_q error is because you need to run `django-admin migrate`[1], but it isn't responsible for your inability to get list pages. Again, what's in Django's logs? These are not the uwsgi logs. If you don't know where they are, look in your Django settings in the LOGGING definition for the filename setting for the file handler. [1] The actual name of the Django admin command may be `django-admin`, `python manage.py` or something else depending on how Mailman web is installed. -- 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

[MM3-users] Re: Cannot connect to SMTP server

by Mark Sapiro

On 8/13/22 15:57, Mark Sapiro wrote: > > Have you put templates in Mailman's var/templates directory (possibly > named /var/lib/mailman/templates in the debian package). If so, can the > Mailman user (I think `list` in a debian package) find and read them? I think that should be /var/lib/mailman3/templates in the debian package. Also, all that directory and all its subordinate directories and files should be user:group list:list. If you ever ran Mailman core as `root` and not as user `list`, this can create things that `list` can't read. See these threads: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…, https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… and https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… and perhaps others from this search https://lists.mailman3.org/archives/search?q=Cannot+connect+to+SMTP+server -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Mailman web interface / uwsgi

by Mark Sapiro

On 11/27/22 10:38, Jan Eden via Mailman-users wrote: > On 2022-11-27 07:08, Mark Sapiro wrote: > >> In that case, it's probably just an oversight. The instructions at >> https://docs.mailman3.org/en/latest/install/virtualenv.html are an evolution >> of a process that started with an obsolete mailman-bundler package, the >> initial iterations of which are documented at >> https://wiki.list.org/x/17891998 and prior revisions of that page. >> https://docs.mailman3.org/en/latest/install/virtualenv.html is still a work >> in progress. > > Ok – as long as I can consolidate all settings in one place for backup > purposes (with symlinks, if need be), any layout is fine. I think it was an oversight. See https://gitlab.com/mailman/mailman-suite-doc/-/issues/46 which I fixed with https://gitlab.com/mailman/mailman-suite-doc/-/merge_requests/121 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

Search results for query "sapiro"