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

[MM3-users] Re: MM3 Docker

by Abhilash Raj

On Tue, Jan 8, 2019, at 5:52 AM, Odhiambo Washington wrote: > On Tue, 8 Jan 2019 at 03:29, Mark Sapiro <mark(a)msapiro.net> wrote: > > > On 1/7/19 1:18 AM, Odhiambo Washington wrote: > > > On Sun, 6 Jan 2019 at 23:39, Mark Sapiro <mark(a)msapiro.net> wrote: > > >> > > >> Please help me understand what steps are missing and I will try to > > >> provide the information. > > > > > > > > > Okay. > > > > > > At the installation stage, you say the following: > > > "I already had some things set up in /opt/mailman including a git > > > subdirectory containing clones of the GitLab mailman, mailmanclient, > > > mailman-hyperkitty, hyperkitty, django-mailman3 and > > > postorius projects. On the third server I have added mailman-suite > > > because I use the settings.py from that project as the basis for mine." > > > > > > Please assume that the reader is a newbie to python3 virtualenv and give > > the > > > details of the commands they need to execute to (a) clone all the > > projects > > > needed > > > and (b) create the virtualenv. > > > > > > The next steps are: > > > mkdir /opt/mailman/mm > > > > > > Then you say "I then created a /opt/mailman/mm directory and within that > > a > > > Python 3.6 virtualenv" > > > What happens here is something that needs clarification, because you are > > > specific about "python3.6". > > > I have googled and realized that one has to be specific about the python > > > version they want to use in their virtualenv > > > as shown here -> > > > > > https://stackoverflow.com/questions/45293436/how-to-specify-python-version-… > > > > > > exact command to execute to create the /opt/mailman/mm/venv > > > exact command to execute to activate virtualenv > > > > > > I have added a comment to the page which I hope gives you what you want. > > > > I also added a section on templates instead of referring to a prior > > version of the page. > > > > That makes it better. > However, as a newbie, something is not yet clear: > > "When active in a particular shell, it can be deactivated with the command > > deactivate > or by exiting that shell." > > HI am trying to understand the effect of detaching from a venv. I am > assuming that a virtualenv is a container that is supposed to be always > active for the services within to be accessible. Is that right? So, how do > I ensure it's always running/up, or that does not matter as the scripts > which run the services will always refer to the files? virtualenv is not actually a container that is supposed to be active. It is merely a set of settings that are applied to your SHELL when you are in the virtual environment. It is not supposed to be always active, only when you actually want to run commands in that virtual environment. The services will keep on running after you deactivate your shell and would function like other normal services on your machine. -- thanks, Abhilash Raj (maxking)

7 years, 9 months

[MM3-users] Re: Weird response to postings after subscriptions and accounts

by Mark Sapiro

On 9/18/19 11:24 PM, Paul Arenson wrote: > > In the case of Mailman 3 much depends on the individual list and its settings, so my conclusion is it is mostly on me. With just a suggestion that you have a SIGN UP blue button to make things less confusing and not necessitating multiple clicking. This is difficult. See my reply to your first message. You will notice that when you click sign-up in either Postorius or HyperKitty, you go to <https://list.tokyoprogressive.org/accounts/signup/> which is neither Postorius nor HyperKitty but Django. So the current process is click sign-up, go to Django and sign up, then go back to Postorius and subscribe. To do this all in one step, Postorius would need to send you to /accounts/signup/?next=/postorius/lists/discuss.list.tokyoprogressive.org/ which it currently does, but there would need to be extra communication between Django and Postorius so that when Django returned to /postorius/lists/discuss.list.tokyoprogressive.org/, Postorius would know to tell Core to subscribe you. However, this is missing a step, because Django sends you an email requesting you to confirm your address, and you don't actually have an account until you confirm. This dance also renders the next=/postorius/lists/discuss.list.tokyoprogressive.org/ ineffective. Presumably Postorius could tell Core to subscribe you anyway even though you haven't confirmed your account, but Postorius doesn't know what address you signed up with. > The main obstacle I found was I had my list settings as NO to "Choose whether to include this list on the list of all lists". Changing this to "Yes" made it a little easier. > > Here are my two tests and conclusion. > > 2) TEST 1 > ________ > Sign up first... > https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > ...you will find that if I have said NO on "Choose whether to include this list on the list of all lists” you will find it hard to go back to the subscribe page. Unless you backspace. Or paste the address again. Not ideal > > > QUESTIONS: Am I missing something? By not having my discussion listed, people cannot find it to subscribe. > > Or is NOT LISTED better where I add people manually to subscribe and then tell them to sign up? If you want people to be able to find your list by going to <https://list.tokyoprogressive.org/postorius/> or for that matter, to <https://mailman3.emwd.com/postorius/> or if you think having it there is helpful in any way, set List Identity -> Show list on index page to Yes. Otherwise set it to No. > 3) TEST 2 > ________ > One solution is I could put the list back on the host’s list of lists back and tell people to click on Discuss. > > That is what I did for now. Then it is rather smooth. I could tell my users (especially ones from previous company’s mailing list who want to interact with the hyperkitty site) > > to > CLICK LOGIN > CLICK SIGNIN > then follow all these steps: > > Verify > > Confirm > > Get taken to sign in page > > Click Discuss > > Subscribe > > Click Archives > > Or I could leave it as it is and tell people to backspace until they find the signup page and then subscribe. > > Or tell them to copy and paste https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > > or https://list.tokyoprogressive.org/accounts/signup/ in the same browser window and then subscribe. > > CONCLUSION and SUGGESTION—> WHY NOT HAVE A SEPARATE BLUE BUTTON TO SIGN UP TO AVOID THE CONFUSING clicking twice? See above. > IS THIS THE ANSWER?— > > Tell my users as follows on a WORDPRESS PAGE as follows: > > - - - - - - - - - - - - > Greetings. If you have never signed up before, follow instructions A. If you are coming from the previous dadamail list, follow instructions B > > > INSTRUCTIONS A > Steps 1-3 to get on the mailing list and be able to post from your email account. > Continue to steps 4 and 5 if you want to see the archives and post from that page. (Note to Mark: I have turned the archives off by default to make it more of a no brainer to want to sign up) > > > INSTRUCTIONS B > You are already registered, you will continue to get messages and be able to send to the list. If you want to keep using the same email address you are all set and do not need to do anything. > > If you want to keep using the same address, but also be able to access the archives, follow steps 4 and 5 only. > > If you want to register a new address, follow steps 1-5 below. > > 1) Go here > https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > Add your email address at the BOTTOM of the page. Name is optional. > > 2) Then wait for email to reply to come. > > 3) That’s it. You can stop here. However, you can sign up to the archives which makes this list more of a forum to see at a glance old conversations. And you can also post from it. To do so, continue to steps 4 and 5, > > 4) Right on the same page, you can sign up and sign in by clicking > log in and then sign up and then follow the same procedure as above. (Mark, SEE SUGGESTION FOR A BLUE SIGN UP BUTTON). > > 5) Once you have signed up, you can log in to access the archives and web posting. > - - - - - - - - - - - - > > Hope the above long winded post was clear. Feel like I am sseing the lite. > _______________________________________________ > 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/ > -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: Auth question

by David Krantz

On Mon, Apr 10, 2017 at 1:06 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > In mailman_hyperkitty.conf, the key isn't quoted. I.e., if in > production.py or wherever, you have set > > MAILMAN_ARCHIVER_KEY = 'arch_secret' > > in mailman_hyperkitty.conf you set > > [general] > ... > api_key: arch_secret > > No quotes around the api_key value. Ok, I'll try that. Thought that I had, but probably not just that combination then. Also: Found a bug in Hyperkitty, or at least in my setup: Private lists are visible in the "By Name" dialog in the archives when not logged in. The actual content is not visible, but the activity statistics is displayed (although there is none as the login for archiving as of yet does not work). Hopefully this will correct itself when the communication mailman3-hyperkitty gets active. cheers // David

9 years, 6 months

[MM3-users] Re: Auth question

by David Krantz

On Mon, Apr 10, 2017 at 1:06 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > In mailman_hyperkitty.conf, the key isn't quoted. I.e., if in > production.py or wherever, you have set > > MAILMAN_ARCHIVER_KEY = 'arch_secret' > > in mailman_hyperkitty.conf you set > > [general] > ... > api_key: arch_secret > > No quotes around the api_key value. Ok, I'll try that. Thought that I had, but probably not just that combination then. Also: Found a bug in Hyperkitty, or at least in my setup: Private lists are visible in the "By Name" dialog in the archives when not logged in. The actual content is not visible, but the activity statistics is displayed (although there is none as the login for archiving as of yet does not work). Hopefully this will correct itself when the communication mailman3-hyperkitty gets active. cheers // David

9 years, 6 months

[MM3-users] Re: LTMP to Postfix problem

by Brian Carpenter

On 6/18/20 6:19 PM, Mark Sapiro wrote: > If you have it, look through the mailman.log for entries around the last > time the connections started to be refused. See if there are entries > about the runner exiting. Also, just before you restarted, there will be > several runner caught SIGTERM. Stopping. and runner exiting. messages. > If lmtp runner is among those, it was still running when you restarted. So lmtp runner was NOT running when I restarted mailman core, however I saw no error messages in the mailman.log at the time of the first instance of the connection refused message. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

6 years, 3 months

[MM3-users] Re: aborted connection

by Sandor Dibuz

On 2/19/22 20:46, Mark Sapiro wrote: > On 2/19/22 05:23, Sandor Dibuz wrote: >> >> Feb 19 14:15:18 localhost mariadbd[28859]: 2022-02-19 14:15:18 22154 >> [Warning] Aborted connection 22154 to db: 'mailman3' user: 'mailman3' >> host: 'localhost' (Got an error reading communication packets) > > You may be correct in your assumption that these are harmless. I would > try to correlate them with access and error logs from the web/wsgi > server to get more information. It's the mailman quarterly cron job: # Every 15 minutes, gate messages from usenet to those lists which have the gateway configured */15 * * * * list if [ -x /usr/bin/mailman ]; then /usr/bin/mailman gatenews; fi And I have no gateway enabled for any of them. Will have to find out what mailman exactly does. And change MariaDB to verbose logging. Sanyi

4 years, 7 months

[MM3-users] Re: Internal Server Errors in mailmanweb.log

by Washington Odhiambo

On Thu, Dec 25, 2025 at 12:07 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/18/25 03:07, Washington Odhiambo via Mailman-users wrote: > > I keep seeing several errors like the below in my mailmanweb.log and not > > sure what the causa is. > > What is your HyperKitty version? If it is 1.3.12 from PyPI and not the > latest from gitlab, See > https://gitlab.com/mailman/hyperkitty/-/issues/529 and > https://gitlab.com/mailman/hyperkitty/-/merge_requests/660 for a patch > to fix this. > It is version 1.3.12. Patch applied. Thank you. -- 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]

9 months, 3 weeks

[MM3-users] Re: Hyperkitty - Non-ascii sender address

by Thomas G

you do > try: > sender_address = from_email.encode('ascii').decode("ascii").strip() > except (UnicodeDecodeError, UnicodeEncodeError): > sender_address = from_email.encode('ascii', errors='replace').decode("ascii").strip() It's perfect, thank ! Le sam. 3 nov. 2018 à 19:11, Mark Sapiro <mark(a)msapiro.net> a écrit : > On 10/31/18 5:57 AM, Thomas G wrote: > > Hi, > > > > > https://gitlab.com/mailman/hyperkitty/blob/master/hyperkitty/lib/incoming.p… > > > > I changed "sender" for this; > > # Sender > > try: > > from_str = header_to_unicode(message['From']) > > from_name, from_email = parseaddr(from_str) > > from_name = unidecode.unidecode(from_name).strip() > > What is unidecode? > > > except (UnicodeDecodeError, UnicodeEncodeError): > > raise (ValueError("Non-ascii sender address", message)) > > > > try: > > sender_address = > from_email.encode('ascii').decode("ascii").strip() > > except (UnicodeDecodeError, UnicodeEncodeError): > > if from_name: > > sender_address = re.sub("[^a-z0-9]", "", from_name.lower()) > > if not sender_address: > > sender_address = "unknown(a)unknown.com" > > else: > > sender_address = "unknown(a)unknown.com" > > print("Non-ascii sender addre -- Sender address replaced by ", > > sender_address) > > > > I got this output (example): > > |Non-ascii sender address -- Sender address replaced by > > stephaneblipblopstlablipblopgmailcom > > It's not really perfect, I'm working to do something better, but > basically > > it's works. > > > The original code intends to provide some value for the email address > where parseaddr returns a null address. > > You have an address, and you would do better to remove the non-ascii > from the address than to try to make and address out of the sanitized > real name. > > Your issue is parseaddr() returns an email address with non-ascii. > > I would suggest that instead of > > > try: > > sender_address = > from_email.encode('ascii').decode("ascii").strip() > > except (UnicodeDecodeError, UnicodeEncodeError): > > if from_name: > > sender_address = re.sub("[^a-z0-9]", "", from_name.lower()) > > if not sender_address: > > sender_address = "unknown(a)unknown.com" > > else: > > sender_address = "unknown(a)unknown.com" > > you do > > > try: > > sender_address = > from_email.encode('ascii').decode("ascii").strip() > > except (UnicodeDecodeError, UnicodeEncodeError): > > sender_address = from_email.encode('ascii', > errors='replace').decode("ascii").strip() > > > > > > I think that there is a issue in the original code: > > Because : "" raise ValueError("Non-ascii sender address", message) "" > > > > The second part will be never call: > > It will if there is no exception. > > > if not sender_address: > > if from_name: > > sender_address = re.sub("[^a-z0-9]", "", from_name.lower()) > > if not sender_address: > > sender_address = "unknown" > > sender_address = "{}(a)example.com".format(sender_address) > > else: > > sender_address = "unknown(a)example.com" > > > > If you bypass : "" raise ValueError("Non-ascii sender address", message) > > "", by a simple print(), you will get an error due to an unassigned > > variable (sender_address). > > -- > 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/ >

7 years, 11 months

[MM3-users] Re: Is there a "global" max_message_size?

by skenny＠scss.tcd.ie

Mark Sapiro wrote: > > Mailman's lmtp runner which implements the server that receives mail via > LMTP uses the aiosmtpd.lmtp.LMTP class to implement the server. This has > a default size limit of 33554432 bytes (32 MB) and that's where the "552 > Error: Too much mail data" comes from. Ah - fantastic! I had tried a fairly crude trawl through the mailman-core container files (not knowing what exactly to look for really), but failed to come up with anything. > There is also the message_size_limit setting in postfix. Presumably > you've changed that because it defaults to 10240000 bytes (about 10 MB). Yes I fortunately did remember to set this to a very high value (way higher than 32MB) during testing. Thanks so much for the explanation Mark, very much appreciated. Stephen

6 years, 3 months

[MM3-users] Re: Moderated Signup with "info" box?

by Brian Carpenter

On 12/7/20 10:13 PM, Mark Sapiro wrote: > On 12/7/20 8:01 AM, Brian Carpenter wrote: >> Keep in mind that Mailman 3's REST API is only accessible locally. So to >> access Mailman 3's REST API from another server is not remotely >> possible. (see what I did there?) > > The REST API is only accessible locally by default. It is certainly > possible to configure the webservice section of mailman.cfg to be able > to access it remotely - if you do this, be sure not to use the default > admin_pass. There is also an authenticating REST proxy project called > lemme (possibly abandoned) at <https://gitlab.com/mailman/lemme>. Thank you for the clarification. I did not know that. Is that made clear in the documentation? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 10 months

Search results for query "sapiro"