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

[MM3-users] Getting connection timed out

by blackout69

Il 22/05/21 23:52, Mark Sapiro ha scritto: > 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. Thanks Mark for the reply, I had already checked with the telnet command on port 25 and everything is fine. The suspicion of the blacklist came to me, but now, after checking https://mxtoolbox.com/blacklists.aspx I saw that the mail.simail.it server is in the SORBS SPAM blacklist. Because my lists work fine on any other mailing address. I also checked my email server reputation at https://www.mail-tester.com and I get 10/10 Apparently it doesn't depend on my postfix server. In this case, what strategy do you recommend? Thank you -- blackout69

4 years, 9 months

[MM3-users] Re: Mailman3 reinstall fail, need some help

by Yvan ♞

Maybe an idea of my problem as I have pgadmin app installed, it could be in conflict to create a postgresql db? Le 13/03/2022 à 13:46, Yvan ♞ a écrit : > Yes, always this folder file problem, if I create the folder, when > trying install > answer is "mailman allready installed" > https://paste.yunohost.org/raw/avaweyiqom > Still searching... But I'm really not an expert... > Yvan > > Le 12/03/2022 à 21:32, Mark Sapiro a écrit : >> On 3/12/22 08:38, Yvan ♞ wrote: >>> Yes it's debian and I have root access but it's a more "user >>> friendly" server release. >>> I tryed this but it block >>> https://github.com/YunoHost-Apps/mailman3_ynh/blob/master/README.md >>> >>> https://yunohost.org/en/administrate/whatisyunohost >>> Sincerely >> >> I don't read French very well, but your original logs at >> https://paste.yunohost.org/raw/xiqoyajegi and >> https://paste.yunohost.org/raw/hujesebita show installation failing >> because it fails to create /etc/mailman3/mailman.cfg. >> >> This is either an issue with the Debian package or the YunoHost >> installer or an incompatibility between them. >> >> I would go first to YunoHost for help and then to Debian if necessary. >> > _______________________________________________ > 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/

4 years

[MM3-users] Re: applying patch 1130

by David Newman

On 8/21/23 7:57 PM, Mark Sapiro wrote: > On 8/21/23 12:45 PM, David Newman wrote: >> >> I'm looking to patch an existing production server running 3.3.8 so >> it will be able to start under Python 3.11 on Debian 12. Thanks in >> advance for additional clues on what seems like a fairly standard >> problem. > > Since !1130 is merged, just `pip install` from the gitlab head. > ``` > pip install git+https://gitlab.com/mailman/mailman@head Perhaps something else is needed first? This is on a Debian 12 system upgraded from 11, with MM3 3.3.8 installed in a venv. (venv) mailman@x12:~$ pip install git+https://gitlab.com/mailman/mailman@head Collecting git+https://gitlab.com/mailman/mailman@head Cloning https://gitlab.com/mailman/mailman (to revision head) to /tmp/pip-req-build-wjge_v67 Running command git clone --filter=blob:none --quiet https://gitlab.com/mailman/mailman /tmp/pip-req-build-wjge_v67 warning: redirecting to https://gitlab.com/mailman/mailman.git/ WARNING: Did not find branch or tag 'head', assuming revision or ref. Running command git checkout -q head error: pathspec 'head' did not match any file(s) known to git error: subprocess-exited-with-error × git checkout -q head did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip. error: subprocess-exited-with-error × git checkout -q head did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip. Thanks dn

2 years, 6 months

[MM3-users] Re: Can't post to my own list from HyperKitty

by MegaBrutal

Mark Sapiro <mark(a)msapiro.net> ezt írta (időpont: 2025. ápr. 7., H, 19:23): > What is the exact email address that you are logging on to the web UI > with. Does it match exactly with the address of a list member or are > there mixed-case differences? You might try an interaction like this: > ``` > mailman-web shell > Python 3.12.8 (main, Dec 21 2024, 12:52:28) [GCC 9.4.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) > >>> from django_mailman3.lib.mailman import get_mailman_client > >>> client = get_mailman_client() > >>> list_id = 'test.example.com' # your actual list_id > >>> rest_list = client.get_list(list_id) > >>> email = 'user(a)example.com' # your actual email > >>> member = rest_list.get_member(email) > >>> member > This should print something like > <Member 'user(a)example.com' on 'test.example.com' with role 'member'> > ``` > This is exactly what HyperKitty is doing except in your case > rest_list.get_member(email) is throwing a ValueError exception instead > of returning the member. I get: <Member 'megabrutal(a)gmail.com' on 'the.correct.list.address' with role 'member'> So it's even weirder – however, I'm really not sure if this is the address HyperKitty is checking for, as I have 3 attached to my account! How may I know which one it's trying to use?

11 months, 1 week

[MM3-users] Re: spanish localization

by Victoriano Giralt

On Fri, 2021-02-12 at 12:24 -0800, Mark Sapiro wrote: > > If the manage.py in the directory in which you ran this is the > correct one for your Mailman Django project, I don't know why it > didn't work. Me neither :-( That's why I asked, and probably Guillermo, as well. > Is your Mailman installed in a virtualenv? If so, was the virtualenv > activated? No virtualenv. Mine is deployed using system python on a CentOS 7 system, toghether with another in house developed low requirements Django project, both served by uWSGI vassals. And then, all of a sudden, while I was writting this, it dawned on me! Postorius, Hyperkitty and django-mailman are installed with pip, so, the end up in the site-packages directory (usually /usr/local/lib/python3.x/site-packages), but, normally, django projects are deployed somewhere in the web server hierarchy (/var/ww/django in my case, due to old personal tastes), and applications properly defined in the settings.py for the project. So, the message files are out of reach for manage.py. Changing to /usr/local/lib/python3.x/site-packages/X (with X being postorius, hyperkitty and django_mailman3) and using django-admin compilemessages all works! Thanks for pushing my thoughts in the right direction! -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

5 years, 1 month

[MM3-users] Re: Postorius no connection to REST API

by Richard Rosner

Mark Sapiro wrote: > > Because those aren't the settings that matter for this. > What if anything are your settings in the mailman.cfg [webservice] > section for > hostname: > port: > admin_user: > admin_pass: > use_https: > (defaults in our distribution are localhost, 8001, restadmin, restpass > and no respectively - I don't know if Debian changes these). > These need to match the Django settings > MAILMAN_REST_API_URL = 'http://localhost:8001' > MAILMAN_REST_API_USER = 'restadmin' > MAILMAN_REST_API_PASS = 'restpass' They do match. Even the port (still on 8001). > > The REST API is apparently not listening on the host/port this is trying > to connest to. Apparently. The question is why. > > What is executing the manage.py command to start Django. Is it user list? Probably. It depends on who is calling it. I understand too little of the new architecture. But mailman3.service is run as list, mailman3-web.service as root. > > I don't use uwsgi and know little about it so I don't know what the Unix > domain socket /run/mailman3-web/uwsgi.sock connection is for, but this > appears to be some miscunfiguration between apache and uwsgi. > Normally, in an apache/uwsgi configuration, apache proxies to uwsgi via > tcp port 8000 and uwsgi is configured with > [uwsgi] > uwsgi-socket = 0.0.0.0:8000 I too have no experience in the combination ow apache and uwsgi. The only other uwsgi app I'm running is on another server and running under nginx.

4 years, 7 months

[MM3-users] Re: How to Increase outgoing mail volume for Mailman 3

by Brian Carpenter

On 11/10/20 4:40 PM, Mark Sapiro wrote: > On 11/10/20 1:22 PM, Mark Dadgar wrote: >> Brian specified: >> >> verp_personalized_deliveries: no >> >> Doesn’t that default back to regular mass delivery, as opposed to individualized VERPed envelopes, which mandates individual deliveries? > > That depends on the setting of verp_delivery_interval. If > verp_delivery_interval = 1, every message will be VERPed regardless of > verp_personalized_deliveries. If verp_delivery_interval = 0 and > verp_personalized_deliveries = no, deliveries won't be VERPed as you > note. If verp_delivery_interval = 0 and verp_personalized_deliveries = > yes, only personalized deliveries (i.e. individual messages, not > digests, from lists with Personalization enabled) will be VERPed. > > The theory is VERPing has a cost because it requires a separate message > sent to each recipient rather than a single message with multiple > recipients, but personalization also requires a separate message sent to > each recipient, so those can be VERPed at no extra cost. > > But to be clear, automated bounce processing does not require VERP. It > just works a tiny bit more reliably with VERP. We actually enable VERP by default on all new installations of Mailman 3 as we don't see a real performance hit and its benefits are generally very good. This new list however was a whole different beast. Also due to the nature of the list, the benefits of VERPing pales in comparison to the timeliness of the mail being sent. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 4 months

[MM3-users] Re: spanish localization

by Victoriano Giralt

On Fri, 2021-02-12 at 12:36 -0800, Mark Sapiro wrote: > > Why do you say the .mo files are old. The timestamps are all Feb 3 > 02:47 which is when the package was built for PyPI. Because my brain goes faster than my fingers and I say the reverse of what I mean. I meant .mo files, all .po where properly dated, and I reversed the meaning of my thoughs while typing. Thanks for brining my confussion to my (and everybody's) attention, and my appologies for the noise. > When things are changed on weblate, we get automatically generated > merge requests to update our source. We don't always merge them > immediately, but we certainly do merge all the outstanding ones > before making a release. I'm 95% certain that I edited messages after Nov 7th in the Spanish translation of both mailman, postorius and hyperkitty, but the .po file is dated Nov 7h. Actually, I did a review of outstanding strings when Abhilash annonced the RC for the current version. That is why I was bit surprised. But then, it may be me and my faint memory. And, of course, I'm very grateful and happy with all the work that is being done on Mailman3. -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

5 years, 1 month

[MM3-users] Re: aborted connection

by Sandor Dibuz

On 2/20/22 01:56, Mark Sapiro wrote: > > First, If your Mailman core version is >= 3.3.5, you shouldn't be > running gatenews via cron. Mailman's nntp runner runs it. See > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… > > But, that probably isn't it because in Mailman >= 3.3.5, running > gatenews via cron should produce this error > > The gatenews command is run periodically by the nntp runner. > If you are running it via cron, you should remove it from the crontab. > If you want to run it manually, set _MAILMAN_GATENEWS_NNTP in the > environment. > > > However, since you have no lists using a news->mail gateway, you don't > need to run gatenews at all so just remove it from the crontab. I installed Mm3 from Debian stable distro packages as one of the suggested installations methods in Mm3 docs. It's a bit of dated though I know but it was the easiest and fastest. Mailman Core Version GNU Mailman 3.3.3 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] So I disabled gatenews cron job. Maybe later I bite the bullet and upgrade to a recent version (either venv or docker haven't decided yet) but will have to learn how to avoid conflicts with already installed deb packages first. So far so good and everything works, have to check changelogs if an upgrade is worth it. Thank you all your help, Mark. Sanyi

4 years

[MM3-users] Re: Permission denied for fulltext_index

by Jan Eden

On 2022-11-27 08:01, Mark Sapiro wrote: > On 11/27/22 00:35, Jan Eden via Mailman-users wrote: > > > > – but the existing directory /opt/mailman/fulltext_index (and its > > contents) are readable and writeable by mailman:mailman: > > > > > drwxrwxr-x 2 mailman mailman 4096 Nov 27 08:00 fulltext_index/ > > > > > > -rw-rw-r-- 1 mailman mailman 4473 Nov 27 08:00 _MAIN_65.toc > > > -rw-rw-r-- 1 mailman mailman 15456 Nov 27 08:00 MAIN_bc0cs2aohovftat6.seg > > > -rw-rw-r-- 1 mailman mailman 15454 Nov 27 06:00 MAIN_brbo8i8edmlz0za4.seg > > > -rw-rw-r-- 1 mailman mailman 15462 Nov 27 07:00 MAIN_ewnemc7lsnodd3y7.seg > > > -rw-rw-r-- 1 mailman mailman 157324 Nov 27 04:00 MAIN_qag60g1rrumshtc2.seg > > > -rw-rw-r-- 1 mailman mailman 15459 Nov 27 05:00 MAIN_w6e0ohurasusy61d.seg > > > -rwxrwxr-x 1 mailman mailman 0 Nov 24 16:00 MAIN_WRITELOCK* > > > > I fail to see where haystack tries (and fails) to create the directory. > > FWIW, deleting threads is not a problem. > > It is uwsgi trying to do this. What user is it running as? Maybe you need to > add that user to the `mailman` group. That's what baffles me – uwsgi is run as the mailman user: mailman 3904667 1.3 0.5 129516 62188 ? Ss 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini mailman 3904668 0.0 0.3 203248 48796 ? Sl 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini mailman 3904670 0.8 0.6 220436 74464 ? Sl 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini - Jan

3 years, 3 months

Search results for query "sapiro"