Re: [Mailman-Users] "Freezing" mailing list

[Tatsuo Ishii]

> Or you could put
> 
> ^.
> 
> in the list's ban_list to ban any address containing at least one
> character from subscribing.

Thanks. This works for me.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
--
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] *** SOLVED *** Re: (2.1.26) Mailman CGI error!!! The Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog: Cannot open wrapper configuration file: N

[michaelof--- via Mailman-Users]

Mark,

pls forget my last email, you've led me already in the right direction:

- tried a sudo -u mailman /usr/lib/mailman/cgi-bin/listinfo and echo $? after 
that
- showed 8 as error code
- downloaded source for mailman 2.1.26, looked into source for cgi-wrapper.c, 
specifically into common.h
- 8 means GROUP_NAME_NOT_FOUND, you mentioned this as possible solution below

With this, and my knowlegde (or trust :-)) that mailman's GID configs in 
OpenSuse are in /etc/mailman, I've doublecked
and found one file missing after upgrade, /etc/mailman/mailman.cgi-gid.
Containing just an 8 :-S

Restored this from last backup, made immediately before I've started the 
upgrade of OpenSuse.

Works like a charm, as before :-)


Mark,
a) THANK YOU VERY, VERY MUCH !!!
b) I'll open an OpenSuse bugzilla issue for this


Regards,
Michael


Am 29.05.2018 um 21:16 schrieb michae...@rocketmail.com:
> Mark,
> 
> thank you for answering so detailed!
> 
> 
> Am 29.05.2018 um 19:37 schrieb Mark Sapiro:
>> On 05/29/2018 03:19 AM, michaelof--- via Mailman-Users wrote:
>>>
>>> After upgrading the VPS to OpenSuse Leap 15.0, Mailman still 2.1.26, Apache 
>>> from 2.4.23 to 2.4.33, Python from 2.7.13 to
>>> 2.7.14, I'm getting the error message in the subject of this mail when 
>>> trying to access the mailman web pages on Apache.
>>
>>
>> Is there anything in Mailman's error log?
> 
> My Mailman has been talking to my Postfix, so (forgot where this was defined) 
> uses also Postfix's log files. Postfix
> errors on OpenSuse go to /var/log/mail.err.
> 
> Independent if I call via Browser / Apache or directly, or in the cgi-bin dir 
> with ./listinfo as root, or with "su -u
> mailman ./listinfo", result in mail.err is always the same added line:
> 
> 2018-05-29T20:31:14.894893+02:00 vserver Mailman cgi-wrapper (listinfo): 
> Cannot open wrapper configuration file: No such
> file or directory
> 
> Means
> a) that logging itself is possible but
> b) log does not add any value for narrowing down the problem, at least not 
> for me :-(
> 
> Maybe a silly question: for what (specific) "wrapper configuration file" 
> mailman is searching for??
> 
> Any chance to get mailman's log more verbosive, temporarily?
> 
> I'm 100% sure for OpenSuse that as well apache (wwwrun/www) as mailman 
> (mailman/mailman) haven't changed their username
> and unix group for at least the last 3 centuries, in IT timing :-) I'm also 
> sure (checked in backup) that the numeric
> UIDs and GIDs haven't changed.
> 
>>
>>
>>> - Got the hint from #httpd, that the error msg has nothing to to with 
>>> apache itself. Tested to run e.g. "listinfo"
>>> manually, same error:
>>>
>>> vserver:/usr/lib/mailman/cgi-bin # ./listinfo
>>> Content-type: text/html
>>>
>>> 
>>> Mailman CGI error!!!
>>> 
>>> Mailman CGI error!!!
>>> The Mailman CGI wrapper encountered a fatal error. This entry is being 
>>> stored in your syslog:
>>> 
>>> Cannot open wrapper configuration file: No such file or directory
>>
>>
>> This comes from the various cgi-bin wrappers themselves when they
>> encounter a fatal error.
>>
>> First of all, when trying to debug by running these from the command
>> line you have to run them as the web server user. I.e.,
>>
>> sudo -u xxx ./listinfo
> 
> done, see above
> 
>>
>> where xxx is the user the web server runs as. The issues that cause this
>> are GROUP_NAME_NOT_FOUND, GROUP_MISMATCH or failure to set the effective
>> GID.
>>
>> If the wrapper was able to write Mailman's error log, the message there
>> should give details. If there's nothing in the error log, you might try
>> temporarily setting o+w in the log file to see if that allows writing
>> the message.
> 
> no (more) details in log except error msg, see above
> 
>>
>> If the upgrade somehow changed the user:group that apaches runs as, that
>> would cause this.
> 
> For sure not changed, see above
> 
>>
>> If your Mailman is installed from source, you may need to rerun
>> configure with a different --with-cgi-gid option and make install. If
>> it's a Suse package, this is a Suse issue.
>>
> 
> no change in gid/uid, could open an OpenSuse Bugzilla issue, but not a real 
> how to start / get the OpenSuse team
> convinced that this is not an issue on my side/config or a mailman issue
> 
> 
--
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] (2.1.26) Mailman CGI error!!! The Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog: Cannot open wrapper configuration file: No such file or

[michaelof--- via Mailman-Users]

Hi Mark,


just clicked "send" for a second answer to you last reply ten second ago, 
overlap with your current reply :-)

I've went a different way, but found the same reason, so thank you very much 
again!


Michael


Am 29.05.2018 um 23:27 schrieb Mark Sapiro:
> On 05/29/2018 12:16 PM, michaelof--- via Mailman-Users wrote:
> 
>> Maybe a silly question: for what (specific) "wrapper configuration file" 
>> mailman is searching for??
> 
> 
> That's a Suse question. Standard GNU Mailman has no such message. Read
> the Suse Mailman docs to see what they say about this.
> 
> 
>> Any chance to get mailman's log more verbosive, temporarily?
> 
> 
> No. Suse changed the wrapper and the message you got is it.
> 
> OK, I googled a bit and found
> 
> 
> They patch out all the nice error messages and instead put in their own
> stuff. The error in the subject means the file
> /etc/mailman/mailman.cgi-gid doesn't exist. It should exist and if I
> read the code correctly, contain the numeric GID of the web server.
> 
--
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] Filtering messages with no subject

[Mark Sapiro]

On 05/29/2018 01:49 PM, Bryan Blackwell wrote:

> Excellent, thanks.  I put them in with 'hold' instead of 'discard' for now 
> just in case I made a mistake.  Right now I have a bunch of lines in the 
> Legacy section, is it ok to leave those in place?


Yes, it's OK to leave them. If all you have there are the default ones,
they're ancient and probably never match anything, but they don't hurt.

-- 
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/archive%40jab.org

Re: [Mailman-Users] (2.1.26) Mailman CGI error!!! The Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog: Cannot open wrapper configuration file: No such file or

[Mark Sapiro]

On 05/29/2018 12:16 PM, michaelof--- via Mailman-Users wrote:

> Maybe a silly question: for what (specific) "wrapper configuration file" 
> mailman is searching for??


That's a Suse question. Standard GNU Mailman has no such message. Read
the Suse Mailman docs to see what they say about this.


> Any chance to get mailman's log more verbosive, temporarily?


No. Suse changed the wrapper and the message you got is it.

OK, I googled a bit and found


They patch out all the nice error messages and instead put in their own
stuff. The error in the subject means the file
/etc/mailman/mailman.cgi-gid doesn't exist. It should exist and if I
read the code correctly, contain the numeric GID of the web server.

-- 
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/archive%40jab.org

Re: [Mailman-Users] Filtering messages with no subject

[Bryan Blackwell]

On May 29, 2018, at 4:33 PM, Mark Sapiro  wrote:
> 
> Use header_filter_rules (on the admin Privacy options... -> Spam filters
> page.
> 
> A regexp of
> 
> ^subject:\s*(\(no subject\))?\s*$
> 
> will match messages with an empty Subject: header or literally '(no
> subject)', but it's more complicated than that because the message may
> have no Subject: header at all. To account for that you need three
> rules. The first of these has the regexp above with an action of
> discard. The second has the regexp
> 
> ^subject:
> 
> and an action of accept to accept messages with Subject: headers that
> didn't match the first rule, and the third has the regexp
> 
> ^.*$
> 
> and action discard to discard all messages that got past the first two,
> i.e. those with no Subject: header at all.
> 
> If you already have header_filter_rules, these three are added after the
> others. Otherwise, they are the only rules.
> 
Excellent, thanks.  I put them in with 'hold' instead of 'discard' for now just 
in case I made a mistake.  Right now I have a bunch of lines in the Legacy 
section, is it ok to leave those in place?

--Bryan
--
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] Filtering messages with no subject

[Mark Sapiro]

On 5/29/18 1:01 PM, Bryan Blackwell wrote:
> Hi folks,
> 
> I'm having trouble with some spam using spoofed addresses getting through to 
> my lists, they all seem to have no subject.  I don't see any obvious way to 
> filter these, am I missing an option?  If not, has anyone implemented a 
> filter to block these sorts of messages?


Use header_filter_rules (on the admin Privacy options... -> Spam filters
page.

A regexp of

^subject:\s*(\(no subject\))?\s*$

will match messages with an empty Subject: header or literally '(no
subject)', but it's more complicated than that because the message may
have no Subject: header at all. To account for that you need three
rules. The first of these has the regexp above with an action of
discard. The second has the regexp

^subject:

and an action of accept to accept messages with Subject: headers that
didn't match the first rule, and the third has the regexp

^.*$

and action discard to discard all messages that got past the first two,
i.e. those with no Subject: header at all.

If you already have header_filter_rules, these three are added after the
others. Otherwise, they are the only rules.

-- 
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/archive%40jab.org

[Mailman-Users] Filtering messages with no subject

[Bryan Blackwell]

Hi folks,

I'm having trouble with some spam using spoofed addresses getting through to my 
lists, they all seem to have no subject.  I don't see any obvious way to filter 
these, am I missing an option?  If not, has anyone implemented a filter to 
block these sorts of messages?

Thanks for any help,

--Bryan

--  Bryan Blackwell --
Unix Systems Engineer
br...@skiblack.com



--
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] confirmation string is not working

[Mark Sapiro]

On 5/29/18 10:57 AM, Henrique Fagundes wrote:
> 
> I solved this problem by disabling https.
> So that when redirecting from http to https occurred, the cache was lost.


If you want to require https, the proper way to fix this is discussed in
steps 2 and 3 at .

-- 
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/archive%40jab.org

Re: [Mailman-Users] (2.1.26) Mailman CGI error!!! The Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog: Cannot open wrapper configuration file: No such file or

[michaelof--- via Mailman-Users]

Mark,

thank you for answering so detailed!


Am 29.05.2018 um 19:37 schrieb Mark Sapiro:
> On 05/29/2018 03:19 AM, michaelof--- via Mailman-Users wrote:
>>
>> After upgrading the VPS to OpenSuse Leap 15.0, Mailman still 2.1.26, Apache 
>> from 2.4.23 to 2.4.33, Python from 2.7.13 to
>> 2.7.14, I'm getting the error message in the subject of this mail when 
>> trying to access the mailman web pages on Apache.
> 
> 
> Is there anything in Mailman's error log?

My Mailman has been talking to my Postfix, so (forgot where this was defined) 
uses also Postfix's log files. Postfix
errors on OpenSuse go to /var/log/mail.err.

Independent if I call via Browser / Apache or directly, or in the cgi-bin dir 
with ./listinfo as root, or with "su -u
mailman ./listinfo", result in mail.err is always the same added line:

2018-05-29T20:31:14.894893+02:00 vserver Mailman cgi-wrapper (listinfo): Cannot 
open wrapper configuration file: No such
file or directory

Means
a) that logging itself is possible but
b) log does not add any value for narrowing down the problem, at least not for 
me :-(

Maybe a silly question: for what (specific) "wrapper configuration file" 
mailman is searching for??

Any chance to get mailman's log more verbosive, temporarily?

I'm 100% sure for OpenSuse that as well apache (wwwrun/www) as mailman 
(mailman/mailman) haven't changed their username
and unix group for at least the last 3 centuries, in IT timing :-) I'm also 
sure (checked in backup) that the numeric
UIDs and GIDs haven't changed.

> 
> 
>> - Got the hint from #httpd, that the error msg has nothing to to with apache 
>> itself. Tested to run e.g. "listinfo"
>> manually, same error:
>>
>> vserver:/usr/lib/mailman/cgi-bin # ./listinfo
>> Content-type: text/html
>>
>> 
>> Mailman CGI error!!!
>> 
>> Mailman CGI error!!!
>> The Mailman CGI wrapper encountered a fatal error. This entry is being 
>> stored in your syslog:
>> 
>> Cannot open wrapper configuration file: No such file or directory
> 
> 
> This comes from the various cgi-bin wrappers themselves when they
> encounter a fatal error.
> 
> First of all, when trying to debug by running these from the command
> line you have to run them as the web server user. I.e.,
> 
> sudo -u xxx ./listinfo

done, see above

> 
> where xxx is the user the web server runs as. The issues that cause this
> are GROUP_NAME_NOT_FOUND, GROUP_MISMATCH or failure to set the effective
> GID.
> 
> If the wrapper was able to write Mailman's error log, the message there
> should give details. If there's nothing in the error log, you might try
> temporarily setting o+w in the log file to see if that allows writing
> the message.

no (more) details in log except error msg, see above

> 
> If the upgrade somehow changed the user:group that apaches runs as, that
> would cause this.

For sure not changed, see above

> 
> If your Mailman is installed from source, you may need to rerun
> configure with a different --with-cgi-gid option and make install. If
> it's a Suse package, this is a Suse issue.
> 

no change in gid/uid, could open an OpenSuse Bugzilla issue, but not a real how 
to start / get the OpenSuse team
convinced that this is not an issue on my side/config or a mailman issue


--
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] confirmation string is not working

[Henrique Fagundes]

Dear,

To give continuity to this topic that I found on the internet 
(https://mail.python.org/pipermail/mailman-users/2012-May/073367.html)


I also went through that.

I solved this problem by disabling https.
So that when redirecting from http to https occurred, the cache was lost.

Forgive me for any incorrect spelling. I am Brazilian and I have 
difficulties with English.


Regards,

Henrique Fagundes
supo...@aprendendolinux.com
Skype: magnata-br-rj
Linux User: 475399

https://www.aprendendolinux.com
https://www.facebook.com/AprendendoLinux
https://youtube.com/AprendendoLinux
https://twitter.com/AprendendoLinux
https://telegram.me/AprendendoLinux
__
Participe do Grupo Aprendendo Linux
https://listas.aprendendolinux.com/listinfo/aprendendolinux

Ou envie um e-mail para:
aprendendolinux-subscr...@listas.aprendendolinux.com

--
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] "Freezing" mailing list

[Tatsuo Ishii]

>>> You could set the list to require moderator approval for subscription,
>>> then simply discard all subscription requests.

I have already done it. Problem is, I'm getting more and more
subscription requests from spammers these days.

>> Or you could put
>>^.
>>in the list's ban_list to ban any address containing at least one
>> character from subscribing.

Thanks. I will try this way.

> Please note, putting pattern to match all addresses, it also prevent
> changing mail address to subscribe.

Thanks for the caution.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
--
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] "Freezing" mailing list

[Yasuhito FUTATSUKI]

On 05/30/18 02:00, Mark Sapiro wrote:

On 05/29/2018 09:45 AM, Phil Stracchino wrote:

On 05/29/18 10:20, Tatsuo Ishii wrote:

Hi,

I would like to "freeze" an existing mailing list: I want to keep the
mailing list but I want no one newly subscribe the list. Can you
please anyone tell me how I can implement it?



You could set the list to require moderator approval for subscription,
then simply discard all subscription requests.



Or you could put

^.

in the list's ban_list to ban any address containing at least one
character from subscribing.


Please note, putting pattern to match all addresses, it also prevent
changing mail address to subscribe.

--

Yasuhito 
--
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] (2.1.26) Mailman CGI error!!! The Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog: Cannot open wrapper configuration file: No such file or

[Mark Sapiro]

On 05/29/2018 03:19 AM, michaelof--- via Mailman-Users wrote:
> 
> After upgrading the VPS to OpenSuse Leap 15.0, Mailman still 2.1.26, Apache 
> from 2.4.23 to 2.4.33, Python from 2.7.13 to
> 2.7.14, I'm getting the error message in the subject of this mail when trying 
> to access the mailman web pages on Apache.


Is there anything in Mailman's error log?


> - Got the hint from #httpd, that the error msg has nothing to to with apache 
> itself. Tested to run e.g. "listinfo"
> manually, same error:
> 
> vserver:/usr/lib/mailman/cgi-bin # ./listinfo
> Content-type: text/html
> 
> 
> Mailman CGI error!!!
> 
> Mailman CGI error!!!
> The Mailman CGI wrapper encountered a fatal error. This entry is being stored 
> in your syslog:
> 
> Cannot open wrapper configuration file: No such file or directory


This comes from the various cgi-bin wrappers themselves when they
encounter a fatal error.

First of all, when trying to debug by running these from the command
line you have to run them as the web server user. I.e.,

sudo -u xxx ./listinfo

where xxx is the user the web server runs as. The issues that cause this
are GROUP_NAME_NOT_FOUND, GROUP_MISMATCH or failure to set the effective
GID.

If the wrapper was able to write Mailman's error log, the message there
should give details. If there's nothing in the error log, you might try
temporarily setting o+w in the log file to see if that allows writing
the message.

If the upgrade somehow changed the user:group that apaches runs as, that
would cause this.

If your Mailman is installed from source, you may need to rerun
configure with a different --with-cgi-gid option and make install. If
it's a Suse package, this is a Suse issue.

-- 
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/archive%40jab.org

Re: [Mailman-Users] Unsubscribe link

[Mark Sapiro]

On 05/29/2018 06:49 AM, nikos wrote:
>Hello list.
> 
>Is possible to insert somehow a unsubscribe link inside the message
>instead in footer?


There is no way short of modifying code to insert personalized
information in the body of a message.

There are ways to ensure the footer is appended to the message body
rather than added as a separate MIME part (attachment), but this
involves setting content filtering to reduce the message to a single
text/plain part or setting scrub_nondigest to Yes. See the wiki page at
 and the "(Details for
scrub_nondigest)" link on the admin Non-digest options page.

-- 
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/archive%40jab.org

Re: [Mailman-Users] "Freezing" mailing list

[Mark Sapiro]

On 05/29/2018 09:45 AM, Phil Stracchino wrote:
> On 05/29/18 10:20, Tatsuo Ishii wrote:
>> Hi,
>>
>> I would like to "freeze" an existing mailing list: I want to keep the
>> mailing list but I want no one newly subscribe the list. Can you
>> please anyone tell me how I can implement it?
> 
> 
> You could set the list to require moderator approval for subscription,
> then simply discard all subscription requests.


Or you could put

^.

in the list's ban_list to ban any address containing at least one
character from subscribing.

-- 
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/archive%40jab.org

Re: [Mailman-Users] "Freezing" mailing list

[Phil Stracchino]

On 05/29/18 10:20, Tatsuo Ishii wrote:
> Hi,
> 
> I would like to "freeze" an existing mailing list: I want to keep the
> mailing list but I want no one newly subscribe the list. Can you
> please anyone tell me how I can implement it?


You could set the list to require moderator approval for subscription,
then simply discard all subscription requests.




-- 
  Phil Stracchino
  Babylon Communications
  ph...@caerllewys.net
  p...@co.ordinate.org
  Landline: +1.603.293.8485
  Mobile:   +1.603.998.6958
--
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] updating mailman

[Mark T]

Hi can anyone give me easy instructions  to update mailman
Using the apt-get install process 
Also will  it keep all my mailing lists and members
Many thanks mark.

Tune in to the number one station on the web TAFN radio 
http://tafn.org.uk/listen
Or for our catch up service on demand http://www.tafn.org.uk/on-demand 
or for our upcoming weekly schedule 
http://www.tafn.org.uk/radio
part of the accessible friends network 
www.tafn.org.uk
Registered UK Charity: #1108043.
Sent from Windows 10 Mail.

--
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] Unsubscribe link

[specktator]

Nick, I've tried that too. I don't think there's a way ... or at least I 
haven't found it yet



On 29/05/2018 04:49 μμ, nikos wrote:

Hello list.

Is possible to insert somehow a unsubscribe link inside the message
instead in footer?

After many tries I manage to put a direct link in footer, setting Full
Personalization ON first. The problem is that Outlook attach footer and
most users ignore it. So it could be useful to putt a link inside message.

I use version 2.1.12 on Centos 6.

Thank you in advance
--
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/specktator%40totallynoob.com


--
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] Unsubscribe link

[Christian F Buser via Mailman-Users]

Hello nikos. On Tue, 29 May 2018 16:49:13 +0300, you wrote:

>Is possible to insert somehow a unsubscribe link inside the message
>instead in footer?
> 
>After many tries I manage to put a direct link in footer, setting Full
>Personalization ON first. The problem is that Outlook attach footer and
>most users ignore it. So it could be useful to putt a link inside 
>message.

I am not sure - but when I was young, I learnt that the standard separator for 
a footer in internet mail is "-- " (without the quotes, of course). 

Try changing that to - for example - "" or 
"" and look how Outlook treats it then. 

Christian 

-- 
Christian F. Buser, Hohle Gasse 6, CH-5507 Mellingen (Switzerland)  
Hilfe fuer Strassenkinder in Ghana: http://www.chance-for-children.org
--
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] (2.1.26) Mailman CGI error!!! The Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog: Cannot open wrapper configuration file: No such file or dire

[michaelof--- via Mailman-Users]

Hello to all,


first post to this mailing list, so first of all thank you very much to all who 
helped to make Mailman and it's
community reality!

I'm running mailman now for a while without issues. On my VPS, not a big 
installation, not many lists, just a few users
per list.

After upgrading the VPS to OpenSuse Leap 15.0, Mailman still 2.1.26, Apache 
from 2.4.23 to 2.4.33, Python from 2.7.13 to
2.7.14, I'm getting the error message in the subject of this mail when trying 
to access the mailman web pages on Apache.

All other Apache sites (non-Mailman, like TYPO3, Nextcloud, Roundcubemail, ...) 
/ their Vhosts are running fine.

Relevant part of Apache's error_log:

[Tue May 29 11:46:07.135217 2018] [cgi:error] [pid 24758] [client (IPV6)] 
AH02811: script not found or unable to stat:
/usr/lib/mailman/cgi-bin/favicon.ico
[Tue May 29 11:46:07.486058 2018] [cgi:error] [pid 24758] [client (IPV6)] 
AH02811: script not found or unable to stat:
/usr/lib/mailman/cgi-bin/error
[Tue May 29 11:46:07.267081 2018] [cgi:error] [pid 25456] [client (IPV6)] 
AH02811: script not found or unable to stat:
/usr/lib/mailman/cgi-bin/favicon.ico
[Tue May 29 11:46:07.486381 2018] [cgi:error] [pid 25456] [client (IPV6)] 
AH02811: script not found or unable to stat:
/usr/lib/mailman/cgi-bin/error

--> which is true, but "favicon.ico" and "error" also haven't been existing on 
the fine running Mailman instance before
the OpenSuse upgrade, checked in server backups.

- I've compared (diff) Apache's config files (before and after the upgrade) 
file by file, most of them, esp. all direct
Mailman files, are untouched by the upgrade, others (general httpd) with 
smaller changes, which really shouldn't affect
Mailman.

- Got the hint from #httpd, that the error msg has nothing to to with apache 
itself. Tested to run e.g. "listinfo"
manually, same error:

vserver:/usr/lib/mailman/cgi-bin # ./listinfo
Content-type: text/html


Mailman CGI error!!!

Mailman CGI error!!!
The Mailman CGI wrapper encountered a fatal error. This entry is being stored 
in your syslog:

Cannot open wrapper configuration file: No such file or directory


- In contrast the executables in /usr/lib/mailman/bin are working fine, tested 
with e.g. "version", "check_db",
"list_lists", all working as expected

- Also Mailman systemd unit seems to run fine:

vserver:~ # systemctl status mailman
● mailman.service - LSB: Starts the mailinglist manager Mailman
   Loaded: loaded (/etc/init.d/mailman; generated; vendor preset: disabled)
   Active: active (running) since Mon 2018-05-28 19:39:09 CEST; 16h ago
 Docs: man:systemd-sysv-generator(8)
Tasks: 9 (limit: 629145)
   CGroup: /system.slice/mailman.service
   ├─1946 /usr/bin/python /usr/lib/mailman/bin/mailmanctl --quiet 
--stale-lock-cleanup start
   ├─1948 /usr/bin/python /usr/lib/mailman/bin/qrunner 
--runner=ArchRunner:0:1 -s
   ├─1949 /usr/bin/python /usr/lib/mailman/bin/qrunner 
--runner=BounceRunner:0:1 -s
   ├─1950 /usr/bin/python /usr/lib/mailman/bin/qrunner 
--runner=CommandRunner:0:1 -s
   ├─1951 /usr/bin/python /usr/lib/mailman/bin/qrunner 
--runner=IncomingRunner:0:1 -s

   ├─1952 /usr/bin/python /usr/lib/mailman/bin/qrunner 
--runner=NewsRunner:0:1 -s

   ├─1953 /usr/bin/python /usr/lib/mailman/bin/qrunner 
--runner=OutgoingRunner:0:1 -s

   ├─1954 /usr/bin/python /usr/lib/mailman/bin/qrunner 
--runner=VirginRunner:0:1 -s

   └─1955 /usr/bin/python /usr/lib/mailman/bin/qrunner 
--runner=RetryRunner:0:1 -s



Mai 28 19:39:08 vserver systemd[1]: Starting LSB: Starts the mailinglist 
manager Mailman...

Mai 28 19:39:09 vserver mailman[1933]: Starting mailman..done

Mai 28 19:39:09 vserver systemd[1]: Started LSB: Starts the mailinglist manager 
Mailman.

- Vhost definition, unchanged:







ServerName mailman.domain.tld:443

Include /etc/apache2/conf.d/mailman.conf


DirectoryIndex listinfo
ScriptAlias /   /usr/lib/mailman/cgi-bin/


#   SSL Engine Switch:
#   Enable/Disable SSL for this virtual host.
SSLEngine on


  Header always set Strict-Transport-Security "max-age=15552000; 
preload"








Stopping now with config files, avoiding getting this mail bigger and bigger :-)


As I'm completely running of of ideas now, I would be very happy about new 
ideas/hints what might be the problem, where
to continue searching for the issue.


Thanks in advance,
regards,
Michael



--
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] "Freezing" mailing list

[Tatsuo Ishii]

Hi,

I would like to "freeze" an existing mailing list: I want to keep the
mailing list but I want no one newly subscribe the list. Can you
please anyone tell me how I can implement it?

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
--
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] Unsubscribe link

[nikos]

   Hello list.

   Is possible to insert somehow a unsubscribe link inside the message
   instead in footer?

   After many tries I manage to put a direct link in footer, setting Full
   Personalization ON first. The problem is that Outlook attach footer and
   most users ignore it. So it could be useful to putt a link inside message.

   I use version 2.1.12 on Centos 6.

   Thank you in advance
--
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