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

[MM3-users] Re: Welcome Message

by brian＠emwd.com

Mark Sapiro wrote: > Can you do bin/mailman shell? > > That would be even better. bin/mailman shell -bash: bin/mailman: No such file or directory Apparently not. Again this is the Docker version. Would love to have the Docker maintainer help out here. > If you're installing via pip you must have Python 3. Your tracebacks show a Python 3 > library in /usr/lib/python3.6/ /usr/lib/python3.6 -bash: /usr/lib/python3.6: No such file or directory I am installing it via pip on a Ubuntu server which is a different server from this template problem. Sorry about the confusion. The one where I need the templates to work is on a Centos server that used Docker to install it. I simply do not know how to get a python3 prompt when it has been setup via Docker. I will be requesting some assistance for the Ubuntu server once I get this template issue resolved. Brian

6 years, 2 months

[MM3-users] Re: Hyperkitty Authorization Required

by Andrew Bernard

Hi Mark, Thanks. But that is not the problem. It's hyperkitty background processes that show the error in the logs. I was probably not clear in my statement of the problem. I was testing it by typing in URL's. Sorry! I solved it by searching these archives. There was a post in January regarding the same issue, and the solution turned out to be replacing the given api keys with new ones, and all it all just works. Why that should be is a mystery to me, but now at least two people have found this. I would have thought a key is just a key. Andrew > -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > Sent: Friday, 7 June 2019 1:22 AM > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Re: Hyperkitty Authorization Required > You have to be logged in to post from HyperKitty. You can't post > anonymously.

6 years, 1 month

[MM3-users] Re: postorius ssl-certificates for virtual hosts

by Wolfgang Bock

Am 15.11.2019 um 02:21 schrieb Mark Sapiro: > Your Apache config needs to define separate a VirtualHost for each > domain, either by IP address or ServerName, and each VirtualHost points > to its own SSL certificates. Thanks for your info, that did it. I had to include the text of the apache.conf in all my apache-config-files for my virtual-domains. >> If I set use_https to yes in mailman.cfg I get on the website for all lists: >> >> postorius: Something went wrong >> Mailman REST API not available. Please start Mailman core. >> >> >> Does your setting in settings(_local).py for MAILMAN_REST_API_URL have >> an https scheme? That doesn't solve the problem. I changed that in mailman-web.py (MAILMAN_REST_API_URL = https://localhost:8001) and after that in mailman.cfg (use_https: yes). But got the same errormessage on postorius website. Regards Wolfgang

5 years, 7 months

[MM3-users] Re: Rejection Reason for refusing a subscription request

by Abhilash Raj

> On Mar 27, 2021, at 6:03 PM, Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > > On 3/27/21 6:42 PM, Mark Sapiro wrote: >> Ooops, Abhilash is correct. I have a bad habit of focusing on what's in >> the body of a post and sometimes missing relevant info in the subject. >> Sorry. > > Ok, can you or Abhilash reply to my previous questions. I thought I did, the support for specifying reason has been added in Postorius’s master branch. It will be in the next release, 1.3.5 probably. Core has had support for specifying reason when rejecting requests since 3.3.3. > > -- > Brian Carpenter > Harmonylists.com > Emwd.com > _______________________________________________ > 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)

4 years, 3 months

[MM3-users] Re: Message shows up individually but not in the thread

by Marvin Gülker

Am 04. November 2017 um 10:51 Uhr -0700 schrieb Mark Sapiro <mark(a)msapiro.net>: > There is a possibly related issues at > <https://gitlab.com/mailman/hyperkitty/issues/151> and some older ones > at <https://gitlab.com/mailman/hyperkitty/issues/131> and > <https://gitlab.com/mailman/hyperkitty/issues/149>. > > I'm sorry I can't offer more help than that at this point. Okay. I'll have an eye on the problem and see whether I can make out any pattern on messages not appearing. I'm not (yet?) seeing the other symptoms described in #151, but our mailinglists are usually rather quiet until some burst of discussion arises. There have not been any newer posts than the linked ones yet. The mails all went out properly via email. It's a problem related to Hyperkitty thus. Marvin -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

7 years, 8 months

[MM3-users] Re: Configure administrative users via command line?

by kjohnson＠eclypse.org

Thank you for the prompt and informative reply. Mark Sapiro wrote: > ... If you are an owner or moderator of a list > or a superuser, you can handle moderation requests via Postorius. If you > are a list owner or a superuser, you can manage owners and moderators > via Postorius. Yes, I would like to do that. > You can add superusers via the command line django admin > createsuperuser command. For the reference of others like me, createsuperuser will allow you to create a user with a non-unique email address. I strongly recommend against that. mailman shell gave me: >>> from django.contrib.auth.models import User >>> User.objects.filter(is_superuser=True) <QuerySet [<User: admin>, <User: xxxx>]> I dredged a password for admin out of my memory and was able to perform the moderation request. I also set a new list owner.

1 year, 11 months

[MM3-users] Re: Subscription requires confirmation when list is set as Open

by Mark

>> On 12/17/24 13:35, Mark wrote: >> ... if I subscribe with an address that has never been used before, I >> receive an email that requires me to confirm the subscription. >> >> The subscription is also held in the administrator's "Subscription >> requests: Pending confirmation". >> >> This happens when subscribing by both email and the web UI. >> >> Ideally, as the Policy is set as "Open", the subscription of any new >> email address should be added automatically. > On 2024-12-18 00:00, Mark Sapiro wrote: > It is not the subscription that requires confirmation. It is the user's > email address. Even though the list's subscribe policy is open, a > previously unknown email address has to be confirmed. Thank you Mark. Your explanation is very much appreciated. Best, Mark

6 months, 3 weeks

[MM3-users] Re: Cannot setup announce-only mailing list

by Stephen J. Turnbull

Mark Sapiro writes: > On 2/1/20 9:53 AM, Abhilash Raj wrote: > > Mark, do you think we should make the actual announce-only style reflect > > these settings so folks don't have to manually set these after they create > > a announce-only list? > > > > I am not sure the reason behind these settings lacking for the current > > announce-only style. Are there situations where announce-only list would > > have different list setting? > > I think it was probably done as it is just as a start. I do think it > would be good to set more things appropriately for the announce-only > style, ultimately we may need to add templates for post rejection > notices and things like that. If this involves a fair amount of coding maybe it could be a suggested GSoC task? Steve

5 years, 5 months

[MM3-users] Re: Centralizing logging

by Odhiambo Washington

On Wed, Sep 29, 2021 at 7:56 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 9/29/21 4:51 AM, Odhiambo Washington wrote: > > > However, there is this process that *forced* me to create > > usr/local/mailman/*logs/mailmansuite.log > > *as opposed to it just writing to var/logs/ path above > > > > Is there a way to make it write its log $var_dir ? > > > This is Django's log. Django knows nothing about mailman.cfg which is > for core only. You can set the path in your Django settings. See > LOGGING['handlers']['file']['filename'] > > I deal with this by creating a symlink like > > /usr/local/mailman/logs -> /usr/local/mailman/var/logs > Wuah. I did not even think about a simple symlink. Thank you so much. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

3 years, 9 months

[MM3-users] Re: All users getting disabled after upgrade of mailman3

by Quanah Gibson-Mount

--On Thursday, January 18, 2024 6:09 PM -0800 Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/18/24 15:08, Quanah Gibson-Mount wrote: >> Hello, >> >> We just upgraded our mailman to the latest provided from Debian bookworm >> (I know, not the recommended installation method). >> >> >> >> Now everyone's having their addresses disabled due to "bounce" errors. >> This is odd, because I'm disabled, even though I received the 2 emails I >> sent to the list today (and that's the only list traffic today). > > > Did you upgrade mailman core from a version older than 3.3.1? > > If so, see this post > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/mess > age/IC3LXQMANJGOVUOCVUBHIOGYZ4PA24F7/>. That's it! Thank you so much Mark! Excellent help as always. Regards, Quanah

1 year, 5 months

Search results for query "sapiro"