[Mailman-Users] Configuration Challenge with Apache and Mailman on OS X Server

[Timothy Jasionowski]

Hello!

Long time, happy mailman administration, first time poster.

The last implementation I did of mailman was on OS X 10.9 Server and it went 
relatively well, but my current attempt at implementing it on a box to replace 
it running OS X 10.11.5/Server 5.x has driven me batty, specifically related to 
the .cgi prefix presentation in the URI.

On the previous implementation of 2.1.15, the URI would be constructed as:

https://server.domain.tld/mailman/admin/mailing_list/members/add

However, in trying to update my implementation of 2.1.22 in the new server, I’m 
getting:

https://server.domain.tld/mailman/admin.cgi/mailing_list/members/add

In the initial implementation, I was using a ScriptAlias to direct mailman to 
the folder, but no rewriting rules.  

ScriptAlias /mailman/ "/usr/local/libexec/mailman/cgi-bin/"

In the new implementation, I’m using an config Include file in the apache 
configuration, as suggested by MacPorts:

Include /opt/local/etc/httpd/mailman.conf

Which reads:

# Mailman configuration file fragment for Apache


ScriptAlias /mailman/ "/opt/local/libexec/mailman/cgi-bin/"
Alias /pipermail/ "/opt/local/var/mailman/archives/public/"
Alias /mailman-icons/ "/opt/local/share/mailman/icons/"



Options Indexes Includes MultiViews SymLinksIfOwnerMatch
AllowOverride FileInfo AuthConfig Limit
Order allow,deny
Allow from all



Options none
AllowOverride FileInfo AuthConfig Limit
Order allow,deny
Allow from all



Options SymLinksIfOwnerMatch
AllowOverride FileInfo AuthConfig Limit
Order allow,deny
Allow from all


I’ve read the wikis and the Apache documentation and, have fiddled with the 
CGIEXT setting in Defaults.py, which currently reads

# CGI extension, change using configure script
CGIEXT = '.cgi'

I have changed it to ‘’ with no success.

Any help or thoughts would be greatly appreciated.

Thanks.

Timothy


--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Useful Mailman-Postfix Configuration Information for OS X Server Implementers on Yosemite, El Capitan and later builds

[Timothy Jasionowski]

All,

After some puzzlement and some hard-earned technical consideration, OS X Server 
5.1.x and later implementers (the current version independent Server bundle) 
have a new challenge to take into consideration.  I’m posting this so that 
people googling/searching later might skip this painful step and/or have it 
added to future documentation.

As configured today, a mailman implementation running locally would face some 
version of this relay error in the mail.log:

postfix/smtpd[53192]: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 554 
5.7.1 mailto:u...@foreigndomain.tld>>: Relay access 
denied; from=mailto:testinglist-boun...@localdomain.tld>> to=mailto:u...@foreigndomain.tld>> proto=ESMTP helo=

Earlier versions of Server shipped with pre-2.10 versions of postfix (10.9.x, 
for example, runs 2.9.4 today).  However, with 5.1.x, Apple now implements 
2.11, though it has not updated the configuration file to cope with the 
transition from the former smtpd_recipient_restrictions to the post-2.10 
smptd_relay_restrictions parameter.  As most people are going to look at 
smtpd_client_restrictions and mynetworks to diagnose and not notice that the 
deprecated parameter is still there in lieu of the current hotness, there may 
be hours of frustration trying to diagnose that the problem lies in a pre-2.10 
configuration file used in the current builds.  

To correct this, might I suggest postfix main.cf changes:

# smtpd_recipient_restrictions = permit_sasl_authenticated 
reject_unauth_destination permit
smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated 
reject_unauth_destination

This change corrected the relay restriction immediately upon restart.

I hope this helps others out in their implementation.  There seems to be little 
documented implementation instruction for mailman on OS X Server 5.1.x.

Good luck!

Timothy
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Update mailman MacServer5

[Timothy Jasionowski]

I think I may have sent this directly, but...

Mattias,

I had good luck installing mailman on El Capitan/Server 5 using MacPorts, as it 
manages all the dependencies and integrates all the chron jobs and startup 
stuff, but due to some legacy issues with the MacPorts configuration file, the 
build appends the .cgi prefix in the URI construction. It, otherwise, works 
fine. It avoided a lot of the issues you had in configuring it and, more 
importantly, maintaining it. 

If you want to get rid of the extension, download macports, refresh the build 
index, then edit the macports mailman build file, replacing:

configure.args  --with-cgi-ext=.cgi \
 --with-cgi-gid=${cgigroup} \

with

configure.args  --with-cgi-gid=${cgigroup} \

Thanks again to Marius Schamschula for that tip, as it drove me crazy. 

Timothy

Sent from my iPhone

> On Sep 4, 2016, at 11:53, Mark Sapiro  wrote:
> 
>> On 09/04/2016 01:56 AM, Matthias Schmidt via Mailman-Users wrote:
>> sorry for being such a pain today _/\_
>> 
>> now the webinterface is not coming up.
>> It looks like the cgi is not executed instead a 404 error is generated
>> 
>> my mailman.conf for apache looks like that (it’s basically the same as on 
>> 10.6, I just changed the path):
>> 
>> ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/"
> 
> 
> This is OK, but ...
> 
> 
>> Alias /pipermail/ "/var/mailman/archives/public/"
>> 
>>Options FollowSymLinks MultiViews Indexes
>>AllowOverride None
>>Order allow,deny
>>Allow from all
>> 
>> 
>> it is included with http.conf
>> 
>> for the site I have a redirect:
>> RewriteCond %{HTTP_HOST}%{REQUEST_URI} ^liste\.dinj\.de.$
>> RewriteRule ^/(.*) https://%{SERVER_NAME}/mailman/listinfo/dinj  
>> [L,R=permanent]
>> and that stuff was working on 10.6
> 
> 
> And all that does is redirect 'http(s)://liste.dinj.de/' to
> 'https://%{SERVER_NAME}/mailman/listinfo/dinj'
> 
> 
>> the logs say this:
>> [Sun Sep 04 17:41:42.375938 2016] [:debug] [pid 95364] 
>> mod_hfs_apple2.c(397): [client 127.0.0.1:59199] mod_hfs_apple: Allowing 
>> access with matching directory. filename = /WebFolder/dinj/mailman
>> [Sun Sep 04 17:41:42.375977 2016] [core:info] [pid 95364] [client 
>> 127.0.0.1:59199] AH00128: File does not exist: 
>> /WebFolder/dinj/mailman/listinfo/dinj
> 
> 
> So why is Apache looking for /WebFolder/dinj/mailman/listinfo/dinj? Is
> /WebFolder/dinj the DocumentRoot?
> 
> Does this happen with any mailman URL? If you go to
> 'https://liste.dinj.de/mailman/admin/dinj' do you get a similar 404 or
> only if you go to' https://liste.dinj.de/'.
> 
> Somehow your 'ScriptAlias /mailman/' directive is not effective. In a
> more or less normal apache configuration it is not sufficient to put
> mailman.conf in /etc/apache2/conf.d/, you must also have a symlink to it
> in /etc/apache2/conf-enabled/. I have no idea if this applies to Mac OX
> X Server, but you need to look at your Include and IncludeOptional
> directives in the main apache2.conf or whatever it's called to ensure
> that mailman.conf is directly or indirectly included.
> 
> 
>> /usr/local/mailman/cgi-bin/ has permissions set to 775
> 
> 
> It should be 2775 (drwxrwsr-w) but the important thing is the files
> therein should be 2755 (-rwxr-sr-x).
> 
> -- 
> Mark Sapiro The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> 
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: 
> https://mail.python.org/mailman/options/mailman-users/timothy.d%40jasionow.ski
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] cannot send mails to yahoo, hotmail and gmail

[Timothy Jasionowski]

You may also want to make sure that you're configured SPF for your domain... I 
know that Google can be suspicious of new or small domains unless SPF (or even 
DKIM) is implemented. 

SPF is easy to implement. You just need to put a TXT entry into DNS. 

Timothy

Sent from my iPhone

> On Sep 18, 2016, at 17:19, Mark Sapiro  wrote:
> 
>> On 09/17/2016 11:05 PM, Eko Budiharto wrote:
>> dear all,
>> I have a list using mailman. It cannot send mails to yahoo, hotmail and 
>> gmail. I check all setting in the mailman, but I still cannot find the 
>> problem yet. Please help me if someone who ever experience like this.
> 
> 
> It's hard to tell without more information such as bounce messages or
> log messages, but this could be a DMARC issue. See
>  and .
> 
> It is also possible your server is on one or more blacklists. Check at,
> e.g., 
> 
> Also see .
> 
> -- 
> Mark Sapiro The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: 
> https://mail.python.org/mailman/options/mailman-users/timothy.d%40jasionow.ski
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Installing Mailman on OS X El Capitan--can’t find source of erroneous call of binary at /usr/share/mailman/mail/mailman

[Timothy Jasionowski]

I’m one of the few people who has blazed this trail on the newer versions of OS 
X Server, mainly using the macports installation method with a few 
modifications.  If you want to email me off the list, I can share my insights.  
Alternately, search the archives for my previous posts/fixes for this, as I’ve 
tried to document my challenges.

Timothy

> On Oct 11, 2016 (Wk 42), at 4:46 PM, Dominik Hoffmann 
>  wrote:
> 
> Hi:
> 
> I have followed Allan Herman's March 29, 2013, instructions for installing 
> Mailman on OS X Mountain Lion. The difference is that my system is OS X El 
> Capitan running Server 5.2. Nonetheless, I have not run into any 
> contradictions. It appears that the choices for the locations of the various 
> configuration files made when transitioning from Mac OS X Snow Leopard to Mac 
> OS X Lion to OS X Mountain Lion have remained stable.
> 
> However, I am now banging my head against the wall, because my server's SMTP 
> logs contain these lines:
> 
> Oct 11 16:04:04 ion local[56963]: fatal: execvp 
> /usr/share/mailman/mail/mailman: No such file or directory
> 
> Allan installs his Mailman deployment in /usr/local/, and I have learned that 
> in one of the more recent iterations of OS X, Apple chose to lock down 
> /usr/share/, so that even the sudo command does not make modifications 
> possible, which I learned, when I tried to create a simlink there. I kept 
> getting the "Operation not permitted." error. I learned that this is due to 
> System Integrity Protection (SIP), introduced in OS X El Capitan.
> 
> I am now on a quest to locate from where the call to mailman originates, so 
> that I can edit the corresponding configuration file, replacing "/usr/share/" 
> with "/usr/local/".
> 
> Any pointers would be much appreciated.
> 
> Dominik Hoffmann
> 
> 
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: 
> https://mail.python.org/mailman/options/mailman-users/timothy.d%40jasionow.ski

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] English (USA)

[Timothy Jasionowski]

I don’t really have a dog in this fight, but can we acknowledge that this 
version of Mailman is effectively on life support for a variety of reasons, 
that the limited developer support on it has been focused primarily on fixing 
critical bugs out of kindness rather than implementing any new features, and 
focus any internationalization efforts where they belong: in the actively 
developed Mailman 3?

Timothy 

Sent from my iPhone

> On Jul 8, 2019, at 15:52, Norbert Bollow  wrote:
> 
> On Mon, 8 Jul 2019 21:06:52 +0200
> Christian F Buser via Mailman-Users  wrote:
> 
>> And there are other expressions which are completely different in UK
>> English and US English - see
>> .
>> There are probably many more. 
>> 
>> So if you want to "unify" those two, which variant to choose? Or
>> better blend them into one - changing the spelling from one occurence
>> to the other? 
> 
> I'd be very surprised if *in Mailman's UI* there are any real causes
> for confusion due to the differences between different variants of
> English.
> 
> I'm running some international mailing lists. On these lists, English
> is not used because it's a language used in the USA, or in any other
> particular country, but because it is generally the best choice of
> language for communicating internationally.
> 
> On some of those lists, it is really strongly desirable to actively
> encourage the list's participants to see themselves as an international
> community, in particular as a community where US centric perspectives
> are not privileged over other perspectives.
> 
> In such contexts, the reference to the English language in Mailman's
> Web UI as "English (USA)" is very irritating.
> 
> I have sometimes modified Mailman to make it simply display "English"
> instead of "English (USA)". But I haven't ever gotten around to
> cleaning this up into a real patch as suggested by the OP.
> 
> I would welcome such a patch.
> 
> Greetings,
> Norbert
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: 
> https://mail.python.org/mailman/options/mailman-users/timothy.d%40jasionow.ski
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Re: blocking a hot/inappropriate topic

[Timothy Jasionowski]

Would they consider moderation? They can let it pile up and reject or let 
things through that meet their objective. 

Timothy

Sent from my iPhone

> On Jun 12, 2020, at 12:12, Bernie Cosell  wrote:
> 
> One mailing list I run has recently been plagued with a very heated, long, 
> inappropriate, and off-topic discussion.  The people in charge of the mailing 
> list 
> have asked me to temporarily turn it off [and I have].   Two questions:
> 
> 1) is there a way to temporarily disable a mailing list short of removing the 
> alias 
> that points to it?   I was thinking that perhaps I could've put in a "sender 
> filter" 
> that rejected everyone or something like that.
> 
> 2) is there a way to block a *single* topic..  I know that can be defeated 
> but it'll 
> stop the particular thread at least for while while the rest of the list can 
> go on.
> 
> Thanks!  /bernie\
>Bernie Cosell
>   ber...@fantasyfarm.com
> -- Too many people; too few sheep --
> 
> 
> 
> --
> Mailman-Users mailing list -- mailman-users@python.org
> To unsubscribe send an email to mailman-users-le...@python.org
> https://mail.python.org/mailman3/lists/mailman-users.python.org/
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
>https://mail.python.org/archives/list/mailman-users@python.org/
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/