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

[MM3-users] Re: Converting discussion list to read-only list (settings)

by Mark Sapiro

On 10/14/19 12:06 AM, Paul Arenson wrote: > Mark Sapiro wrote: > >> If by "read only" you mean the "Announce only mailing list style" as >> opposed to the "Ordinary discussion mailing list style" the only >> difference is that for the Announce only style the list attribute >> allow_list_posts is False and for the Discussion style, it's True. >> >> This is the setting in Postorius -> Settings -> Alter Messages -> >> Include the list post header an all it does is include or not include >> the List-Post: header in mail from the list. > > Ok...there is no specific setting I see "allow_list_posts" but you wrote "Include the list post header " later on. So i set THAT one to NO? allow_list_posts is the name of the attribute in Mailman core. It is exposed in Postorius as "Include the list post header". I.e., they are the same thing. Note however that unless your users are using MUAs to reply by email and their MUAs offer a "reply-list" function for replies to mailing list posts, this setting will make no difference. It is the presence of the List-Post: header in the message that allows the MUA to offer/process the "reply-list" function. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] Re: Huge performance issue: Mailman doesn't (seem to) receive any mails.

by Mark Sapiro

On 9/19/19 12:02 AM, Henrik Rasmussen wrote: > Abhilash Raj wrote: >> On Wed, Sep 18, 2019, at 8:14 AM, Mark Sapiro wrote: >>> each other, but Postfix is trying to deliver mail via lmtp to >>> [172.19.199.2]:8024. Mailman's lmtp runner should be running and >>> listening on port 8024. Either that is not the case or that port is not >>> exposed to Postfix on IP 172.19.199.2. >>> Right, that is what I was wondering, you verify that by using telnet >> on the specified IP and Port (172.19.199.2:8024). > > Yes, the postfix container listens on 172.19.199.2:8024 > ``` > [root@postfix /]# nc -v 172.19.199.2 8024 > Ncat: Version 7.50 ( https://nmap.org/ncat ) > Ncat: Connected to 172.19.199.2:8024. > 220 mailman-core GNU Mailman LMTP runner 2.0 > ``` This seems to say that the Postfix container can connect to 172.19.199.2:8024 and receive the greeting from Mailman's lmtp runner. So, why can't Postfix send to 172.19.199.2:8024? The only log entry you postes just says "Sep 18 10:07:47 postfix postfix/qmgr[98]: warning: mail for [172.19.199.2]:8024 is using up 7844 of 7844 active queue entries". What other log entries relate to attempts to send to 172.19.199.2:8024? You may have to go back to when this first started to see them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[Test] posting here

by Mark Sapiro

This is a list post. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 8 months

[Test] Test after reboot

by Mark Sapiro

-- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 8 months

[Test] Test after second reboot

by Mark Sapiro

-- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 8 months

[Test] Re: Is there anybody out there?

by Mark Sapiro

On 03/17/2016 11:54 AM, Florian Fuchs wrote: > Ping! Pong! -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 8 months

[Test] Down time.

by Mark Sapiro

Later this evening (maybe March 19 02:00 UTC) I will be attempting to reconfigure things to use the gitlab master branches of MailmanClient, Postorius, HyperKitty and the HyperKitty-Mailman plugin in addition to using gitlab master branch of Mailman itself which is already the case. This will probably involve down time and/or anomalous behavior. You have been warned. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 8 months

[Test] Re: Baseline

by Mark Sapiro

On 03/20/2016 01:22 PM, Playground for testing wrote: > I'm going to try a few config changes. > > This post is just to establish a baseline. All those prior posts were unintentionally anonymized due to my not setting things completely back after playing with some settings. This one should not be anonomized. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 8 months

[Test] setting up the mailman-users@mailman3.org list

by Mark Sapiro

I think we are very close to going live with a mailman-users(a)mailman3.org list. I am comfortable that between Postorius and mailman shell I can create and configure the list. The HyperKitty issues that were blockers for me have been fixed. The one remaining blocker that I see[1] is that Google login doesn't work. This is reported here <https://gitlab.com/mailman/hyperkitty/issues/73>. Any ideas on that? [1] Steve has an issue trying to add a second address, but I am unable to duplicate that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 8 months

[Mailman-users] Initial post

by Mark Sapiro

Create an archive. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 8 months

Search results for query "sapiro"