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

[MM3-users] Re: where to configure max_days_to_hold on MM3 GUI interface?

by Shashikanth Komandoor

Thank you Abilash Raj for your help which made me step ahead. With your help, I have written a for loop as below which makes all the lists on my Mailman 3 box set the configuration of max_days_to_hold as 1 and of course I am successful in setting so. And the for loop is as below: *for listid in `curl -u restadmin:restpass -X GET http://localhost:8001/3.1/lists <http://localhost:8001/3.1/lists> | python -mjson.tool| grep "list_id" | awk -F"\"" '{print $4}'` * *do * * curl -u restadmin:restpass -X PATCH http://localhost:8001/3.1/lists/$listid/config <http://localhost:8001/3.1/lists/$listid/config> -d max_days_to_hold='1'* *done* With the above script I am able to set the value of max_days_to_hold as required but how to check manually and make my held messages discarded automatically which are after the specified period configured for max_days_to_hold. If I am able to do it manually I can be confident to take in to production so that the held messages after a specific period would not be appeared under "held messages" tab. On Sat, Feb 1, 2020 at 11:14 PM Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Sat, Feb 1, 2020, at 5:27 AM, Shashikanth Komandoor wrote: > > Hello Mark, > > > > Thanks for helping me for moving ahead in my project. > > > > Troubling you again, I would like to put another request at you. > > > > As per your suggestion, I am trying to configure my list > > configuration through REST API for specially the parameter like > > max_days_to_hold as it is not available through interface and I am > > following the official links of mailman 3 i.e > > > https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/listconf.html > > > > But I am getting "name is not defined" sort of errors as below: > > > > > > > > > > > > *>>> dump_json('http://localhost:9001/3.0/lists/ > > <http://localhost:9001/3.0/lists/>','ant(a)example.com/config > > <http://ant@example.com/config>',dict(display_name='My > > List'),'PATCH')Traceback (most recent call last): File "<stdin>", line > 1, > > in <module>NameError: name 'dump_json' is not defined>>>* > > > > Actually I am new to REST API but hope this is the only issue > that > > is preventing me to go ahead. > > > > Could you please help me by saying how should I handle this so > that > > I should be able to configure *max_days_to_hold* of a list or multiple ? > > > > > dump_json is basically a Python function which sends the request to the > URL you add as the first parameter (GET, if any data isn't specified and > uses POST if data is specified or explicitly define the PATCH or method > like you have above) and prints the json response. > > You can easily do the same using curl with the right authorization > headers, with something like: > > > $ curl -u restadmin:restpass -X PATCH \ > http://localhost:8001/3.1/lists/somelist.example.com/config -d > display_name='Patched Name' > > > Note that "restadmin:restpass" is the username password that you have set > in your mailman.cfg. > > If you do want to use Python, you can just use a regular PATCH request > using requests or standard library urllib3. > > Finally, dump_json is documented here: > https://mailman.readthedocs.io/en/latest/src/mailman/docs/documentation.htm… > > > > On Wed, Jan 29, 2020 at 11:20 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > > > On 1/28/20 8:42 PM, Shashikanth Komandoor wrote: > > > > > > > > But I could see that parameter value configurable on MM2 GUI > > > > interface in General Options but I don't see the same on the MM3 GUI > > > > interface. > > > > > > > > > There are many core settings not (yet) exposed in Postorius. > > > max_days_to_hold. is one of them. It can be set via `mailman shell` or > > > via the REST API > > > < > > > > https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/rest.html#re… > > > >. > > > > > > -- > > > 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/ > > > > > > > > > -- > > Thanks & Regards, > > Shashi Kanth.K > > 9052671936 > > _______________________________________________ > > 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) > _______________________________________________ > 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 & Regards, Shashi Kanth.K 9052671936

5 years, 4 months

[MM3-users] Re: User settings triggers error

by Mark Dadgar

On Jun 28, 2020, at 4:22 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > If I'm reading the above correctly, it appears that there is a message > in the archive database whose message_id value is > 'BYAPR02MB5976132151FF19510269C44CB3940(a)BYAPR02MB5976.namprd02.prod.outlook.com>'. > The trailing '>' is causing HyperKitty's Email.as_message() method to > try to set a value of > '<BYAPR02MB5976132151FF19510269C44CB3940(a)BYAPR02MB5976.namprd02.prod.outlook.com>>'. > > Or maybe there's leading white space in the value, or both. > > Try the following patch. > > > --- a/hyperkitty/models/email.py > +++ b/hyperkitty/models/email.py > @@ -24,7 +24,7 @@ import logging > import os > import re > from email.message import EmailMessage > -from email.utils import formataddr > +from email.utils import formataddr, make_msgid > > from django.conf import settings > from django.db import IntegrityError, models > @@ -175,7 +175,12 @@ class Email(models.Model): > header_date = self.date.astimezone(tz).replace(microsecond=0) > # Date format: http://tools.ietf.org/html/rfc5322#section-3.3 > msg["Date"] = header_date.strftime("%a, %d %b %Y %H:%M:%S %z") > - msg["Message-ID"] = "<%s>" % self.message_id > + try: > + msg["Message-ID"] = "<%s>" % re.sub('[<>\s]', '', > + self.message_id) > + except: > + msg["Message-ID"] = make_msgid() > if self.in_reply_to: > msg["In-Reply-To"] = unfold(self.in_reply_to) > The patch does not apply cleanly against /usr/lib/python3/dist-packages/hyperkitty/models/email.py patching file email.py patch: **** malformed patch at line 4: import os I am assuming that this is because I am running the Ubuntu packages, which are a year down-rev: Mailman Core Version GNU Mailman 3.2.2 (La Villa Strangiato) Mailman Core API Version 3.0 Mailman Core Python Version 3.8.2 (default, Apr 27 2020, 15:53:34) [GCC 9.3.0] - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years

[MM3-users] Re: Timeout error on anonymous subscribe

by Gerald Vogt

On 23.10.24 21:35, Mark Sapiro wrote: > On 10/22/24 23:07, Gerald Vogt wrote: >> >> For testing I have set >> >> POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.example.org' >> >> to the URL of our main domain, however, if I test an anonymous >> subscribe through the list info page I still get the timeout error > > This will have no effect unless you delete and recreate the template in > Postorius because simple changing the setting won't change the `uri` in > the template table. O.K. Did that. Now the uri in mailman.template is https://lists.example.org/mailman3/api/templates/list/community.lists.examp… However, it doesn't change the timeout issue, except now the error is HTTPSConnectionPool(host='lists.example.org', port=443): Read timed out. (read timeout=5) instead of localhost:8000. >> I can access http://localhost:8000/mailman3/api/templates/list/ >> community.lists.example.com/list:user:action:subscribe with curl and >> immediately get the response. > > Can you do that as the Mailman user?, e.g. > ``` > sudo -u mailman curl http://localhost:8000/mailman3/api/templates/list/ > community.lists.example.com/list:user:action:subscribe > ``` > assuming the Mailman user is `mailman`. I don't quite understand the relevance of the user accessing the localhost tcp port. Any local user can do that. I can access the template content with curl http://localhost:8000/mailman3/api/templates/list/community.lists.example.c… as well as curl http://lists.example.org/mailman3/api/templates/list/community.lists.exampl… as any user on the mailman server. And I can use the latter to access the template from anywhere as it's a public server. In any case, curl immediately returns the content. There is no delay. Thanks, Gerald

8 months, 1 week

[MM3-users] Re: Template's encoding setup

by Ugnius S

Hi. I am not sure, maybe it could be another topic about header and footer, but I have met one additional issue related to that. This noticed only on HTML text messages. If message comes in HTML the header does not add extra <enter> new line, new paragraph and footer as well. For example if message body has no additional, list's decorated message looks next: TEST HEADER _____________________Hello, text text text, pictures, text regards Ugnius____________________ TEST FOOTER I have tried to add more empty lines in "The footer for a regular (non-digest) message.", but mailman removes these empty lines. Work around is put dot "." and then several empty lines. Mark, I have found Your post about HTML headers and footers: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… YES, that works good, I have tested it, but only in cases if message comes in HTML. If sender sends plain text message, mailman adds footer with all HTML code: <BR>__________________<BR> <B> LIST NAME </B> Could it be possible that decorate.py would recognise message and if it has HTML text body, then just would add header/footer and if not (if message body is plain text) , then would strip header/footer "html to plain text" may removing html code from it? Kind regards Ugnius 2019-09-14, št, 23:07 Ugnius S <ugniusviln(a)gmail.com> rašė: > Mark, You were 100% right for fixing. I was not sure what the > language setting were on list creating, but one of the lists was created a > day ago and I was doubt about it a little. So I made test: I have checked > that default language is lt, and then I created the new list for testing. > I had language issues with the HTML as well. Your recipe helped to resolve > the issue. :) I fixed all my lists. > I have stopped the mailman (just in case), than executed as You had told: > > $ mailman shell -l test(a)example.com > Welcome to the GNU Mailman shell > The variable 'm' is the test(a)example.com mailing list > >>> m.preferred_language > <Language [en] English (USA)> > >>> m.preferred_language = 'lt' > >>> > <Ctrl>+D > > Thank You very much. This fix made magic. > > Kind regards > Ugnius > > > > 2019-09-14, št, 20:20 Mark Sapiro <mark(a)msapiro.net> rašė: > >> On 9/14/19 4:06 AM, Ugnius S wrote: >> >> > Yes, I have made several tests. I have set charset: iso-8859-13 >> > and default_language: lt in mailman.cfg. >> >> If you created the list before you set default_language: lt in >> mailman.cfg, the list's preferred_language is possibly 'en;' with >> character set us-ascii. >> >> >> > (Also I have set LANGUAGE_CODE = 'lt' in the settings_local.py, but I >> think >> > it is not related to this case.) >> >> >> Yes, LANGUAGE_CODE in settings_local.py is not relevant to this. >> >> >> > I have tried to set utf-8 as well in mailman.cfg as well. And I can >> > confirm - in all tested cases >> > text characters are correct (in footer as well) if sender sends text >> only. >> >> OK >> >> >> > If sender sends message in HTML (mostly all users send) then no >> > matter what the encoding is set in my mailman's >> > configuration or iso-8859-13, or utf-8 message body looks correct, but >> in >> > footer all national characters are replaced with >> > question marks " ? ". >> >> >> The addition of the footer is done by mailman/handlers/decorate.py. In >> the plain text case the message body is converted to unicode, the >> unicode footer is appended to the body and the new body is encoded for >> transmission. The encoding is the first of the list's character set, the >> incoming message's character set or utf-8 which produces no error. >> >> >> In the case where the incoming message is not a single plain text >> message part, the footer is added as a separate MIME part with the >> unicode footer encoded in the list's character set with >> errors='replace'. This is what produces the '?' characters. I suspect >> this happens because the list's preferred_language is 'en' with >> character set us-ascii. >> >> try running Mailman's >> >> bin/mailman shell -l your_list@domain >> >> at the prompt enter >> >> m.preferred_language >> >> if the response is not >> >> <Language [lt] Lithuanian> >> >> do >> >> m.preferred_language = 'lt' >> >> and then control-D to exit. >> >> -- >> 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/ >> >

5 years, 9 months

[MM3-users] [Solved] PAM error (was Re: Re: OK, so I backed out completely and re-installed....)

by Bill Oliver

On Wed, 2024-10-16 at 12:19 -0700, Mark Sapiro wrote: > On 10/16/24 10:26, Bill Oliver wrote: > > > > 1) I set up a mailinglist (tradfp(a)forensicpath.us) for "old school" > > forensic pathologists to discuss cases. > > > Does the forensicpath.us domain have an alias_domain configured in > mailman causing mailman to create > /opt/mailman/mm/var/data/postfix_vmap > and /opt/mailman/mm/var/data/postfix_vmap.db? You need this. Yes, I created a "lists.forensicpath.us" early on. > > > > In my previous attempt, I added > > > > hash:/opt/mailman/mm/var/data/postfix_lmtp > > > > to both virtual_mailbox_maps and virtual_alias_maps, but I haven't > > done that yet here. I thought I'd ask and make sure I should. > > > > Should that be my next step? > > You should add hash:/opt/mailman/mm/var/data/postfix_vmap to > virtual_alias_maps only. Done. I started getting the disappearing mail problem again, though none of the references to errors from the changes I made originally. After spending a few hours going over debug files, I noticed that I kept getting a pam error. The mails were getting rejected over authentication errors. It turns out it was all a permissions problem with /sbin/unix_chkpwd. Apparently the sticky bit was not set correctly on installation. Here's a discussion of the problem: https://unix.stackexchange.com/questions/422411/pam-authentication-failure-… I still don't understand why this was a problem with mailman and not with "regular" mail, but doing the "chmod u+s /sbin/unix_chkpwd" resulted in things magically working just like it's supposed to. Thanks for the help! billo

8 months, 2 weeks

[MM3-users] Re: MM2.1 -> MM3.3 migration. To hold or not hold

by mark＠suburbia.org.au

Hi Mark, Thanks for taking the time to reply. Mark Sapiro wrote: > On 11/16/24 21:41, mark(a)suburbia.org.au wrote: > > However, I've just done a test of a newly added user (a test email account for me), seen that the Moderation Action is None, but when I posted to the list from the address, it was not held for moderation, and went through. > > Am I missing something with the expected functionality? > > A member's moderation action of None means use the Default action to take when a member posts to the list. Is that set to Hold for moderation? > Actually, it is good practice to set that to Hold for moderation for > all lists or at least all those that don't require moderator approval > for subscription to prevent a spammer from subscribing and spamming the > list. Then, upon approving a member's post you can also set the member's > moderation action to default processing and upon discarding a spammers > post, you can also set the spammer's moderation action to Discard. I agree. My point was that the list is set as default to hold for moderation. But, a new user who sends an email to the list, whose Moderation Action is set to "none", was able to email the list without the email being held for moderation. I would have expected based on the threads I quoted, that a user who is added to the list via Mass subscribe, would not be able to send to the list without it being held. I'm happy to do more testing, provide other information/logs as desired if that would help? cheers, Mark

7 months, 2 weeks

[MM3-users] Re: hyperkitty url not found

by Eggert Ehmke

So I have to use the external url via https? I can access the address https://lists.[1]<tld>_/mailman3/archives/api/_ so I set: (<tld> is my existing domain) base_url: https://lists.<tld>/mailman3/archives Now I get this in the mailman.log: Mar 14 19:40:21 2022 (166928) ACCEPT: <12973151.uLZWGnKmhe@wookie> Mar 14 19:40:21 2022 (166932) HyperKitty failure on https://lists.<tld>/mailman3/archives/ api/mailman/urls: <html><title>Forbidden</title><body> <h1>Access is forbidden</h1><p>Please check the IP addresses assigned to MAILMAN_ARCHIVER_FROM in the settings file. </p></body></html> (403) In my settings I have my local IP and 127.0.0.1 and ::1. What should I set there? Am Montag, 14. März 2022, 18:48:51 CET schrieb Mark Sapiro: > On 3/9/22 07:13, Eggert Ehmke wrote: > > I installed mailman3 in a virtualenv following this guide: > > > > https://docs.mailman3.org/en/latest/install/virtualenv.html[1] > > The mailinglists work very good. However, I did not manage to set up > > hyperkitty archiving. Archiving is enabled in mailman.cfg. I can call the > > Archive site from my configuration page, but it is empty. > > > > In my /opt/mailman/mm/var/logs/mailman.log > > file I find error messages like: > > > > HyperKitty failure on > > http://localhost/mailman/hyperkitty/api/mailman/archive: The requested > > URL was not found on this server. > > Your setting in mailman-hyperkitty.cfg for base_url is > > base_url: http://localhost/mailman/hyperkitty/ > > It needs to be the base URL for accessing hyperkitty, possibly > > base_url: http://localhost/mailman3/hyperkitty/ > > or whatever you use to access hyperkitty from a web browser. > > Whatever it is, `<base_url>/api` should return a page of API documentation. -------- [1] https://lists.ftv-spandau.de/mailman3/archives/api/

3 years, 3 months

[MM3-users] Re: Sending a message to a subscription applicant when a subscription request is made

by Allan Hansen

Mark, I tried doing this. I unsubscribed myself from a list, set the policy as you suggest and re-applied. I got no confirmation messages but as moderator I got the moderate message. I then tried a bogus email and saw that a message was sent to that and no moderator message to me. Would the server skip the verification message because I'm a moderator/admin? Yours, Allan On 3/28/23, 08:57, "Mark Sapiro" <mark(a)msapiro.net <mailto:mark@msapiro.net>> wrote: On 3/28/23 01:49, Allan Hansen wrote: > > There is a template, 'list:user:action:subscribe' that almost does this, but it gets sent only if the email address of the applicant is unverified. A good number of our applicants are already on our lists, so they would not get this template if we set the Subscription Policy to 'Confirm, then moderate'. > > Our Subscription Policy is currently: 'Moderate' for all lists. If you set the subscription policy to 'Confirm, then moderate' the user will receive a confirmation request based on the list:user:action:subscribe template whether or not the address is verified. -- Mark Sapiro <mark(a)msapiro.net <mailto:mark@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 <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org <mailto:mailman-users@mailman3.org>/message/ORDAIBK4JUICZADYPEPWDVV2WP5EXWEB/ This message sent to hansen(a)rc.org <mailto:hansen@rc.org>

2 years, 3 months

[MM3-users] Re: Migrating Mailman 3 lists

by Mark Dadgar

On May 24, 2020, at 7:24 AM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: >> Mark Sapiro wrote: >>> On 5/19/20 7:25 PM, Mark Dadgar wrote: > >>>> For reference my pgloader script looks like: >>>> >>>> load database >>>> from sqlite:///var/lib/dbconfig-common/sqlite3/mailman3-web/mailman3web.db >>>> into postgresql://mailman3:XXREDACTEDXX@localhost/mailman >>>> >>>> with include drop, create tables, create indexes, reset sequences, no truncate > >> Have you tried this without indexes and then run the migrate >> script? It may re-create them as part of the schema upgrade >> check. > > That was my immediate guess. I'm not an SQL expert, but I believe > that sequences and indexes are different entities, they're both > optimizations that you don't need (ie, ignoring performance), and > implementations differ on how they're implemented. Eg, if sqlite > implements them as tables, while PostgreSQL has a special data > structure, you could run into this kind of behavior. I'm pretty sure > that these will be recreated appropriate to the new database when the > schema validator is done. > > But don't trust me, and *do* keep a backup. ;-) 😁 I did try it without indexes and it started showing the same warnings. I will give this another try and let it run to completion. I was hesitant to do that because the core database is 7.5 GB and the web database is 35 GB so there are only so many copies I can keep hanging around on the cloud volume. Since the data is mostly text, I am hoping that postgres will compress the bejeesus out of it. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 1 month

[MM3-users] Re: Gmail emails bouncing - anybody seen this problem?

by worik

On 12/02/19 11:25 AM, worik wrote: > Friends > > On a fresh install (docker) on a fresh VPS I am getting all Mailman > messages to Gmail addresses bouncing telling me I am sending too many > messages. Has anybody else have this problem? > > I am getting the following error in mail.log: "Our system has detected > an unusual rate of 550-5.7.1 unsolicited mail originating from your IP > address. To protect our 550-5.7.1 users from spam, mail sent from your > IP address has been blocked. 550-5.7.1 Please visit 550-5.7.1 > https://support.google.com/mail/?p=UnsolicitedIPError to review our 550 > 5.7.1 Bulk Email Senders Guidelines. l26si395949wme.8 - gsmtp" > > I have been to the URL mentioned and exhausted my options there. > > Worik > Well. Golly. I complained to Google, and heard nothing back. But with no changes on my end they have stopped bouncing my emails. Now they are just marked as spam. I can live with that. Very frustrated with google's levels of service. What a pain! Thank you Brian Carpenter, who may well have been right about "warming up the IP". What ever that might mean. I have not read that RFC, but I have a lot to learn. Thank you Mark Sapiro, for your patience. Thank you every body for the obviously hard work creating this system. I have a long way to go until I know how to use it properly, but I am no longer stopped at the google cliff. Worik -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand) I have a lot of onion pie, that explains the aroma

6 years, 4 months

Search results for query "sapiro"