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

[MM3-users] Re: using SSH/TLS with external MTA

by Odhiambo Washington

On Sat, Jul 27, 2024 at 11:34 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/27/24 13:05, Odhiambo Washington via Mailman-users wrote: > > > > ASMTP works on the premise of "we can relay mail for you if we can > > authenticate you with certain credentials" > > Adding the IP to "hosts we can relay mail for" negates the need to > > authenticate, IMHO. > > So I am still waiting for how MM3 does ASMTP. Does it? > > > If by ASMTP, you mean SMTP AUTH, Mailman does it if smtp_user: and > smtp_pass: are provided in mailman.cfg. > > > I agree that an authenticated user should be able to submit mail to be > relayed. Just guessing here, but perhaps the issue is the OP is > submitting to the deprecated port 465 instead of 587. > Port 465 is not quite depreciated. It's the decision of the Admin to decide to listen on/and accept SMTP AUTH on which port. On the servers I run, and based on Exim as the MTA, I accept SMTP AUTH On ports 465, 587 and 2525 (this is meant to subvert some ISPs!). But let's await Roland's response. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 10 months

[MM3-users] Re: Adding members to a mailman3 mailing list

by Onyeibo Oku

On Wed, 14 Oct 2020 08:53:23 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > > #!/bin/bash > exec /opt/mailman/mm/venv/bin/mailman \ > -C "/opt/mailman/mm/mailman.cfg" \ > $@ > Greetings Mark, I gave up on setting up mailman using option #2 while following https://docs.mailman3.org/en/latest/install/install.html (there are lots of unknowns on that route. Certainly, the packagers are considering a lot of things that are not immediately apparent to users). Perhaps, we will see elaborate guides/docs soon. In the meantime, I moved to option #3 (recommended for production). I hit a grey area when setting up the virtual environment. At https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…, I see: $ cd /opt/mailman $ python3 -m venv venv The documentation imply that a 'user' creates the virtual environment but is not explicit about that 'user'. OUTPUT: Error: [Errno 13] Permission denied: '/opt/mailman/venv' This is expected. Which makes me wonder ... hmm, how did you do it? (1) Is it better to have a dedicated user (say 'mailman') then use that while following the docs? I see a lot of docs referring to a 'mailman' user. Installing mailman3 from distribution repository introduced a 'mailman' user to my box (with special UID). There has to be reasons for that. (2) Should the setup proceed with 'root'? (why do I get the feeling that this is not the design?) (3) How about using an already existing local user? What are the implications? Regards Onyeibo

5 years, 8 months

[MM3-users] Re: How to delete non-users

by Allan Hansen

Sure: >>> lm = getUtility(IListManager) >>> for l in lm: ... print(l.posting_address) ... >>> Nothing here, either. Yours, Allan On 9/17/22, 10:30 , "Mark Sapiro" <mark(a)msapiro.net> wrote: On 9/17/22 10:03, Allan Hansen wrote: > Hi Mike, > > Yes, the users can be subscribed, but they think that they can't because it seems they are until the moderator accepts them. > > I tried your script again, with nothing happening. So I tried this: > >>>> >>>> a = 1 >>>> b = 1 >>>> for l in lm: > ... print(a) > ... a = a+1 > ... for nm in l.nonmembers.members: > ... print(b) > ... b = b + 1 > ... nm.unsubscribe() > ... >>>> commit() >>>> print(a) > 1 >>>> print(b) > 1 > > > It appears that lm can't see the lists (I have 50+ of them). Did you start with lm = getUtility(IListManager) ? What if you do ``` >>> lm = getUtility(IListManager) >>> for l in lm: ... print(l.posting_address) ... ``` That should print the posting address for all the lists. What does `mailman info` show? In particular, for `config file:` -- 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/

3 years, 9 months

[MM3-users] Re: Footer variables

by Washington Odhiambo

On Mon, Mar 2, 2026 at 8:23 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/2/26 05:03, Washington Odhiambo via Mailman-users wrote: > > On Mon, Mar 2, 2026 at 3:41 PM Stephen J. Turnbull <steve(a)turnbull.jp> > > wrote: >> > >> Have you tried using "$hyperkitty_url" instead of "${hyperkitty_url}"? > >> > > > > I have now removed the curly braces. Let me see what follows. > > > That shouldn't matter. It should work with or without the curly braces. > > Is there anything relevant in mailman.log? Does Mailman have permission > to access > /opt/mailman/mm/var/templates/lists/ > kictanet.lists.kictanet.or.ke/en/list:member:regular:footer.txt? > I will have to check the mailman.log. What should I look for? Right now it looks so clean - without anything to worry about. Yes. all files in /optmailman/ are owned by mailman:mailman In the OP you said "in my posts, it's blank". Do you mean the entire > footer is blank or is it just that ${hyperkitty_url} is replaced with > nothing and the rest of the footer is OK? > Only the ${hyperkitty_url} is replaced with nothing. I suppose there may be another way to get the end result, no? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

3 months, 2 weeks

[MM3-users] Re: Change digest frequency and default threshold

by Henrik Rasmussen

Mark Sapiro wrote: > On 9/21/18 6:21 AM, Henrik Rasmussen wrote: > > When Digest Size Threshold is not reached, mails seems to be sent > > according to digest_volume_frequency': which is set to 'monthly'. The web > > interface doesn't seem to have a setting for this. > > No. digest_volume_frequency only controls how often the digest volume > number increments (and issue number resets). > > In order to send periodic digests, you need to run 'mailman digests > --periodic' via cron. Currently I am running Mailman version 3.2.0a1 which doesn't seem to have a --periodic option. When running "docker exec mailman-core mailman digests --send --verbose -l listname(a)lists.example.com", output is "listname.lists.example.com sent volume 11, number 4" and this increases each time, but even I do approve held mails, none are sent (according to the smtp.log and docker logs posrfix). As I understand, using --sent should send a digest immediately (except when used with --dry-run). As the default Digest size threshold was 30KB, making very small digests being sent, I increased this (for test) to 5000 KB (or is it Kilo bits, as the text says "How big in Kb should a digest be before it gets sent out?"? Could Digest size threshold have any impact on why no digests are sent even I run "docker exec mailman-core mailman digests --send --verbose -l listname(a)lists.example.com" or is this an issue in the version I am using? -- Henrik Rasmussen

7 years, 8 months

[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

5 years

[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, 3 months

[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, 9 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?

1 year, 2 months

[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, 4 months

Search results for query "sapiro"