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

[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

6 years

[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, 8 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

8 years, 1 month

[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.

2 years, 4 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

11 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, 10 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 '^$|^.*#' :-)

4 years, 2 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, 10 months

[MM3-users] Looking for large sites that have migrated to mailman3

by Stephen J. Turnbull

ssw(a)washington.edu writes: > We're looking for information on large sites that have migrated to > mailman3. Preferably academic institutions. As we start to look > at a migration project we're hoping to hear any 'lessons learned' > from those who have gone before us. The largest site I know of that has begun migration to Mailman 3, and has a non-trivial (dozens, maybe?) number of lists in operation is python.org. You can try searching the archives for this list and in mailman-developers(a)python.org for python.org and mailman3.org postmaster Mark Sapiro's opinions on the matter. I think the EMWD hosting site is also in process of migrating. I know there are several others (specifically a couple of academic institutions) basically at the very beginning of their migrations, but I don't know any in the later stages. Steve

6 years, 5 months

[MM3-users] Re: {Spam?} Re: Installation Wooes

by Samir Faci

Oh wow.. so that was special. Sorry for the massive logs and back and forth. It turns out all I was missing was that I needed to re-run sudo mailman aliases before restarting the service. I have a different set of issues right now but I need to debug that a bit more to figure out what is going on. Thanks for all the help Mark, much appreciated. -- Samir Faci On Mon, May 4, 2020 at 11:49 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/4/20 11:07 AM, Samir Faci wrote: > > The only way I've gotten it to work so far is by using the FQN. I can > > switch back to 127.0.0.1 but that wasn't working. > > > > Here's the configuration I have. > > > > incoming: mailman.mta.postfix.LMTP > > outgoing: mailman.mta.deliver.deliver > > smtp_host: 127.0.0.1 > > smtp_port: 25 > > smtp_user: > > smtp_pass: > > > > lmtp_host: 127.0.0.1 > > lmtp_port: 8024 > > > > > > > > and the end result: > > > > https://gist.github.com/safaci2000/b1c91f936df1c0d5668250cf1d503494 > > which includes > > May 4 17:50:09 lists postfix/lmtp[2600677]: connect to > lists.domain.org[198.199.98.177]:8024: Connection refused > > So the question is, why is Postfix trying to connect to > lists.domain.org[198.199.98.177] and not to localhost[127.0.0.1] > > > > > smtp_host: 127.0.0.1 > > lmtp_host: 127.0.0.1 > > > > #fail > > > But it should work. > > > > smtp_host: lists.domain.org > > lmtp_host: lists.domain.org > > > > # success. > > > And this should not be necessary. > > > > The error I get if I don't open port 8024 is below and in the gist i > linked > > earlier. > > > > May 4 17:50:09 lists postfix/lmtp[2600677]: D98A21473D5: to=< > > testing(a)lists.domain.org>, relay=none, delay=0.05, delays=0.03/0.01/0/0, > > dsn=4.4.1, status=deferred (connect to lists.domain.org > [198.199.98.177]:8024: > > Connection refused) > > > This is what is expected if port 8024 is not open and you are connecting > to lists.domain.org. > > > > The only way I've gotten it to work so far is by binding both the > smtp_host > > and lmtp_host to be lists.domain.org and opening up port 8024. > > > > I'd rather not have that port open but I'm open to suggestions on what > else > > to try. > > > You need to get Postfix to use localhost[127.0.0.1] and not > lists.domain.org[198.199.98.177]. > > One issue is when you change > > lmtp_host: lists.domain.org > > to > > lmtp_host: 127.0.0.1 > > you need to run `mailman aliases` to change the settings in > var/data/postfix_lmtp. I think if you go back to > > smtp_host: 127.0.0.1 > lmtp_host: 127.0.0.1 > > and run `mailman aliases`, restart mailman and reload Postfix, it should > all work without opening port 8024 and probably without needing to put > 198.199.98.177 explicitly in mynetworks in Postfix. > > I suspect you will have issues with mail not being accepted or treated > as spam by some recipient ISPs however. See > <https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS> > > -- > 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/ > -- Thank you Samir Faci https://keybase.io/csgeek

5 years, 7 months

Search results for query "sapiro"