From mark at msapiro.net  Wed Jul  1 16:24:03 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 01 Jul 2015 07:24:03 -0700
Subject: [Mailman-Users] Sub-lists
In-Reply-To: <CAGrTZgwZBxNhPCLoscMO1uOLoGZeVBqjpXrK=SUNeMqezgNwKw@mail.gmail.com>
References: <CAGrTZgwZBxNhPCLoscMO1uOLoGZeVBqjpXrK=SUNeMqezgNwKw@mail.gmail.com>
Message-ID: <5593F803.70904@msapiro.net>

On 06/30/2015 12:56 PM, Ron Webb wrote:
> I am looking to set-up a mailing list for a group of people but was hoping
> there is a way to have sub-lists. For example, I'd like to have one group
> be everyone, then another group that is regional. I was thinking of "
> group-all at mydomain.com" for messages covering everyone but they could send
> a message to "group-sacramento at mydomain.com" to and it will only go to
> those that are interested in "Sacramento" specific messages. I would like
> to make subscribers opt-in or opt-out of the regional. At this point, I
> have not selected a hosting service yet. I wish to bring my own domain to
> wherever I choose. I'm not sure if someone that just advertises that they
> use Mailman is sufficient or if I need to find a hosting company that
> provides shell access for setup is what I need. I'm sure there is some Wiki
> or something if this sub-lists works but I must be using the wrong search
> term for what I want.


Mailman can do this in a few different ways, all with standard list
configuration settings available to the list owner.

One possibility is 'topics'. You could have a list with several defined
topics like 'Sacramento'. You define regular expressions to be matched
against the message's Subject:. These can be simple like

a Sacramento topic with a regex of 'sac'
a Washington topic with a regex of 'wash'

and so on. Then, by default, a user gets all messages, but if she
subscribes to the Sacramento topic and also elects to receive posts that
match no topic, she will receive posts whose Subject: contains ...sac...
and those whose Subject : matches none of the topic regexes (keywords),
but not posts with ...wash..., etc. in the Subject:

Other ways to do this are umbrella lists and sibling lists.

See the FAQs at <http://wiki.list.org/x/4030574> and
<http://wiki.list.org/x/4030540>. Also, see
<http://wiki.list.org/x/8683547>.


> Another thing that is important for me is I do NOT want to archive or cache
> messages, at least for not much more than a day.


Archiving is a list option which is generally on by default, but easily
turned off.


> I will also wish to add some type of disclaimer that no one will probably
> give it much thought, but it will state that statements made are the of the
> sole responsibility of the author of the statement and they are not the
> official opinion of the corporation nor the union and the maintainer of the
> list does not archive messages. I'm sure I'll come up with much better
> wording than that but I'm sure you get the gist.


Mailman can add a header and/or a footer to each message with any text
you want.


> I'm just hoping I've found the right product and can receive some advice
> from those that have set up lists.


I think Mailman can do what you want. We are here to help.

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

From mark at msapiro.net  Wed Jul  1 16:29:35 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 01 Jul 2015 07:29:35 -0700
Subject: [Mailman-Users] HTML footers in multipart emails
In-Reply-To: <1993545582.1784545.1435656508803.JavaMail.zimbra@albourne.com>
References: <1993545582.1784545.1435656508803.JavaMail.zimbra@albourne.com>
Message-ID: <5593F94F.4010603@msapiro.net>

On 06/30/2015 02:28 AM, Yiannis Pericleous wrote:
> 
> I have a multipart (html and text) email and I wish to add an unsubscribe footer to it. However mailman appends the footer as a new section that is plain text. Is there a way of making the footer section text/html. If not, any other way to include the unsubscribe link in the html part of the email?


Standard Mailman does not do either of those things. See the FAQ at
<http://wiki.list.org/x/4030707> for info on footers. You could use a
custom handler to add text to message bodies. See
<http://wiki.list.org/x/4030615> for info on using custom handlers.

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

From Jan at EcoReality.org  Wed Jul  1 22:17:23 2015
From: Jan at EcoReality.org (Jan Steinman)
Date: Wed, 1 Jul 2015 13:17:23 -0700
Subject: [Mailman-Users] Cannot remove a person! Help!
In-Reply-To: <mailman.52.1433239204.17090.mailman-users@python.org>
References: <mailman.52.1433239204.17090.mailman-users@python.org>
Message-ID: <66DFAED6-3739-4309-97E5-0A5BF357F7D3@EcoReality.org>

I run a half-dozen lists using Mailman 2.1.14 as supplied by Mac OS X Server 10.6.8 (please don't shoot me for using that evil hacked version that came with my system!)

My not-soon-enough-to-be-ex spouse is getting bounce notices at the end of the month, when the monthly reminder goes out.

Going through the Mailman web admin, I can't see anywhere that her address (or any addresses likely to be forwarded to her) is being used.

What else can I do to purge her email from Mailman? We have a tentative settlement, and she's itching for reasons to fight, and getting unwanted email might be enough to nix the whole deal...

Jan

From pshute at nuw.org.au  Thu Jul  2 01:22:57 2015
From: pshute at nuw.org.au (Peter Shute)
Date: Thu, 2 Jul 2015 09:22:57 +1000
Subject: [Mailman-Users] Sub-lists
In-Reply-To: <CAGrTZgwZBxNhPCLoscMO1uOLoGZeVBqjpXrK=SUNeMqezgNwKw@mail.gmail.com>
References: <CAGrTZgwZBxNhPCLoscMO1uOLoGZeVBqjpXrK=SUNeMqezgNwKw@mail.gmail.com>
Message-ID: <C2F1879073AE7347BAB44065F143E17001955CF917@nuwvicms2>

Ron Webb wrote:
> If there 
> is any concern about something said, as the facilitator of 
> communications, I wish to just say I do not save 
> communications. If a group member wishes to save something, 
> that is up to them, as is the case with how we are doing email now.
> 
> I will also wish to add some type of disclaimer that no one 
> will probably give it much thought, but it will state that 
> statements made are the of the sole responsibility of the 
> author of the statement and they are not the official opinion 
> of the corporation nor the union and the maintainer of the 
> list does not archive messages. I'm sure I'll come up with 
> much better wording than that but I'm sure you get the gist.

This part could be tricky. Most list members will "save" (i.e. forget to delete) at least some if not most of the messages they receive. Lots of them will contain quoted material written by other list members. In other words, none of you will have much control over how much of what you say on the list will be available to others later if they get access to list members' mailboxes.

Are these corporate mailboxes you'll be using, or private ones? I've never used it, but you can have regular expression in ban_list to prevent people subscribing with their work addresses. 

Peter Shute

From mark at msapiro.net  Thu Jul  2 02:23:59 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 01 Jul 2015 17:23:59 -0700
Subject: [Mailman-Users] Cannot remove a person! Help!
In-Reply-To: <66DFAED6-3739-4309-97E5-0A5BF357F7D3@EcoReality.org>
References: <mailman.52.1433239204.17090.mailman-users@python.org>
 <66DFAED6-3739-4309-97E5-0A5BF357F7D3@EcoReality.org>
Message-ID: <5594849F.6010105@msapiro.net>

On 07/01/2015 01:17 PM, Jan Steinman wrote:
> 
> My not-soon-enough-to-be-ex spouse is getting bounce notices at the end of the month, when the monthly reminder goes out.


You mean what? She is being sent password reminders that bounce or just
what do you mean by "getting bounce notices at the end of the month".
Are thes notices bounce of mail sent to her that you receive or is she
receiving a bounce of something she's sending or a bounce as a list
owner/moderator?

Do you have a copy of one of these messages. If so, the headers and or
body should reveal where it comes from and where it is sent.


> Going through the Mailman web admin, I can't see anywhere that her address (or any addresses likely to be forwarded to her) is being used.


If she's getting mail from Mailman, an address that delivers to her is
an owner or moderator or member of some list. Mailman's bin/find_members
will find all members of all lists matching a provided regexp.
'bin/list_owners -wm' will list all owners and moderators by list.

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

From mark at msapiro.net  Thu Jul  2 03:24:21 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 01 Jul 2015 18:24:21 -0700
Subject: [Mailman-Users] Mailman 2.1.18-1 not respecting add_virtualhost
In-Reply-To: <55943A56.4000208@scratchspace.com>
References: <53EBEB9C.3060806@scratchspace.com> <53ED01FE.2080908@msapiro.net>
 <53ED08F8.8010100@scratchspace.com> <53ED123E.6040307@msapiro.net>
 <53ED196F.6060108@scratchspace.com> <53ED54EF.3040301@msapiro.net>
 <53ED5D23.4070705@scratchspace.com> <53ED6093.9090304@msapiro.net>
 <55943A56.4000208@scratchspace.com>
Message-ID: <559492C5.6080702@msapiro.net>

On 07/01/2015 12:07 PM, Chris Miller wrote:

> 
> We have corrected this problem by creating the subdirectories, moving
> the lists in to the proper sub directory, and setting permissions. We
> are still having trouble with fix_url.


I'm just confirming that I've seen this and will look at it at some
point this week, but not immediately.

It may be that fix_url never did the right thing, but I need to look in
detail.

I think however that you have made a mistake in that both the
subdirectory name in the lists/ directory and the domain part of the
listname in the fix_url command should be the email host, not the web
host. I.e. no lists. prefix, at least with settings like

add_virtualhost('lists.fakedomain.com', 'fakedomain.com')


> To clarify, mm_cfg.py does contain the correct info for the lists, this all broke during the upgrade to 2.1.18 to utilize the DMARC features.


What exactly are you running? Are you running code from
<https://code.launchpad.net/~msapiro/mailman/vhost>? I wouldn't be too
surprised if it's broken. I think the last thing I actually did to that
branch other than untested merges of the upstream branch upon releases
was over two years ago.

I will look into it.

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

From stephen at xemacs.org  Thu Jul  2 05:07:07 2015
From: stephen at xemacs.org (Stephen J. Turnbull)
Date: Thu, 02 Jul 2015 12:07:07 +0900
Subject: [Mailman-Users] Sub-lists
In-Reply-To: <C2F1879073AE7347BAB44065F143E17001955CF917@nuwvicms2>
References: <CAGrTZgwZBxNhPCLoscMO1uOLoGZeVBqjpXrK=SUNeMqezgNwKw@mail.gmail.com>
 <C2F1879073AE7347BAB44065F143E17001955CF917@nuwvicms2>
Message-ID: <87ioa3i7fo.fsf@uwakimon.sk.tsukuba.ac.jp>

Peter Shute writes:
 > Ron Webb wrote:

 > > I will also wish to add some type of disclaimer that no one 
 > > will probably give it much thought, but it will state that 
 > > statements made are the of the sole responsibility of the 
 > > author of the statement and they are not the official opinion 
 > > of the corporation nor the union and the maintainer of the 
 > > list does not archive messages. I'm sure I'll come up with 
 > > much better wording than that but I'm sure you get the gist.
 > 
 > This part could be tricky. Most list members will "save"
 > (i.e. forget to delete) at least some if not most of the messages
 > they receive. Lots of them will contain quoted material written by
 > other list members. In other words, none of you will have much
 > control over how much of what you say on the list will be available
 > to others later if they get access to list members' mailboxes.

That's certainly true, but I suppose Ron is mostly worried here about
his *personal* liability as list admin, both legal and ethically to
the members whose posts are supposed to be off-the-record.  Compare
http://www.jwz.org/gruntle/rbarip.html.  Centralized list archives are
an obvious target, and I suspect that subpoena'ing everyone in the
company would be less likely to convince a judge.

 > Are these corporate mailboxes you'll be using, or private ones?
 > I've never used it, but you can have regular expression in ban_list
 > to prevent people subscribing with their work addresses.

That's a good idea for dealing with corporate policy toward mailbox
use, but as Jamie points out, if there's a court involved, anything
can be subpoena'ed.

Of course all of the above is based on US law, your venue may vary.





From pshute at nuw.org.au  Thu Jul  2 07:21:10 2015
From: pshute at nuw.org.au (Peter Shute)
Date: Thu, 2 Jul 2015 15:21:10 +1000
Subject: [Mailman-Users] Sub-lists
In-Reply-To: <87ioa3i7fo.fsf@uwakimon.sk.tsukuba.ac.jp>
References: <CAGrTZgwZBxNhPCLoscMO1uOLoGZeVBqjpXrK=SUNeMqezgNwKw@mail.gmail.com>
 <C2F1879073AE7347BAB44065F143E17001955CF917@nuwvicms2>
 <87ioa3i7fo.fsf@uwakimon.sk.tsukuba.ac.jp>
Message-ID: <C2F1879073AE7347BAB44065F143E17001955CF925@nuwvicms2>

Stephen J. Turnbull wrote:

>  > Are these corporate mailboxes you'll be using, or private ones?
>  > I've never used it, but you can have regular expression in 
> ban_list  > to prevent people subscribing with their work addresses.
> 
> That's a good idea for dealing with corporate policy toward 
> mailbox use, but as Jamie points out, if there's a court 
> involved, anything can be subpoena'ed.

True. I was thinking more along the lines of someone taking an unofficial peek at a few mailboxes to compile an unofficial hit list.

Peter Shute

From Y.Pericleous at albourne.com  Thu Jul  2 11:30:48 2015
From: Y.Pericleous at albourne.com (Yiannis Pericleous)
Date: Thu, 2 Jul 2015 09:30:48 +0000 (UTC)
Subject: [Mailman-Users] HTML footers in multipart emails
In-Reply-To: <5593F94F.4010603@msapiro.net>
References: <1993545582.1784545.1435656508803.JavaMail.zimbra@albourne.com>
 <5593F94F.4010603@msapiro.net>
Message-ID: <578996416.1884005.1435829448947.JavaMail.zimbra@albourne.com>

Ok, thanks for the tip.

It seems I need to provide a custom Decorate Handler, as I need personalization data in my footer.

What is the recommended way of doing it?, edit Decorate.py directly (I'd rather not), create a custom SMTPDirect.py that calls my CustomDecorate.py, something else?
If I create a custom SMTPDirect, can I set the DELIVERY_MODULE per list or is it a global only option?

thanks

----- Original Message -----
> On 06/30/2015 02:28 AM, Yiannis Pericleous wrote:
> > 
> > I have a multipart (html and text) email and I wish to add an unsubscribe
> > footer to it. However mailman appends the footer as a new section that is
> > plain text. Is there a way of making the footer section text/html. If not,
> > any other way to include the unsubscribe link in the html part of the
> > email?
> 
> 
> Standard Mailman does not do either of those things. See the FAQ at
> <http://wiki.list.org/x/4030707> for info on footers. You could use a
> custom handler to add text to message bodies. See
> <http://wiki.list.org/x/4030615> for info on using custom handlers.
> 
> --
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at 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/y.pericleous%40albourne.com
> 

From ctodd at scratchspace.com  Wed Jul  1 21:07:02 2015
From: ctodd at scratchspace.com (Chris Miller)
Date: Wed, 01 Jul 2015 12:07:02 -0700
Subject: [Mailman-Users] Mailman 2.1.18-1 not respecting add_virtualhost
In-Reply-To: <53ED6093.9090304@msapiro.net>
References: <53EBEB9C.3060806@scratchspace.com> <53ED01FE.2080908@msapiro.net>
 <53ED08F8.8010100@scratchspace.com> <53ED123E.6040307@msapiro.net>
 <53ED196F.6060108@scratchspace.com> <53ED54EF.3040301@msapiro.net>
 <53ED5D23.4070705@scratchspace.com> <53ED6093.9090304@msapiro.net>
Message-ID: <55943A56.4000208@scratchspace.com>

On 8/14/2014 6:21 PM, Mark Sapiro wrote:
> On 08/14/2014 06:06 PM, Chris Miller wrote:
>> On 8/14/2014 5:31 PM, Mark Sapiro wrote:
>>
>> I sent you a PM with output.
>
> OK. I'll respond when it gets through my greylisting.
>
>
>>> The vhost has issues. In particular bin/withlist -l does not work with
>>> hostname/listname type lists.
>
> Actually, it does. It's been so long since I looked at this, I forgot.
> the command for a list whose config directory is hostname/listname is
>
> bin/withlist -l -r fix_url listname at hostname -u web_hostname
>
>
>> I am confused as well. To restate the question is it possible I just
>> need to create the hostname directories and reorganize everything?
>
> That might work, but fix_url should work on a list whose directory is
> directly under lists/. The mystery here is it apparently doesn't.
>


Sorry to re-ignite this so late. To recap, the problem with our 
Mailman config is that all mailing lists were created under 
/var/lib/mailman/lists instead of /var/lib/mailman/lists/<hostname>.

We have corrected this problem by creating the subdirectories, 
moving the lists in to the proper sub directory, and setting 
permissions. We are still having trouble with fix_url.

If we run this the traditional way, we get an error :

root at mail /var/lib/mailman/lists $ ~mailman/bin/withlist -l -r 
fix_url brewclubtest -u lists.fakedomain.com
Importing fix_url...
Running fix_url.fix_url()...
Loading list brewclubtest (locked)
Unknown list: brewclubtest
Traceback (most recent call last):
   File "/usr/lib/mailman/bin/withlist", line 299, in <module>
     main()
   File "/usr/lib/mailman/bin/withlist", line 277, in main
     r = do_list(listname, args, func)
   File "/usr/lib/mailman/bin/withlist", line 202, in do_list
     return func(m, *args)
   File "/usr/lib/mailman/bin/fix_url.py", line 73, in fix_url
     if not mlist.Locked():
AttributeError: 'NoneType' object has no attribute 'Locked'


If we use the <listname at hostname> method, the command completes 
correctly, but then we have issues with the web interface :

root at mail /var/lib/mailman/lists $ ~mailman/bin/withlist -l -r 
fix_url brewclubtest at lists.brewclub.org -u lists.fakedomain.com
Importing fix_url...
Running fix_url.fix_url()...
Loading list brewclubtest at lists.fakedomain.com (locked)
Saving list
Finalizing

When we go to the list page here :

http://lists.fakedomain.com/mailman/admin/brewclubtest

The list is present, but there is an error in red at the top of the 
screen that says "No such list brewclubtest at fakedomain.com". Please 
note that the hostname "lists" was stripped from the error.

We are able to login to the list URL which now contains 
<listname at hostname> in the URL :

http://lists.fakedomain.com/mailman/admin/brewclubtest at lists.fakedomain.com

But clicking any links in the admin interface appends 
@fakedomain.com which results in a new login prompt :

http://lists.fakedomain.com/mailman/admin/brewclubtest at lists.fakedomain.com@fakedomain.com/members



It seems like fix_url needs to be patched to use the traditional 
method of using only the list URL, and/or needs to be patched to 
properly handle the <listname at hostname> method.

To clarify, mm_cfg.py does contain the correct info for the lists, 
this all broke during the upgrade to 2.1.18 to utilize the DMARC 
features.

VIRTUAL_HOSTS.clear()
DEFAULT_URL_PATTERN = 'http://%s/mailman/'
VIRTUAL_HOST_OVERVIEW = On
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
add_virtualhost('lists.fakedomain.com', 'fakedomain.com')

Thoughts?

-- 

Regards,
     Chris

Chris Miller
President - Rocket Scientist
ScratchSpace Inc.
(831) 621-7928
http://www.scratchspace.com


From mark at msapiro.net  Thu Jul  2 15:47:32 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 02 Jul 2015 06:47:32 -0700
Subject: [Mailman-Users] HTML footers in multipart emails
In-Reply-To: <578996416.1884005.1435829448947.JavaMail.zimbra@albourne.com>
References: <1993545582.1784545.1435656508803.JavaMail.zimbra@albourne.com>
 <5593F94F.4010603@msapiro.net>
 <578996416.1884005.1435829448947.JavaMail.zimbra@albourne.com>
Message-ID: <559540F4.7050408@msapiro.net>

On 07/02/2015 02:30 AM, Yiannis Pericleous wrote:
> 
> It seems I need to provide a custom Decorate Handler, as I need personalization data in my footer.


No. You have a couple of choices. You can investigate using either the
"Patching Mailman to solve this problem" patches ot the "Using
mimedefang to solve this problem" method referenced in the FAQ at
<http://wiki.list.org/x/4030707>

Or you can develop your own custom handler which will add your
unsubscribe footer directly to the text/plain and text/html body parts
of the message.


> What is the recommended way of doing it?, edit Decorate.py directly (I'd rather not), create a custom SMTPDirect.py that calls my CustomDecorate.py, something else?
> If I create a custom SMTPDirect, can I set the DELIVERY_MODULE per list or is it a global only option?


You don't do any of that.

You create Add_Footer.py (or whatever you want to call it), save it in
the Mailman/Handlers/ directory and add 'Add_Footer' to the pipeline
just before 'ToOutgoing' for the lists you want by following
instructions in the FAQ at <http://wiki.list.org/x/4030615>.

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

From sm at noisynotes.com  Thu Jul  2 16:56:26 2015
From: sm at noisynotes.com (Steve Matzura)
Date: Thu, 02 Jul 2015 10:56:26 -0400
Subject: [Mailman-Users] Permissions error
Message-ID: <q2kapaptrp3okh2cf0f9patkhgj0dij0hp@4ax.com>

I have a new Mailman implementation connected to Postfix which is in
turn connected to Dovecot. These two components are working correctly,
as I have mailboxes set up with them and have created a test Mailman
mailing list and received confirmation that it has in fact been
created. Now I'm attempting to subscribe a test user in the normal
way, by sending an email to {list-name}-subscribe at MyDomain.com. I have
not received a subscription confirmation, but the following
information from /var/log/mailman/error shows a problem:

Jul 02 14:15:01 2015 gate_news(18693): Traceback (most recent call
last):
Jul 02 14:15:01 2015 gate_news(18693):   File
"/usr/lib/mailman/cron/gate_news", line 293, in <module>
Jul 02 14:15:01 2015 gate_news(18693):      main()
Jul 02 14:15:01 2015 gate_news(18693):   File
"/usr/lib/mailman/cron/gate_news", line 268, in main
Jul 02 14:15:01 2015 gate_news(18693):      lock.lock(timeout=0.5)
Jul 02 14:15:01 2015 gate_news(18693):   File
"/usr/lib/mailman/Mailman/LockFile.py", line 243, in lock
Jul 02 14:15:01 2015 gate_news(18693):      self.__write()
Jul 02 14:15:01 2015 gate_news(18693):   File
"/usr/lib/mailman/Mailman/LockFile.py", line 422, in __write
Jul 02 14:15:01 2015 gate_news(18693):      fp = open(self.__tmpfname,
'w')
Jul 02 14:15:01 2015 gate_news(18693): IOError :  [Errno 13]
Permission denied:
'/var/lock/mailman/gate_news.lock.{my-system-name}.{MyDomain.com}.18693.0'
Here are the directory permissions:

drwxrwsr-x 2 root mailman 80 Jul  2 13:57 mailman
lrwxrwxrwx 1 root root 11 Sep 14  2012 lock -> ../run/lock

I also receive messages like these about every fifteen minutes in
/var/log/mailman/bounce:

Jul 02 14:42:12 2015 (1308) post to mailman from
mailman-owner@{my-domain.com}, size=1736,
message-id=<mailman.53.1435726803.13146.mailman@{my-domain.com}>, 1
failures
Jul 02 14:42:16 2015 (1308) post to mailman from
mailman-owner@{my-domain.com}, size=1733,
message-id=<mailman.98.1435726804.13146.mailman@{my-domain.com}>, 1
failures

Thanks in advance for any assistance. I suspect it's something I've
overlooked.

From sm at noisynotes.com  Thu Jul  2 16:56:27 2015
From: sm at noisynotes.com (Steve Matzura)
Date: Thu, 02 Jul 2015 10:56:27 -0400
Subject: [Mailman-Users] Unable to access Mailman Web interface
Message-ID: <n6kapadt6pek0cnpdqfqhb6agqt6usk20b@4ax.com>

If I browse to http://{my-node.my-domain.com}/mailman/admin, I get the
following:

Bug in Mailman version 2.1.18-1

Bug in Mailman version 2.1.18-1
We're sorry, we hit a bug!

Please inform the webmaster for this site of this problem. Printing of
traceback and other system information has been explicitly inhibited,
but the webmaster
can find this information in the Mailman error logs. 

If that's supposed to be /var/log/mailman/error, the only thing in
there is what I posted in my previous message. Maybe the two are
related?

From mark at msapiro.net  Thu Jul  2 17:23:23 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 02 Jul 2015 08:23:23 -0700
Subject: [Mailman-Users] Permissions error
In-Reply-To: <q2kapaptrp3okh2cf0f9patkhgj0dij0hp@4ax.com>
References: <q2kapaptrp3okh2cf0f9patkhgj0dij0hp@4ax.com>
Message-ID: <5595576B.3070606@msapiro.net>

On 07/02/2015 07:56 AM, Steve Matzura wrote:
> I have a new Mailman implementation connected to Postfix which is in
> turn connected to Dovecot. These two components are working correctly,
> as I have mailboxes set up with them and have created a test Mailman
> mailing list and received confirmation that it has in fact been
> created. Now I'm attempting to subscribe a test user in the normal
> way, by sending an email to {list-name}-subscribe at MyDomain.com. I have
> not received a subscription confirmation, but the following
> information from /var/log/mailman/error shows a problem:
> 
> Jul 02 14:15:01 2015 gate_news(18693): Traceback (most recent call
> last):
> Jul 02 14:15:01 2015 gate_news(18693):   File
> "/usr/lib/mailman/cron/gate_news", line 293, in <module>
> Jul 02 14:15:01 2015 gate_news(18693):      main()
> Jul 02 14:15:01 2015 gate_news(18693):   File
> "/usr/lib/mailman/cron/gate_news", line 268, in main
> Jul 02 14:15:01 2015 gate_news(18693):      lock.lock(timeout=0.5)
> Jul 02 14:15:01 2015 gate_news(18693):   File
> "/usr/lib/mailman/Mailman/LockFile.py", line 243, in lock
> Jul 02 14:15:01 2015 gate_news(18693):      self.__write()
> Jul 02 14:15:01 2015 gate_news(18693):   File
> "/usr/lib/mailman/Mailman/LockFile.py", line 422, in __write
> Jul 02 14:15:01 2015 gate_news(18693):      fp = open(self.__tmpfname,
> 'w')
> Jul 02 14:15:01 2015 gate_news(18693): IOError :  [Errno 13]
> Permission denied:
> '/var/lock/mailman/gate_news.lock.{my-system-name}.{MyDomain.com}.18693.0'
> Here are the directory permissions:
> 
> drwxrwsr-x 2 root mailman 80 Jul  2 13:57 mailman
> lrwxrwxrwx 1 root root 11 Sep 14  2012 lock -> ../run/lock


gate_news runs every 5 minutes. do you see this error every 5 minutes?
Have you run Mailman's bin/check_perms?

In any case, issues with gate_news only affect gating from usenet of
those lists that have Mail<->News gateways -> gateway_to_mail = Yes.


> I also receive messages like these about every fifteen minutes in
> /var/log/mailman/bounce:
> 
> Jul 02 14:42:12 2015 (1308) post to mailman from
> mailman-owner@{my-domain.com}, size=1736,
> message-id=<mailman.53.1435726803.13146.mailman@{my-domain.com}>, 1
> failures
> Jul 02 14:42:16 2015 (1308) post to mailman from
> mailman-owner@{my-domain.com}, size=1733,
> message-id=<mailman.98.1435726804.13146.mailman@{my-domain.com}>, 1
> failures


Mailman is sending a notice to the 'mailman' list and it's
undeliverable. That doesn't look like a 'bounce' log message. It looks
more like 'post' log. What's in the 'smtp-failure' log?


> Thanks in advance for any assistance. I suspect it's something I've
> overlooked.


Yes. What's in the Postfix logs for these failures and for the message
sent to {list-name}-subscribe at MyDomain.com?

The most common issue here is you are using the Dovecot LDA and it
doesn't know how to deliver to Mailman. If you are using aliases to
deliver to Mailman, you have to ensure that mail to Mailman is handles
by the Postfix 'local' LDA, not Dovecot. See the FAQ at
<http://wiki.list.org/x/10715238> for a way to do this.

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

From mark at msapiro.net  Thu Jul  2 17:24:12 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 02 Jul 2015 08:24:12 -0700
Subject: [Mailman-Users] Unable to access Mailman Web interface
In-Reply-To: <n6kapadt6pek0cnpdqfqhb6agqt6usk20b@4ax.com>
References: <n6kapadt6pek0cnpdqfqhb6agqt6usk20b@4ax.com>
Message-ID: <5595579C.8020502@msapiro.net>

On 07/02/2015 07:56 AM, Steve Matzura wrote:
> If I browse to http://{my-node.my-domain.com}/mailman/admin, I get the
> following:
> 
> Bug in Mailman version 2.1.18-1
> 
> Bug in Mailman version 2.1.18-1
> We're sorry, we hit a bug!
> 
> Please inform the webmaster for this site of this problem. Printing of
> traceback and other system information has been explicitly inhibited,
> but the webmaster
> can find this information in the Mailman error logs. 
> 
> If that's supposed to be /var/log/mailman/error, the only thing in
> there is what I posted in my previous message. Maybe the two are
> related?


Run check_perms.

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

From sm at noisynotes.com  Thu Jul  2 18:01:03 2015
From: sm at noisynotes.com (Steve Matzura)
Date: Thu, 02 Jul 2015 12:01:03 -0400
Subject: [Mailman-Users] Unable to access Mailman Web interface
In-Reply-To: <5595579C.8020502@msapiro.net>
References: <n6kapadt6pek0cnpdqfqhb6agqt6usk20b@4ax.com>
 <5595579C.8020502@msapiro.net>
Message-ID: <srnapatkglnopuoqtq7v44h86i8b0uh8ej@4ax.com>

On Thu, 02 Jul 2015 08:24:12 -0700, you wrote:

>On 07/02/2015 07:56 AM, Steve Matzura wrote:
>> If I browse to http://{my-node.my-domain.com}/mailman/admin, I get the
>> following:
>> 
>> Bug in Mailman version 2.1.18-1
>> 
>> Bug in Mailman version 2.1.18-1
>> We're sorry, we hit a bug!
>> 
>> Please inform the webmaster for this site of this problem. Printing of
>> traceback and other system information has been explicitly inhibited,
>> but the webmaster
>> can find this information in the Mailman error logs. 
>> 
>> If that's supposed to be /var/log/mailman/error, the only thing in
>> there is what I posted in my previous message. Maybe the two are
>> related?
>
>
>Run check_perms.

Did that. 898 problems found! I hope I didn't break Postfix. Luckily I
logged before and after in case I have to revert.

After check_perms fixed all problems, I re-ran it and got this:

Warning: Private archive directory is other-executable (o+x).
         This could allow other users on your system to read private
archives.
         If you're on a shared multiuser system, you should consult
the installation manual on how to fix this.
No problems found

Which section should I be reading?

From sm at noisynotes.com  Thu Jul  2 18:23:40 2015
From: sm at noisynotes.com (Steve Matzura)
Date: Thu, 02 Jul 2015 12:23:40 -0400
Subject: [Mailman-Users] Permissions error
In-Reply-To: <5595576B.3070606@msapiro.net>
References: <q2kapaptrp3okh2cf0f9patkhgj0dij0hp@4ax.com>
 <5595576B.3070606@msapiro.net>
Message-ID: <63papa5rfqvveo1eo86m34q9vu1qqoreno@4ax.com>

On Thu, 02 Jul 2015 08:23:23 -0700, you wrote:

>Mailman is sending a notice to the 'mailman' list and it's
>undeliverable. That doesn't look like a 'bounce' log message. It looks
>more like 'post' log. What's in the 'smtp-failure' log?

Jul 02 16:12:13 2015 (1308)
<mailman.53.1435726803.13146.mailman@{my-domain.com}> smtp to mailman
for 1 recips, completed in 4.225 seconds
Jul 02 16:12:17 2015 (1308)
<mailman.98.1435726804.13146.mailman@{my-domain.com}> smtp to mailman
for 1 recips, completed in 4.159 seconds

I get this about every fifteen minutes.

There is one additional wrinkle here. I have two systems, one
production, one test. They are near duplicates of each other except
for age of software--production's old, test is near-current. Haven't
installed MM 2.1.20 yet. It would be all right if the messages to
mailman@{my-domain.com} went to the wrong machine, but they don't seem
to be going anywhere.



From mark at msapiro.net  Fri Jul  3 01:39:36 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 02 Jul 2015 16:39:36 -0700
Subject: [Mailman-Users] Unable to access Mailman Web interface
In-Reply-To: <srnapatkglnopuoqtq7v44h86i8b0uh8ej@4ax.com>
References: <n6kapadt6pek0cnpdqfqhb6agqt6usk20b@4ax.com>
 <5595579C.8020502@msapiro.net> <srnapatkglnopuoqtq7v44h86i8b0uh8ej@4ax.com>
Message-ID: <5595CBB8.8010404@msapiro.net>

On 07/02/2015 09:01 AM, Steve Matzura wrote:
> On Thu, 02 Jul 2015 08:24:12 -0700, you wrote:
> 
>> Run check_perms.
> 
> Did that. 898 problems found! I hope I didn't break Postfix. Luckily I
> logged before and after in case I have to revert.


Check_perms only affects files and directories in Mailman's tree(s).
Postfix should be unaffected.


> After check_perms fixed all problems, I re-ran it and got this:
> 
> Warning: Private archive directory is other-executable (o+x).
>          This could allow other users on your system to read private
> archives.
>          If you're on a shared multiuser system, you should consult
> the installation manual on how to fix this.
> No problems found
> 
> Which section should I be reading?


<http://www.list.org/mailman-install/node9.html>, but the question is
this. Are there users who can log in to a shell or sftp or whatever who
should not have any access to private list archives? If the answer is
no, o+x on /path/to/mailman/archives/private is not a problem. If the
answer is yes, set it o-x and change its owner to the web server uid. If
you set it o-x and don't change the owner, public archive access won't work.

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

From mark at msapiro.net  Fri Jul  3 01:46:00 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 02 Jul 2015 16:46:00 -0700
Subject: [Mailman-Users] Permissions error
In-Reply-To: <63papa5rfqvveo1eo86m34q9vu1qqoreno@4ax.com>
References: <q2kapaptrp3okh2cf0f9patkhgj0dij0hp@4ax.com>
 <5595576B.3070606@msapiro.net> <63papa5rfqvveo1eo86m34q9vu1qqoreno@4ax.com>
Message-ID: <5595CD38.8000605@msapiro.net>

On 07/02/2015 09:23 AM, Steve Matzura wrote:
> On Thu, 02 Jul 2015 08:23:23 -0700, you wrote:
> 
>> Mailman is sending a notice to the 'mailman' list and it's
>> undeliverable. That doesn't look like a 'bounce' log message. It looks
>> more like 'post' log. What's in the 'smtp-failure' log?
> 
> Jul 02 16:12:13 2015 (1308)
> <mailman.53.1435726803.13146.mailman@{my-domain.com}> smtp to mailman
> for 1 recips, completed in 4.225 seconds
> Jul 02 16:12:17 2015 (1308)
> <mailman.98.1435726804.13146.mailman@{my-domain.com}> smtp to mailman
> for 1 recips, completed in 4.159 seconds


And those look like 'smtp' log messages, not 'smtp-failure'


> There is one additional wrinkle here. I have two systems, one
> production, one test. They are near duplicates of each other except
> for age of software--production's old, test is near-current. Haven't
> installed MM 2.1.20 yet. It would be all right if the messages to
> mailman@{my-domain.com} went to the wrong machine, but they don't seem
> to be going anywhere.


And once again, what's in the Postfix logs for these failures and for
the message sent to {list-name}-subscribe at MyDomain.com?

If messages to Mailman are being routed to the Dovecot transport, they
won't be properly delivered. If you are using aliases, Mailman's mail
has to be routed to the 'local' transport.

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

From number6 at noisynotes.com  Thu Jul  2 18:07:15 2015
From: number6 at noisynotes.com (Steve Matzura)
Date: Thu, 02 Jul 2015 12:07:15 -0400
Subject: [Mailman-Users] Permissions error
In-Reply-To: <5595576B.3070606@msapiro.net>
References: <q2kapaptrp3okh2cf0f9patkhgj0dij0hp@4ax.com>
 <5595576B.3070606@msapiro.net>
Message-ID: <13oapaleiqg94jbq2gjffqv7fpmjils9td@4ax.com>

On Thu, 02 Jul 2015 08:23:23 -0700, you wrote:

>On 07/02/2015 07:56 AM, Steve Matzura wrote:
>> I have a new Mailman implementation connected to Postfix which is in
>> turn connected to Dovecot. These two components are working correctly,
>> as I have mailboxes set up with them and have created a test Mailman
>> mailing list and received confirmation that it has in fact been
>> created. Now I'm attempting to subscribe a test user in the normal
>> way, by sending an email to {list-name}-subscribe at MyDomain.com. I have
>> not received a subscription confirmation, but the following
>> information from /var/log/mailman/error shows a problem:
>> 
>> Jul 02 14:15:01 2015 gate_news(18693): Traceback (most recent call
>> last):
>> Jul 02 14:15:01 2015 gate_news(18693):   File
>> "/usr/lib/mailman/cron/gate_news", line 293, in <module>
>> Jul 02 14:15:01 2015 gate_news(18693):      main()
>> Jul 02 14:15:01 2015 gate_news(18693):   File
>> "/usr/lib/mailman/cron/gate_news", line 268, in main
>> Jul 02 14:15:01 2015 gate_news(18693):      lock.lock(timeout=0.5)
>> Jul 02 14:15:01 2015 gate_news(18693):   File
>> "/usr/lib/mailman/Mailman/LockFile.py", line 243, in lock
>> Jul 02 14:15:01 2015 gate_news(18693):      self.__write()
>> Jul 02 14:15:01 2015 gate_news(18693):   File
>> "/usr/lib/mailman/Mailman/LockFile.py", line 422, in __write
>> Jul 02 14:15:01 2015 gate_news(18693):      fp = open(self.__tmpfname,
>> 'w')
>> Jul 02 14:15:01 2015 gate_news(18693): IOError :  [Errno 13]
>> Permission denied:
>> '/var/lock/mailman/gate_news.lock.{my-system-name}.{MyDomain.com}.18693.0'
>> Here are the directory permissions:
>> 
>> drwxrwsr-x 2 root mailman 80 Jul  2 13:57 mailman
>> lrwxrwxrwx 1 root root 11 Sep 14  2012 lock -> ../run/lock
>
>
>gate_news runs every 5 minutes. do you see this error every 5 minutes?
>Have you run Mailman's bin/check_perms?

I just ran check_perms to fix another problem, and it appears the two
*were* related, as this one's now gone as well.

>In any case, issues with gate_news only affect gating from usenet of
>those lists that have Mail<->News gateways -> gateway_to_mail = Yes.

Mine don't, or shouldn't. If they do, I'll turn that off immediately.

>
>> I also receive messages like these about every fifteen minutes in
>> /var/log/mailman/bounce:
>> 
>> Jul 02 14:42:12 2015 (1308) post to mailman from
>> mailman-owner@{my-domain.com}, size=1736,
>> message-id=<mailman.53.1435726803.13146.mailman@{my-domain.com}>, 1
>> failures
>> Jul 02 14:42:16 2015 (1308) post to mailman from
>> mailman-owner@{my-domain.com}, size=1733,
>> message-id=<mailman.98.1435726804.13146.mailman@{my-domain.com}>, 1
>> failures
>
>
>Mailman is sending a notice to the 'mailman' list and it's
>undeliverable. That doesn't look like a 'bounce' log message. It looks
>more like 'post' log. What's in the 'smtp-failure' log?

The smpt log is now clean. Newest message is ten minutes older than
the current date and time. I suspect running check_perms fixed
everything.

From ctodd at scratchspace.com  Fri Jul  3 00:33:26 2015
From: ctodd at scratchspace.com (Chris Miller)
Date: Thu, 02 Jul 2015 15:33:26 -0700
Subject: [Mailman-Users] Mailman 2.1.18-1 not respecting add_virtualhost
In-Reply-To: <559492C5.6080702@msapiro.net>
References: <53EBEB9C.3060806@scratchspace.com> <53ED01FE.2080908@msapiro.net>
 <53ED08F8.8010100@scratchspace.com> <53ED123E.6040307@msapiro.net>
 <53ED196F.6060108@scratchspace.com> <53ED54EF.3040301@msapiro.net>
 <53ED5D23.4070705@scratchspace.com> <53ED6093.9090304@msapiro.net>
 <55943A56.4000208@scratchspace.com> <559492C5.6080702@msapiro.net>
Message-ID: <5595BC36.8020302@scratchspace.com>

On 7/1/2015 6:24 PM, Mark Sapiro wrote:
> On 07/01/2015 12:07 PM, Chris Miller wrote:
>
>> We have corrected this problem by creating the subdirectories, moving
>> the lists in to the proper sub directory, and setting permissions. We
>> are still having trouble with fix_url.
>
> I'm just confirming that I've seen this and will look at it at some
> point this week, but not immediately.



Awesome. Much appreciated.



> It may be that fix_url never did the right thing, but I need to look in
> detail.
>
> I think however that you have made a mistake in that both the
> subdirectory name in the lists/ directory and the domain part of the
> listname in the fix_url command should be the email host, not the web
> host. I.e. no lists. prefix, at least with settings like
>
> add_virtualhost('lists.fakedomain.com', 'fakedomain.com')



I renamed the directory to just "fakedomain.com" and re-ran fix_url. 
I no longer see the red error message in the web interface, however 
once logged in I continue to see @fakedomain appended in the URL 
when clicking any navigation item. While I can login again with the 
invalid URL, each navigation click continues to append @fakedomain 
in a cumulative fashion.



>> To clarify, mm_cfg.py does contain the correct info for the lists, this all broke during the upgrade to 2.1.18 to utilize the DMARC features.
>
> What exactly are you running? Are you running code from
> <https://code.launchpad.net/~msapiro/mailman/vhost>?



Yes. 2.1.18-1

http://bazaar.launchpad.net/~msapiro/mailman/vhost/revision/868


> I wouldn't be too
> surprised if it's broken. I think the last thing I actually did to that
> branch other than untested merges of the upstream branch upon releases
> was over two years ago.



We downloaded this version last year to utilize the DMARC patches 
after Yahoo changed their SPF policy and our mailman posts were 
getting rejected.


-- 

Regards,
     Chris

Chris Miller
President - Rocket Scientist
ScratchSpace Inc.
(831) 621-7928
http://www.scratchspace.com


From mark at msapiro.net  Fri Jul  3 02:07:21 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 02 Jul 2015 17:07:21 -0700
Subject: [Mailman-Users] Permissions error
In-Reply-To: <13oapaleiqg94jbq2gjffqv7fpmjils9td@4ax.com>
References: <q2kapaptrp3okh2cf0f9patkhgj0dij0hp@4ax.com>
 <5595576B.3070606@msapiro.net> <13oapaleiqg94jbq2gjffqv7fpmjils9td@4ax.com>
Message-ID: <5595D239.1030707@msapiro.net>

On 07/02/2015 09:07 AM, Steve Matzura wrote:
> On Thu, 02 Jul 2015 08:23:23 -0700, you wrote:
> 
>>
>> gate_news runs every 5 minutes. do you see this error every 5 minutes?
>> Have you run Mailman's bin/check_perms?
> 
> I just ran check_perms to fix another problem, and it appears the two
> *were* related, as this one's now gone as well.


Good. Incorrect permissions can cause many issues.


>> In any case, issues with gate_news only affect gating from usenet of
>> those lists that have Mail<->News gateways -> gateway_to_mail = Yes.
> 
> Mine don't, or shouldn't. If they do, I'll turn that off immediately.


I'm sure they don't, but cron/gate_news still runs and checks to see if
any lists have newsgroups that might need polling. If you won't ever do
any usenet gatewaying, you can comment out or remove the gate_news entry
in Mailman's crontab.


> The smpt log is now clean. Newest message is ten minutes older than
> the current date and time. I suspect running check_perms fixed
> everything.


Does a 'subscribe' email get delivered to Mailman? That could have been
a permissions issue, but it's usually something else.

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

From stephen at xemacs.org  Fri Jul  3 07:48:43 2015
From: stephen at xemacs.org (Stephen J. Turnbull)
Date: Fri, 03 Jul 2015 14:48:43 +0900
Subject: [Mailman-Users] Sub-lists
In-Reply-To: <C2F1879073AE7347BAB44065F143E17001955CF925@nuwvicms2>
References: <CAGrTZgwZBxNhPCLoscMO1uOLoGZeVBqjpXrK=SUNeMqezgNwKw@mail.gmail.com>
 <C2F1879073AE7347BAB44065F143E17001955CF917@nuwvicms2>
 <87ioa3i7fo.fsf@uwakimon.sk.tsukuba.ac.jp>
 <C2F1879073AE7347BAB44065F143E17001955CF925@nuwvicms2>
Message-ID: <87fv55iyf8.fsf@uwakimon.sk.tsukuba.ac.jp>

Peter Shute writes:

 > True. I was thinking more along the lines of someone taking an
 > unofficial peek at a few mailboxes to compile an unofficial hit
 > list.

A valid concern, and I agree that it could easily apply to the OP's
use case.

Steve

From sm at noisynotes.com  Fri Jul  3 11:59:43 2015
From: sm at noisynotes.com (Steve Matzura)
Date: Fri, 03 Jul 2015 05:59:43 -0400
Subject: [Mailman-Users] Learning to use withlist
Message-ID: <k4ncpahl0b9fpk4et9glu1gb4hrfj9ndj3@4ax.com>

What's the best section of the standard documentation or the wiki to
consult in order to learn how to correctly use withlist?

From sm at noisynotes.com  Fri Jul  3 12:24:08 2015
From: sm at noisynotes.com (Steve Matzura)
Date: Fri, 03 Jul 2015 06:24:08 -0400
Subject: [Mailman-Users] Unable to access Mailman Web interface
In-Reply-To: <5595CBB8.8010404@msapiro.net>
References: <n6kapadt6pek0cnpdqfqhb6agqt6usk20b@4ax.com>
 <5595579C.8020502@msapiro.net> <srnapatkglnopuoqtq7v44h86i8b0uh8ej@4ax.com>
 <5595CBB8.8010404@msapiro.net>
Message-ID: <mgocpah5ild748db2splnd3lihqfhlfu28@4ax.com>

On Thu, 02 Jul 2015 16:39:36 -0700, you wrote:

>> After check_perms fixed all problems, I re-ran it and got this:
>> 
>> Warning: Private archive directory is other-executable (o+x).
>>          This could allow other users on your system to read private
>> archives.
>>          If you're on a shared multiuser system, you should consult
>> the installation manual on how to fix this.
>> No problems found
>> 
>> Which section should I be reading?
>
>
><http://www.list.org/mailman-install/node9.html>, but the question is
>this. Are there users who can log in to a shell or sftp or whatever who
>should not have any access to private list archives? If the answer is
>no, o+x on /path/to/mailman/archives/private is not a problem. If the
>answer is yes, set it o-x and change its owner to the web server uid. If
>you set it o-x and don't change the owner, public archive access won't work.

Understood. Since this is really a new installation (I didn't copy
archives from the old system because they're not really of any use),
$prefix/archives doesn't exist yet. I'll keep the above in mind and
implement it when list traffic commences on this installation.

From number6 at noisynotes.com  Fri Jul  3 12:17:06 2015
From: number6 at noisynotes.com (Steve Matzura)
Date: Fri, 03 Jul 2015 06:17:06 -0400
Subject: [Mailman-Users] Permissions error
In-Reply-To: <5595CD38.8000605@msapiro.net>
References: <q2kapaptrp3okh2cf0f9patkhgj0dij0hp@4ax.com>
 <5595576B.3070606@msapiro.net> <63papa5rfqvveo1eo86m34q9vu1qqoreno@4ax.com>
 <5595CD38.8000605@msapiro.net>
Message-ID: <brncpa1oi2ifvfpo9evhrfqnslm62throj@4ax.com>

On Thu, 02 Jul 2015 16:46:00 -0700, you wrote:

>On 07/02/2015 09:23 AM, Steve Matzura wrote:
>> On Thu, 02 Jul 2015 08:23:23 -0700, you wrote:
>> 
>>> Mailman is sending a notice to the 'mailman' list and it's
>>> undeliverable. That doesn't look like a 'bounce' log message. It looks
>>> more like 'post' log. What's in the 'smtp-failure' log?

This sequence occurs every fifteen minutes:

Jul 03 09:57:21 2015 (1308) All recipients refused:
{'kelly@{mydomain.com}': (450, '4.1.1 <kelly@{mydomain.com}>:
Recipient address rejected: User unknown in virtual mailbox table')},
msgid: <mailman.53.1435726803.13146.mailman@{mydomain.com}>
Jul 03 09:57:21 2015 (1308) delivery to kelly@{mydomain.com} failed
with code 450: 4.1.1 <kelly@{mydomain.com}>: Recipient address
rejected: User unknown in virtual mailbox table
Jul 03 09:57:25 2015 (1308) All recipients refused:
{'lynn@{mydomain.com}': (450, '4.1.1 <lynn@{mydomain.com}>: Recipient
address rejected: User unknown in virtual mailbox table')}, msgid:
<mailman.98.1435726804.13146.mailman@{mydomain.com}>
Jul 03 09:57:25 2015 (1308) delivery to lynn@{mydomain.com} failed
with code 450: 4.1.1 <lynn@{mydomain.com}>: Recipient address
rejected: User unknown in virtual mailbox table

From number6 at noisynotes.com  Fri Jul  3 12:26:44 2015
From: number6 at noisynotes.com (Steve Matzura)
Date: Fri, 03 Jul 2015 06:26:44 -0400
Subject: [Mailman-Users] Permissions error
In-Reply-To: <5595D239.1030707@msapiro.net>
References: <q2kapaptrp3okh2cf0f9patkhgj0dij0hp@4ax.com>
 <5595576B.3070606@msapiro.net> <13oapaleiqg94jbq2gjffqv7fpmjils9td@4ax.com>
 <5595D239.1030707@msapiro.net>
Message-ID: <ooocpa1jd7got0qj3td48fqmlaf16kibj9@4ax.com>

Mark:

On Thu, 02 Jul 2015 17:07:21 -0700, you wrote:

>> The smpt log is now clean. Newest message is ten minutes older than
>> the current date and time. I suspect running check_perms fixed
>> everything.
>
>
>Does a 'subscribe' email get delivered to Mailman? That could have been
>a permissions issue, but it's usually something else.

Still problems there, but there are other things I'm working on that
are probably related. Will report on those later this a.m.

From mark at msapiro.net  Fri Jul  3 15:38:49 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 03 Jul 2015 06:38:49 -0700
Subject: [Mailman-Users] Learning to use withlist
In-Reply-To: <k4ncpahl0b9fpk4et9glu1gb4hrfj9ndj3@4ax.com>
References: <k4ncpahl0b9fpk4et9glu1gb4hrfj9ndj3@4ax.com>
Message-ID: <55969069.5060800@msapiro.net>

On 07/03/2015 02:59 AM, Steve Matzura wrote:
> What's the best section of the standard documentation or the wiki to
> consult in order to learn how to correctly use withlist?


If you mean usage of the command, 'bin/withlist --help'.

If you mean what can you do interactively after invoking withlist on a
list and have a '>>>' prompt, see
<https://wiki.python.org/moin/BeginnersGuide#Learning_Python> for the
Python part. For the Mailman specific stuff, You need to understand what
list attributes, functions and methods are available and not of this is
documented in a single place, you really have to read the source.

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

From mark at msapiro.net  Fri Jul  3 15:50:58 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 03 Jul 2015 06:50:58 -0700
Subject: [Mailman-Users] Unable to access Mailman Web interface
In-Reply-To: <mgocpah5ild748db2splnd3lihqfhlfu28@4ax.com>
References: <n6kapadt6pek0cnpdqfqhb6agqt6usk20b@4ax.com>
 <5595579C.8020502@msapiro.net> <srnapatkglnopuoqtq7v44h86i8b0uh8ej@4ax.com>
 <5595CBB8.8010404@msapiro.net> <mgocpah5ild748db2splnd3lihqfhlfu28@4ax.com>
Message-ID: <55969342.2070703@msapiro.net>

On 07/03/2015 03:24 AM, Steve Matzura wrote:
> 
> Understood. Since this is really a new installation (I didn't copy
> archives from the old system because they're not really of any use),
> $prefix/archives doesn't exist yet. I'll keep the above in mind and
> implement it when list traffic commences on this installation.


$prefix/archives and the private/ and public/ sub-directories thereof
are created on installation, and if Mailman is running there must be a
'mailman' site list and thus $prefix/archives/private/mailman/ and
$prefix/archives/private/mailman.mbox/ subdirectories whether or not
they contain any actual archives.

Further, If $prefix/archives/private didn't exist, check_perms would
have thrown a "OSError: [Errno 2] No such file or directory:" exception
instead of reporting it was o+x.

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

From mark at msapiro.net  Fri Jul  3 16:01:57 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 03 Jul 2015 07:01:57 -0700
Subject: [Mailman-Users] Permissions error
In-Reply-To: <brncpa1oi2ifvfpo9evhrfqnslm62throj@4ax.com>
References: <q2kapaptrp3okh2cf0f9patkhgj0dij0hp@4ax.com>
 <5595576B.3070606@msapiro.net> <63papa5rfqvveo1eo86m34q9vu1qqoreno@4ax.com>
 <5595CD38.8000605@msapiro.net> <brncpa1oi2ifvfpo9evhrfqnslm62throj@4ax.com>
Message-ID: <559695D5.1030704@msapiro.net>

On 07/03/2015 03:17 AM, Steve Matzura wrote:
> 
> This sequence occurs every fifteen minutes:
> 
> Jul 03 09:57:21 2015 (1308) All recipients refused:
> {'kelly@{mydomain.com}': (450, '4.1.1 <kelly@{mydomain.com}>:
> Recipient address rejected: User unknown in virtual mailbox table')},
> msgid: <mailman.53.1435726803.13146.mailman@{mydomain.com}>
> Jul 03 09:57:21 2015 (1308) delivery to kelly@{mydomain.com} failed
> with code 450: 4.1.1 <kelly@{mydomain.com}>: Recipient address
> rejected: User unknown in virtual mailbox table
> Jul 03 09:57:25 2015 (1308) All recipients refused:
> {'lynn@{mydomain.com}': (450, '4.1.1 <lynn@{mydomain.com}>: Recipient
> address rejected: User unknown in virtual mailbox table')}, msgid:
> <mailman.98.1435726804.13146.mailman@{mydomain.com}>
> Jul 03 09:57:25 2015 (1308) delivery to lynn@{mydomain.com} failed
> with code 450: 4.1.1 <lynn@{mydomain.com}>: Recipient address
> rejected: User unknown in virtual mailbox table


Mailman is trying to send some notices to 'kelly' and 'lynn' and Postfix
is not accepting them with a 450 status. Since it is a 4xx retryable
status, Mailman keeps retrying every 15 minutes. Mailman will eventually
give up and return bounces after 5 days (default DELIVERY_RETRY_PERIOD).

In order to help you proceed, I'd like to see the output from
'postconf -n' and the postfix log message from one of the above rejects.

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

From mark at msapiro.net  Fri Jul  3 16:25:16 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 03 Jul 2015 07:25:16 -0700
Subject: [Mailman-Users] Permissions error
In-Reply-To: <559695D5.1030704@msapiro.net>
References: <q2kapaptrp3okh2cf0f9patkhgj0dij0hp@4ax.com>
 <5595576B.3070606@msapiro.net> <63papa5rfqvveo1eo86m34q9vu1qqoreno@4ax.com>
 <5595CD38.8000605@msapiro.net> <brncpa1oi2ifvfpo9evhrfqnslm62throj@4ax.com>
 <559695D5.1030704@msapiro.net>
Message-ID: <55969B4C.6020407@msapiro.net>

On 07/03/2015 07:01 AM, Mark Sapiro wrote:
> On 07/03/2015 03:17 AM, Steve Matzura wrote:
>>
>> This sequence occurs every fifteen minutes:
>>
>> Jul 03 09:57:21 2015 (1308) All recipients refused:
>> {'kelly@{mydomain.com}': (450, '4.1.1 <kelly@{mydomain.com}>:
>> Recipient address rejected: User unknown in virtual mailbox table')},
>> msgid: <mailman.53.1435726803.13146.mailman@{mydomain.com}>
>> Jul 03 09:57:21 2015 (1308) delivery to kelly@{mydomain.com} failed
>> with code 450: 4.1.1 <kelly@{mydomain.com}>: Recipient address
>> rejected: User unknown in virtual mailbox table
>> Jul 03 09:57:25 2015 (1308) All recipients refused:
>> {'lynn@{mydomain.com}': (450, '4.1.1 <lynn@{mydomain.com}>: Recipient
>> address rejected: User unknown in virtual mailbox table')}, msgid:
>> <mailman.98.1435726804.13146.mailman@{mydomain.com}>
>> Jul 03 09:57:25 2015 (1308) delivery to lynn@{mydomain.com} failed
>> with code 450: 4.1.1 <lynn@{mydomain.com}>: Recipient address
>> rejected: User unknown in virtual mailbox table
> 
> 
> Mailman is trying to send some notices to 'kelly' and 'lynn' and Postfix
> is not accepting them with a 450 status. Since it is a 4xx retryable
> status, Mailman keeps retrying every 15 minutes. Mailman will eventually
> give up and return bounces after 5 days (default DELIVERY_RETRY_PERIOD).
> 
> In order to help you proceed, I'd like to see the output from
> 'postconf -n' and the postfix log message from one of the above rejects.


Note that the above messages are not really Mailman related. They don't
indicate that Postfix can't deliver to Mailman, although that may also
be true. They indicate that Postfix cannot deliver to 'lynn' or 'kelly'.
If these should be valid, deliverable addresses, there is a Postfix
configuration issue. If they are in fact invalid, you can check your
main.cf settings for things like 'soft_bounce' and
'unknown_virtual_mailbox_reject_code'. You may want 'soft_bounce = no'
and unknown_virtual_mailbox_reject_code = 550.

Also, to get rid of these retries before they expire, you can remove the
four $prefix/qfiles/retry/*.pck files. You can also do

$prefix/bin/show_qfiles $prefix/qfiles/retry/*.pck

to see what the messages are.

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

From mark at msapiro.net  Fri Jul  3 21:02:55 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 03 Jul 2015 12:02:55 -0700
Subject: [Mailman-Users] Mailman 2.1.18-1 not respecting add_virtualhost
In-Reply-To: <5595BC36.8020302@scratchspace.com>
References: <53EBEB9C.3060806@scratchspace.com> <53ED01FE.2080908@msapiro.net>
 <53ED08F8.8010100@scratchspace.com> <53ED123E.6040307@msapiro.net>
 <53ED196F.6060108@scratchspace.com> <53ED54EF.3040301@msapiro.net>
 <53ED5D23.4070705@scratchspace.com> <53ED6093.9090304@msapiro.net>
 <55943A56.4000208@scratchspace.com> <559492C5.6080702@msapiro.net>
 <5595BC36.8020302@scratchspace.com>
Message-ID: <5596DC5F.9090308@msapiro.net>

On 07/02/2015 03:33 PM, Chris Miller wrote:
> 
> I renamed the directory to just "fakedomain.com" and re-ran fix_url. I
> no longer see the red error message in the web interface, however once
> logged in I continue to see @fakedomain appended in the URL when
> clicking any navigation item. While I can login again with the invalid
> URL, each navigation click continues to append @fakedomain in a
> cumulative fashion.


I do not see this in my test/development installation.

I have however made a few other changes:

- Added '@' to ACCEPTABLE_LISTNAME_CHARACTERS because of fix for
  LP: #1437145.
- Changed fix_url.py to better handle vhost lists.
- Fixed CSRFcheck.py to account for '@' to '%40' changes.
- Fixed generated public archive URL for vhost lists.

The fix_url changes make it more robust in updating lists with '@' in
the name.

In any case, I recommend getting the latest rev. 874 from
<http://bazaar.launchpad.net/~msapiro/mailman/vhost/revision/874> and
upgrading to that.

As far as fix_url is concerned, there are four attributes it is
concerned with, two of which are vhost only. You can see these if you do
(for listname at emaildomain in the web domain webdomain)

bin/dumpdb lists/emaildomain/listname/config.pck

you should see

hostname = 'emaildomain'
list_address = 'listname at emaildomain'
local_part = 'listname'
web_page_url = 'http://webdomain/mailman/'

(the last assumes the default setting for DEFAULT_URL_PATTERN)

If you install rev. 874 and you still have the spurious appending of
'@emaildomain' to URLs issue, I will look further. I suspect there is
some issue with older code assuming the list name is just the short name
and appending '@emaildomain' to 'correct' the URL, but as I say, I don't
see it in my system.

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

From sm at noisynotes.com  Sat Jul  4 15:36:08 2015
From: sm at noisynotes.com (Steve Matzura)
Date: Sat, 04 Jul 2015 09:36:08 -0400
Subject: [Mailman-Users] Nightly Messages Show Problems
Message-ID: <dqmfpa5moidabrlrch22fl87t8d3vis579@4ax.com>

I guess things are getting better with my new mailman implementation,
as I received nine messages overnight I've never gotten before. four
are Errno 13 permission denied, five only contain one line:

/bin/sh: mailman: command not found

The subject fields of these five all begin with the same text telling
me they're from Mailman at my node, etc. The rest of the subject field
for each message was this:

/usr/lib/mailman/cron/cull_bad_shunt
/usr/lib/mailman/cron/checkdbs
/usr/lib/mailman/cron/disabled
/usr/lib/mailman/cron/senddigests
/usr/lib/mailman/cron/nightly_gzip

Here are the four Errno13 messages:

Subject: Cron <mailman@{mynode}> /usr/lib/mailman/cron/nightly_gzip
From: "(Cron Daemon)" <mailman@{mydomain.com}>
Date: Sat,  4 Jul 2015 03:27:02 +0000 (UTC)

Traceback (most recent call last):
  File "/usr/lib/mailman/cron/nightly_gzip", line 158, in <module>
    main()
  File "/usr/lib/mailman/cron/nightly_gzip", line 114, in main
    mlist = MailList.MailList(name, lock=0)
  File "/usr/lib/mailman/Mailman/MailList.py", line 130, in __init__
    self.Load()
  File "/usr/lib/mailman/Mailman/MailList.py", line 655, in Load
    dict, e = self.__load(file)
  File "/usr/lib/mailman/Mailman/MailList.py", line 620, in __load
    fp = open(dbfile)
IOError: [Errno 13] Permission denied:
'/var/lib/mailman/lists/mailman/config.pck'

Subject: Cron <mailman@{mynode}> /usr/lib/mailman/cron/checkdbs
From: "(Cron Daemon)" <mailman@{mydomain.com}>
Date: Sat,  4 Jul 2015 08:00:02 +0000 (UTC)

Traceback (most recent call last):
  File "/usr/lib/mailman/cron/checkdbs", line 211, in <module>
    main()
  File "/usr/lib/mailman/cron/checkdbs", line 87, in main
    mlist = MailList.MailList(name)
  File "/usr/lib/mailman/Mailman/MailList.py", line 128, in __init__
    self.Lock()
  File "/usr/lib/mailman/Mailman/MailList.py", line 161, in Lock
    self.__lock.lock(timeout)
  File "/usr/lib/mailman/Mailman/LockFile.py", line 243, in lock
    self.__write()
  File "/usr/lib/mailman/Mailman/LockFile.py", line 422, in __write
    fp = open(self.__tmpfname, 'w')
IOError: [Errno 13] Permission denied:
'/var/lock/mailman/mailman.lock.{mynode}.Mydomain.com}.3681.0'

Subject: Cron <mailman@{mynode}> /usr/lib/mailman/cron/disabled
From: "(Cron Daemon)" <mailman@{mydomain.com}>
Date: Sat,  4 Jul 2015 09:00:02 +0000 (UTC)

Traceback (most recent call last):
  File "/usr/lib/mailman/cron/disabled", line 227, in <module>
    main()
  File "/usr/lib/mailman/cron/disabled", line 150, in main
    mlist = MailList.MailList(listname)
  File "/usr/lib/mailman/Mailman/MailList.py", line 128, in __init__
    self.Lock()
  File "/usr/lib/mailman/Mailman/MailList.py", line 161, in Lock
    self.__lock.lock(timeout)
  File "/usr/lib/mailman/Mailman/LockFile.py", line 243, in lock
    self.__write()
  File "/usr/lib/mailman/Mailman/LockFile.py", line 422, in __write
    fp = open(self.__tmpfname, 'w')
IOError: [Errno 13] Permission denied:
'/var/lock/mailman/mailman.lock.{mynode}.{mydomain.com}.4471.0'

Subject: Cron <mailman@{mynode}> /usr/lib/mailman/cron/senddigests
From: "(Cron Daemon)" <mailman@{mydomain.com}>
Date: Sat,  4 Jul 2015 12:00:02 +0000 (UTC)

Traceback (most recent call last):
  File "/usr/lib/mailman/cron/senddigests", line 106, in <module>
    main()
  File "/usr/lib/mailman/cron/senddigests", line 84, in main
    mlist = MailList.MailList(listname, lock=0)
  File "/usr/lib/mailman/Mailman/MailList.py", line 130, in __init__
    self.Load()
  File "/usr/lib/mailman/Mailman/MailList.py", line 655, in Load
    dict, e = self.__load(file)
  File "/usr/lib/mailman/Mailman/MailList.py", line 620, in __load
    fp = open(dbfile)
IOError: [Errno 13] Permission denied:
'/var/lib/mailman/lists/mailman/config.pck'

Thinking a run of check_perms might help, I did so and got (then
fixed) this one error, which I reran with -f to fix:

/usr/lib/mailman/Mailman/mm_cfg.pyc bad group (has: root, expected
mailman) (fixing)

Not wanting to overload the list with diagnostics, hope this is
sufficient to start. More info on request of course.

From bernie at fantasyfarm.com  Fri Jul  3 18:03:42 2015
From: bernie at fantasyfarm.com (Bernie Cosell)
Date: Fri, 03 Jul 2015 12:03:42 -0400
Subject: [Mailman-Users] spam filter not working
Message-ID: <5596B25E.18125.5C156950@bernie.fantasyfarm.com>

I've looked through the FAQs and the archives and my spam filters *OUGHT* 
to work.  But it seems they're not and I don't know why.

I have a spam filter set to 'hold':

X-Spam-Level:\s*\*\*\*

And a message with these headers just got blasted out to the list:

X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on 
box913.bluehost.com
X-Spam-Level: ********
X-Spam-Status: No, score=8.0 required=10.0 
tests=BAYES_50,HELO_DYNAMIC_IPADDR,
	HK_RANDOM_REPLYTO,RCVD_IN_PSBL,RDNS_NONE,SPF_NEUTRAL shortcircuit=no
	autolearn=no version=3.3.2

Do I have the RE wrong somehow?  THANKS!

  /b\
-- 
Bernie Cosell                     Fantasy Farm Fibers
mailto:bernie at fantasyfarm.com     Pearisburg, VA
    -->  Too many people, too few sheep  <--       




From number6 at noisynotes.com  Fri Jul  3 15:52:55 2015
From: number6 at noisynotes.com (Steve Matzura)
Date: Fri, 03 Jul 2015 09:52:55 -0400
Subject: [Mailman-Users] Learning to use withlist
In-Reply-To: <55969069.5060800@msapiro.net>
References: <k4ncpahl0b9fpk4et9glu1gb4hrfj9ndj3@4ax.com>
 <55969069.5060800@msapiro.net>
Message-ID: <7n4dpa987m78gqe926d12fj42lq092b01a@4ax.com>

On Fri, 03 Jul 2015 06:38:49 -0700, you wrote:

>If you mean what can you do interactively after invoking withlist on a
>list and have a '>>>' prompt, see
><https://wiki.python.org/moin/BeginnersGuide#Learning_Python> for the
>Python part. For the Mailman specific stuff, You need to understand what
>list attributes, functions and methods are available and not of this is
>documented in a single place, you really have to read the source.

Oh boy. Not good. Here's what I'm after finding: I want to find
something I can use to look at a list's properties in order to
possibly determine what is wrong with my setup that's generating the
smtp-failure messages and generally inhibiting or prohibiting mail
from passing through lists.

From number6 at noisynotes.com  Sat Jul  4 00:59:11 2015
From: number6 at noisynotes.com (Steve Matzura)
Date: Fri, 03 Jul 2015 18:59:11 -0400
Subject: [Mailman-Users] Unable to access Mailman Web interface
In-Reply-To: <55969342.2070703@msapiro.net>
References: <n6kapadt6pek0cnpdqfqhb6agqt6usk20b@4ax.com>
 <5595579C.8020502@msapiro.net> <srnapatkglnopuoqtq7v44h86i8b0uh8ej@4ax.com>
 <5595CBB8.8010404@msapiro.net> <mgocpah5ild748db2splnd3lihqfhlfu28@4ax.com>
 <55969342.2070703@msapiro.net>
Message-ID: <123epahcd3g06n3jrreu3372eq1h7ds2vs@4ax.com>

On Fri, 03 Jul 2015 06:50:58 -0700, you wrote:

>$prefix/archives and the private/ and public/ sub-directories thereof
>are created on installation, and if Mailman is running there must be a
>'mailman' site list and thus $prefix/archives/private/mailman/ and
>$prefix/archives/private/mailman.mbox/ subdirectories whether or not
>they contain any actual archives.
>
>Further, If $prefix/archives/private didn't exist, check_perms would
>have thrown a "OSError: [Errno 2] No such file or directory:" exception
>instead of reporting it was o+x.

Interesting: My $prefix is /usr/lib/mailman. However, there is a
/var/lib/mailman as that's where archives is. It's owned and grouped
properly, and it does have the 1-bit set in the 'other' portion of its
permissions mask. I can definitely fix that. But why does this all
appear in /var/lib/mailman and not /usr/lib/mailman?


From mark at msapiro.net  Sat Jul  4 16:13:18 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 04 Jul 2015 07:13:18 -0700
Subject: [Mailman-Users] Learning to use withlist
In-Reply-To: <7n4dpa987m78gqe926d12fj42lq092b01a@4ax.com>
References: <k4ncpahl0b9fpk4et9glu1gb4hrfj9ndj3@4ax.com>
 <55969069.5060800@msapiro.net> <7n4dpa987m78gqe926d12fj42lq092b01a@4ax.com>
Message-ID: <5597E9FE.40407@msapiro.net>

On 07/03/2015 06:52 AM, Steve Matzura wrote:
> 
> Oh boy. Not good. Here's what I'm after finding: I want to find
> something I can use to look at a list's properties in order to
> possibly determine what is wrong with my setup that's generating the
> smtp-failure messages and generally inhibiting or prohibiting mail
> from passing through lists.


As I have tried to point out in other replies, your remaining mail
delivery problems are with your Postfix configuration. There is no point
in looking at Mailman settings until you resolve your Postfix issues.
See my replies at
<https://mail.python.org/pipermail/mailman-users/2015-July/079369.html>
and <https://mail.python.org/pipermail/mailman-users/2015-July/079370.html>.

Also, please post to this list from your subscribed address
<sm at noisynotes.com>. Posting from alternative addresses results in
moderation delay and possible rejection or discard of your 'non-member'
posts.

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

From mark at msapiro.net  Sat Jul  4 16:22:43 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 04 Jul 2015 07:22:43 -0700
Subject: [Mailman-Users] Unable to access Mailman Web interface
In-Reply-To: <123epahcd3g06n3jrreu3372eq1h7ds2vs@4ax.com>
References: <n6kapadt6pek0cnpdqfqhb6agqt6usk20b@4ax.com>
 <5595579C.8020502@msapiro.net> <srnapatkglnopuoqtq7v44h86i8b0uh8ej@4ax.com>
 <5595CBB8.8010404@msapiro.net> <mgocpah5ild748db2splnd3lihqfhlfu28@4ax.com>
 <55969342.2070703@msapiro.net> <123epahcd3g06n3jrreu3372eq1h7ds2vs@4ax.com>
Message-ID: <5597EC33.6050101@msapiro.net>

On 07/03/2015 03:59 PM, Steve Matzura wrote:
> 
> Interesting: My $prefix is /usr/lib/mailman. However, there is a
> /var/lib/mailman as that's where archives is. It's owned and grouped
> properly, and it does have the 1-bit set in the 'other' portion of its
> permissions mask. I can definitely fix that. But why does this all
> appear in /var/lib/mailman and not /usr/lib/mailman?


Mailman has two main configuration paths, $prefix for immutable code,
etc. and $var_prefix for mutable data. By default, $var_prefix =
$prefix, but in your case, you or the packager whose package you
installed configured mailman with $prefix=/usr/lib/mailman and
$var_prefix=/var/lib/mailman. This is not unusual.

I referred to $prefix rather than $var_prefix in a prior reply only
because that was the term you used.

Also, please post to this list from your subscribed address
<sm at noisynotes.com>. Posting from alternative addresses results in
moderation delay and possible rejection or discard of your 'non-member'
posts.

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

From mark at msapiro.net  Sat Jul  4 16:48:52 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 04 Jul 2015 07:48:52 -0700
Subject: [Mailman-Users] Nightly Messages Show Problems
In-Reply-To: <dqmfpa5moidabrlrch22fl87t8d3vis579@4ax.com>
References: <dqmfpa5moidabrlrch22fl87t8d3vis579@4ax.com>
Message-ID: <5597F254.7080202@msapiro.net>

On 07/04/2015 06:36 AM, Steve Matzura wrote:
> I guess things are getting better with my new mailman implementation,
> as I received nine messages overnight I've never gotten before. four
> are Errno 13 permission denied, five only contain one line:
> 
> /bin/sh: mailman: command not found
> 
> The subject fields of these five all begin with the same text telling
> me they're from Mailman at my node, etc. The rest of the subject field
> for each message was this:
> 
> /usr/lib/mailman/cron/cull_bad_shunt
> /usr/lib/mailman/cron/checkdbs
> /usr/lib/mailman/cron/disabled
> /usr/lib/mailman/cron/senddigests
> /usr/lib/mailman/cron/nightly_gzip


These occur because you have installed a crontab which has been
formatted as a system crontab and intended to be installed in a place
like /etc/cron.d/mailman as a user contab somewhere in /var/spool/cron.

System crontabs have an extra field between the days/times and the
command which is the user to run as. In this case, that user (mailman)
is interpreted as part of the command because the crontab is installed
for a user.


> Here are the four Errno13 messages:
> 
> Subject: Cron <mailman@{mynode}> /usr/lib/mailman/cron/nightly_gzip
> From: "(Cron Daemon)" <mailman@{mydomain.com}>
> Date: Sat,  4 Jul 2015 03:27:02 +0000 (UTC)
> 
> Traceback (most recent call last):
>   File "/usr/lib/mailman/cron/nightly_gzip", line 158, in <module>
>     main()
>   File "/usr/lib/mailman/cron/nightly_gzip", line 114, in main
>     mlist = MailList.MailList(name, lock=0)
>   File "/usr/lib/mailman/Mailman/MailList.py", line 130, in __init__
>     self.Load()
>   File "/usr/lib/mailman/Mailman/MailList.py", line 655, in Load
>     dict, e = self.__load(file)
>   File "/usr/lib/mailman/Mailman/MailList.py", line 620, in __load
>     fp = open(dbfile)
> IOError: [Errno 13] Permission denied:
> '/var/lib/mailman/lists/mailman/config.pck'
...


> Thinking a run of check_perms might help, I did so and got (then
> fixed) this one error, which I reran with -f to fix:
> 
> /usr/lib/mailman/Mailman/mm_cfg.pyc bad group (has: root, expected
> mailman) (fixing)


The four are all permissions issues. Since check_perms thinks the
permissions are OK, the issue could be that the user as which the crons
are running is not in the 'mailman' group, or it could be a SELinux or
other policy manager issue.


> Not wanting to overload the list with diagnostics, hope this is
> sufficient to start. More info on request of course.


It seems there are at least two mailman crontabs. One is a user crontab
in /var/spool/cron/mailman (or maybe /var/spool/cron/crontabs/mailman or
??) that is not formatted as a user crontab and is responsible for the
/bin/sh: mailman: command not found messages. The other is probably in
/etc/cron.d/mailman and is the one giving the permission exceptions.

What are the contents of these crontabs? You only want one of these.
Which may be important if there are SELinux issues, but otherwise, it
doesn't matter as long as the one is correct.

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

From mark at msapiro.net  Sat Jul  4 17:22:08 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 04 Jul 2015 08:22:08 -0700
Subject: [Mailman-Users] spam filter not working
In-Reply-To: <5596B25E.18125.5C156950@bernie.fantasyfarm.com>
References: <5596B25E.18125.5C156950@bernie.fantasyfarm.com>
Message-ID: <5597FA20.4050105@msapiro.net>

On 07/03/2015 09:03 AM, Bernie Cosell wrote:
> I've looked through the FAQs and the archives and my spam filters *OUGHT* 
> to work.  But it seems they're not and I don't know why.
> 
> I have a spam filter set to 'hold':
> 
> X-Spam-Level:\s*\*\*\*
> 
> And a message with these headers just got blasted out to the list:
> 
> X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on 
> box913.bluehost.com
> X-Spam-Level: ********
> X-Spam-Status: No, score=8.0 required=10.0 
> tests=BAYES_50,HELO_DYNAMIC_IPADDR,
> 	HK_RANDOM_REPLYTO,RCVD_IN_PSBL,RDNS_NONE,SPF_NEUTRAL shortcircuit=no
> 	autolearn=no version=3.3.2
> 
> Do I have the RE wrong somehow?  THANKS!


I would use

^X-Spam-Level:\s*\*\*\*

but yours should match any with 3 or more stars, in particular the one
above.

Is it possible it was held and approved? Check Mailman's 'vette' log or
check the received massage for an X-Mailman-Approved-At: header.

Do you have other header_filter_rules? In particular, one before this
with an action of Accept?

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

From sm at noisynotes.com  Sat Jul  4 17:23:26 2015
From: sm at noisynotes.com (Steve Matzura)
Date: Sat, 04 Jul 2015 11:23:26 -0400
Subject: [Mailman-Users] Unable to access Mailman Web interface
In-Reply-To: <5597EC33.6050101@msapiro.net>
References: <n6kapadt6pek0cnpdqfqhb6agqt6usk20b@4ax.com>
 <5595579C.8020502@msapiro.net> <srnapatkglnopuoqtq7v44h86i8b0uh8ej@4ax.com>
 <5595CBB8.8010404@msapiro.net> <mgocpah5ild748db2splnd3lihqfhlfu28@4ax.com>
 <55969342.2070703@msapiro.net> <123epahcd3g06n3jrreu3372eq1h7ds2vs@4ax.com>
 <5597EC33.6050101@msapiro.net>
Message-ID: <ueufpapl3ievkl5rm28th6784g58cujtrm@4ax.com>

On Sat, 04 Jul 2015 07:22:43 -0700, Mark wrote:

>Mailman has two main configuration paths, $prefix for immutable code,
>etc. and $var_prefix for mutable data. By default, $var_prefix =
>$prefix, but in your case, you or the packager whose package you
>installed configured mailman with $prefix=/usr/lib/mailman and
>$var_prefix=/var/lib/mailman. This is not unusual.
>
>I referred to $prefix rather than $var_prefix in a prior reply only
>because that was the term you used.

Because that's the only one I knew of. Blame Red Hat for this one. :-)
I installed the package as-was from their repository. In fact, if I
didn't read up on it, I'd never know what $prefix is or is meant to
be, as it's neither a defined global environment variable nor symbol.
No matter, that one's cleared up.

>Also, please post to this list from your subscribed address

Oversight.

From sm at noisynotes.com  Sat Jul  4 17:27:49 2015
From: sm at noisynotes.com (Steve Matzura)
Date: Sat, 04 Jul 2015 11:27:49 -0400
Subject: [Mailman-Users] Nightly Messages Show Problems
Message-ID: <lnufpahtru1g1thkg1tfbv6fnqertekki0@4ax.com>

This should have gone to the list instead of where it went.

On Sat, 04 Jul 2015 07:45:07 -0700, Mark Shapiro <mark at msapiro.net>
wrote:

>These occur because you have installed a crontab which has been
>formatted as a system crontab and intended to be installed in a place
>like /etc/cron.d/mailman as a user contab somewhere in /var/spool/cron.

Interesting. I followed the directions at
http://www.gnu.org/software/mailman/mailman-install/node41.html which
say:

If your version of crontab supports the -u option, you must be root to
do this next step. Add $prefix/cron/crontab.in as a crontab entry by
executing these commands: 

    % cd $prefix/cron
    % crontab -u mailman crontab.in

>System crontabs have an extra field between the days/times and the
>command which is the user to run as. In this case, that user (mailman)
>is interpreted as part of the command because the crontab is installed
>for a user.

Should I remove the mailman ones and install it as root instead?

>The four are all permissions issues. Since check_perms thinks the
>permissions are OK, the issue could be that the user as which the crons
>are running is not in the 'mailman' group, or it could be a SELinux or
>other policy manager issue.

mailman is not a group in root's passwd record. Sounds like the
crontab.in needs editing to remove the mailman username from it?

>It seems there are at least two mailman crontabs. One is a user crontab
>in /var/spool/cron/mailman (or maybe /var/spool/cron/crontabs/mailman or
>??) that is not formatted as a user crontab and is responsible for the
>/bin/sh: mailman: command not found messages. The other is probably in
>/etc/cron.d/mailman and is the one giving the permission exceptions.
>
>What are the contents of these crontabs? You only want one of these.
>Which may be important if there are SELinux issues, but otherwise, it
>doesn't matter as long as the one is correct.

The two in /etc/cron.d and /var/spool/cron are identical. Here's the
contents with the comment lines removed:

MAILTO=sm at noisynotes.com
0 8 * * * mailman /usr/lib/mailman/cron/checkdbs
0 9 * * * mailman /usr/lib/mailman/cron/disabled
0 12 * * * mailman /usr/lib/mailman/cron/senddigests
0 5 1 * * mailman /usr/lib/mailman/cron/mailpasswds
27 3 * * * mailman /usr/lib/mailman/cron/nightly_gzip
30 4 * * * mailman /usr/lib/mailman/cron/cull_bad_shunt

From mark at msapiro.net  Sat Jul  4 17:54:44 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 04 Jul 2015 08:54:44 -0700
Subject: [Mailman-Users] Unable to access Mailman Web interface
In-Reply-To: <ueufpapl3ievkl5rm28th6784g58cujtrm@4ax.com>
References: <n6kapadt6pek0cnpdqfqhb6agqt6usk20b@4ax.com>
 <5595579C.8020502@msapiro.net> <srnapatkglnopuoqtq7v44h86i8b0uh8ej@4ax.com>
 <5595CBB8.8010404@msapiro.net> <mgocpah5ild748db2splnd3lihqfhlfu28@4ax.com>
 <55969342.2070703@msapiro.net> <123epahcd3g06n3jrreu3372eq1h7ds2vs@4ax.com>
 <5597EC33.6050101@msapiro.net> <ueufpapl3ievkl5rm28th6784g58cujtrm@4ax.com>
Message-ID: <559801C4.20109@msapiro.net>

On 07/04/2015 08:23 AM, Steve Matzura wrote:
> 
> Because that's the only one I knew of. Blame Red Hat for this one. :-)


The RedHat/Centos package is even more complex. See the FAQ at
<http://wiki.list.org/x/8486953>.

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

From mark at msapiro.net  Sat Jul  4 18:11:54 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 04 Jul 2015 09:11:54 -0700
Subject: [Mailman-Users] Nightly Messages Show Problems
In-Reply-To: <lnufpahtru1g1thkg1tfbv6fnqertekki0@4ax.com>
References: <lnufpahtru1g1thkg1tfbv6fnqertekki0@4ax.com>
Message-ID: <559805CA.8070700@msapiro.net>

On 07/04/2015 08:27 AM, Steve Matzura wrote:
> 
> On Sat, 04 Jul 2015 07:45:07 -0700, Mark Sapiro <mark at msapiro.net>
> wrote:
> 
>> These occur because you have installed a crontab which has been
>> formatted as a system crontab and intended to be installed in a place
>> like /etc/cron.d/mailman as a user contab somewhere in /var/spool/cron.
> 
> Interesting. I followed the directions at
> http://www.gnu.org/software/mailman/mailman-install/node41.html which
> say:


This is just one of many reasons for the advice in the FAQ at
<http://wiki.list.org/x/12812344>.

Packagers do various things that don't always align with what we
recommend. In short, If you install from source, follow our docs; if you
install a package, follow the packager's docs.

In your case, the RedHat package has modified Mailman's crontab.in to be
a system crontab and already installed it in /etc/cron.d/.

Thus it was wrong to follow our manual and try to install it ads the
Mailman user's crontab.


> If your version of crontab supports the -u option, you must be root to
> do this next step. Add $prefix/cron/crontab.in as a crontab entry by
> executing these commands: 
> 
>     % cd $prefix/cron
>     % crontab -u mailman crontab.in


To correct this, just do

sudo crontab -u mailman -r


> Should I remove the mailman ones and install it as root instead?


Remove the 'mailman' one as above. The system one was already installed
by the package.


...
> The two in /etc/cron.d and /var/spool/cron are identical. Here's the
> contents with the comment lines removed:
> 
> MAILTO=sm at noisynotes.com
> 0 8 * * * mailman /usr/lib/mailman/cron/checkdbs
> 0 9 * * * mailman /usr/lib/mailman/cron/disabled
> 0 12 * * * mailman /usr/lib/mailman/cron/senddigests
> 0 5 1 * * mailman /usr/lib/mailman/cron/mailpasswds
> 27 3 * * * mailman /usr/lib/mailman/cron/nightly_gzip
> 30 4 * * * mailman /usr/lib/mailman/cron/cull_bad_shunt


The one in /etc/cron.d/ is fine as is. The other should be removed as
above. Since the system one runs as 'mailman' and has permission issues
and check_perms reports no problems, I suspect the permission issues are
SELinux related.

Disabling SELinix may help, but you may not want to do that. Otherwise,
you'd need to address this via SELinux policies, and I don't know what
would need to be changed. This is interesting because the motivation for
RedHat's file location changes to be FHS compliant was at least in part
to make their Mailman package work well with SELinux.

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

From sm at noisynotes.com  Sat Jul  4 18:15:54 2015
From: sm at noisynotes.com (Steve Matzura)
Date: Sat, 04 Jul 2015 12:15:54 -0400
Subject: [Mailman-Users] Unable to access Mailman Web interface
In-Reply-To: <559801C4.20109@msapiro.net>
References: <n6kapadt6pek0cnpdqfqhb6agqt6usk20b@4ax.com>
 <5595579C.8020502@msapiro.net> <srnapatkglnopuoqtq7v44h86i8b0uh8ej@4ax.com>
 <5595CBB8.8010404@msapiro.net> <mgocpah5ild748db2splnd3lihqfhlfu28@4ax.com>
 <55969342.2070703@msapiro.net> <123epahcd3g06n3jrreu3372eq1h7ds2vs@4ax.com>
 <5597EC33.6050101@msapiro.net> <ueufpapl3ievkl5rm28th6784g58cujtrm@4ax.com>
 <559801C4.20109@msapiro.net>
Message-ID: <hi1gpaptuohf43qdihq7pn9r2s243r1jft@4ax.com>

On Sat, 04 Jul 2015 08:54:44 -0700, Mark Sapiro <mark at msapiro.net>
wrote:

>The RedHat/Centos package is even more complex. See the FAQ at
><http://wiki.list.org/x/8486953>.

Thanks. Noted and saved for future reference.

From sm at noisynotes.com  Sat Jul  4 19:19:28 2015
From: sm at noisynotes.com (Steve Matzura)
Date: Sat, 04 Jul 2015 13:19:28 -0400
Subject: [Mailman-Users] Nightly Messages Show Problems
In-Reply-To: <559805CA.8070700@msapiro.net>
References: <lnufpahtru1g1thkg1tfbv6fnqertekki0@4ax.com>
 <559805CA.8070700@msapiro.net>
Message-ID: <v15gpat43cg9v8fu1tnp4m5g245ld59ksi@4ax.com>

On Sat, 04 Jul 2015 09:11:54 -0700, you wrote:

>On 07/04/2015 08:27 AM, Steve Matzura wrote:
>> 
>> On Sat, 04 Jul 2015 07:45:07 -0700, Mark Sapiro <mark at msapiro.net>
>> wrote:
>> 
>>> These occur because you have installed a crontab which has been
>>> formatted as a system crontab and intended to be installed in a place
>>> like /etc/cron.d/mailman as a user contab somewhere in /var/spool/cron.
>> 
>> Interesting. I followed the directions at
>> http://www.gnu.org/software/mailman/mailman-install/node41.html which
>> say:
>
>
>This is just one of many reasons for the advice in the FAQ at
><http://wiki.list.org/x/12812344>.
>
>Packagers do various things that don't always align with what we
>recommend. In short, If you install from source, follow our docs; if you
>install a package, follow the packager's docs.
>
>In your case, the RedHat package has modified Mailman's crontab.in to be
>a system crontab and already installed it in /etc/cron.d/.
>
>Thus it was wrong to follow our manual and try to install it ads the
>Mailman user's crontab.

Right. And it was wrong of RH not to tell me that up front, or if it
does, it didn't jump up and tell me. Sometimes there's just so much to
read and digest, and much of it has to be done after the fact. I'll
comb their docs and if it's not present, will let you know so somehow
it can be included somewhere.

>To correct this, just do
>
>sudo crontab -u mailman -r

Done.

>Disabling SELinix may help, but you may not want to do that. Otherwise,
>you'd need to address this via SELinux policies, and I don't know what
>would need to be changed. This is interesting because the motivation for
>RedHat's file location changes to be FHS compliant was at least in part
>to make their Mailman package work well with SELinux.

Then calling on my fine command of all things Linux (NOT), I'll leave
it alone.

From bernie at fantasyfarm.com  Sat Jul  4 19:32:13 2015
From: bernie at fantasyfarm.com (Bernie Cosell)
Date: Sat, 04 Jul 2015 13:32:13 -0400
Subject: [Mailman-Users] spam filter not working
In-Reply-To: <5597FA20.4050105@msapiro.net>
References: <5596B25E.18125.5C156950@bernie.fantasyfarm.com>,
 <5597FA20.4050105@msapiro.net>
Message-ID: <5598189D.24288.618CCF02@bernie.fantasyfarm.com>

On 4 Jul 2015 at 8:22, Mark Sapiro wrote:

> On 07/03/2015 09:03 AM, Bernie Cosell wrote:

> > I have a spam filter set to 'hold':
> > 
> > X-Spam-Level:\s*\*\*\*

> I would use
> 
> ^X-Spam-Level:\s*\*\*\*
> 
> but yours should match any with 3 or more stars, in particular the one
> above.
> 
> Is it possible it was held and approved? Check Mailman's 'vette' log
> or
> check the received massage for an X-Mailman-Approved-At: header.

I've looked through the headers and it appears that my service provider 
only runs spam assassin *AFTER* the message goes through mailman -- the 
spam assassin headers come *after* all the mailman headers.   I don't 
know if I can fix/change that or what to do.   I'll have to talk to the 
service provider about that.

   /b\


-- 
Bernie Cosell                     Fantasy Farm Fibers
mailto:bernie at fantasyfarm.com     Pearisburg, VA
    -->  Too many people, too few sheep  <--       




From jebva at yahoo.com  Sun Jul  5 03:45:29 2015
From: jebva at yahoo.com (JB)
Date: Sat, 4 Jul 2015 18:45:29 -0700
Subject: [Mailman-Users] Migrate 2.x -> 3.x
In-Reply-To: <k4ncpahl0b9fpk4et9glu1gb4hrfj9ndj3@4ax.com>
Message-ID: <1436060729.4910.YahooMailBasic@web122502.mail.ne1.yahoo.com>

Is there an ETA on when a migration path from MM 2.x to 3.x will be ready or is there even a plan in place to develop such an animal? 

From mark at msapiro.net  Sun Jul  5 04:01:16 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 04 Jul 2015 19:01:16 -0700
Subject: [Mailman-Users] Migrate 2.x -> 3.x
In-Reply-To: <1436060729.4910.YahooMailBasic@web122502.mail.ne1.yahoo.com>
References: <1436060729.4910.YahooMailBasic@web122502.mail.ne1.yahoo.com>
Message-ID: <55988FEC.5030305@msapiro.net>

On 07/04/2015 06:45 PM, JB via Mailman-Users wrote:
> Is there an ETA on when a migration path from MM 2.x to 3.x will be ready or is there even a plan in place to develop such an animal? 


The short answer is yes, there is a plan and it is one of the things we
plan to include with Mailman 3.1, but no, there is not yet an ETA for MM
3.1.

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

From mark at msapiro.net  Sun Jul  5 05:01:09 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 04 Jul 2015 20:01:09 -0700
Subject: [Mailman-Users] spam filter not working
In-Reply-To: <5598189D.24288.618CCF02@bernie.fantasyfarm.com>
References: <5596B25E.18125.5C156950@bernie.fantasyfarm.com>,
 <5597FA20.4050105@msapiro.net>
 <5598189D.24288.618CCF02@bernie.fantasyfarm.com>
Message-ID: <55989DF5.1080008@msapiro.net>

On 07/04/2015 10:32 AM, Bernie Cosell wrote:
> 
> I've looked through the headers and it appears that my service provider 
> only runs spam assassin *AFTER* the message goes through mailman -- the 
> spam assassin headers come *after* all the mailman headers.   I don't 
> know if I can fix/change that or what to do.   I'll have to talk to the 
> service provider about that.


You can verify this be say setting yourself moderated on the list,
sending a post and then examining the headers od the held message in the
admindb interface. It seems to me that your reasoning is sound, but if
the headers aren't there in the held message, that would be good evidence.

It does seem strange however if the outbound mail is going through the
same MTA that it would apply spam filtering to outbound mail and not to
inbound mail. Perhaps the spamassassin headers are added even further
down stream, e.g. by your own fantasyfarm.com MTA, and not by the
Mailman server at all.

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

From mark at msapiro.net  Sun Jul  5 05:15:38 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 04 Jul 2015 20:15:38 -0700
Subject: [Mailman-Users] Nightly Messages Show Problems
In-Reply-To: <v15gpat43cg9v8fu1tnp4m5g245ld59ksi@4ax.com>
References: <lnufpahtru1g1thkg1tfbv6fnqertekki0@4ax.com>
 <559805CA.8070700@msapiro.net> <v15gpat43cg9v8fu1tnp4m5g245ld59ksi@4ax.com>
Message-ID: <5598A15A.5020301@msapiro.net>

On 07/04/2015 10:19 AM, Steve Matzura wrote:
> 
> Right. And it was wrong of RH not to tell me that up front, or if it
> does, it didn't jump up and tell me. Sometimes there's just so much to
> read and digest, and much of it has to be done after the fact. I'll
> comb their docs and if it's not present, will let you know so somehow
> it can be included somewhere.


Letting me know doesn't help. You have to tell RedHat. The documentation
the GNU Mailman project produces documents our GNU Mailman distribution.
If there is something incorrect or confusing in that documentation as
applied to our distribution, then we want to know about it and we will
do our best to fix it.

We cannot however document or even know about everything that downstream
packagers do in modifying and packaging our product in ways that make it
no longer aligned with our documentation. That is the reason for the
advice in the FAQ at <http://wiki.list.org/x/12812344> and the post
linked therefrom. That's not to say that we won't try to help you if you
have issues with a downstream package, but we are at a disadvantage for
doing so.

And, if you come here for help because we are more responsive and the
packager is less so, perhaps you should reconsider your decision to use
the downstream package.

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

From sylvain at opensource-expert.com  Sun Jul  5 08:49:51 2015
From: sylvain at opensource-expert.com (Sylvain Viart)
Date: Sun, 05 Jul 2015 08:49:51 +0200
Subject: [Mailman-Users] maiman3 demo and VM?
Message-ID: <5598D38F.9050701@opensource-expert.com>

Hi,


Could you point me to some mailman3 online demo, please?

I would like to play with turnkey <https://www.turnkeylinux.org/> VM
image, I discovered recently, may be it will be a good challenge to have
a working mailman3 image in that format?

Is there a wiki page or something uptodate with such way how to quickly
setup such visualized environment?

Regards,
Sylvain.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20150705/f45da175/attachment.sig>

From stephen at xemacs.org  Mon Jul  6 06:06:42 2015
From: stephen at xemacs.org (Stephen J. Turnbull)
Date: Mon, 06 Jul 2015 13:06:42 +0900
Subject: [Mailman-Users] Migrate 2.x -> 3.x
In-Reply-To: <55988FEC.5030305@msapiro.net>
References: <1436060729.4910.YahooMailBasic@web122502.mail.ne1.yahoo.com>
 <55988FEC.5030305@msapiro.net>
Message-ID: <87bnfqhqul.fsf@uwakimon.sk.tsukuba.ac.jp>

Mark Sapiro writes:

 > The short answer is yes, there is a plan and it is one of the things we
 > plan to include with Mailman 3.1, but no, there is not yet an ETA for MM
 > 3.1.

I'm planning to migrate a bunch of lists by the end of July.  I will
be moving from Mailman2 + Exim on Debian GNU/Linux (IIRC) to Mailman3
+ Postfix on a Mac Mini running Yosemite (don't ask, it's grant money
politics).  I have a bunch more which will be migrating from some sort
of Linux + Postfix to Centos (IIRC) + an MTA to be named later by the
end of August.  All that should provide some, uh, "interesting"
experiences.

I plan to document my experience and produce scripts.  If y'all have
specific requirements or configurations you'd like us to consider in
producing the migration scripts, feel free to post here or mail me
personally, as appropriate.  (Will summarize anything generally
relevant, of course.)

Steve


From g.aloitus at gmail.com  Mon Jul  6 13:05:23 2015
From: g.aloitus at gmail.com (Teijo)
Date: Mon, 6 Jul 2015 14:05:23 +0300
Subject: [Mailman-Users] Unsure what to do with web page "Bug in Mailman
	version 2.1.20"
Message-ID: <559A60F3.6080500@gmail.com>

Hello,

After updating from Ubuntu 12.04 to 14.04 (Apache 2.2 to 2.4), only page 
content I seem to get is "Bug in Mailman version 2.1.20". No matter if I 
navigate to my Mailman's main page or to the given list's page.

One problem is that there seems to be nothing useful in error log, 
although I set loglevel to debug.

I have chrooted Apache some years ago, and it's still chrooted.

I have not noticed any other problems with Mailman after server update.

Best,

Teijo

From mark at msapiro.net  Mon Jul  6 14:56:11 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 06 Jul 2015 05:56:11 -0700
Subject: [Mailman-Users] Unsure what to do with web page "Bug in
	Mailman	version 2.1.20"
In-Reply-To: <559A60F3.6080500@gmail.com>
References: <559A60F3.6080500@gmail.com>
Message-ID: <6584893B-E19B-4E57-A21D-8F18A8C1FEFB@msapiro.net>

On July 6, 2015 4:05:23 AM PDT, Teijo <g.aloitus at gmail.com> wrote:
>Hello,
>
>After updating from Ubuntu 12.04 to 14.04 (Apache 2.2 to 2.4), only
>page 
>content I seem to get is "Bug in Mailman version 2.1.20". No matter if
>I 
>navigate to my Mailman's main page or to the given list's page.
>
>One problem is that there seems to be nothing useful in error log, 
>although I set loglevel to debug.
>
>I have chrooted Apache some years ago, and it's still chrooted.
>
>I have not noticed any other problems with Mailman after server update.


I suspect the upgrade 'upgraded' Mailman and changed the group of Mailman's files and directories to 'list'.

Run bin/check_perms


-- 
Mark Sapiro <mark at msapiro.net>
Sent from my Android phone with K-9 Mail. [Unpaid endorsement]

From g.aloitus at gmail.com  Mon Jul  6 15:06:15 2015
From: g.aloitus at gmail.com (Teijo)
Date: Mon, 6 Jul 2015 16:06:15 +0300
Subject: [Mailman-Users] Unsure what to do with web page "Bug in Mailman
 version 2.1.20"
In-Reply-To: <6584893B-E19B-4E57-A21D-8F18A8C1FEFB@msapiro.net>
References: <559A60F3.6080500@gmail.com>
 <6584893B-E19B-4E57-A21D-8F18A8C1FEFB@msapiro.net>
Message-ID: <559A7D47.5010306@gmail.com>

Hello,

I did that before writing my message - in fact I reinstalled Mailman and 
checked permissions.

Best,

Teijo

6.7.2015, 15:56, Mark Sapiro kirjoitti:
> On July 6, 2015 4:05:23 AM PDT, Teijo <g.aloitus at gmail.com> wrote:
>> Hello,
>>
>> After updating from Ubuntu 12.04 to 14.04 (Apache 2.2 to 2.4), only
>> page
>> content I seem to get is "Bug in Mailman version 2.1.20". No matter if
>> I
>> navigate to my Mailman's main page or to the given list's page.
>>
>> One problem is that there seems to be nothing useful in error log,
>> although I set loglevel to debug.
>>
>> I have chrooted Apache some years ago, and it's still chrooted.
>>
>> I have not noticed any other problems with Mailman after server update.
>
> I suspect the upgrade 'upgraded' Mailman and changed the group of Mailman's files and directories to 'list'.
>
> Run bin/check_perms
>
>


From lac at openend.se  Mon Jul  6 15:26:02 2015
From: lac at openend.se (Laura Creighton)
Date: Mon, 6 Jul 2015 15:26:02 +0200
Subject: [Mailman-Users] merging 2 mailing lists
Message-ID: <201507061326.t66DQ2Rl020978@fido.openend.se>

2 somebodies I know want to merge their mailing lists.  They are
both lists for recipes for people who have impaired kidney function.
A complication is that these lists are hosted on different machines,
with completely different names, etc.  But picking a third name
and setting things up so that posters to both old names get their
mail sent to the third place, while receiving a message informing
them to use the new address seems to work in testing.

The problem is with the archives.  They want to change the footers
in each of the old list messages to say 'this was posted to old_list,
use new_list instead if you want to post a new message' and point to
the new archives.  I can write a script to do that.

But then, having modified the footers they want to store the 2 past
archives as 1 archive, so that people who search the thing will get
hits wherever the old article was posted.  I don't see any out-of-the-box
solutions, am I missing something?

Laura




From bsfinkel at att.net  Mon Jul  6 16:25:29 2015
From: bsfinkel at att.net (Barry S. Finkel)
Date: Mon, 06 Jul 2015 09:25:29 -0500
Subject: [Mailman-Users] merging 2 mailing lists
In-Reply-To: <201507061326.t66DQ2Rl020978@fido.openend.se>
References: <201507061326.t66DQ2Rl020978@fido.openend.se>
Message-ID: <559A8FD9.60503@att.net>

On 7/6/2015 8:26 AM, Laura Creighton wrote:
> 2 somebodies I know want to merge their mailing lists.  They are
> both lists for recipes for people who have impaired kidney function.
> A complication is that these lists are hosted on different machines,
> with completely different names, etc.  But picking a third name
> and setting things up so that posters to both old names get their
> mail sent to the third place, while receiving a message informing
> them to use the new address seems to work in testing.
>
> The problem is with the archives.  They want to change the footers
> in each of the old list messages to say 'this was posted to old_list,
> use new_list instead if you want to post a new message' and point to
> the new archives.  I can write a script to do that.
>
> But then, having modified the footers they want to store the 2 past
> archives as 1 archive, so that people who search the thing will get
> hits wherever the old article was posted.  I don't see any out-of-the-box
> solutions, am I missing something?
>
> Laura


I am not an expert in Mailman archives, and I do not have a machine
on which to test.  I think that if you take the two mbox archive
files (probably after you have run your footer modification scripts)
and combine them into one file - then you can build the archives of
the new list from this combined file.  I believe (but I may be wrong)
that you do not have to sort the messages in the combined file by date.

What I would do as a test is take the two mbox files, maybe extract
a handful of messages from each (or take the entire files), combine
them, and make an archive for a new test list.

If I remember correctly,

      bin/arch --wipe ...

I do not remember the other parameters, but a search of this list's
archives will find the command.

--Barry Finkel

From mcnutt at utk.edu  Mon Jul  6 15:18:19 2015
From: mcnutt at utk.edu (McNutt Jr, William R)
Date: Mon, 6 Jul 2015 13:18:19 +0000
Subject: [Mailman-Users] Full List of Lists
Message-ID: <CY1PR02MB17382A7CFE04062F4086B39ADF930@CY1PR02MB1738.namprd02.prod.outlook.com>

Is there a report or accepted technique that I can use to get a list of all the lists on my server, even the unadvertised ones?

Bill

From draksler at mcmaster.ca  Mon Jul  6 17:00:16 2015
From: draksler at mcmaster.ca (Peter Draksler)
Date: Mon, 06 Jul 2015 11:00:16 -0400
Subject: [Mailman-Users] Full List of Lists
In-Reply-To: <CY1PR02MB17382A7CFE04062F4086B39ADF930@CY1PR02MB1738.namprd02.prod.outlook.com>
References: <CY1PR02MB17382A7CFE04062F4086B39ADF930@CY1PR02MB1738.namprd02.prod.outlook.com>
Message-ID: <559A9800.9060807@mcmaster.ca>

On 15-07-06 09:18 AM, McNutt Jr, William R wrote:
> Is there a report or accepted technique that I can use to get a list of all the lists on my server, even the unadvertised ones?

You should be able to get this by running bin/list_lists.

Peter


From sm at noisynotes.com  Mon Jul  6 17:10:16 2015
From: sm at noisynotes.com (Steve Matzura)
Date: Mon, 06 Jul 2015 11:10:16 -0400
Subject: [Mailman-Users] Nightly Messages Show Problems
In-Reply-To: <559805CA.8070700@msapiro.net>
References: <lnufpahtru1g1thkg1tfbv6fnqertekki0@4ax.com>
 <559805CA.8070700@msapiro.net>
Message-ID: <4k5lpatpt2lo60o2el9oq82hpmqgnp39ih@4ax.com>

On Sat, 04 Jul 2015 09:11:54 -0700, Mark Sapiro <mark at msapiro.net>
wrote:

>In your case, the RedHat package has modified Mailman's crontab.in to be
>a system crontab and already installed it in /etc/cron.d/.

It did, but the file is virtually empty (only three or four comment
lines warning not to edit it and that its contents is managed by
/usr/lib/mailman/cron/crontab.in). I have restarted mm thinking the
contents of crontab.in would be copied to /etc/cron.d/mailman like it
was when it lived in /var/spool/cron. Should this be done manually?

From bernie at fantasyfarm.com  Mon Jul  6 17:53:02 2015
From: bernie at fantasyfarm.com (Bernie Cosell)
Date: Mon, 06 Jul 2015 11:53:02 -0400
Subject: [Mailman-Users] spam filter not working
In-Reply-To: <5597FA20.4050105@msapiro.net>
References: <5596B25E.18125.5C156950@bernie.fantasyfarm.com>,
 <5597FA20.4050105@msapiro.net>
Message-ID: <559AA45E.32072.6B7EB713@bernie.fantasyfarm.com>

> > I have a spam filter set to 'hold':
> > 
> > X-Spam-Level:\s*\*\*\*

> I would use
> 
> ^X-Spam-Level:\s*\*\*\*
> 
> but yours should match any with 3 or more stars, in particular the one
> above.

I have confirmed with the sysadmins:

	 There is no way to set it to use spam assassin first.

So my problem is the obvious one: the filter isn't working because spam 
assassin isn't there.  I need to figure out something to do about this.  
I can close the list, which will be a nuisance for me [to approve-through 
legit emails from alternate addreses] but that may be my only recourse.

I'm actually thinking of a little hack that'd probably work: set up a 
*real* mailbox as the target of the list.  That _will_ get 
spam-assassined.  Then set up a cron-job that runs every few minutes to 
grab the mailbox and 'bounce' it to the mailman list.  Dunno if I can 
pull that off and it might be more trouble than it saves...

   Thanks for the help, though.
      /b\

-- 
Bernie Cosell                     Fantasy Farm Fibers
mailto:bernie at fantasyfarm.com     Pearisburg, VA
    -->  Too many people, too few sheep  <--       




From bernie at fantasyfarm.com  Mon Jul  6 22:27:05 2015
From: bernie at fantasyfarm.com (Bernie Cosell)
Date: Mon, 06 Jul 2015 16:27:05 -0400
Subject: [Mailman-Users] Can't "close" a list
Message-ID: <559AE499.16681.6C799DFD@bernie.fantasyfarm.com>

Sorry to be posting another incredibly dumb question, but after my last 
go-round [wherein I learned that I had the RE just right but my #@#%$@#$% 
ISP runs spam assassing *after* mailman] I decided to try "closing" the 
list.  So I checked thet FAQs and the manuals and did what I thought 
should do the job.  In my otherwise empty 'sender filters' I changed:

Action to take for postings from non-members for which no explicit action 
is defined.

to "hold"

The membership list consists of a single address, and I sent a message to 
the list from a different address and I was very surprised that it just 
went through.  So I tried a more brute-force thing for my test: I changed

   List of non-member addresses whose postings will be automatically 
rejected.

to "^.*"

And it came right through:

From: "Bernie Cosell" <bpcosell at email.vccs.edu>
Organization: Fantasy Farm Fibers
To: testlist at cosell.net
Date: Mon, 06 Jul 2015 15:38:20 -0400

Is there something else I need to enable or set or something other than 
the settings on the "sender filters" page to get outsiders blocked?

THANKS!  /bernie\

-- 
Bernie Cosell                     Fantasy Farm Fibers
mailto:bernie at fantasyfarm.com     Pearisburg, VA
    -->  Too many people, too few sheep  <--       




From mark at msapiro.net  Mon Jul  6 15:22:00 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 06 Jul 2015 06:22:00 -0700
Subject: [Mailman-Users] Unsure what to do with web page "Bug in Mailman
	version 2.1.20"
In-Reply-To: <559A7D47.5010306@gmail.com>
References: <559A60F3.6080500@gmail.com>
 <6584893B-E19B-4E57-A21D-8F18A8C1FEFB@msapiro.net>
 <559A7D47.5010306@gmail.com>
Message-ID: <D7FFB188-E746-487A-A08F-2584423EEA0D@msapiro.net>

On July 6, 2015 6:06:15 AM PDT, Teijo <g.aloitus at gmail.com> wrote:
>Hello,
>
>I did that before writing my message - in fact I reinstalled Mailman
>and 
>checked permissions.


Have you looked in Mailman's error log (not just Apache's)?

Also, in the FAQ

>Mailman FAQ: http://wiki.list.org/x/AgA3

there is an article about upgrading Debian/Ubuntu from source with an attached script that fixes some things.



-- 
Mark Sapiro <mark at msapiro.net>
Sent from my Android phone with K-9 Mail. [Unpaid endorsement]

From jebva at yahoo.com  Tue Jul  7 02:09:44 2015
From: jebva at yahoo.com (JB)
Date: Mon, 6 Jul 2015 17:09:44 -0700
Subject: [Mailman-Users] Migrate 2.x -> 3.x
In-Reply-To: <87bnfqhqul.fsf@uwakimon.sk.tsukuba.ac.jp>
Message-ID: <1436227784.91782.YahooMailBasic@web122504.mail.ne1.yahoo.com>

I for one run a number of server with cPanel/WHM.  They are using the latest 2.x version of MM now.  I was hoping that there would be a way for cPanel/WHM to update to he 3.x tree and have all existing list migrated to the new tree.

--------------------------------------------
On Mon, 7/6/15, Stephen J. Turnbull <stephen at xemacs.org> wrote:

 Subject: Re: [Mailman-Users] Migrate 2.x -> 3.x
 To: "Mark Sapiro" <mark at msapiro.net>
 Cc: mailman-users at python.org
 Date: Monday, July 6, 2015, 12:06 AM
 
 Mark Sapiro writes:
 
  > The short answer is yes, there is a plan and it is one
 of the things we
  > plan to include with Mailman 3.1, but no, there is not
 yet an ETA for MM
  > 3.1.
 
 I'm planning to migrate a bunch of lists by the end of
 July.? I will
 be moving from Mailman2 + Exim on Debian GNU/Linux (IIRC) to
 Mailman3
 + Postfix on a Mac Mini running Yosemite (don't ask, it's
 grant money
 politics).? I have a bunch more which will be migrating
 from some sort
 of Linux + Postfix to Centos (IIRC) + an MTA to be named
 later by the
 end of August.? All that should provide some, uh,
 "interesting"
 experiences.
 
 I plan to document my experience and produce scripts.?
 If y'all have
 specific requirements or configurations you'd like us to
 consider in
 producing the migration scripts, feel free to post here or
 mail me
 personally, as appropriate.? (Will summarize anything
 generally
 relevant, of course.)
 
 Steve
 
 ------------------------------------------------------
 Mailman-Users mailing list Mailman-Users at 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/jebva%40yahoo.com
 

From mark at msapiro.net  Tue Jul  7 04:17:23 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 06 Jul 2015 19:17:23 -0700
Subject: [Mailman-Users] Nightly Messages Show Problems
In-Reply-To: <4k5lpatpt2lo60o2el9oq82hpmqgnp39ih@4ax.com>
References: <lnufpahtru1g1thkg1tfbv6fnqertekki0@4ax.com>
 <559805CA.8070700@msapiro.net> <4k5lpatpt2lo60o2el9oq82hpmqgnp39ih@4ax.com>
Message-ID: <559B36B3.1090907@msapiro.net>

On 07/06/2015 08:10 AM, Steve Matzura wrote:
> On Sat, 04 Jul 2015 09:11:54 -0700, Mark Sapiro <mark at msapiro.net>
> wrote:
> 
>> In your case, the RedHat package has modified Mailman's crontab.in to be
>> a system crontab and already installed it in /etc/cron.d/.
> 
> It did, but the file is virtually empty (only three or four comment
> lines warning not to edit it and that its contents is managed by
> /usr/lib/mailman/cron/crontab.in). I have restarted mm thinking the
> contents of crontab.in would be copied to /etc/cron.d/mailman like it
> was when it lived in /var/spool/cron. Should this be done manually?


RedHat's /etc/init.d/mailman copies the cron/crontab.in to
/etc/cron.d/mailman. So if you start Mailman via 'service mailman
start', the crontab in crontab.in will be installed.

At least that's the way I *think* it works. Ask RedHat or look at the
init.d script to be sure.

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

From mark at msapiro.net  Tue Jul  7 04:31:22 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 06 Jul 2015 19:31:22 -0700
Subject: [Mailman-Users] merging 2 mailing lists
In-Reply-To: <559A8FD9.60503@att.net>
References: <201507061326.t66DQ2Rl020978@fido.openend.se>
 <559A8FD9.60503@att.net>
Message-ID: <559B39FA.4030700@msapiro.net>

On 07/06/2015 07:25 AM, Barry S. Finkel wrote:
> 
> I am not an expert in Mailman archives, and I do not have a machine
> on which to test.  I think that if you take the two mbox archive
> files (probably after you have run your footer modification scripts)
> and combine them into one file - then you can build the archives of
> the new list from this combined file.  I believe (but I may be wrong)
> that you do not have to sort the messages in the combined file by date.


That's essentially what I would do. I.e. modify the
listname.mbox/listname.mbox archive mbox files to add the desired
footers, concatenate them and use the result as input to 'bin/arch
--wipe' to build the new combined archive.

But sequence does matter. If you concatenate two mboxes and keep the two
parts in sequence, that will be OK. There are two issues with sequence.
One is that the message numbering in the new html archive, and hence
URLs to individual messages, is the overall sequence in the input mbox.
That won't matter in your case, because it's a new archive and no one
has saved URLs to its messages.

The other issue is bin/arch does extra work every time the 'period'
changes. E.g., if archive_volume_frequency is Monthly, each time the
Month/Year changes in the input, extra work is done. If the input is two
big chunks, each of which is in sequence, this won't be noticeable, but
if the input is large and more or less random, bin/arch can take a very
long time to process it.

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

From mark at msapiro.net  Tue Jul  7 04:47:29 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 06 Jul 2015 19:47:29 -0700
Subject: [Mailman-Users] spam filter not working
In-Reply-To: <559AA45E.32072.6B7EB713@bernie.fantasyfarm.com>
References: <5596B25E.18125.5C156950@bernie.fantasyfarm.com>,
 <5597FA20.4050105@msapiro.net>
 <559AA45E.32072.6B7EB713@bernie.fantasyfarm.com>
Message-ID: <559B3DC1.1080106@msapiro.net>

On 07/06/2015 08:53 AM, Bernie Cosell wrote:
> 
> I have confirmed with the sysadmins:
> 
> 	 There is no way to set it to use spam assassin first.


Which means they run spamassassin against outgoing mail but not incoming
mail. The mind boggles at the absurdity ...

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

From mark at msapiro.net  Tue Jul  7 04:57:27 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 06 Jul 2015 19:57:27 -0700
Subject: [Mailman-Users] Can't "close" a list
In-Reply-To: <559AE499.16681.6C799DFD@bernie.fantasyfarm.com>
References: <559AE499.16681.6C799DFD@bernie.fantasyfarm.com>
Message-ID: <559B4017.7040501@msapiro.net>

On 07/06/2015 01:27 PM, Bernie Cosell wrote:
> 
> Action to take for postings from non-members for which no explicit action 
> is defined.
> 
> to "hold"


This should work to hold all messages from non-members, but more below.


> The membership list consists of a single address, and I sent a message to 
> the list from a different address and I was very surprised that it just 
> went through.  So I tried a more brute-force thing for my test: I changed
> 
>    List of non-member addresses whose postings will be automatically 
> rejected.
> 
> to "^.*"


If you put

^.*

Or just

^.

in reject_these_nonmembers, all non member posts will be rejected.


> And it came right through:
> 
> From: "Bernie Cosell" <bpcosell at email.vccs.edu>
> Organization: Fantasy Farm Fibers
> To: testlist at cosell.net
> Date: Mon, 06 Jul 2015 15:38:20 -0400
> 
> Is there something else I need to enable or set or something other than 
> the settings on the "sender filters" page to get outsiders blocked?


Both the things you did apply to non-member posts. I suspect the issue
is that Mailman thinks your test posts are from a member because (by
default at least) if any of the smtp envelope sender or any From:,
Reply-To: or Sender: header contains a member address, Mailman considers
it a member post.

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

From mailmanu-20150316 at billmail.scconsult.com  Tue Jul  7 06:33:00 2015
From: mailmanu-20150316 at billmail.scconsult.com (Bill Cole)
Date: Tue, 07 Jul 2015 00:33:00 -0400
Subject: [Mailman-Users] merging 2 mailing lists
In-Reply-To: <201507061326.t66DQ2Rl020978@fido.openend.se>
References: <201507061326.t66DQ2Rl020978@fido.openend.se>
Message-ID: <E6D5C49F-1D98-4620-869C-04AABF45C374@billmail.scconsult.com>

On 6 Jul 2015, at 9:26, Laura Creighton wrote:

> 2 somebodies I know want to merge their mailing lists.

Have they bothered asking each and every subscriber and received an 
affirmative reply? No? Imagine my shock...

The correct answer to this is "No, you can't. You don't have subscriber 
permission to do so."

Unless you think having all of the IPs of the list service provider 
*correctly* blacklisted in many places is a good thing.

From stephen at xemacs.org  Tue Jul  7 09:26:36 2015
From: stephen at xemacs.org (Stephen J. Turnbull)
Date: Tue, 07 Jul 2015 16:26:36 +0900
Subject: [Mailman-Users] Unsure what to do with web page "Bug in
	Mailman	version 2.1.20"
In-Reply-To: <559A60F3.6080500@gmail.com>
References: <559A60F3.6080500@gmail.com>
Message-ID: <873810ig2b.fsf@uwakimon.sk.tsukuba.ac.jp>

Teijo writes:

 > After updating from Ubuntu 12.04 to 14.04 (Apache 2.2 to 2.4), only page 
 > content I seem to get is "Bug in Mailman version 2.1.20".

Don't assume it's Mailman, although the fact that you're getting to a
bug page is a strong indication that it is Mailman.  The upgrade from
Apache 2.2 to 2.4 is likely to have whacked any custom configuration
you've done, especially of virtual hosts.  Check your Apache configs.




From stephen at xemacs.org  Tue Jul  7 09:41:12 2015
From: stephen at xemacs.org (Stephen J. Turnbull)
Date: Tue, 07 Jul 2015 16:41:12 +0900
Subject: [Mailman-Users] merging 2 mailing lists
In-Reply-To: <E6D5C49F-1D98-4620-869C-04AABF45C374@billmail.scconsult.com>
References: <201507061326.t66DQ2Rl020978@fido.openend.se>
 <E6D5C49F-1D98-4620-869C-04AABF45C374@billmail.scconsult.com>
Message-ID: <87zj38h0tj.fsf@uwakimon.sk.tsukuba.ac.jp>

Bill Cole writes:
 > On 6 Jul 2015, at 9:26, Laura Creighton wrote:
 > 
 > > 2 somebodies I know want to merge their mailing lists.
 > 
 > Have they bothered asking each and every subscriber and received an 
 > affirmative reply? No? Imagine my shock...
 > 
 > The correct answer to this is "No, you can't. You don't have subscriber 
 > permission to do so."

That's one correct answer.  But if the original lists are
open-subscription, open-archive, I really don't see a need for
permission.  The listmasters are just doing automatically and
efficiently what anybody could do by hand (or by 'bot).


From g.aloitus at gmail.com  Tue Jul  7 11:03:06 2015
From: g.aloitus at gmail.com (Teijo)
Date: Tue, 7 Jul 2015 12:03:06 +0300
Subject: [Mailman-Users] Unsure what to do with web page "Bug in Mailman
 version 2.1.20" (solved)
In-Reply-To: <D7FFB188-E746-487A-A08F-2584423EEA0D@msapiro.net>
References: <559A60F3.6080500@gmail.com>
 <6584893B-E19B-4E57-A21D-8F18A8C1FEFB@msapiro.net>
 <559A7D47.5010306@gmail.com>
 <D7FFB188-E746-487A-A08F-2584423EEA0D@msapiro.net>
Message-ID: <559B95CA.2040101@gmail.com>

Hello,

Thank you for your reply. Checking Mailman's error log (what I never 
did) was the key to the solution.

There was module named _io import error so I supposed there was 
something wrong in my chrooted environment. On the basis of this question:

https://stackoverflow.com/questions/23176697/importerror-no-module-named-io-in-ubuntu-14-04

I noticed that Python version of system was 2.7.6 but 2.7.3 in the 
chrooted system. I have script which should keep chrooted system updated 
but clearly it does not work perfectly.

On the basis of the Wiki article I added --with-cgi-gid=www-data to my 
configuration options.

Best,

Teijo

6.7.2015, 16:22, Mark Sapiro kirjoitti:
> On July 6, 2015 6:06:15 AM PDT, Teijo <g.aloitus at gmail.com> wrote:
>> Hello,
>>
>> I did that before writing my message - in fact I reinstalled Mailman
>> and
>> checked permissions.
>
> Have you looked in Mailman's error log (not just Apache's)?
>
> Also, in the FAQ
>
>> Mailman FAQ: http://wiki.list.org/x/AgA3
> there is an article about upgrading Debian/Ubuntu from source with an attached script that fixes some things.
>
>
>


From skip.montanaro at gmail.com  Tue Jul  7 13:00:29 2015
From: skip.montanaro at gmail.com (Skip Montanaro)
Date: Tue, 7 Jul 2015 06:00:29 -0500
Subject: [Mailman-Users] spam filter not working
In-Reply-To: <559B3DC1.1080106@msapiro.net>
References: <5596B25E.18125.5C156950@bernie.fantasyfarm.com>
 <5597FA20.4050105@msapiro.net>
 <559AA45E.32072.6B7EB713@bernie.fantasyfarm.com>
 <559B3DC1.1080106@msapiro.net>
Message-ID: <CANc-5UzDVfgywkPEHLUQ6XQC5RtfOnYEDoR6hSuKWq=yqkT9uw@mail.gmail.com>

On Mon, Jul 6, 2015 at 9:47 PM, Mark Sapiro <mark at msapiro.net> wrote:
> Which means they run spamassassin against outgoing mail but not incoming
> mail. The mind boggles at the absurdity ...

It might be possible to worm around this craziness. You'd need two lists
though, one which just forwards to the second. The second should see the SA
header.

Also, I would use SpamBayes, but that's just me... (Let's try one of these
new fangled Unicode Emojis...)?

Skip Montanaro

From sm at noisynotes.com  Tue Jul  7 13:11:40 2015
From: sm at noisynotes.com (Steve Matzura)
Date: Tue, 07 Jul 2015 07:11:40 -0400
Subject: [Mailman-Users] Nightly Messages Show Problems
In-Reply-To: <559B36B3.1090907@msapiro.net>
References: <lnufpahtru1g1thkg1tfbv6fnqertekki0@4ax.com>
 <559805CA.8070700@msapiro.net> <4k5lpatpt2lo60o2el9oq82hpmqgnp39ih@4ax.com>
 <559B36B3.1090907@msapiro.net>
Message-ID: <cncnpapo74tasd0coma30vc0irr43ea0o2@4ax.com>

On Mon, 06 Jul 2015 19:17:23 -0700, you wrote:

>RedHat's /etc/init.d/mailman copies the cron/crontab.in to
>/etc/cron.d/mailman. So if you start Mailman via 'service mailman
>start', the crontab in crontab.in will be installed.
>
>At least that's the way I *think* it works. Ask RedHat or look at the
>init.d script to be sure.

I thought so, to, but believe it or not, there is no such script in
init.d. In fact, of all the packages I have installed, and there
aren't more than half a dozen, only two have startup scripts in
/etc/init.d.

On to Red Hat support.


From lac at openend.se  Tue Jul  7 13:15:15 2015
From: lac at openend.se (Laura Creighton)
Date: Tue, 07 Jul 2015 13:15:15 +0200
Subject: [Mailman-Users] merging 2 mailing lists
In-Reply-To: Message from "Bill Cole"
 <mailmanu-20150316@billmail.scconsult.com> of "Tue,
 07 Jul 2015 00:33:00 -0400."
 <E6D5C49F-1D98-4620-869C-04AABF45C374@billmail.scconsult.com>
References: <201507061326.t66DQ2Rl020978@fido.openend.se><E6D5C49F-1D98-4620-869C-04AABF45C374@billmail.scconsult.com>
Message-ID: <201507071115.t67BFFUv019352@fido.openend.se>

In a message of Tue, 07 Jul 2015 00:33:00 -0400, "Bill Cole" writes:
>On 6 Jul 2015, at 9:26, Laura Creighton wrote:
>
>> 2 somebodies I know want to merge their mailing lists.
>
>Have they bothered asking each and every subscriber and received an 
>affirmative reply? No? Imagine my shock...
>
>The correct answer to this is "No, you can't. You don't have subscriber 
>permission to do so."
>
>Unless you think having all of the IPs of the list service provider 
>*correctly* blacklisted in many places is a good thing.

??? There's  been major discussion about this on both lists, and
everybody thinks it's a wonderful idea.  Not a single objection.
And for the life of me, I cannot imagine why there would be.  Recipes
developed by members of the Stockholm region support group for families
with kidney disease are perfectly edible by V?rmland families in
the same position, and vice versa.  Why on earth shouldn't they be
able to combine their lists if they want to?

Laura

From bernie at fantasyfarm.com  Tue Jul  7 13:19:57 2015
From: bernie at fantasyfarm.com (Bernie Cosell)
Date: Tue, 07 Jul 2015 07:19:57 -0400
Subject: [Mailman-Users] Can't "close" a list
In-Reply-To: <559B4017.7040501@msapiro.net>
References: <559AE499.16681.6C799DFD@bernie.fantasyfarm.com>,
 <559B4017.7040501@msapiro.net>
Message-ID: <559BB5DD.18438.6FAB104F@bernie.fantasyfarm.com>

> Both the things you did apply to non-member posts. I suspect the issue
> is that Mailman thinks your test posts are from a member because (by
> default at least) if any of the smtp envelope sender or any From:,
> Reply-To: or Sender: header contains a member address, Mailman
> considers
> it a member post.

Ah, that solves the problem.   I don't think that was made clear.  So it 
probably was working, but I couldn't test it because although I was using 
other identities, the envelope still said it was from me.

thanks!  /b\

-- 
Bernie Cosell                     Fantasy Farm Fibers
mailto:bernie at fantasyfarm.com     Pearisburg, VA
    -->  Too many people, too few sheep  <--       




From sm at noisynotes.com  Tue Jul  7 15:48:58 2015
From: sm at noisynotes.com (Steve Matzura)
Date: Tue, 07 Jul 2015 09:48:58 -0400
Subject: [Mailman-Users] Nightly Messages Show Problems
In-Reply-To: <cncnpapo74tasd0coma30vc0irr43ea0o2@4ax.com>
References: <lnufpahtru1g1thkg1tfbv6fnqertekki0@4ax.com>
 <559805CA.8070700@msapiro.net> <4k5lpatpt2lo60o2el9oq82hpmqgnp39ih@4ax.com>
 <559B36B3.1090907@msapiro.net> <cncnpapo74tasd0coma30vc0irr43ea0o2@4ax.com>
Message-ID: <jdjnpatbogm42gfjd5uu94blbhag3gh7ak@4ax.com>

On Tue, 07 Jul 2015 07:11:40 -0400, Mark wrote:

>>RedHat's /etc/init.d/mailman copies the cron/crontab.in to
>>/etc/cron.d/mailman. So if you start Mailman via 'service mailman
>>start', the crontab in crontab.in will be installed.

It's done in the Mailman service definition, which means the crontab
copy is done only when the service is started via systemctl. If
pre-mailmanctl processing is desired, the only way to make that happen
is via systemctl.

From mailmanu-20150316 at billmail.scconsult.com  Tue Jul  7 16:55:52 2015
From: mailmanu-20150316 at billmail.scconsult.com (Bill Cole)
Date: Tue, 07 Jul 2015 10:55:52 -0400
Subject: [Mailman-Users] merging 2 mailing lists
In-Reply-To: <201507071115.t67BFFUv019352@fido.openend.se>
References: <201507061326.t66DQ2Rl020978@fido.openend.se>
 <E6D5C49F-1D98-4620-869C-04AABF45C374@billmail.scconsult.com>
 <201507071115.t67BFFUv019352@fido.openend.se>
Message-ID: <46FCA49D-0A00-4F99-A5EF-0AFD85CB8F54@billmail.scconsult.com>

On 7 Jul 2015, at 7:15, Laura Creighton wrote:

> In a message of Tue, 07 Jul 2015 00:33:00 -0400, "Bill Cole" writes:
>> On 6 Jul 2015, at 9:26, Laura Creighton wrote:
>>
>>> 2 somebodies I know want to merge their mailing lists.
>>
>> Have they bothered asking each and every subscriber and received an
>> affirmative reply? No? Imagine my shock...
>>
>> The correct answer to this is "No, you can't. You don't have 
>> subscriber
>> permission to do so."
>>
>> Unless you think having all of the IPs of the list service provider
>> *correctly* blacklisted in many places is a good thing.
>
> ??? There's  been major discussion about this on both lists, and
> everybody thinks it's a wonderful idea.  Not a single objection.

I am sorry. By way of explanation, it was late and I skimmed with tired 
eyes, missing the key point that these are traditional discussion lists 
rather than unidirectional broadcast lists.

For a pair of active discussion lists, open discussions of a merger 
on-list is absolutely fair warning.


From sjohn at mni-news.com  Tue Jul  7 13:43:31 2015
From: sjohn at mni-news.com (Sibi John)
Date: Tue, 7 Jul 2015 04:43:31 -0700
Subject: [Mailman-Users] Header filtering regex issue
Message-ID: <524CCF72D1F3634892B27FB204E8317EE22E695635@EX-BE-026-SV1.shared.themessagecenter.com>

Guys,

I am not sure what I am doing wrong here with the header filter especially since I know this used to work in the past.

For one of my mailing lists, I would like to automatically discard any emails that do not from the two domains xxx and yyy listed below. The regex matches any other email address.

In my spam filter rules, this is the regex that I have and it matches perfectly.

From: .+@(?!(xxx|yyy)\.com)<mailto:.+@(?!(xxx|yyy)\.com)>.+


For some reason, it discards all email and I cannot seem to figure out what I am doing wrong. Any suggestions ?

From turnbull at sk.tsukuba.ac.jp  Tue Jul  7 09:30:20 2015
From: turnbull at sk.tsukuba.ac.jp (Stephen J. Turnbull)
Date: Tue, 07 Jul 2015 16:30:20 +0900
Subject: [Mailman-Users] Migrate 2.x -> 3.x
In-Reply-To: <1436227784.91782.YahooMailBasic@web122504.mail.ne1.yahoo.com>
References: <87bnfqhqul.fsf@uwakimon.sk.tsukuba.ac.jp>
 <1436227784.91782.YahooMailBasic@web122504.mail.ne1.yahoo.com>
Message-ID: <871tgkifw3.fsf@uwakimon.sk.tsukuba.ac.jp>

JB via Mailman-Users writes:

 > I for one run a number of server with cPanel/WHM.  They are using
 > the latest 2.x version of MM now.  I was hoping that there would be
 > a way for cPanel/WHM to update to he 3.x tree and have all existing
 > list migrated to the new tree.

Thanks for the suggestion.  I don't think it's going to be easy
because cPanel uses custom mods to Mailman, and it's kind of out of
scope for me/us (they're a commercial enterprise and undoubtedly would
want to integrate Mailman 3 into next year's version of cPanal rather
than last year's).

I will talk to the cPanel guys about avoiding duplication of effort,
but most likely they will do the work on their own schedule.

Steve




From mark at msapiro.net  Tue Jul  7 21:39:31 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 07 Jul 2015 12:39:31 -0700
Subject: [Mailman-Users] Header filtering regex issue
In-Reply-To: <524CCF72D1F3634892B27FB204E8317EE22E695635@EX-BE-026-SV1.shared.themessagecenter.com>
References: <524CCF72D1F3634892B27FB204E8317EE22E695635@EX-BE-026-SV1.shared.themessagecenter.com>
Message-ID: <559C2AF3.7090505@msapiro.net>

On 07/07/2015 04:43 AM, Sibi John wrote:
> 
> In my spam filter rules, this is the regex that I have and it matches perfectly.
> 
> From: .+@(?!(xxx|yyy)\.com).+
> 
> 
> For some reason, it discards all email and I cannot seem to figure out what I am doing wrong. Any suggestions ?


The regexp should work. It might match some desired addresses like
user at sub.xxx.com and not match some undesired ones like user at xxx.com.au,
but it should work for the obvious cases.

Do you have any other header_filter_rules? If so, what are they?

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

From mark at msapiro.net  Tue Jul  7 22:54:58 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 07 Jul 2015 13:54:58 -0700
Subject: [Mailman-Users] Header filtering regex issue
In-Reply-To: <524CCF72D1F3634892B27FB204E8317EE22E69568A@EX-BE-026-SV1.shared.themessagecenter.com>
References: <524CCF72D1F3634892B27FB204E8317EE22E695635@EX-BE-026-SV1.shared.themessagecenter.com>
 <559C2AF3.7090505@msapiro.net>
 <524CCF72D1F3634892B27FB204E8317EE22E69568A@EX-BE-026-SV1.shared.themessagecenter.com>
Message-ID: <559C3CA2.7020708@msapiro.net>

On 07/07/2015 12:41 PM, Sibi John wrote:
> None whatsoever !! which is what boggles my mind !

In reply to:
> -----Original Message-----
> From: Mailman-Users On Behalf Of Mark Sapiro
> Sent: July 07, 2015 2:40 PM
> To: mailman-users at python.org
> Subject: Re: [Mailman-Users] Header filtering regex issue
> 
> On 07/07/2015 04:43 AM, Sibi John wrote:
>>
>> In my spam filter rules, this is the regex that I have and it matches perfectly.
>>
>> From: .+@(?!(xxx|yyy)\.com).+
>>
>>
>> For some reason, it discards all email and I cannot seem to figure out what I am doing wrong. Any suggestions ?
> 
> 
> The regexp should work. It might match some desired addresses like user at sub.xxx.com and not match some undesired ones like user at xxx.com.au, but it should work for the obvious cases.
> 
> Do you have any other header_filter_rules? If so, what are they?


Actually, there is a problem with your regexp. header_filter_rules
regexps are searched (re.search, not re.match) in multiline mode case
insensitively. This your regexp will match 'from:' in other places in
the headers. Try

^From: .+@(?!(xxx|yyy)\.com).+

to match only a true 'From: header.

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

From lac at openend.se  Wed Jul  8 01:05:33 2015
From: lac at openend.se (Laura Creighton)
Date: Wed, 08 Jul 2015 01:05:33 +0200
Subject: [Mailman-Users] merging 2 mailing lists
In-Reply-To: Message from "Bill Cole"
 <mailmanu-20150316@billmail.scconsult.com> of "Tue,
 07 Jul 2015 10:55:52 -0400."
 <46FCA49D-0A00-4F99-A5EF-0AFD85CB8F54@billmail.scconsult.com>
References: <201507061326.t66DQ2Rl020978@fido.openend.se>
 <E6D5C49F-1D98-4620-869C-04AABF45C374@billmail.scconsult.com>
 <201507071115.t67BFFUv019352@fido.openend.se><46FCA49D-0A00-4F99-A5EF-0AFD85CB8F54@billmail.scconsult.com>
Message-ID: <201507072305.t67N5XW7003435@fido.openend.se>

In a message of Tue, 07 Jul 2015 10:55:52 -0400, "Bill Cole" writes:
>> ??? There's  been major discussion about this on both lists, and
>> everybody thinks it's a wonderful idea.  Not a single objection.
>
>I am sorry. By way of explanation, it was late and I skimmed with tired 
>eyes, missing the key point that these are traditional discussion lists 
>rather than unidirectional broadcast lists.

Well, actually, I didn't make it clear.  The real situation is that
the recipe-list ( 2 of them) each have a reply-to:
setting for recipe-discussion (to translate from the Swedish to
the English).

So it's on the discuss side that all the agreement happened.

At any rate, the movement to a new list name went well -- and over
this evening the merging of archiving will happen.

Thank you everybody.

tack s? mycket!
Laura



From jebva at yahoo.com  Thu Jul  9 00:19:31 2015
From: jebva at yahoo.com (JB)
Date: Wed, 8 Jul 2015 15:19:31 -0700
Subject: [Mailman-Users] Migrate 2.x -> 3.x
In-Reply-To: <871tgkifw3.fsf@uwakimon.sk.tsukuba.ac.jp>
Message-ID: <1436393971.80041.YahooMailBasic@web122502.mail.ne1.yahoo.com>

Thanks for the feedback.  Please keep me updated as o what you find out.  I will be very interested in seeing how this proceeds.

--------------------------------------------
On Tue, 7/7/15, Stephen J. Turnbull <turnbull at sk.tsukuba.ac.jp> wrote:

 Subject: Re: [Mailman-Users] Migrate 2.x -> 3.x
 To: "JB" <jebva at yahoo.com>
 Cc: mailman-users at python.org
 Date: Tuesday, July 7, 2015, 3:30 AM
 
 JB via Mailman-Users
 writes:
 
  > I for one run
 a number of server with cPanel/WHM.? They are using
  > the latest 2.x version of MM now.? I was
 hoping that there would be
  > a way for
 cPanel/WHM to update to he 3.x tree and have all existing
  > list migrated to the new tree.
 
 Thanks for the suggestion.? I
 don't think it's going to be easy
 because cPanel uses custom mods to Mailman, and
 it's kind of out of
 scope for me/us
 (they're a commercial enterprise and undoubtedly
 would
 want to integrate Mailman 3 into next
 year's version of cPanal rather
 than
 last year's).
 
 I will
 talk to the cPanel guys about avoiding duplication of
 effort,
 but most likely they will do the
 work on their own schedule.
 
 Steve
 
 
 
 

From sm at noisynotes.com  Thu Jul  9 15:48:31 2015
From: sm at noisynotes.com (Steve Matzura)
Date: Thu, 09 Jul 2015 09:48:31 -0400
Subject: [Mailman-Users] Wrong perms?(fwd) Cron <mailman@patronus>
	/usr/lib/mailman/cron/nightly_gzip
Message-ID: <8iuspadn349csvdai1obqqmmu9f4nt3es8@4ax.com>

After solving my cron confusions, I get these messages daily:

Subject: Cron <mailman@{mynode}> /usr/lib/mailman/cron/checkdbs

...
IOError: [Errno 13] Permission denied:
'/var/lock/mailman/mailman.lock.{mynode}.{mydomain.com}.7552.0'

Subject: Cron <mailman@{mynode}> /usr/lib/mailman/cron/disabled

...
IOError: [Errno 13] Permission denied:
'/var/lock/mailman/mailman.lock.{mynode}.{mydomain.com}.7837.0'

When I looked for this file, it wasn't even there.

Subject: Cron <mailman@{mynode}> /usr/lib/mailman/cron/senddigests

...
IOError: [Errno 13] Permission denied:
'/var/lib/mailman/lists/mailman/config.pck'

This file is owned by root and is in the mailman group. 

check_perms reports no problems found.

From mark at msapiro.net  Thu Jul  9 17:00:38 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 09 Jul 2015 08:00:38 -0700
Subject: [Mailman-Users] Wrong perms?(fwd) Cron <mailman@patronus>
	/usr/lib/mailman/cron/nightly_gzip
In-Reply-To: <8iuspadn349csvdai1obqqmmu9f4nt3es8@4ax.com>
References: <8iuspadn349csvdai1obqqmmu9f4nt3es8@4ax.com>
Message-ID: <559E8C96.9090704@msapiro.net>

On 07/09/2015 06:48 AM, Steve Matzura wrote:
> After solving my cron confusions, I get these messages daily:
> 
> Subject: Cron <mailman@{mynode}> /usr/lib/mailman/cron/checkdbs
> 
> ...
> IOError: [Errno 13] Permission denied:
> '/var/lock/mailman/mailman.lock.{mynode}.{mydomain.com}.7552.0'
> 
> Subject: Cron <mailman@{mynode}> /usr/lib/mailman/cron/disabled
> 
> ...
> IOError: [Errno 13] Permission denied:
> '/var/lock/mailman/mailman.lock.{mynode}.{mydomain.com}.7837.0'
> 
> When I looked for this file, it wasn't even there.
> 
> Subject: Cron <mailman@{mynode}> /usr/lib/mailman/cron/senddigests
> 
> ...
> IOError: [Errno 13] Permission denied:
> '/var/lib/mailman/lists/mailman/config.pck'
> 
> This file is owned by root and is in the mailman group. 
> 
> check_perms reports no problems found.


In that case, these are almost certainly SELinux issues. Google things like

selinux logging
redhat disable selinux
redhat disable selinux without reboot

for information.

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

From bennetch at gmail.com  Fri Jul 10 03:02:16 2015
From: bennetch at gmail.com (Isaac Bennetch)
Date: Thu, 09 Jul 2015 21:02:16 -0400
Subject: [Mailman-Users] MM3/HyperKitty and importing Malman2 lists
Message-ID: <559F1998.3040606@gmail.com>

Hi,

Thanks for the good work bringing us Mailman3. I'm doing a new install,
which is intended to import data from a different server which had been
running Mailman2. I've used the mailman-bundler to install and have a
few questions. At this point, I'm still using the SQLite backend but
have hopes of using MySQL (I know MySQL better than PostgreSQL, and the
manual seems to imply that sticking with SQLite may not be ideal).

I'm currently attempting to import the old mbox into Hyperkitty[0],
which I think I've adapted in to

> ./bin/django-admin hyperkitty-import --pythonpath
eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/ -l testing at example.org
/home/mailman/old-list.mbox

Which doesn't say much (full output below[1]), but didn't fully work.
Out of approximately 18300 messages, only six are visible to me through
the "Mailing-List Archives" web page, and one of them has a very strange
date. It is the second message of the mbox, from 9 Apr 2001, but appears
in the web page with approximately the date/time of the import: 9 July
2015  7:27 p.m. Additionally, the remaining five messages are all the
most recent -- with the exception of the most recent message not
appearing at all.

Additionally, if I use the Search box to search for a word that I know
appears in (at least) one message, I get no results found.

I feel I'm missing something here, any idea what it could be?

Furthermore, I haven't found any substantial documentation on importing
a subscriber list from Mailman2; is there anything that will allow me to
transfer subscribers, their digest preference, and so on without
requiring them all to resubscribe manually?

Thanks in advance,
~isaac


0 - https://hyperkitty.readthedocs.org/en/latest/development.html

1 -
> Importing from mbox file /home/mailman/old-list.mbox to testing at example.org
> /No 'Message-Id' header in email from None about None
> -No 'Message-Id' header in email from None about None
> \No 'Message-Id' header in email from None about None
> |No 'Message-Id' header in email from None about None
> /No 'Message-Id' header in email from None about None
> -No 'Message-Id' header in email from None about None
> \No 'Message-Id' header in email from None about None
> |No 'Message-Id' header in email from None about None
> /No 'Message-Id' header in email from None about None
> -No 'Message-Id' header in email from None about None
> \No 'Message-Id' header in email from None about None
> |No 'Message-Id' header in email from None about None
> Computing thread structure
> Synchronizing properties with Mailman
> /usr/local/src/mailman-bundler/eggs/Django-1.7.8-py2.7.egg/django/db/models/fields/__init__.py:1282: RuntimeWarning: DateTimeField MailingList.created_at received a naive datetime (2015-07-04 14:30:22.803087) while time zone support is active.
>   RuntimeWarning)
> 
> WARNING /usr/local/src/mailman-bundler/eggs/Django-1.7.8-py2.7.egg/django/db/models/fields/__init__.py:1282: RuntimeWarning: DateTimeField MailingList.created_at received a naive datetime (2015-07-04 14:30:22.803087) while time zone support is active.
>   RuntimeWarning)
> 
> The full-text search index will be updated every minute. Run the 'manage.py runjob update_index' command to update it now.



From sjohn at mni-news.com  Thu Jul  9 21:26:11 2015
From: sjohn at mni-news.com (Sibi John)
Date: Thu, 9 Jul 2015 12:26:11 -0700
Subject: [Mailman-Users] Header filtering regex issue
In-Reply-To: <559C3CA2.7020708@msapiro.net>
References: <524CCF72D1F3634892B27FB204E8317EE22E695635@EX-BE-026-SV1.shared.themessagecenter.com>
 <559C2AF3.7090505@msapiro.net>
 <524CCF72D1F3634892B27FB204E8317EE22E69568A@EX-BE-026-SV1.shared.themessagecenter.com>
 <559C3CA2.7020708@msapiro.net>
Message-ID: <524CCF72D1F3634892B27FB204E8317EE22E6957D3@EX-BE-026-SV1.shared.themessagecenter.com>

Mark that was the issue !

You are the dude, behind the dude who is behind the other dude ! Super excited that this is working again :)

Again for people that did not see the solution,  the regex needed to be ^From: .+@(?!(xxx|yyy)\.com).+

-----Original Message-----
From: Mark Sapiro [mailto:mark at msapiro.net] 
Sent: July 07, 2015 3:55 PM
To: Sibi John
Cc: Mailman Users
Subject: Re: [Mailman-Users] Header filtering regex issue

On 07/07/2015 12:41 PM, Sibi John wrote:
> None whatsoever !! which is what boggles my mind !

In reply to:
> -----Original Message-----
> From: Mailman-Users On Behalf Of Mark Sapiro
> Sent: July 07, 2015 2:40 PM
> To: mailman-users at python.org
> Subject: Re: [Mailman-Users] Header filtering regex issue
> 
> On 07/07/2015 04:43 AM, Sibi John wrote:
>>
>> In my spam filter rules, this is the regex that I have and it matches perfectly.
>>
>> From: .+@(?!(xxx|yyy)\.com).+
>>
>>
>> For some reason, it discards all email and I cannot seem to figure out what I am doing wrong. Any suggestions ?
> 
> 
> The regexp should work. It might match some desired addresses like user at sub.xxx.com and not match some undesired ones like user at xxx.com.au, but it should work for the obvious cases.
> 
> Do you have any other header_filter_rules? If so, what are they?


Actually, there is a problem with your regexp. header_filter_rules regexps are searched (re.search, not re.match) in multiline mode case insensitively. This your regexp will match 'from:' in other places in the headers. Try

^From: .+@(?!(xxx|yyy)\.com).+

to match only a true 'From: header.

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

From stephen at xemacs.org  Fri Jul 10 16:59:45 2015
From: stephen at xemacs.org (Stephen J. Turnbull)
Date: Fri, 10 Jul 2015 23:59:45 +0900
Subject: [Mailman-Users]  MM3/HyperKitty and importing Malman2 lists
In-Reply-To: <559F1998.3040606@gmail.com>
References: <559F1998.3040606@gmail.com>
Message-ID: <87a8v4gise.fsf@uwakimon.sk.tsukuba.ac.jp>

Isaac Bennetch writes:

 > I feel I'm missing something here, any idea what it could be?

Dunno what's going with your import, but you probably won't find the
core HyperKitty devs here -- they are mostly on
mailman-developers at python.org.

Sorry I can't be of more direct help!

Steve

From sm at noisynotes.com  Sat Jul 11 02:11:28 2015
From: sm at noisynotes.com (Steve Matzura)
Date: Fri, 10 Jul 2015 20:11:28 -0400
Subject: [Mailman-Users] Wrong perms?(fwd) Cron <mailman@patronus>
	/usr/lib/mailman/cron/nightly_gzip
In-Reply-To: <559E8C96.9090704@msapiro.net>
References: <8iuspadn349csvdai1obqqmmu9f4nt3es8@4ax.com>
 <559E8C96.9090704@msapiro.net>
Message-ID: <lmn0qatksperric825ohiqfj83lp57m6a1@4ax.com>

On Thu, 09 Jul 2015 08:00:38 -0700, Mark wrote:

>On 07/09/2015 06:48 AM, Steve Matzura wrote:
>> After solving my cron confusions, I get these messages daily:
>> 
>> Subject: Cron <mailman@{mynode}> /usr/lib/mailman/cron/checkdbs
>> 
>> ...
>> IOError: [Errno 13] Permission denied:
>> '/var/lock/mailman/mailman.lock.{mynode}.{mydomain.com}.7552.0'
>> 
>> Subject: Cron <mailman@{mynode}> /usr/lib/mailman/cron/disabled
>> 
>> ...
>> IOError: [Errno 13] Permission denied:
>> '/var/lock/mailman/mailman.lock.{mynode}.{mydomain.com}.7837.0'
>> 
>> When I looked for this file, it wasn't even there.
>> 
>> Subject: Cron <mailman@{mynode}> /usr/lib/mailman/cron/senddigests
>> 
>> ...
>> IOError: [Errno 13] Permission denied:
>> '/var/lib/mailman/lists/mailman/config.pck'
>> 
>> This file is owned by root and is in the mailman group. 
>> 
>> check_perms reports no problems found.
>
>
>In that case, these are almost certainly SELinux issues. Google things like
>
>selinux logging
>redhat disable selinux
>redhat disable selinux without reboot
>
>for information.

I checked to see if SELinux is even enabled on this system. It isn't.
getenforce says disabled.

From mark at msapiro.net  Sat Jul 11 07:40:47 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 10 Jul 2015 22:40:47 -0700
Subject: [Mailman-Users] Wrong perms?(fwd) Cron <mailman@patronus>
 /usr/lib/mailman/cron/nightly_gzip
In-Reply-To: <lmn0qatksperric825ohiqfj83lp57m6a1@4ax.com>
References: <8iuspadn349csvdai1obqqmmu9f4nt3es8@4ax.com>
 <559E8C96.9090704@msapiro.net> <lmn0qatksperric825ohiqfj83lp57m6a1@4ax.com>
Message-ID: <55A0AC5F.8080704@msapiro.net>

On 7/10/15 5:11 PM, Steve Matzura wrote:
> On Thu, 09 Jul 2015 08:00:38 -0700, Mark wrote:
> 
>> On 07/09/2015 06:48 AM, Steve Matzura wrote:

>>> ...
>>> IOError: [Errno 13] Permission denied:
>>> '/var/lib/mailman/lists/mailman/config.pck'
>>>
>>> This file is owned by root and is in the mailman group. 
>>>
>>> check_perms reports no problems found.
>>
>>
>> In that case, these are almost certainly SELinux issues. Google things like
>>
>> selinux logging
>> redhat disable selinux
>> redhat disable selinux without reboot
>>
>> for information.
> 
> I checked to see if SELinux is even enabled on this system. It isn't.
> getenforce says disabled.


What happens if you do

sudo -u mailman file /var/lib/mailman/lists/mailman/config.pck

If that fails with permissions denied, you'll need to figure out why. If
it succeeds, you'll vave to figure out why you running as 'mailman' can
access the file, but cron running as 'mailman' can't.

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

From bonsaiviking at gmail.com  Fri Jul 10 15:41:08 2015
From: bonsaiviking at gmail.com (Daniel Miller)
Date: Fri, 10 Jul 2015 08:41:08 -0500
Subject: [Mailman-Users] Mapping member options from Mailman 2 to 3
Message-ID: <CABmvJnOz5rt8fKwrOHcYT3gUe5eC5Fzn8g0KHbqXirKuVyUoTQ@mail.gmail.com>

Hello,

I'm trying to migrate an existing list from Mailman 2 to Mailman 3, and I
wanted to know more about user preferences and member options. Here is the
mapping I have so far:

Mailman 2: Mailman 3
realname: {address, user}.display_name
password: user.password
language: preferences.preferred_language
delivery.status: preferences.delivery_status
delivery.delivery: prefererences.delivery_mode
noremind: ???
nodupes: ~preferences.receive_list_copy
notmetoo: ~preferences.receive_own_postings
hide: preferences.hide_address
ack: preferences.acknowledge_posts
mod: ???
nomail: ???
nmtopics: ???
topics: ???

Do the missing (???) options have any corresponding attribute in Mailman 3,
and are these accessible through mailman.client?

I am particularly interested in the moderation flag, but any other
information you may have would be useful. I am not entirely clear on
whether an Address or Membership can exist without an associated User, and
if I copy our existing roster as address-only memberships whether our
subscribers will be able to update their preferences.

Thanks!
Dan

From robert-mailman at susmilch.com  Fri Jul 10 18:12:16 2015
From: robert-mailman at susmilch.com (Robert Susmilch)
Date: Fri, 10 Jul 2015 11:12:16 -0500
Subject: [Mailman-Users] Mailman list mail for server loops back to myself
Message-ID: <559FEEE0.2070706@susmilch.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hello Everyone,

I apologize in advance for anything I've overlooked, I'm not a postfix
expert. Additionally, my wife and I are returning to school after 10
years out of the system and now have much more grabbing at our time
with a little one. I am attempting to create a mailing list for a
group project of my wife, and now it's a personal battle.

I spent several hours last night Googling, and have tried to implement
several different "solutions."

I have "successfully" created a list with mailman, on CentOS 7 running
on a VPS. The server was setup with ISPConfig 3. Additionally postfix
is setup to run multiple virtual domains for myself and friends.

I have updated the binary file locations of postmap and postalias,
however genalias does not create virtual-mailman.db, though it does
populate the virtual-mailman table. Postfix complains it does not find
the users until I manually run postmap on that file to create the
database.

Additionally I cannot get the web admin pages to work, as I get a 500
error. However I've read many comments that I need to disable suexec
and other options. I am running Wordpress as well as many other odds
and ends and would prefer to not screw those up. My main concern is
just to get the list working, webpage admin would just be icing.


Here is the maillog for a "loop"

Jul 10 10:55:00 server1 postfix/postfix-script[4275]: refreshing the
Postfix mail system
Jul 10 10:55:00 server1 postfix/master[1637]: reload -- version
2.10.1, configuration /etc/postfix
Jul 10 10:55:00 server1 postfix/anvil[3400]: statistics: max
connection rate 3/60s for (submission:96.2.151.202) at Jul 10 10:54:39
Jul 10 10:55:00 server1 postfix/anvil[3400]: statistics: max
connection count 1 for (submission:96.2.151.202) at Jul 10 10:53:42
Jul 10 10:55:00 server1 postfix/anvil[3400]: statistics: max message
rate 3/60s for (submission:96.2.151.202) at Jul 10 10:54:40
Jul 10 10:55:00 server1 postfix/anvil[3400]: statistics: max recipient
rate 3/60s for (submission:96.2.151.202) at Jul 10 10:54:40
Jul 10 10:55:00 server1 postfix/anvil[3400]: statistics: max cache
size 1 at Jul 10 10:53:42
Jul 10 10:55:01 server1 dovecot: imap-login: Disconnected
(disconnected before auth was ready, waited 0 secs): user=<>, rip=::1,
lip=::1, secured
Jul 10 10:55:01 server1 postfix/postscreen[4319]: CONNECT from
[127.0.0.1]:37965 to [127.0.0.1]:25
Jul 10 10:55:01 server1 postfix/postscreen[4319]: WHITELISTED
[127.0.0.1]:37965
Jul 10 10:55:01 server1 dovecot: pop3-login: Disconnected (no auth
attempts in 0 secs): user=<>, rip=::1, lip=::1, secured
Jul 10 10:55:01 server1 postfix/smtpd[4324]: connect from
localhost[127.0.0.1]
Jul 10 10:55:01 server1 postfix/smtpd[4324]: lost connection after
CONNECT from localhost[127.0.0.1]
Jul 10 10:55:01 server1 postfix/smtpd[4324]: disconnect from
localhost[127.0.0.1]
Jul 10 10:55:15 server1 postfix/submission/smtpd[3399]: disconnect
from unknown[96.2.151.202]
Jul 10 10:55:16 server1 postfix/submission/smtpd[4534]: warning:
hostname host-202-151-2-96-static.midco.net does not resolve to
address 96.2.151.202: Name or service not known
Jul 10 10:55:16 server1 postfix/submission/smtpd[4534]: connect from
unknown[96.2.151.202]
Jul 10 10:55:16 server1 postfix/submission/smtpd[4534]: Anonymous TLS
connection established from unknown[96.2.151.202]: TLSv1.2 with cipher
ECDHE-RSA-AES256-SHA (256/256 bits)
Jul 10 10:55:16 server1 postfix/submission/smtpd[4534]: NOQUEUE:
filter: RCPT from unknown[96.2.151.202]: <robert at rootunlimited.com>:
Sender address triggers FILTER amavis:[127.0.0.1]:10026;
from=<robert at rootunlimited.com> to=<test1 at susmilch.com> proto=ESMTP
helo=<archer.susmilch.com>
Jul 10 10:55:16 server1 postfix/submission/smtpd[4534]: CE95B10269ED:
client=unknown[96.2.151.202], sasl_method=PLAIN,
sasl_username=robert at rootunlimited.com
Jul 10 10:55:17 server1 postfix/cleanup[4553]: CE95B10269ED:
message-id=<559FEAEF.8000202 at rootunlimited.com>
Jul 10 10:55:17 server1 postfix/qmgr[4279]: CE95B10269ED:
from=<robert at rootunlimited.com>, sizef7, nrcpt=1 (queue active)
Jul 10 10:55:17 server1 postfix/smtpd[4557]: connect from
unknown[127.0.0.1]
Jul 10 10:55:17 server1 postfix/smtpd[4557]: 246D610269EF:
client=unknown[127.0.0.1]
Jul 10 10:55:17 server1 postfix/cleanup[4553]: 246D610269EF:
message-id=<559FEAEF.8000202 at rootunlimited.com>
Jul 10 10:55:17 server1 postfix/smtpd[4557]: disconnect from
unknown[127.0.0.1]
Jul 10 10:55:17 server1 postfix/qmgr[4279]: 246D610269EF:
from=<robert at rootunlimited.com>, size90, nrcpt=1 (queue active)
Jul 10 10:55:17 server1 amavis[23237]: (23237-16) Passed CLEAN
{RelayedInternal}, ORIGINATING LOCAL [96.2.151.202]:46678
[96.2.151.202] <robert at rootunlimited.com> ->
<test1 at server1.susmilch.com>, Queue-ID: CE95B10269ED, Message-ID:
<559FEAEF.8000202 at rootunlimited.com>, mail_id: biCr3Qlg5n88, Hits: -,
size: 667, queued_as: 246D610269EF, dkim_new=mail:rootunlimited.com,
105 ms
Jul 10 10:55:17 server1 postfix/smtp[4556]: CE95B10269ED:
to=<test1 at server1.susmilch.com>, orig_to=<test1 at susmilch.com>,
relay7.0.0.1[127.0.0.1]:10026, delay=0.43, delays=0.31/0.01/0/0.11,
dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025):
250 2.0.0 Ok: queued as 246D610269EF)
Jul 10 10:55:17 server1 postfix/qmgr[4279]: CE95B10269ED: removed
Jul 10 10:55:17 server1 postfix/smtp[4558]: 246D610269EF:
to=<test1 at server1.susmilch.com>, relay=none, delay=0.03,
delays=0.01/0.02/0/0, dsn=5.4.6, status=bounced (mail for
server1.susmilch.com loops back to myself)
Jul 10 10:55:17 server1 postfix/cleanup[4553]: 2E25010269ED:
message-id=<20150710155517.2E25010269ED at server1.susmilch.com>
Jul 10 10:55:17 server1 postfix/bounce[4559]: 246D610269EF: sender
non-delivery notification: 2E25010269ED
Jul 10 10:55:17 server1 postfix/qmgr[4279]: 2E25010269ED: from=<>,
size773, nrcpt=1 (queue active)
Jul 10 10:55:17 server1 postfix/qmgr[4279]: 246D610269EF: removed
Jul 10 10:55:17 server1 postfix/submission/smtpd[4534]: disconnect
from unknown[96.2.151.202]
Jul 10 10:55:17 server1 dovecot: lda(robert at rootunlimited.com): sieve:
msgid=<20150710155517.2E25010269ED at server1.susmilch.com>:
MAILER-DAEMON at server1.susmilch.com stored mail into mailbox 'INBOX'
Jul 10 10:55:17 server1 postfix/pipe[4560]: 2E25010269ED:
to=<robert at rootunlimited.com>, relay=dovecot, delay=0.11,
delays=0.01/0.01/0/0.09, dsn=2.0.0, status=sent (delivered via dovecot
service)
Jul 10 10:55:17 server1 postfix/qmgr[4279]: 2E25010269ED: removed




mm_cfg.py

MAILMAN_SITE_LIST = 'mailman'
DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/'
PRIVATE_ARCHIVE_URL = '/cgi-bin/mailman/private'
IMAGE_LOGOS         = '/images/mailman/'
DEFAULT_EMAIL_HOST = 'server1.rootunlimited.com'
DEFAULT_URL_HOST   = 'server1.rootunlimited.com'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
DEFAULT_SERVER_LANGUAGE = 'en'
DEFAULT_SEND_REMINDERS = 0
MTA='Postfix'
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['susmilch.com']
POSTFIX_MAP_CMD = '/etc/mailman/virtual_to_transport.sh'




Output of postconf -d

2bounce_notice_recipient = postmaster
access_map_defer_code = 450
access_map_reject_code = 554
address_verify_cache_cleanup_interval = 12h
address_verify_default_transport = $default_transport
address_verify_local_transport = $local_transport
address_verify_map = btree:$data_directory/verify_cache
address_verify_negative_cache = yes
address_verify_negative_expire_time = 3d
address_verify_negative_refresh_time = 3h
address_verify_poll_count = ${stress?1}${stress:3}
address_verify_poll_delay = 3s
address_verify_positive_expire_time = 31d
address_verify_positive_refresh_time = 7d
address_verify_relay_transport = $relay_transport
address_verify_relayhost = $relayhost
address_verify_sender = $double_bounce_sender
address_verify_sender_dependent_default_transport_maps $sender_dependent_default_transport_maps
address_verify_sender_dependent_relayhost_maps $sender_dependent_relayhost_maps
address_verify_sender_ttl = 0s
address_verify_service_name = verify
address_verify_transport_maps = $transport_maps
address_verify_virtual_transport = $virtual_transport
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases, nis:mail.aliases
allow_mail_to_commands = alias, forward
allow_mail_to_files = alias, forward
allow_min_user = no
allow_percent_hack = yes
allow_untrusted_routing = no
alternate_config_directories always_add_missing_headers = no
always_bcc amavis_delivery_slot_cost = $default_delivery_slot_cost
amavis_delivery_slot_discount = $default_delivery_slot_discount
amavis_delivery_slot_loan = $default_delivery_slot_loan
amavis_destination_concurrency_failed_cohort_limit $default_destination_concurrency_failed_cohort_limit
amavis_destination_concurrency_limit $default_destination_concurrency_limit
amavis_destination_concurrency_negative_feedback $default_destination_concurrency_negative_feedback
amavis_destination_concurrency_positive_feedback $default_destination_concurrency_positive_feedback
amavis_destination_rate_delay = $default_destination_rate_delay
amavis_destination_recipient_limit = $default_destination_recipient_limi
t
amavis_extra_recipient_limit = $default_extra_recipient_limit
amavis_initial_destination_concurrency = $initial_destination_concurrenc
y
amavis_minimum_delivery_slots = $default_minimum_delivery_slots
amavis_recipient_limit = $default_recipient_limit
amavis_recipient_refill_delay = $default_recipient_refill_delay
amavis_recipient_refill_limit = $default_recipient_refill_limit
anvil_rate_time_unit = 60s
anvil_status_update_time = 600s
append_at_myorigin = yes
append_dot_mydomain = yes
application_event_drain_time = 100s
authorized_flush_users = static:anyone
authorized_mailq_users = static:anyone
authorized_submit_users = static:anyone
tlsproxy_tls_key_file = $smtpd_tls_key_file
tlsproxy_tls_loglevel = $smtpd_tls_loglevel
tlsproxy_tls_mandatory_ciphers = $smtpd_tls_mandatory_ciphers
tlsproxy_tls_mandatory_exclude_ciphers $smtpd_tls_mandatory_exclude_ciphers
tlsproxy_tls_mandatory_protocols = $smtpd_tls_mandatory_protocols
tlsproxy_tls_protocols = $smtpd_tls_protocols
tlsproxy_tls_req_ccert = $smtpd_tls_req_ccert
tlsproxy_tls_security_level = $smtpd_tls_security_level
tlsproxy_tls_session_cache_timeout = $smtpd_tls_session_cache_timeout
tlsproxy_use_tls = $smtpd_use_tls
tlsproxy_watchdog_timeout = 10s
trace_service_name = trace
transport_maps transport_retry_time = 60s
trigger_timeout = 10s
undisclosed_recipients_header unknown_address_reject_code = 450
unknown_address_tempfail_action = $reject_tempfail_action
unknown_client_reject_code = 450
unknown_helo_hostname_tempfail_action = $reject_tempfail_action
unknown_hostname_reject_code = 450
unknown_local_recipient_reject_code = 550
unknown_relay_recipient_reject_code = 550
unknown_virtual_alias_reject_code = 550
unknown_virtual_mailbox_reject_code = 550
unverified_recipient_defer_code = 450
unverified_recipient_reject_code = 450
unverified_recipient_reject_reason unverified_recipient_tempfail_action = $reject_tempfail_action
unverified_sender_defer_code = 450
unverified_sender_reject_code = 450
unverified_sender_reject_reason unverified_sender_tempfail_action = $reject_tempfail_action
verp_delimiter_filter = -=+
virtual_alias_domains = $virtual_alias_maps
virtual_alias_expansion_limit = 1000
virtual_alias_maps = $virtual_maps
virtual_alias_recursion_limit = 1000
virtual_delivery_slot_cost = $default_delivery_slot_cost
virtual_delivery_slot_discount = $default_delivery_slot_discount
virtual_delivery_slot_loan = $default_delivery_slot_loan
virtual_destination_concurrency_failed_cohort_limit $default_destination_concurrency_failed_cohort_limit
virtual_destination_concurrency_limit $default_destination_concurrency_limit
virtual_destination_concurrency_negative_feedback $default_destination_concurrency_negative_feedback
virtual_destination_concurrency_positive_feedback $default_destination_concurrency_positive_feedback
virtual_destination_rate_delay = $default_destination_rate_delay
virtual_destination_recipient_limit = $default_destination_recipient_lim
it
virtual_extra_recipient_limit = $default_extra_recipient_limit
virtual_gid_maps virtual_initial_destination_concurrency = $initial_destination_concurren
cy
virtual_mailbox_base virtual_mailbox_domains = $virtual_mailbox_maps
virtual_mailbox_limit = 51200000
virtual_mailbox_lock = fcntl, dotlock
virtual_mailbox_maps virtual_minimum_delivery_slots = $default_minimum_delivery_slots
virtual_minimum_uid = 100
virtual_recipient_limit = $default_recipient_limit
virtual_recipient_refill_delay = $default_recipient_refill_delay
virtual_recipient_refill_limit = $default_recipient_refill_limit
virtual_transport = virtual
virtual_uid_maps 
- -- 
Respectfully,

Robert Susmilch
=======The "gobbledygook" in this email is due to this email having been
"signed" with PGP (or the free GPG). If both parties (sender and
receiver) had PGP key's the entire email could be encrypted (rendered
secure and unreadable except by the key holders) for confidentiality
and security.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJVn+7gAAoJEJvhIiLnDQ8qONwP/RhgtCnxJ4TVi1tTLFZmPtBk
X0KEH55jcnp5c2sFLWRh/gC3gEQS6npL0e2X2WQIRZa4dtadLu8bwYhoWrvzC3QY
M2D6zO/0TN5TKHarXDCTYFks5ZcVcWkDyj3lW/MowPqDcHMCzJ2InXK95BSFef8n
8VrFMfiuv5rA7CmFkhC8VWwrKSMzJsDu3Cq+Rh0oj7enQ9l3UFn7x6sgfKlul5dp
hIwa9Lhkw4JwNy9N8Np7vM25UL0Kh6Zn6kaEVUuMeDNDeKcbyD0NZswYzBi8GqWG
VMJE7mTRuH93yA34IZJd2obv1PvNuq9nuR2RE3Xb0Wb/MsmdCG0Dq8DljNjGk9Wg
YhKLrOk5dVRKhfc8pEkTS7FlPElcu25JTqAF04e3NP95oiFiYaBp81SM01Ebm9KX
ja2oC99IBFBLEDhsx9q3fEtJ5Tu6bnAugJMBQhfkpDCoxdsPYW135RtZ3M3ClcLz
DbbVACmP0cYOzxXopNmepT4NZnuz/NxM/neXSH6z2SrEd8jGpNNrsLFUvAEynYPP
XMatbwPye6n4jtPRMtyB+GeW1PI+8gedWTF05FBDhU/wXuaBxBqGPFz8ujZ7fozM
Wa3sAV68SU6tvnTaOwcbSgEoUktjNZbL9CEvOC9sx4rVaC/9n/BBLec/+Iftl16K
WngV6F82NEBnC1DQnM6t
=4SpA
-----END PGP SIGNATURE-----

From mark at msapiro.net  Sat Jul 11 18:12:01 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 11 Jul 2015 09:12:01 -0700
Subject: [Mailman-Users] Mailman list mail for server loops back to
	myself
In-Reply-To: <559FEEE0.2070706@susmilch.com>
References: <559FEEE0.2070706@susmilch.com>
Message-ID: <55A14051.603@msapiro.net>

On 7/10/15 9:12 AM, Robert Susmilch wrote:
> 
> I have updated the binary file locations of postmap and postalias,
> however genalias does not create virtual-mailman.db, though it does
> populate the virtual-mailman table. Postfix complains it does not find
> the users until I manually run postmap on that file to create the
> database.


Because you apparently have at least partially followed
<http://wiki.list.org/x/10715238> which alters POSTFIX_MAP_CMD to point
to a script which doesn't do postmap on virtual-mailman.


> Additionally I cannot get the web admin pages to work, as I get a 500
> error. However I've read many comments that I need to disable suexec
> and other options. I am running Wordpress as well as many other odds
> and ends and would prefer to not screw those up. My main concern is
> just to get the list working, webpage admin would just be icing.


What's in the web server (Apache) error log?


> Here is the maillog for a "loop"
> 
...
> Jul 10 10:55:16 server1 postfix/submission/smtpd[4534]: connect from
> unknown[96.2.151.202]
> Jul 10 10:55:16 server1 postfix/submission/smtpd[4534]: Anonymous TLS
> connection established from unknown[96.2.151.202]: TLSv1.2 with cipher
> ECDHE-RSA-AES256-SHA (256/256 bits)
> Jul 10 10:55:16 server1 postfix/submission/smtpd[4534]: NOQUEUE:
> filter: RCPT from unknown[96.2.151.202]: <robert at rootunlimited.com>:
> Sender address triggers FILTER amavis:[127.0.0.1]:10026;
> from=<robert at rootunlimited.com> to=<test1 at susmilch.com> proto=ESMTP
> helo=<archer.susmilch.com>
> Jul 10 10:55:16 server1 postfix/submission/smtpd[4534]: CE95B10269ED:
> client=unknown[96.2.151.202], sasl_method=PLAIN,
> sasl_username=robert at rootunlimited.com
> Jul 10 10:55:17 server1 postfix/cleanup[4553]: CE95B10269ED:
> message-id=<559FEAEF.8000202 at rootunlimited.com>
> Jul 10 10:55:17 server1 postfix/qmgr[4279]: CE95B10269ED:
> from=<robert at rootunlimited.com>, sizef7, nrcpt=1 (queue active)

Your message got submitted.


> Jul 10 10:55:17 server1 postfix/smtpd[4557]: connect from
> unknown[127.0.0.1]
> Jul 10 10:55:17 server1 postfix/smtpd[4557]: 246D610269EF:
> client=unknown[127.0.0.1]
> Jul 10 10:55:17 server1 postfix/cleanup[4553]: 246D610269EF:
> message-id=<559FEAEF.8000202 at rootunlimited.com>
> Jul 10 10:55:17 server1 postfix/smtpd[4557]: disconnect from
> unknown[127.0.0.1]

And came back from amavis


> Jul 10 10:55:17 server1 postfix/qmgr[4279]: 246D610269EF:
> from=<robert at rootunlimited.com>, size90, nrcpt=1 (queue active)
> Jul 10 10:55:17 server1 amavis[23237]: (23237-16) Passed CLEAN
> {RelayedInternal}, ORIGINATING LOCAL [96.2.151.202]:46678
> [96.2.151.202] <robert at rootunlimited.com> ->
> <test1 at server1.susmilch.com>, Queue-ID: CE95B10269ED, Message-ID:
> <559FEAEF.8000202 at rootunlimited.com>, mail_id: biCr3Qlg5n88, Hits: -,
> size: 667, queued_as: 246D610269EF, dkim_new=mail:rootunlimited.com,
> 105 ms
> Jul 10 10:55:17 server1 postfix/smtp[4556]: CE95B10269ED:
> to=<test1 at server1.susmilch.com>, orig_to=<test1 at susmilch.com>,
> relay7.0.0.1[127.0.0.1]:10026, delay=0.43, delays=0.31/0.01/0/0.11,
> dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025):
> 250 2.0.0 Ok: queued as 246D610269EF)
> Jul 10 10:55:17 server1 postfix/qmgr[4279]: CE95B10269ED: removed

Relayed to localhost, why?


> Jul 10 10:55:17 server1 postfix/smtp[4558]: 246D610269EF:
> to=<test1 at server1.susmilch.com>, relay=none, delay=0.03,
> delays=0.01/0.02/0/0, dsn=5.4.6, status=bounced (mail for
> server1.susmilch.com loops back to myself)

and bounces. It should have been delivered above instead of relayed to
itself.


...
> mm_cfg.py
> 
> MAILMAN_SITE_LIST = 'mailman'
> DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/'
> PRIVATE_ARCHIVE_URL = '/cgi-bin/mailman/private'
> IMAGE_LOGOS         = '/images/mailman/'
> DEFAULT_EMAIL_HOST = 'server1.rootunlimited.com'
> DEFAULT_URL_HOST   = 'server1.rootunlimited.com'
> add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
> DEFAULT_SERVER_LANGUAGE = 'en'
> DEFAULT_SEND_REMINDERS = 0
> MTA='Postfix'
> POSTFIX_STYLE_VIRTUAL_DOMAINS = ['susmilch.com']

You probably want

add_virtualhost('???.susmilch.com', 'susmilch.com')

and likewise other virtual domains.


> POSTFIX_MAP_CMD = '/etc/mailman/virtual_to_transport.sh'

Presumably you are doing this because Dovecot is the default LDA in your
postfix. It should work if properly configured. It doesn't create
virtual-mailman.db because it doesn't use it. it uses transport_maps to
map list addresses to Postfix's local transport and that in turn uses
aliases to deliver to Mailman.


> Output of postconf -d


This says nothing about YOUR Postfix config. -d says output the
defaults. 'postconf -n' is what we want to see.


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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20150711/dd56ac9f/attachment-0001.sig>

From mark at msapiro.net  Sun Jul 12 06:14:02 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 11 Jul 2015 21:14:02 -0700
Subject: [Mailman-Users] Mapping member options from Mailman 2 to 3
In-Reply-To: <CABmvJnOz5rt8fKwrOHcYT3gUe5eC5Fzn8g0KHbqXirKuVyUoTQ@mail.gmail.com>
References: <CABmvJnOz5rt8fKwrOHcYT3gUe5eC5Fzn8g0KHbqXirKuVyUoTQ@mail.gmail.com>
Message-ID: <55A1E98A.1070903@msapiro.net>

On 7/10/15 6:41 AM, Daniel Miller wrote:
> 
> I'm trying to migrate an existing list from Mailman 2 to Mailman 3, and I
> wanted to know more about user preferences and member options. Here is the
> mapping I have so far:
> 
> Mailman 2: Mailman 3
> realname: {address, user}.display_name
> password: user.password
> language: preferences.preferred_language
> delivery.status: preferences.delivery_status
> delivery.delivery: prefererences.delivery_mode
> noremind: ???

Mailman 3 doesn't send password reminders so the list member option to
suppress them doesn't exist in MM 3


> nodupes: ~preferences.receive_list_copy
> notmetoo: ~preferences.receive_own_postings
> hide: preferences.hide_address
> ack: preferences.acknowledge_posts
> mod: ???

I'm sure there is a concept of member moderation in MM 3, but I don't
know offhand exactly how it is implemented.


> nomail: ???

This is the member options name for mlist.delivery_status[member]

> nmtopics: ???
> topics: ???

I don't think topics are implemented in MM3. I think there is a Google
Summer of Code student working on dynamic sublists which is a different
approach to topics.


> Do the missing (???) options have any corresponding attribute in Mailman 3,
> and are these accessible through mailman.client?
> 
> I am particularly interested in the moderation flag, but any other
> information you may have would be useful. I am not entirely clear on
> whether an Address or Membership can exist without an associated User, and
> if I copy our existing roster as address-only memberships whether our
> subscribers will be able to update their preferences.


These questions are better asked on mailman-developers at python.org.

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

From danil at smirnov.la  Sun Jul 12 12:03:47 2015
From: danil at smirnov.la (Danil Smirnov)
Date: Sun, 12 Jul 2015 13:03:47 +0300
Subject: [Mailman-Users] best configuration for usenet group relay
Message-ID: <CAMrrXboWsKH7z4GXMrrpbE8xu0gu17N3Y3y3gWrTjmH9afQ=Cw@mail.gmail.com>

Hi all!

I need an advice from people who have experience in Usenet group
gateway into the Mailman 2 mailing list (when this is a main purpose
of the mailling list).

AFAIK, there are no limitation on senders email in the Usenet. One can
put there any crap he wants. But I doubt that it's appropriate for
modern mail servers/services.

So we probably need to configure list as anonymous to prevent using
this fake emails in messages, but it would be great to somehow keep
users' identification strings.

What do you suggest?

Danil

From danil at smirnov.la  Sun Jul 12 17:05:21 2015
From: danil at smirnov.la (Danil Smirnov)
Date: Sun, 12 Jul 2015 18:05:21 +0300
Subject: [Mailman-Users] newsgroup->mailman moderation
Message-ID: <CAMrrXbqn1gGkuJFr0RYd=TZVi2RHMmtTe4Q5ZZucLtwVyWdXTQ@mail.gmail.com>

Hi Mark!

I've found your posting advising how to set all posts from Usenet
group to moderation:

https://mail.python.org/pipermail/mailman-users/2013-June/075346.html

When look into Moderate.py I've found another code than mentioned in the post:

---
    # Okay, so the sender wasn't specified explicitly by any of the non-member
    # moderation configuration variables.  Handle by way of generic non-member
    # action.
    assert 0 <= mlist.generic_nonmember_action <= 4
    if mlist.generic_nonmember_action == 0 or msgdata.get('fromusenet'):
        # Accept
        return
    elif mlist.generic_nonmember_action == 1:
        Hold.hold_for_approval(mlist, msg, msgdata, Hold.NonMemberPost)
    elif mlist.generic_nonmember_action == 2:
        do_reject(mlist)
    elif mlist.generic_nonmember_action == 3:
        do_discard(mlist, msg)
---

Is it correct to change the code in this way?

---
    # Okay, so the sender wasn't specified explicitly by any of the non-member
    # moderation configuration variables.  Handle by way of generic non-member
    # action.
    assert 0 <= mlist.generic_nonmember_action <= 4
    if mlist.generic_nonmember_action == 0:
        # Accept
        return
    elif mlist.generic_nonmember_action == 1 or msgdata.get('fromusenet'):
        Hold.hold_for_approval(mlist, msg, msgdata, Hold.NonMemberPost)
    elif mlist.generic_nonmember_action == 2:
        do_reject(mlist)
    elif mlist.generic_nonmember_action == 3:
        do_discard(mlist, msg)
---

TIA,
Danil

From mark at msapiro.net  Sun Jul 12 18:42:00 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 12 Jul 2015 09:42:00 -0700
Subject: [Mailman-Users] newsgroup->mailman moderation
In-Reply-To: <CAMrrXbqn1gGkuJFr0RYd=TZVi2RHMmtTe4Q5ZZucLtwVyWdXTQ@mail.gmail.com>
References: <CAMrrXbqn1gGkuJFr0RYd=TZVi2RHMmtTe4Q5ZZucLtwVyWdXTQ@mail.gmail.com>
Message-ID: <55A298D8.7080706@msapiro.net>

On 7/12/15 8:05 AM, Danil Smirnov wrote:
> Hi Mark!
> 
> I've found your posting advising how to set all posts from Usenet
> group to moderation:
> 
> https://mail.python.org/pipermail/mailman-users/2013-June/075346.html


The change suggested in that post was applied to the distributed code as
of Mailman 2.1.17. See <https://bugs.launchpad.net/mailman/+bug/1252575>.


> When look into Moderate.py I've found another code than mentioned in the post:
> 
> ---
>     # Okay, so the sender wasn't specified explicitly by any of the non-member
>     # moderation configuration variables.  Handle by way of generic non-member
>     # action.
>     assert 0 <= mlist.generic_nonmember_action <= 4
>     if mlist.generic_nonmember_action == 0 or msgdata.get('fromusenet'):
>         # Accept
>         return
>     elif mlist.generic_nonmember_action == 1:
>         Hold.hold_for_approval(mlist, msg, msgdata, Hold.NonMemberPost)
>     elif mlist.generic_nonmember_action == 2:
>         do_reject(mlist)
>     elif mlist.generic_nonmember_action == 3:
>         do_discard(mlist, msg)
> ---
> 
> Is it correct to change the code in this way?
> 
> ---
>     # Okay, so the sender wasn't specified explicitly by any of the non-member
>     # moderation configuration variables.  Handle by way of generic non-member
>     # action.
>     assert 0 <= mlist.generic_nonmember_action <= 4
>     if mlist.generic_nonmember_action == 0:
>         # Accept
>         return
>     elif mlist.generic_nonmember_action == 1 or msgdata.get('fromusenet'):
>         Hold.hold_for_approval(mlist, msg, msgdata, Hold.NonMemberPost)
>     elif mlist.generic_nonmember_action == 2:
>         do_reject(mlist)
>     elif mlist.generic_nonmember_action == 3:
>         do_discard(mlist, msg)
> ---


The change you suggest will 'hold' all non-member posts from usenet as
long as generic_nonmember_action is other than accept and the poster's
address is not in one of the *_these_nonmember filters.

If that's what you want, then the change looks correct.

On the other hand, you could just remove the fromusenet test and apply
generic_nonmember_action to all posts whether or not from Usenet. I.e.,
just change

    if mlist.generic_nonmember_action == 0 or msgdata.get('fromusenet'):

to

    if mlist.generic_nonmember_action == 0:


The difference is with your change if generic_nonmember_action is Reject
or Discard, posts from Usenet will still be held and not rejected or
discarded, but just removing the fromusenet test will allow
generic_nonmember_action to apply to all posts.

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

From mark at msapiro.net  Sun Jul 12 18:47:06 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 12 Jul 2015 09:47:06 -0700
Subject: [Mailman-Users] best configuration for usenet group relay
In-Reply-To: <CAMrrXboWsKH7z4GXMrrpbE8xu0gu17N3Y3y3gWrTjmH9afQ=Cw@mail.gmail.com>
References: <CAMrrXboWsKH7z4GXMrrpbE8xu0gu17N3Y3y3gWrTjmH9afQ=Cw@mail.gmail.com>
Message-ID: <55A29A0A.2050102@msapiro.net>

On 7/12/15 3:03 AM, Danil Smirnov wrote:
> 
> So we probably need to configure list as anonymous to prevent using
> this fake emails in messages, but it would be great to somehow keep
> users' identification strings.
> 
> What do you suggest?


You could use from_is_list rather than anonymous_list, but perhaps this
question is rendered moot by
<https://mail.python.org/pipermail/mailman-users/2015-July/079437.html>.

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

From danil at smirnov.la  Sun Jul 12 23:06:17 2015
From: danil at smirnov.la (Danil Smirnov)
Date: Mon, 13 Jul 2015 00:06:17 +0300
Subject: [Mailman-Users] newsgroup->mailman moderation
In-Reply-To: <55A298D8.7080706@msapiro.net>
References: <CAMrrXbqn1gGkuJFr0RYd=TZVi2RHMmtTe4Q5ZZucLtwVyWdXTQ@mail.gmail.com>
 <55A298D8.7080706@msapiro.net>
Message-ID: <CAMrrXbqsy8c1yeEFGQLN7tgnfu2-SyBpHK=ppXYqP436-DUhLw@mail.gmail.com>

2015-07-12 19:42 GMT+03:00 Mark Sapiro <mark at msapiro.net>:
> On the other hand, you could just remove the fromusenet test and apply
> generic_nonmember_action to all posts whether or not from Usenet. I.e.,
> just change
>
>     if mlist.generic_nonmember_action == 0 or msgdata.get('fromusenet'):
>
> to
>
>     if mlist.generic_nonmember_action == 0:

Mark, I've made this correction but posts from Usenet continue to be
posted to the list without any moderation.
generic_nonmember_action is set to 'Hold'.

Danil

From mark at msapiro.net  Sun Jul 12 23:54:19 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 12 Jul 2015 14:54:19 -0700
Subject: [Mailman-Users] newsgroup->mailman moderation
In-Reply-To: <CAMrrXbqsy8c1yeEFGQLN7tgnfu2-SyBpHK=ppXYqP436-DUhLw@mail.gmail.com>
References: <CAMrrXbqn1gGkuJFr0RYd=TZVi2RHMmtTe4Q5ZZucLtwVyWdXTQ@mail.gmail.com>
 <55A298D8.7080706@msapiro.net>
 <CAMrrXbqsy8c1yeEFGQLN7tgnfu2-SyBpHK=ppXYqP436-DUhLw@mail.gmail.com>
Message-ID: <BF6552BD-1556-4B1E-A36B-3802A89061A8@msapiro.net>

On July 12, 2015 2:06:17 PM PDT, Danil Smirnov <danil at smirnov.la> wrote:
>2015-07-12 19:42 GMT+03:00 Mark Sapiro <mark at msapiro.net>:
>> On the other hand, you could just remove the fromusenet test and
>apply
>> generic_nonmember_action to all posts whether or not from Usenet.
>I.e.,
>> just change
>>
>>     if mlist.generic_nonmember_action == 0 or
>msgdata.get('fromusenet'):
>>
>> to
>>
>>     if mlist.generic_nonmember_action == 0:
>
>Mark, I've made this correction but posts from Usenet continue to be
>posted to the list without any moderation.
>generic_nonmember_action is set to 'Hold'.
>
>Danil

Did you restart Mailman?

Are the posts from nonmembers?


-- 
Mark Sapiro <mark at msapiro.net>
Sent from my Android phone with K-9 Mail. [Unpaid endorsement]

From stephen at xemacs.org  Mon Jul 13 02:39:19 2015
From: stephen at xemacs.org (Stephen J. Turnbull)
Date: Mon, 13 Jul 2015 09:39:19 +0900
Subject: [Mailman-Users] Mapping member options from Mailman 2 to 3
In-Reply-To: <55A1E98A.1070903@msapiro.net>
References: <CABmvJnOz5rt8fKwrOHcYT3gUe5eC5Fzn8g0KHbqXirKuVyUoTQ@mail.gmail.com>
 <55A1E98A.1070903@msapiro.net>
Message-ID: <87380show8.fsf@uwakimon.sk.tsukuba.ac.jp>

Mark Sapiro writes:

 > > nmtopics: ???
 > > topics: ???
 > 
 > I don't think topics are implemented in MM3.

No.

 > I think there is a Google Summer of Code student working on dynamic
 > sublists which is a different approach to topics.

Yes.  Topics are system whose structure is controlled by the list
admin (owner) through the web, and whose "subsubscriptions" are
controlled by the subscriber, also through the web.  A dynamic sublist
("dlist" for short) as implemented by the Systers' fork of Mailman 2
is created by one user by sending mail to a special mailbox, and
subscribed to by other users in the same way.  Dlists in Mailman 3
will follow the same pattern at first but it should be easy to add a
Postorius interface to allow users to create and subscribe to new
dlists, and view a list of active dlists, thus providing a superset of
"topic" functionality.  The main thing missing that might be desired
by some list admins is the ability to limit creation of dlists to
designated individuals.  (Offhand, I can't think of an application
where I would consider this limitation justified, but I'm sure they
exist.  However, this could be emulated to a certain degree with a
system of regular lists and umbrella lists.)

 > These questions are better asked on mailman-developers at python.org.

+1


From noah-list at enabled.com  Mon Jul 13 02:58:00 2015
From: noah-list at enabled.com (Noah)
Date: Sun, 12 Jul 2015 17:58:00 -0700
Subject: [Mailman-Users] private and public archive directory permissions
Message-ID: <55A30D18.7070301@enabled.com>

Hi there,

I migrated to a new server and I am back again with permission issues.
I am running apache2 on an ubuntu 14.04 server.

is there a good tutorial out there that explains the best practices for 
ownership for the different directories and sub-directories

I run check_perms -f as root and some of the same directories still need 
correcting even after running 'check_perms -f' as root many times.

I have a list user and a mailman user and group that I moved over from 
my old server.   Apache2 is running as www-data .


I am using mbox is that matters.

here is some config:

/var/lib/mailman/archives $ ls -l
total 8.0K
drwxrws--x 110 mailman 4.0K Jul  4 22:44 private/
drwxrwsr-x   2 mailman 4.0K Jun  2  2012 public/


/etc/apache2/conf-enabled $ ls -l mailman.conf
lrwxrwxrwx 1 root 30 Jul 13 00:52 mailman.conf -> 
../conf-available/mailman.conf



/etc/apache2/conf-enabled $ cat ../conf-available/mailman.conf

Alias /pipermail/ /var/lib/mailman/archives/public/
Alias /images/mailman/ /usr/share/images/mailman/
ScriptAlias /mailman/ /usr/lib/cgi-bin/mailman/
<Directory /usr/lib/cgi-bin/mailman/>
      AllowOverride None
      Options ExecCGI
      AddHandler cgi-script .cgi
      Order allow,deny
      Allow from all
</Directory>
<Directory /var/lib/mailman/archives/public/>
      Options Indexes FollowSymlinks
      AllowOverride None
      Order allow,deny
      Allow from all
</Directory>
<Directory /usr/share/images/mailman/>
      AllowOverride None
      Order allow,deny
      Allow from all
</Directory>


Cheers,

Noah



From mark at msapiro.net  Mon Jul 13 03:54:16 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 12 Jul 2015 18:54:16 -0700
Subject: [Mailman-Users] private and public archive directory permissions
In-Reply-To: <55A30D18.7070301@enabled.com>
References: <55A30D18.7070301@enabled.com>
Message-ID: <55A31A48.2030107@msapiro.net>

On 7/12/15 5:58 PM, Noah wrote:
> 
> I migrated to a new server and I am back again with permission issues.
> I am running apache2 on an ubuntu 14.04 server.
> 
> is there a good tutorial out there that explains the best practices for
> ownership for the different directories and sub-directories


Everything should be in Mailman's group ('mailman' or '_mailman' or
maybe 'list' in your case) and all the directories and the cgi and mail
compiled wrappers should be SETGID.

See the FAQ at <http://wiki.list.org/x/4030645>.


> I run check_perms -f as root and some of the same directories still need
> correcting even after running 'check_perms -f' as root many times.


check_perms gets confused by symlinks. It checks and complains about the
group and permissions of the symlink itself which are really irrelevant.
When fixing, it actually fixes the target which is what you want, but
next time it will complain again because it is still looking at the
symlink. Bottom line is ignore the errors it reports about symlinks.


> I have a list user and a mailman user and group that I moved over from
> my old server.   Apache2 is running as www-data .


In your Debian/Ubuntu package, Mailman's user:group are list:list.


> I am using mbox is that matters.
> 
> here is some config:
> 
> /var/lib/mailman/archives $ ls -l
> total 8.0K
> drwxrws--x 110 mailman 4.0K Jul  4 22:44 private/
> drwxrwsr-x   2 mailman 4.0K Jun  2  2012 public/


Is 'mailman' the owner or group? Perhaps these came from another system,
but for the Ubuntu package if that's what you're using, group should be
'list'.


> /etc/apache2/conf-enabled $ ls -l mailman.conf
> lrwxrwxrwx 1 root 30 Jul 13 00:52 mailman.conf ->
> ../conf-available/mailman.conf
> 
> 
> 
> /etc/apache2/conf-enabled $ cat ../conf-available/mailman.conf
> 
> Alias /pipermail/ /var/lib/mailman/archives/public/
> Alias /images/mailman/ /usr/share/images/mailman/
> ScriptAlias /mailman/ /usr/lib/cgi-bin/mailman/
> <Directory /usr/lib/cgi-bin/mailman/>
>      AllowOverride None
>      Options ExecCGI
>      AddHandler cgi-script .cgi
>      Order allow,deny
>      Allow from all
> </Directory>
> <Directory /var/lib/mailman/archives/public/>
>      Options Indexes FollowSymlinks
>      AllowOverride None
>      Order allow,deny
>      Allow from all
> </Directory>
> <Directory /usr/share/images/mailman/>
>      AllowOverride None
>      Order allow,deny
>      Allow from all
> </Directory>


This looks OK.

What exactly is your problem? Is there actually something that doesn't
work? If so, what?

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

From noah-list at enabled.com  Mon Jul 13 05:43:52 2015
From: noah-list at enabled.com (Noah)
Date: Sun, 12 Jul 2015 20:43:52 -0700
Subject: [Mailman-Users] private and public archive directory permissions
In-Reply-To: <55A31A48.2030107@msapiro.net>
References: <55A30D18.7070301@enabled.com> <55A31A48.2030107@msapiro.net>
Message-ID: <55A333F8.1030208@enabled.com>

Hi Mark,

Thank you for supporting mailman all these years.

Here is the error

--- snip ----

[Mon Jul 13 03:29:36.036929 2015] [authz_core:error] [pid 739] [client 
<ip_addr>:64962] AH01630: client denied by server configuration: 
/var/lib/mailman/archives/public/<list>, referer: 
http://<domain>/mailman/admin/<list>

--- snip ---

I think I did what was suggested in the FAQ but still getting the above 
error when I attempt to go to the list's archive URL

/var/lib/mailman/archives $ ls -ld
drwxrwsr-x 4 list list 4096 Oct  2  2002 .

/var/lib/mailman/archives $ ls -l
total 8
drwxrws--- 110 list list 4096 Jul  4 22:44 private
drwxrwsr-x   2 list list 4096 Jun  2  2012 public

/var/lib/mailman/archives $ ls -l public/<list>
lrwxrwxrwx 1 root list 43 Mar  9  2014 public/<list> -> 
/var/lib/mailman/archives/private/<list>

/var/lib/mailman/archives/private $ ls -ld <list>*
drwxrwsr-x 97 list     list 16384 Jul  2 10:27 <list>
drwxrwsr-x  2 www-data list  4096 Nov  5  2007 <list>.mbox

-- qrunner is running as list ---

root      3847  0.0  0.1  11748  2172 pts/1    S+   03:36   0:00 grep 
qrunner
list      8075  0.0  0.5  55560 10348 ?        S    Jul12   0:12 
/usr/bin/python /var/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s
list      8076  0.0  0.5  56500 11932 ?        S    Jul12   0:12 
/usr/bin/python /var/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s
list      8077  0.0  0.5  55584 11116 ?        S    Jul12   0:13 
/usr/bin/python /var/lib/mailman/bin/qrunner --runner=CommandRunner:0:1 -s
list      8078  0.0  0.6  57212 12844 ?        S    Jul12   0:13 
/usr/bin/python /var/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s
list      8079  0.0  0.3  54872  7408 ?        S    Jul12   0:12 
/usr/bin/python /var/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s
list      8080  0.0  0.6  59656 13528 ?        S    Jul12   0:14 
/usr/bin/python /var/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s
list      8081  0.0  0.5  56600 12132 ?        S    Jul12   0:12 
/usr/bin/python /var/lib/mailman/bin/qrunner --runner=VirginRunner:0:1 -s
list      8082  0.0  0.4  54848  8980 ?        S    Jul12   0:00 
/usr/bin/python /var/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s


---- snip ---


Cheers,

Noah


On 7/12/15 6:54 PM, Mark Sapiro wrote:> On 7/12/15 5:58 PM, Noah wrote:
 >>
 >> I migrated to a new server and I am back again with permission issues.
 >> I am running apache2 on an ubuntu 14.04 server.
 >>
 >> is there a good tutorial out there that explains the best practices for
 >> ownership for the different directories and sub-directories
 >
 >
 > Everything should be in Mailman's group ('mailman' or '_mailman' or
 > maybe 'list' in your case) and all the directories and the cgi and mail
 > compiled wrappers should be SETGID.
 >
 > See the FAQ at <http://wiki.list.org/x/4030645>.
 >
 >
 >> I run check_perms -f as root and some of the same directories still need
 >> correcting even after running 'check_perms -f' as root many times.
 >
 >
 > check_perms gets confused by symlinks. It checks and complains about the
 > group and permissions of the symlink itself which are really irrelevant.
 > When fixing, it actually fixes the target which is what you want, but
 > next time it will complain again because it is still looking at the
 > symlink. Bottom line is ignore the errors it reports about symlinks.
 >
 >
 >> I have a list user and a mailman user and group that I moved over from
 >> my old server.   Apache2 is running as www-data .
 >
 >
 > In your Debian/Ubuntu package, Mailman's user:group are list:list.
 >
 >
 >> I am using mbox is that matters.
 >>
 >> here is some config:
 >>
 >> /var/lib/mailman/archives $ ls -l
 >> total 8.0K
 >> drwxrws--x 110 mailman 4.0K Jul  4 22:44 private/
 >> drwxrwsr-x   2 mailman 4.0K Jun  2  2012 public/
 >
 >
 > Is 'mailman' the owner or group? Perhaps these came from another system,
 > but for the Ubuntu package if that's what you're using, group should be
 > 'list'.
 >
 >
 >> /etc/apache2/conf-enabled $ ls -l mailman.conf
 >> lrwxrwxrwx 1 root 30 Jul 13 00:52 mailman.conf ->
 >> ../conf-available/mailman.conf
 >>
 >>
 >>
 >> /etc/apache2/conf-enabled $ cat ../conf-available/mailman.conf
 >>
 >> Alias /pipermail/ /var/lib/mailman/archives/public/
 >> Alias /images/mailman/ /usr/share/images/mailman/
 >> ScriptAlias /mailman/ /usr/lib/cgi-bin/mailman/
 >> <Directory /usr/lib/cgi-bin/mailman/>
 >>       AllowOverride None
 >>       Options ExecCGI
 >>       AddHandler cgi-script .cgi
 >>       Order allow,deny
 >>       Allow from all
 >> </Directory>
 >> <Directory /var/lib/mailman/archives/public/>
 >>       Options Indexes FollowSymlinks
 >>       AllowOverride None
 >>       Order allow,deny
 >>       Allow from all
 >> </Directory>
 >> <Directory /usr/share/images/mailman/>
 >>       AllowOverride None
 >>       Order allow,deny
 >>       Allow from all
 >> </Directory>
 >
 >
 > This looks OK.
 >
 > What exactly is your problem? Is there actually something that doesn't
 > work? If so, what?
 >


From mark at msapiro.net  Mon Jul 13 06:04:17 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 12 Jul 2015 21:04:17 -0700
Subject: [Mailman-Users] private and public archive directory permissions
In-Reply-To: <55A333F8.1030208@enabled.com>
References: <55A30D18.7070301@enabled.com> <55A31A48.2030107@msapiro.net>
 <55A333F8.1030208@enabled.com>
Message-ID: <55A338C1.1090706@msapiro.net>

On 7/12/15 8:43 PM, Noah wrote:
> 
> Here is the error
> 
> --- snip ----
> 
> [Mon Jul 13 03:29:36.036929 2015] [authz_core:error] [pid 739] [client
> <ip_addr>:64962] AH01630: client denied by server configuration:
> /var/lib/mailman/archives/public/<list>, referer:
> http://<domain>/mailman/admin/<list>
> 
> --- snip ---
...
>>> <Directory /var/lib/mailman/archives/public/>
>>>       Options Indexes FollowSymlinks
>>>       AllowOverride None
>>>       Order allow,deny
>>>       Allow from all
>>> </Directory> 
...

If this is Apache 2.4, you need

    Require all granted

instead of

    Order allow,deny
    Allow from all

In the Directory blocks.

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

From danil at smirnov.la  Mon Jul 13 07:53:39 2015
From: danil at smirnov.la (Danil Smirnov)
Date: Mon, 13 Jul 2015 08:53:39 +0300
Subject: [Mailman-Users] newsgroup->mailman moderation
In-Reply-To: <BF6552BD-1556-4B1E-A36B-3802A89061A8@msapiro.net>
References: <CAMrrXbqn1gGkuJFr0RYd=TZVi2RHMmtTe4Q5ZZucLtwVyWdXTQ@mail.gmail.com>
 <55A298D8.7080706@msapiro.net>
 <CAMrrXbqsy8c1yeEFGQLN7tgnfu2-SyBpHK=ppXYqP436-DUhLw@mail.gmail.com>
 <BF6552BD-1556-4B1E-A36B-3802A89061A8@msapiro.net>
Message-ID: <CAMrrXbqx9wn70YSDbukQRZdF9mb5Cd+h9ccB4oHTSBJz3jBd6Q@mail.gmail.com>

2015-07-13 0:54 GMT+03:00 Mark Sapiro <mark at msapiro.net>:
> Did you restart Mailman?

Oops, forgot it.

Thanks!

Danil

From noah-list at enabled.com  Mon Jul 13 08:53:17 2015
From: noah-list at enabled.com (Noah)
Date: Sun, 12 Jul 2015 23:53:17 -0700
Subject: [Mailman-Users] private and public archive directory permissions
In-Reply-To: <55A338C1.1090706@msapiro.net>
References: <55A30D18.7070301@enabled.com> <55A31A48.2030107@msapiro.net>
 <55A333F8.1030208@enabled.com> <55A338C1.1090706@msapiro.net>
Message-ID: <55A3605D.3020003@enabled.com>

Hi there Mark,

getting the following error now.  Still looks like a filesystem 
permissions thing.

--- snip ---

[Mon Jul 13 06:46:52.951120 2015] [core:error] [pid 7324] [client 
<ipaddr>:50359] AH00037: Symbolic link not allowed or link target not 
accessible: /var/lib/mailman/archives/public/<maillist_name>, referer: 
http://<hostname>/mailman/admin/<maillist_name>

--- snip ---

/etc/apache2 $ cat sites-enabled/<hostname>.conf
<VirtualHost *:80>
         ServerAdmin webmaster@<domain.com>
         ServerName <hostname>
         ServerAlias www.<hostname> w.<hostname>
         ServerAlias ww.<hostname> wwww.<hostname>

         DocumentRoot /var/www

	Redirect permanent /index.html http://<hostname>/mailman/listinfo/

         <Directory /var/lib/mailman/archives/>
             Options FollowSymLinks
             AllowOverride None
         </Directory>

	Alias /pipermail/ /var/lib/mailman/archives/public/
	Alias /images/mailman/ /usr/share/images/mailman/
	ScriptAlias /mailman/ /usr/lib/cgi-bin/mailman/

         RewriteEngine on
         RewriteCond %{REQUEST_METHOD} !^(GET|POST|HEAD)$
         RewriteRule .* - [F]

	ErrorLog /var/log/apache2/error.log

	# Possible values include: debug, info, notice, warn, error, crit,
	# alert, emerg.
	LogLevel warn

	CustomLog /var/log/apache2/access.log combined
	ServerSignature On

	<Directory "/usr/share/doc/">
              Options Indexes MultiViews FollowSymLinks
	     AllowOverride None
              Order deny,allow
              Deny from all
              Allow from 127.0.0.0/255.0.0.0 ::1/128
	</Directory>

</VirtualHost>


/etc/apache2 $ cat conf-enabled/mailman.conf

Alias /pipermail/ /var/lib/mailman/archives/public/
Alias /images/mailman/ /usr/share/images/mailman/
ScriptAlias /mailman/ /usr/lib/cgi-bin/mailman/
<Directory /usr/lib/cgi-bin/mailman/>
      AllowOverride None
      Options ExecCGI
      AddHandler cgi-script .cgi
      Require all granted
</Directory>
<Directory /var/lib/mailman/archives/public/>
      Options Indexes FollowSymlinks
      AllowOverride None
      Require all granted
</Directory>
<Directory /usr/share/images/mailman/>
      AllowOverride None
      Require all granted
</Directory>


Cheers,

Noah



On 7/12/15 9:04 PM, Mark Sapiro wrote:
> On 7/12/15 8:43 PM, Noah wrote:
>>
>> Here is the error
>>
>> --- snip ----
>>
>> [Mon Jul 13 03:29:36.036929 2015] [authz_core:error] [pid 739] [client
>> <ip_addr>:64962] AH01630: client denied by server configuration:
>> /var/lib/mailman/archives/public/<list>, referer:
>> http://<domain>/mailman/admin/<list>
>>
>> --- snip ---
> ...
>>>> <Directory /var/lib/mailman/archives/public/>
>>>>        Options Indexes FollowSymlinks
>>>>        AllowOverride None
>>>>        Order allow,deny
>>>>        Allow from all
>>>> </Directory>
> ...
>
> If this is Apache 2.4, you need
>
>      Require all granted
>
> instead of
>
>      Order allow,deny
>      Allow from all
>
> In the Directory blocks.
>

From noah-list at enabled.com  Mon Jul 13 09:28:54 2015
From: noah-list at enabled.com (Noah)
Date: Mon, 13 Jul 2015 00:28:54 -0700
Subject: [Mailman-Users] private and public archive directory
 permissions [solved]
In-Reply-To: <55A3605D.3020003@enabled.com>
References: <55A30D18.7070301@enabled.com> <55A31A48.2030107@msapiro.net>
 <55A333F8.1030208@enabled.com> <55A338C1.1090706@msapiro.net>
 <55A3605D.3020003@enabled.com>
Message-ID: <55A368B6.2040304@enabled.com>

Hi there,

Okay I needed to have www-data own the private directory.  THanks for 
all your assistance.

--- snip ---

  /var/lib/mailman/archives/private $ chown www-data .
  /var/lib/mailman/archives/private $ ls -ld
drwxrws--- 110 www-data list 4096 Jul  4 22:44 .

Cheers,

Noah



On 7/12/15 11:53 PM, Noah wrote:
> Hi there Mark,
>
> getting the following error now.  Still looks like a filesystem
> permissions thing.
>
> --- snip ---
>
> [Mon Jul 13 06:46:52.951120 2015] [core:error] [pid 7324] [client
> <ipaddr>:50359] AH00037: Symbolic link not allowed or link target not
> accessible: /var/lib/mailman/archives/public/<maillist_name>, referer:
> http://<hostname>/mailman/admin/<maillist_name>
>
> --- snip ---
>
> /etc/apache2 $ cat sites-enabled/<hostname>.conf
> <VirtualHost *:80>
>          ServerAdmin webmaster@<domain.com>
>          ServerName <hostname>
>          ServerAlias www.<hostname> w.<hostname>
>          ServerAlias ww.<hostname> wwww.<hostname>
>
>          DocumentRoot /var/www
>
>      Redirect permanent /index.html http://<hostname>/mailman/listinfo/
>
>          <Directory /var/lib/mailman/archives/>
>              Options FollowSymLinks
>              AllowOverride None
>          </Directory>
>
>      Alias /pipermail/ /var/lib/mailman/archives/public/
>      Alias /images/mailman/ /usr/share/images/mailman/
>      ScriptAlias /mailman/ /usr/lib/cgi-bin/mailman/
>
>          RewriteEngine on
>          RewriteCond %{REQUEST_METHOD} !^(GET|POST|HEAD)$
>          RewriteRule .* - [F]
>
>      ErrorLog /var/log/apache2/error.log
>
>      # Possible values include: debug, info, notice, warn, error, crit,
>      # alert, emerg.
>      LogLevel warn
>
>      CustomLog /var/log/apache2/access.log combined
>      ServerSignature On
>
>      <Directory "/usr/share/doc/">
>               Options Indexes MultiViews FollowSymLinks
>           AllowOverride None
>               Order deny,allow
>               Deny from all
>               Allow from 127.0.0.0/255.0.0.0 ::1/128
>      </Directory>
>
> </VirtualHost>
>
>
> /etc/apache2 $ cat conf-enabled/mailman.conf
>
> Alias /pipermail/ /var/lib/mailman/archives/public/
> Alias /images/mailman/ /usr/share/images/mailman/
> ScriptAlias /mailman/ /usr/lib/cgi-bin/mailman/
> <Directory /usr/lib/cgi-bin/mailman/>
>       AllowOverride None
>       Options ExecCGI
>       AddHandler cgi-script .cgi
>       Require all granted
> </Directory>
> <Directory /var/lib/mailman/archives/public/>
>       Options Indexes FollowSymlinks
>       AllowOverride None
>       Require all granted
> </Directory>
> <Directory /usr/share/images/mailman/>
>       AllowOverride None
>       Require all granted
> </Directory>
>
>
> Cheers,
>
> Noah
>
>
>
> On 7/12/15 9:04 PM, Mark Sapiro wrote:
>> On 7/12/15 8:43 PM, Noah wrote:
>>>
>>> Here is the error
>>>
>>> --- snip ----
>>>
>>> [Mon Jul 13 03:29:36.036929 2015] [authz_core:error] [pid 739] [client
>>> <ip_addr>:64962] AH01630: client denied by server configuration:
>>> /var/lib/mailman/archives/public/<list>, referer:
>>> http://<domain>/mailman/admin/<list>
>>>
>>> --- snip ---
>> ...
>>>>> <Directory /var/lib/mailman/archives/public/>
>>>>>        Options Indexes FollowSymlinks
>>>>>        AllowOverride None
>>>>>        Order allow,deny
>>>>>        Allow from all
>>>>> </Directory>
>> ...
>>
>> If this is Apache 2.4, you need
>>
>>      Require all granted
>>
>> instead of
>>
>>      Order allow,deny
>>      Allow from all
>>
>> In the Directory blocks.
>>
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at 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/noah-list%40enabled.com
>

From stephen at xemacs.org  Mon Jul 13 09:29:02 2015
From: stephen at xemacs.org (Stephen J. Turnbull)
Date: Mon, 13 Jul 2015 16:29:02 +0900
Subject: [Mailman-Users] private and public archive directory permissions
In-Reply-To: <55A3605D.3020003@enabled.com>
References: <55A30D18.7070301@enabled.com> <55A31A48.2030107@msapiro.net>
 <55A333F8.1030208@enabled.com> <55A338C1.1090706@msapiro.net>
 <55A3605D.3020003@enabled.com>
Message-ID: <87oajgfrcx.fsf@uwakimon.sk.tsukuba.ac.jp>

Noah writes:

 > [Mon Jul 13 06:46:52.951120 2015] [core:error] [pid 7324] [client 
 > <ipaddr>:50359] AH00037: Symbolic link not allowed or link target not 
 > accessible: /var/lib/mailman/archives/public/<maillist_name>, referer: 
 > http://<hostname>/mailman/admin/<maillist_name>

This is an Apache message, not a filesystem message.  I suspect you
need

         <Directory //mailman/admin/>
             Options FollowSymLinks
             AllowOverride None
         </Directory>

in your Apache config.


From stephen at xemacs.org  Mon Jul 13 10:40:23 2015
From: stephen at xemacs.org (Stephen J. Turnbull)
Date: Mon, 13 Jul 2015 17:40:23 +0900
Subject: [Mailman-Users] private and public archive directory permissions
In-Reply-To: <87oajgfrcx.fsf@uwakimon.sk.tsukuba.ac.jp>
References: <55A30D18.7070301@enabled.com> <55A31A48.2030107@msapiro.net>
 <55A333F8.1030208@enabled.com> <55A338C1.1090706@msapiro.net>
 <55A3605D.3020003@enabled.com>
 <87oajgfrcx.fsf@uwakimon.sk.tsukuba.ac.jp>
Message-ID: <87mvz0fo20.fsf@uwakimon.sk.tsukuba.ac.jp>

Stephen J. Turnbull writes:

 > I suspect you need
 > 
 >          <Directory //mailman/admin/>
 >              Options FollowSymLinks
 >              AllowOverride None
 >          </Directory>

Oops, that "//" in the Directory start tag should be a single "/".

Sorry!

From danil at smirnov.la  Mon Jul 13 12:16:48 2015
From: danil at smirnov.la (Danil Smirnov)
Date: Mon, 13 Jul 2015 13:16:48 +0300
Subject: [Mailman-Users] newsgroup->mailman moderation
In-Reply-To: <CAMrrXbqx9wn70YSDbukQRZdF9mb5Cd+h9ccB4oHTSBJz3jBd6Q@mail.gmail.com>
References: <CAMrrXbqn1gGkuJFr0RYd=TZVi2RHMmtTe4Q5ZZucLtwVyWdXTQ@mail.gmail.com>
 <55A298D8.7080706@msapiro.net>
 <CAMrrXbqsy8c1yeEFGQLN7tgnfu2-SyBpHK=ppXYqP436-DUhLw@mail.gmail.com>
 <BF6552BD-1556-4B1E-A36B-3802A89061A8@msapiro.net>
 <CAMrrXbqx9wn70YSDbukQRZdF9mb5Cd+h9ccB4oHTSBJz3jBd6Q@mail.gmail.com>
Message-ID: <CAMrrXbrwzSgj4P_BoD1dNCEvAO6hWV2-aJ8n7Danc+GE0zGrNw@mail.gmail.com>

Another question: how about acknowledges for users from the Usernet?
Will they get them after post will be gatewaying to the list?

From barry at python.org  Mon Jul 13 16:04:41 2015
From: barry at python.org (Barry Warsaw)
Date: Mon, 13 Jul 2015 10:04:41 -0400
Subject: [Mailman-Users] [Mailman-Developers] Mailman 3 status
In-Reply-To: <871tgchlq6.fsf@uwakimon.sk.tsukuba.ac.jp>
References: <871tgchlq6.fsf@uwakimon.sk.tsukuba.ac.jp>
Message-ID: <20150713100441.6608d622@anarchist.wooz.org>

[resend w/proper address]

On Jul 13, 2015, at 10:47 AM, Stephen J. Turnbull wrote:

>- Performance measurements.  There are theoretical reasons to believe
>  that under certain circumstances a "large" Mailman 3 under "heavy"
>  use *might* suffer bottlenecks, but we just don't know yet.

Note that the message delivery subsystem, while modernized and ported to
Python 3, is largely inherited from Mailman 2, which means that reliability
and performance *of message delivery* should be about the same.

Over in mailman-developers we've had some discussion about performance of the
REST server, which by default gets vended by Python 3's stdlib wsgiref module
and probably would be improved by a better wsgi application server such as
gunicorn.  Follow ups to -developers on that topic please.

>The information provided above is accurate to the best of my ability,
>but it has not been checked by the responsible developers.  It is
>provided in hope of may be of use to those considering installation of
>Mailman 3.  If you're still on the fence after reading this post,
>please do get more accurate information from the responsible
>developers on the Mailman Developers list.

You did good, Steve! :)

Cheers,
-Barry

From mark at msapiro.net  Mon Jul 13 16:09:53 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 13 Jul 2015 07:09:53 -0700
Subject: [Mailman-Users] private and public archive directory
 permissions [solved]
In-Reply-To: <55A368B6.2040304@enabled.com>
References: <55A30D18.7070301@enabled.com> <55A31A48.2030107@msapiro.net>
 <55A333F8.1030208@enabled.com> <55A338C1.1090706@msapiro.net>
 <55A3605D.3020003@enabled.com> <55A368B6.2040304@enabled.com>
Message-ID: <55A3C6B1.1090201@msapiro.net>

On 7/13/15 12:28 AM, Noah wrote:
> 
> Okay I needed to have www-data own the private directory.  THanks for
> all your assistance.


In a prior post at
<https://mail.python.org/pipermail/mailman-users/2015-July/079443.html>
you posted

> /var/lib/mailman/archives $ ls -l
> total 8.0K
> drwxrws--x 110 mailman 4.0K Jul  4 22:44 private/
> drwxrwsr-x   2 mailman 4.0K Jun  2  2012 public/


Did you subsequently remove o+x from /var/lib/mailman/archives/private?
The private directory should need to be owned by the web server only if
it is not world searchable.

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

From mark at msapiro.net  Mon Jul 13 16:23:46 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 13 Jul 2015 07:23:46 -0700
Subject: [Mailman-Users] newsgroup->mailman moderation
In-Reply-To: <CAMrrXbrwzSgj4P_BoD1dNCEvAO6hWV2-aJ8n7Danc+GE0zGrNw@mail.gmail.com>
References: <CAMrrXbqn1gGkuJFr0RYd=TZVi2RHMmtTe4Q5ZZucLtwVyWdXTQ@mail.gmail.com>
 <55A298D8.7080706@msapiro.net>
 <CAMrrXbqsy8c1yeEFGQLN7tgnfu2-SyBpHK=ppXYqP436-DUhLw@mail.gmail.com>
 <BF6552BD-1556-4B1E-A36B-3802A89061A8@msapiro.net>
 <CAMrrXbqx9wn70YSDbukQRZdF9mb5Cd+h9ccB4oHTSBJz3jBd6Q@mail.gmail.com>
 <CAMrrXbrwzSgj4P_BoD1dNCEvAO6hWV2-aJ8n7Danc+GE0zGrNw@mail.gmail.com>
Message-ID: <55A3C9F2.9030304@msapiro.net>

On 7/13/15 3:16 AM, Danil Smirnov wrote:
> Another question: how about acknowledges for users from the Usernet?
> Will they get them after post will be gatewaying to the list?


If a post from someone who is a member of the gated mail list is gated
from the Usenet group to the mail list, and the poster's "Receive
acknowledgement mail when you send mail to the list?" (ack) option is
Yes, an acknowledgement will be sent when the post is delivered to the
mail list.

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

From danil at smirnov.la  Mon Jul 13 16:36:18 2015
From: danil at smirnov.la (Danil Smirnov)
Date: Mon, 13 Jul 2015 17:36:18 +0300
Subject: [Mailman-Users] newsgroup->mailman moderation
In-Reply-To: <55A3C9F2.9030304@msapiro.net>
References: <CAMrrXbqn1gGkuJFr0RYd=TZVi2RHMmtTe4Q5ZZucLtwVyWdXTQ@mail.gmail.com>
 <55A298D8.7080706@msapiro.net>
 <CAMrrXbqsy8c1yeEFGQLN7tgnfu2-SyBpHK=ppXYqP436-DUhLw@mail.gmail.com>
 <BF6552BD-1556-4B1E-A36B-3802A89061A8@msapiro.net>
 <CAMrrXbqx9wn70YSDbukQRZdF9mb5Cd+h9ccB4oHTSBJz3jBd6Q@mail.gmail.com>
 <CAMrrXbrwzSgj4P_BoD1dNCEvAO6hWV2-aJ8n7Danc+GE0zGrNw@mail.gmail.com>
 <55A3C9F2.9030304@msapiro.net>
Message-ID: <CAMrrXbqioKTQO=xAExAtE5JxFykekkdAwMvKBaEdnVw+sLrnwA@mail.gmail.com>

2015-07-13 17:23 GMT+03:00 Mark Sapiro <mark at msapiro.net>:
> If a post from someone who is a member of the gated mail list is gated
> from the Usenet group to the mail list, and the poster's "Receive
> acknowledgement mail when you send mail to the list?" (ack) option is
> Yes, an acknowledgement will be sent when the post is delivered to the
> mail list.

It looks like I'm confused with this topic.

I'm afraid of the situation where people from Usenet become get some
notifications from the Mailman saying, for instance, that their
message is placed on hold for moderation or similar. This is very
undesirable situation (actual spamming of them) and I worry a lot
about it after correction in Moderate.py I made.

Danil

From googleersatz at oliverniebuhr.de  Mon Jul 13 16:42:08 2015
From: googleersatz at oliverniebuhr.de (Google Ersatz)
Date: Mon, 13 Jul 2015 16:42:08 +0200
Subject: [Mailman-Users] [Mailman-Developers] Mailman 3 status
In-Reply-To: <20150713100441.6608d622@anarchist.wooz.org>
References: <871tgchlq6.fsf@uwakimon.sk.tsukuba.ac.jp>
 <20150713100441.6608d622@anarchist.wooz.org>
Message-ID: <20150713144208.5984339.71151.2256@oliverniebuhr.de>



Send?from?a?Mobile?Device.?Encoding?Problems can?happen.
? Originalnachricht ?
Von: Barry Warsaw
Gesendet: Montag, 13. Juli 2015 16:06
Cc: Mailman Developers; Mailman Users
Betreff: Re: [Mailman-Users] [Mailman-Developers] Mailman 3 status

[resend w/proper address]

On Jul 13, 2015, at 10:47 AM, Stephen J. Turnbull wrote:

>- Performance measurements. There are theoretical reasons to believe
> that under certain circumstances a "large" Mailman 3 under "heavy"
> use *might* suffer bottlenecks, but we just don't know yet.

Note that the message delivery subsystem, while modernized and ported to
Python 3, is largely inherited from Mailman 2, which means that reliability
and performance *of message delivery* should be about the same.

Over in mailman-developers we've had some discussion about performance of the
REST server, which by default gets vended by Python 3's stdlib wsgiref module
and probably would be improved by a better wsgi application server such as
gunicorn. Follow ups to -developers on that topic please.

>The information provided above is accurate to the best of my ability,
>but it has not been checked by the responsible developers. It is
>provided in hope of may be of use to those considering installation of
>Mailman 3. If you're still on the fence after reading this post,
>please do get more accurate information from the responsible
>developers on the Mailman Developers list.

You did good, Steve! :)

Cheers,
-Barry
------------------------------------------------------
Mailman-Users mailing list Mailman-Users at 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/googleersatz%40oliverniebuhr.de

From mark at msapiro.net  Mon Jul 13 17:05:05 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 13 Jul 2015 08:05:05 -0700
Subject: [Mailman-Users] newsgroup->mailman moderation
In-Reply-To: <CAMrrXbqioKTQO=xAExAtE5JxFykekkdAwMvKBaEdnVw+sLrnwA@mail.gmail.com>
References: <CAMrrXbqn1gGkuJFr0RYd=TZVi2RHMmtTe4Q5ZZucLtwVyWdXTQ@mail.gmail.com>
 <55A298D8.7080706@msapiro.net>
 <CAMrrXbqsy8c1yeEFGQLN7tgnfu2-SyBpHK=ppXYqP436-DUhLw@mail.gmail.com>
 <BF6552BD-1556-4B1E-A36B-3802A89061A8@msapiro.net>
 <CAMrrXbqx9wn70YSDbukQRZdF9mb5Cd+h9ccB4oHTSBJz3jBd6Q@mail.gmail.com>
 <CAMrrXbrwzSgj4P_BoD1dNCEvAO6hWV2-aJ8n7Danc+GE0zGrNw@mail.gmail.com>
 <55A3C9F2.9030304@msapiro.net>
 <CAMrrXbqioKTQO=xAExAtE5JxFykekkdAwMvKBaEdnVw+sLrnwA@mail.gmail.com>
Message-ID: <55A3D3A1.2000801@msapiro.net>

On 7/13/15 7:36 AM, Danil Smirnov wrote:
> 2015-07-13 17:23 GMT+03:00 Mark Sapiro <mark at msapiro.net>:
>> If a post from someone who is a member of the gated mail list is gated
>> from the Usenet group to the mail list, and the poster's "Receive
>> acknowledgement mail when you send mail to the list?" (ack) option is
>> Yes, an acknowledgement will be sent when the post is delivered to the
>> mail list.
> 
> It looks like I'm confused with this topic.


Or I was confused ...


> I'm afraid of the situation where people from Usenet become get some
> notifications from the Mailman saying, for instance, that their
> message is placed on hold for moderation or similar. This is very
> undesirable situation (actual spamming of them) and I worry a lot
> about it after correction in Moderate.py I made.


Notices to the poster of held posts are not sent if the post is gated
from Usenet.

If a post gated from Usenet is rejected because it is from a non-member
in reject_these_nonmembers or with your change a non-member with
generic_nonmember_action = Reject or from a moderated member with
member_moderation action = Reject, a notice  will be sent. The moral
here is never Reject non-member posts, either Hold them or Discard them.

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

From noah-list at enabled.com  Mon Jul 13 17:19:53 2015
From: noah-list at enabled.com (Noah)
Date: Mon, 13 Jul 2015 08:19:53 -0700
Subject: [Mailman-Users] private and public archive directory
 permissions [solved]
In-Reply-To: <55A3C6B1.1090201@msapiro.net>
References: <55A30D18.7070301@enabled.com> <55A31A48.2030107@msapiro.net>
 <55A333F8.1030208@enabled.com> <55A338C1.1090706@msapiro.net>
 <55A3605D.3020003@enabled.com> <55A368B6.2040304@enabled.com>
 <55A3C6B1.1090201@msapiro.net>
Message-ID: <55A3D719.9050700@enabled.com>

Yes I did Mark - thanks.

$ ls -l /var/lib/mailman/archives
total 8
drwxrws--- 110 www-data list 4096 Jul  4 22:44 private
drwxrwsr-x   2 root     list 4096 Jun  2  2012 public



On 7/13/15 7:09 AM, Mark Sapiro wrote:
> On 7/13/15 12:28 AM, Noah wrote:
>>
>> Okay I needed to have www-data own the private directory.  THanks for
>> all your assistance.
>
>
> In a prior post at
> <https://mail.python.org/pipermail/mailman-users/2015-July/079443.html>
> you posted
>
>> /var/lib/mailman/archives $ ls -l
>> total 8.0K
>> drwxrws--x 110 mailman 4.0K Jul  4 22:44 private/
>> drwxrwsr-x   2 mailman 4.0K Jun  2  2012 public/
>
>
> Did you subsequently remove o+x from /var/lib/mailman/archives/private?
> The private directory should need to be owned by the web server only if
> it is not world searchable.
>

From lists at damorris.com  Wed Jul 15 02:12:30 2015
From: lists at damorris.com (Adam Morris)
Date: Wed, 15 Jul 2015 10:12:30 +1000
Subject: [Mailman-Users] implicit destination error.
Message-ID: <55A5A56E.7070700@damorris.com>

Hi all,

is there a way to set up mailman so if people send messages to one of my 
lists and put the address in the cc field it is accepted instead of me 
as owner having to approve the message?


-- 


Adam Morris

email:
adam at damorris.com


		


From mark at msapiro.net  Wed Jul 15 04:16:48 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 14 Jul 2015 19:16:48 -0700
Subject: [Mailman-Users] implicit destination error.
In-Reply-To: <55A5A56E.7070700@damorris.com>
References: <55A5A56E.7070700@damorris.com>
Message-ID: <55A5C290.3050306@msapiro.net>

On 7/14/15 5:12 PM, Adam Morris wrote:
> 
> is there a way to set up mailman so if people send messages to one of my
> lists and put the address in the cc field it is accepted instead of me
> as owner having to approve the message?


If the list address is in Cc:, the message will not be held for implicit
destination. It is a post with the list address not in From: or Cc:,
possibly a Bcc: or spam sent to Undisclosed recipients:; or ?? that is
held for implicit destination.

If you don't want this hold, set Privacy options... -> Recipient filters
-> require_explicit_destination to No.

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

From robert at susmilch.com  Thu Jul 16 01:48:26 2015
From: robert at susmilch.com (Robert Susmilch)
Date: Wed, 15 Jul 2015 18:48:26 -0500
Subject: [Mailman-Users] Mailman list mail for server loops back to
	myself
In-Reply-To: <55A14051.603@msapiro.net>
References: <559FEEE0.2070706@susmilch.com> <55A14051.603@msapiro.net>
Message-ID: <55A6F14A.3060406@susmilch.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Dear Mr. Sapiro,

I will attempt to answer best I can inline.

On 07/11/2015 11:12 AM, Mark Sapiro wrote:
> On 7/10/15 9:12 AM, Robert Susmilch wrote:
>> 
>> I have updated the binary file locations of postmap and
>> postalias, however genalias does not create virtual-mailman.db,
>> though it does populate the virtual-mailman table. Postfix
>> complains it does not find the users until I manually run postmap
>> on that file to create the database.
> 
> 
> Because you apparently have at least partially followed 
> <http://wiki.list.org/x/10715238> which alters POSTFIX_MAP_CMD to
> point to a script which doesn't do postmap on virtual-mailman.
> 
> 
>> Additionally I cannot get the web admin pages to work, as I get a
>> 500 error. However I've read many comments that I need to disable
>> suexec and other options. I am running Wordpress as well as many
>> other odds and ends and would prefer to not screw those up. My
>> main concern is just to get the list working, webpage admin would
>> just be icing.
> 
> 
> What's in the web server (Apache) error log?

I absolutely hate ISPConfig... it fights me at every turn. I'm also an
apache newbie and that doesn't help. I'd be happy to run a small list
for maybe a dozen people, I can manually add them to not fight with
apache right now.

> 
> 
>> Here is the maillog for a "loop"
>> 
> ...
>> Jul 10 10:55:16 server1 postfix/submission/smtpd[4534]: connect
>> from unknown[96.2.151.202] Jul 10 10:55:16 server1
>> postfix/submission/smtpd[4534]: Anonymous TLS connection
>> established from unknown[96.2.151.202]: TLSv1.2 with cipher 
>> ECDHE-RSA-AES256-SHA (256/256 bits) Jul 10 10:55:16 server1
>> postfix/submission/smtpd[4534]: NOQUEUE: filter: RCPT from
>> unknown[96.2.151.202]: <robert at rootunlimited.com>: Sender address
>> triggers FILTER amavis:[127.0.0.1]:10026; 
>> from=<robert at rootunlimited.com> to=<test1 at susmilch.com>
>> proto=ESMTP helo=<archer.susmilch.com> Jul 10 10:55:16 server1
>> postfix/submission/smtpd[4534]: CE95B10269ED: 
>> client=unknown[96.2.151.202], sasl_method=PLAIN, 
>> sasl_username=robert at rootunlimited.com Jul 10 10:55:17 server1
>> postfix/cleanup[4553]: CE95B10269ED: 
>> message-id=<559FEAEF.8000202 at rootunlimited.com> Jul 10 10:55:17
>> server1 postfix/qmgr[4279]: CE95B10269ED: 
>> from=<robert at rootunlimited.com>, sizef7, nrcpt=1 (queue active)
> 
> Your message got submitted.
> 
> 
>> Jul 10 10:55:17 server1 postfix/smtpd[4557]: connect from 
>> unknown[127.0.0.1] Jul 10 10:55:17 server1 postfix/smtpd[4557]:
>> 246D610269EF: client=unknown[127.0.0.1] Jul 10 10:55:17 server1
>> postfix/cleanup[4553]: 246D610269EF: 
>> message-id=<559FEAEF.8000202 at rootunlimited.com> Jul 10 10:55:17
>> server1 postfix/smtpd[4557]: disconnect from unknown[127.0.0.1]
> 
> And came back from amavis
> 
> 
>> Jul 10 10:55:17 server1 postfix/qmgr[4279]: 246D610269EF: 
>> from=<robert at rootunlimited.com>, size90, nrcpt=1 (queue active) 
>> Jul 10 10:55:17 server1 amavis[23237]: (23237-16) Passed CLEAN 
>> {RelayedInternal}, ORIGINATING LOCAL [96.2.151.202]:46678 
>> [96.2.151.202] <robert at rootunlimited.com> -> 
>> <test1 at server1.susmilch.com>, Queue-ID: CE95B10269ED,
>> Message-ID: <559FEAEF.8000202 at rootunlimited.com>, mail_id:
>> biCr3Qlg5n88, Hits: -, size: 667, queued_as: 246D610269EF,
>> dkim_new=mail:rootunlimited.com, 105 ms Jul 10 10:55:17 server1
>> postfix/smtp[4556]: CE95B10269ED: 
>> to=<test1 at server1.susmilch.com>, orig_to=<test1 at susmilch.com>, 
>> relay7.0.0.1[127.0.0.1]:10026, delay=0.43,
>> delays=0.31/0.01/0/0.11, dsn=2.0.0, status=sent (250 2.0.0 from
>> MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as
>> 246D610269EF) Jul 10 10:55:17 server1 postfix/qmgr[4279]:
>> CE95B10269ED: removed
> 
> Relayed to localhost, why?

I believe it is going for tagging as either internal or external which
then leads into the DKIM signatures. It's been a year or so since I
set it all up, and I should have kept better notes.

I have noticed that the submission email gets rewritten as
"test1 at server1.susmilch.com" and that can't be good.

> 
>> Jul 10 10:55:17 server1 postfix/smtp[4558]: 246D610269EF: 
>> to=<test1 at server1.susmilch.com>, relay=none, delay=0.03, 
>> delays=0.01/0.02/0/0, dsn=5.4.6, status=bounced (mail for 
>> server1.susmilch.com loops back to myself)
> 
> and bounces. It should have been delivered above instead of relayed
> to itself.
> 
> 
> ...
>> mm_cfg.py
>> 
>> MAILMAN_SITE_LIST = 'mailman' DEFAULT_URL_PATTERN =
>> 'http://%s/cgi-bin/mailman/' PRIVATE_ARCHIVE_URL =
>> '/cgi-bin/mailman/private' IMAGE_LOGOS         =
>> '/images/mailman/' DEFAULT_EMAIL_HOST =
>> 'server1.rootunlimited.com' DEFAULT_URL_HOST   =
>> 'server1.rootunlimited.com' add_virtualhost(DEFAULT_URL_HOST,
>> DEFAULT_EMAIL_HOST) DEFAULT_SERVER_LANGUAGE = 'en' 
>> DEFAULT_SEND_REMINDERS = 0 MTA='Postfix' 
>> POSTFIX_STYLE_VIRTUAL_DOMAINS = ['susmilch.com']
> 
> You probably want
> 
> add_virtualhost('???.susmilch.com', 'susmilch.com')
> 
> and likewise other virtual domains.

So that virtual domain should be already taken care of with
DEFAULT_EMAIL_HOST?

> 
> 
>> POSTFIX_MAP_CMD = '/etc/mailman/virtual_to_transport.sh'
> 
> Presumably you are doing this because Dovecot is the default LDA in
> your postfix. It should work if properly configured. It doesn't
> create virtual-mailman.db because it doesn't use it. it uses
> transport_maps to map list addresses to Postfix's local transport
> and that in turn uses aliases to deliver to Mailman.
> 

I was doing this because someone, somewhere, said to create this script.

> 
>> Output of postconf -d
> 
> 
> This says nothing about YOUR Postfix config. -d says output the 
> defaults. 'postconf -n' is what we want to see.
> 
Sorry I was tired and did the wrong command. D'oh.

[root at server1 log]# postconf -n
postconf: warning: /etc/postfix/master.cf: undefined parameter:
mua_client_restrictions
postconf: warning: /etc/postfix/master.cf: undefined parameter:
mua_client_restrictions
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
anvil_rate_time_unit = 60s
body_checks = regexp:/etc/postfix/body_checks
broken_sasl_auth_clients = yes
check_greylist = check_policy_service unix:postgrey/socket
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
data_directory = /var/lib/postfix
debug_peer_level = 2
debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
ddd $daemon_directory/$process_name $process_id & sleep 5
default_destination_concurrency_limit = 20
disable_vrfy_command = yes
dovecot_destination_recipient_limit = 1
header_checks = regexp:/etc/postfix/header_checks
html_directory = no
inet_interfaces = all
inet_protocols = ipv4
local_destination_concurrency_limit = 2
mail_owner = postfix
mailbox_size_limit = 8489271296
maildrop_destination_concurrency_limit = 1
maildrop_destination_recipient_limit = 1
mailq_path = /usr/bin/mailq.postfix
manpage_directory = /usr/share/man
message_size_limit = 209715200
mime_header_checks = regexp:/etc/postfix/mime_header_checks
mydestination = server1.rootunlimited.com, localhost,
localhost.localdomain
myhostname = server1.susmilch.com
mynetworks = 127.0.0.0/8 [::1]/128 188.166.17.164/32 192.249.60.160/32
107.191.103.120/32
nested_header_checks = regexp:/etc/postfix/nested_header_checks
newaliases_path = /usr/bin/newaliases.postfix
policy-spf_time_limit = 3600s
postscreen_access_list = permit_mynetworks,
cidr:/etc/postfix/postscreen_access.cidr
postscreen_bare_newline_action = enforce
postscreen_bare_newline_enable = yes
postscreen_bare_newline_ttl = 30d
postscreen_blacklist_action = drop
postscreen_dnsbl_action = enforce
postscreen_dnsbl_sites = zen.spamhaus.org*3 b.barracudacentral.org*2
bl.spameatingmonkey.net*2 dnsbl.ahbl.org*2 bl.spamcop.net
dnsbl.sorbs.net psbl.surriel.com bl.mailspike.net swl.spamhaus.org*-4
list.dnswl.org=127.[0..255].[0..255].0*-
2 list.dnswl.org=127.[0..255].[0..255].1*-3
list.dnswl.org=127.[0..255].[0..255].[2..255]*-4
postscreen_dnsbl_threshold = 3
postscreen_greet_action = enforce
postscreen_greet_wait = ${stress?5}${stress:15}s
postscreen_non_smtp_command_action = enforce
postscreen_non_smtp_command_enable = yes
postscreen_non_smtp_command_ttl = 30d
postscreen_pipelining_action = enforce
postscreen_pipelining_enable = yes
postscreen_pipelining_ttl = 30d
proxy_read_maps = $local_recipient_maps $mydestination
$virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps
$virtual_mailbox_domains $relay_recipient_maps $relay_domains
$canonical_maps $sender_canonical_maps $recipient_canon
ical_maps $relocated_maps $transport_maps $mynetworks
queue_directory = /var/spool/postfix
readme_directory = /usr/share/doc/postfix-2.10.1/README_FILES
recipient_delimiter = -
relay_domains = mysql:/etc/postfix/mysql-virtual_relaydomains.cf
relay_recipient_maps =
mysql:/etc/postfix/mysql-virtual_relayrecipientmaps.cf
relayhost =
sample_directory = /usr/share/doc/postfix-2.10.1/samples
sendmail_path = /usr/sbin/sendmail.postfix
setgid_group = postdrop
smtp_tls_loglevel = 1
smtp_tls_protocols = !SSLv2,!SSLv3
smtp_tls_security_level = may
smtpd_banner = $myhostname ESMTP $mail_name
smtpd_client_event_limit_exceptions = $mynetworks
smtpd_client_message_rate_limit = 100
smtpd_client_recipient_rate_limit = 15
smtpd_client_restrictions = check_client_access
mysql:/etc/postfix/mysql-virtual_client.cf, permit
smtpd_data_restrictions = reject_unauth_pipelining, permit
smtpd_delay_reject = yes
smtpd_error_sleep_time = 10s
smtpd_hard_error_limit = 20
smtpd_helo_required = yes
smtpd_recipient_restrictions = permit_mynetworks,
permit_sasl_authenticated, reject_unauth_destination,
reject_invalid_hostname, reject_unauth_pipelining,
reject_non_fqdn_sender, check_recipient_access
mysql:/etc/postfix/mysql-virtual_re
cipient.cf, check_sender_access hash:/etc/postfix/access_sender_hash,
check_client_access hash:/etc/postfix/white_list_hash,
reject_unknown_sender_domain, reject_non_fqdn_recipient,
reject_unknown_recipient_domain, check_helo_access hash
:/etc/postfix/helo_checks, check_policy_service
unix:private/policy-spf, permit
smtpd_restriction_classes = check_greylist
smtpd_sasl_auth_enable = yes
smtpd_sasl_authenticated_header = yes
smtpd_sasl_path = private/auth
smtpd_sasl_type = dovecot
smtpd_sender_restrictions = check_sender_access
regexp:/etc/postfix/tag_as_originating.re, permit_mynetworks,
permit_sasl_authenticated, permit_tls_clientcerts, check_sender_access
regexp:/etc/postfix/tag_as_foreign.re, check_sender_acce
ss mysql:/etc/postfix/mysql-virtual_sender.cf
smtpd_soft_error_limit = 1
smtpd_tls_cert_file = /etc/postfix/smtpd.cert
smtpd_tls_dh1024_param_file = /etc/postfix/dh_1024.pem
smtpd_tls_dh512_param_file = /etc/postfix/dh_512.pem
smtpd_tls_eecdh_grade = strong
smtpd_tls_key_file = /etc/postfix/smtpd.key
smtpd_tls_loglevel = 1
smtpd_tls_mandatory_protocols = !SSLv2,!SSLv3
smtpd_tls_protocols = !SSLv2,!SSLv3
smtpd_tls_security_level = may
smtpd_use_tls = yes
soft_bounce = no
tls_preempt_cipherlist = yes
transport_maps = hash:/var/lib/mailman/data/transport-mailman,
proxy:mysql:/etc/postfix/mysql-virtual_transports.cf
unknown_local_recipient_reject_code = 550
virtual_alias_domains =
virtual_alias_maps = hash:/etc/mailman/virtual-mailman,
proxy:mysql:/etc/postfix/mysql-virtual_forwardings.cf,
proxy:mysql:/etc/postfix/mysql-virtual_email2email.cf,
hash:/etc/postfix/psy2200
virtual_gid_maps = static:5000
virtual_mailbox_base = /var/vmail
virtual_mailbox_domains =
proxy:mysql:/etc/postfix/mysql-virtual_domains.cf
virtual_mailbox_limit = $message_size_limit
virtual_mailbox_maps = proxy:mysql:/etc/postfix/mysql-virtual_mailboxes.cf
virtual_transport = dovecot
virtual_uid_maps = static:5000


I'm unsure what more configuration you require. Amavisd.conf?
- -- 
Respectfully,

Robert Susmilch
===============
The "gobbledygook" in this email is due to this email having been
"signed" with PGP (or the free GPG). If both parties (sender and
receiver) had PGP key's the entire email could be encrypted (rendered
secure and unreadable except by the key holders) for confidentiality
and security.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJVpvFKAAoJEJvhIiLnDQ8qczoP/3U7XD0K3l0xkMwAGwF7KMOo
C+GRZ4DXymUFxxRvTMa/4aVBEpn1X7UjfMeWS3IpS6V/nbtNjBmpTVEsvytqfpYz
TG6aHq2oj9rZXHHBAAo8xby9NJGLT5G9mpq6YjBCPi9IQqGqvmAWNT6lPedrD3tW
VbIOOQlkuC5ZSAXkcZMgRA6l+PFZ03iQwouvHNfMPqSSL8OFyYIj69PizGshvfVf
yfA8NarlEv0FMZrf9lfXZ3xh1Tyfh1NFa6YByEYKmuxizSIlWh9kMYxliyy8cxL4
9EjoCgj+Q8G8icwU0//513el2N6ZJWt+8r0nh1TJICG8K+/w/srHAQKkGnW+yaSC
oP0kukTmBcfQOmYYidq+KulGRGqov9QaoWoBH1wLH2xJPAh80lrSRC6yTRFIEBXo
xxmol945IwfLhF7g/uXGV+I/cfZYFrdNU7gIxz2eFhiPmxwrZhQHmOVF7rf9TZgi
1bpHqfG2SBivixo8ePfyNhkkfLkNquCpPCULjNB89zrzC7MTzdJP9HUp1kduLnOr
2no8WCVou43UYVeUArooMljcCCDB8g333Cpd3ZrYwxxH9sbJNG0mM/lNBuDseDgT
tmxsSQ6+pZCYKSGnW9Skap6DlqPcCmyHroXRqRjAs/xgWIAN/g8spmnGgXQ/u1XP
Z9yz5bKx7UAE7O1xpbZo
=qZxx
-----END PGP SIGNATURE-----

From robert at susmilch.com  Thu Jul 16 02:33:04 2015
From: robert at susmilch.com (Robert Susmilch)
Date: Wed, 15 Jul 2015 19:33:04 -0500
Subject: [Mailman-Users] Mailman list mail for server loops back to
	myself
In-Reply-To: <55A14051.603@msapiro.net>
References: <559FEEE0.2070706@susmilch.com> <55A14051.603@msapiro.net>
Message-ID: <55A6FBC0.4020904@susmilch.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

By disabling the amavis filters in main.cf I get a successful delivery.

Jul 15 19:10:25 server1 postfix/submission/smtpd[26594]: warning:
hostname host-202-151-2-96-static.midco.net does not resolve to
address 96.2.151.202: Name or service not known
Jul 15 19:10:25 server1 postfix/submission/smtpd[26594]: connect from
unknown[96.2.151.202]
Jul 15 19:10:26 server1 postfix/submission/smtpd[26594]: Anonymous TLS
connection established from unknown[96.2.151.202]: TLSv1.2 with cipher
ECDHE-RSA-AES256-SHA (256/256 bits)
Jul 15 19:10:26 server1 postfix/submission/smtpd[26594]: 8AFA527C8D71:
client=unknown[96.2.151.202], sasl_method=PLAIN,
sasl_username=katherine at susmilch.com
Jul 15 19:10:26 server1 postfix/cleanup[26497]: 8AFA527C8D71:
message-id=<55A6F686.2040309 at susmilch.com>
Jul 15 19:10:26 server1 postfix/qmgr[26466]: 8AFA527C8D71:
from=<katherine at susmilch.com>, size=634, nrcpt=1 (queue active)
Jul 15 19:10:27 server1 postfix/local[26604]: 8AFA527C8D71:
to=<test1 at susmilch.com>, relay=local, delay=0.54,
delays=0.3/0.04/0/0.2, dsn=2.0.0, status=sent (delivered to command:
/usr/lib/mailman/mail/mailman post test1)
Jul 15 19:10:27 server1 postfix/qmgr[26466]: 8AFA527C8D71: removed
Jul 15 19:10:27 server1 postfix/submission/smtpd[26594]: disconnect
from unknown[96.2.151.202]
Jul 15 19:10:28 server1 dovecot: imap-login: Login:
user=<katherine at susmilch.com>, method=PLAIN, rip=96.2.151.202,
lip=192.249.60.160, mpid=26632, TLS, TLSv1.2 with cipher
ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)
Jul 15 19:10:29 server1 postfix/postscreen[26640]: CONNECT from
[127.0.0.1]:52202 to [127.0.0.1]:25
Jul 15 19:10:29 server1 postfix/postscreen[26640]: WHITELISTED
[127.0.0.1]:52202
Jul 15 19:10:29 server1 postfix/smtpd[26641]: connect from
localhost[127.0.0.1]
Jul 15 19:10:29 server1 postfix/smtpd[26641]: 4F1A32B8AF0B:
client=localhost[127.0.0.1]
Jul 15 19:10:29 server1 postfix/cleanup[26497]: 4F1A32B8AF0B:
message-id=<55A6F686.2040309 at susmilch.com>
Jul 15 19:10:29 server1 postfix/qmgr[26466]: 4F1A32B8AF0B:
from=<test1-bounces at susmilch.com>, size=1623, nrcpt=2 (queue active)
Jul 15 19:10:29 server1 postfix/smtpd[26641]: disconnect from
localhost[127.0.0.1]
Jul 15 19:10:29 server1 dovecot: lda(robert at rootunlimited.com): sieve:
msgid=<55A6F686.2040309 at susmilch.com>: katherine at susmilch.com stored
mail into mailbox 'INBOX'
Jul 15 19:10:29 server1 postfix/pipe[26644]: 4F1A32B8AF0B:
to=<robert at rootunlimited.com>, relay=dovecot, delay=0.23,
delays=0.05/0.03/0/0.14, dsn=2.0.0, status=sent (delivered via dovecot
service)
Jul 15 19:10:29 server1 dovecot: lda(katherine at susmilch.com): sieve:
msgid=<55A6F686.2040309 at susmilch.com>: katherine at susmilch.com stored
mail into mailbox 'INBOX'
Jul 15 19:10:29 server1 postfix/pipe[26532]: 4F1A32B8AF0B:
to=<katherine at susmilch.com>, relay=dovecot, delay=0.33,
delays=0.05/0.03/0/0.25, dsn=2.0.0, status=sent (delivered via dovecot
service)
Jul 15 19:10:29 server1 postfix/qmgr[26466]: 4F1A32B8AF0B: removed

By disabling content_filter = amavis:[127.0.0.1]:10024 it doesn't seem
to double up and rewrite the address to test1 at server1.susmilch.com.


- -- 
Respectfully,

Robert Susmilch
===============
The "gobbledygook" in this email is due to this email having been
"signed" with PGP (or the free GPG). If both parties (sender and
receiver) had PGP key's the entire email could be encrypted (rendered
secure and unreadable except by the key holders) for confidentiality
and security.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJVpvvAAAoJEJvhIiLnDQ8q6lkP/02n3xiYHd0gcKIHv20J/gdn
ochbYLQwx8YVk/Ly2dguKiu2NT0cAsgRQ4MDxFoy1hXcXbS6eWAqV30p33ydhSHJ
txXX+8K6CyEpEv+VL/tYogQmW89GpwIpt3qJCPXGMIUido+boHokokvtwNQ5/jaA
bsc4scfdO1qt4gt6W6wZ+cgBXY8ngZdrx5jdfrwdpimCT0rRcItfXj3qNNTMDiOc
zUfTo3lUOnd4eKxg9o/DQWxkrp5Ji+gG/kbucDGMh/79xGcoNSyhxktQ1wGmiFu0
bfaB7tLIdTWVRODl4hmp5J8nmldKI7vr2tBkrXeCQ84t2oFnGUuR5iKWuOruHdoS
4PQzyvcrecVcPOcxuq2L9AyTDZScqCifucZEYqMwlPiQb9aEKMSlL+AzyrDjwgf8
hQkXk/5y/nIzR1YoUNoPVsLPaUt2zXSHv6WZV1RWFmpT1txsckCRXnoqsJzSNFc+
VFm5NjALE3XRGQESR3c/rZFl7DCWfjjm7ZvmFNxHwfmK28l3L/VLBwNOdoJdkqwM
mVM4v6oTAJOezIrwSgKC7Ai3ZkzYP0W4o3/aPEACQTAVFx/XOyf49rXM2f3KXGGW
uG7OTNoSirBMFVJtmvAlAR5f9oPsNo5GKRgwLHrWXYcKz6dgas2n4uJ6r1yyLqwn
Lw9ynG/G9nEUkLtiBZVy
=9u/f
-----END PGP SIGNATURE-----

From mark at msapiro.net  Thu Jul 16 02:43:10 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 15 Jul 2015 17:43:10 -0700
Subject: [Mailman-Users] Mailman list mail for server loops back to
	myself
In-Reply-To: <55A6F14A.3060406@susmilch.com>
References: <559FEEE0.2070706@susmilch.com> <55A14051.603@msapiro.net>
 <55A6F14A.3060406@susmilch.com>
Message-ID: <55A6FE1E.9040206@msapiro.net>

On 7/15/15 4:48 PM, Robert Susmilch wrote:
> On 07/11/2015 11:12 AM, Mark Sapiro wrote:
>> On 7/10/15 9:12 AM, Robert Susmilch wrote:
> 
>>> Additionally I cannot get the web admin pages to work, as I get a
>>> 500 error. However I've read many comments that I need to disable
>>> suexec and other options. I am running Wordpress as well as many
>>> other odds and ends and would prefer to not screw those up. My
>>> main concern is just to get the list working, webpage admin would
>>> just be icing.
> 
> 
>> What's in the web server (Apache) error log?
> 
> I absolutely hate ISPConfig... it fights me at every turn. I'm also an
> apache newbie and that doesn't help. I'd be happy to run a small list
> for maybe a dozen people, I can manually add them to not fight with
> apache right now.


That doesn't answer my question?


...
>>> mm_cfg.py
>>>
>>> MAILMAN_SITE_LIST = 'mailman' DEFAULT_URL_PATTERN =
>>> 'http://%s/cgi-bin/mailman/' PRIVATE_ARCHIVE_URL =
>>> '/cgi-bin/mailman/private' IMAGE_LOGOS         =
>>> '/images/mailman/' DEFAULT_EMAIL_HOST =
>>> 'server1.rootunlimited.com' DEFAULT_URL_HOST   =
>>> 'server1.rootunlimited.com' add_virtualhost(DEFAULT_URL_HOST,
>>> DEFAULT_EMAIL_HOST) DEFAULT_SERVER_LANGUAGE = 'en' 
>>> DEFAULT_SEND_REMINDERS = 0 MTA='Postfix' 
>>> POSTFIX_STYLE_VIRTUAL_DOMAINS = ['susmilch.com']
> 
>> You probably want
> 
>> add_virtualhost('???.susmilch.com', 'susmilch.com')
> 
>> and likewise other virtual domains.
> 
> So that virtual domain should be already taken care of with
> DEFAULT_EMAIL_HOST?


But DEFAULT_EMAIL_HOST is 'server1.rootunlimited.com' which is not
'susmilch.com'.


>>> POSTFIX_MAP_CMD = '/etc/mailman/virtual_to_transport.sh'
> 
>> Presumably you are doing this because Dovecot is the default LDA in
>> your postfix. It should work if properly configured. It doesn't
>> create virtual-mailman.db because it doesn't use it. it uses
>> transport_maps to map list addresses to Postfix's local transport
>> and that in turn uses aliases to deliver to Mailman.
> 
> 
> I was doing this because someone, somewhere, said to create this script.


OK, we'll go with it it the remarks below.


> [root at server1 log]# postconf -n
> ...
> alias_maps = hash:/etc/aliases

Here you need to add hash:/etc/mailman/aliases, i.e.,

alias_maps = hash:/etc/aliases hash:/etc/mailman/aliases


> virtual_alias_maps = hash:/etc/mailman/virtual-mailman,

Remove hash:/etc/mailman/virtual-mailman. It is not used in your case
which is why Mailman doesn't create virtual-mailman.db automatically

> proxy:mysql:/etc/postfix/mysql-virtual_forwardings.cf,
> proxy:mysql:/etc/postfix/mysql-virtual_email2email.cf,
> hash:/etc/postfix/psy2200

...
> I'm unsure what more configuration you require. Amavisd.conf?


If you make the above changes to main.cf, i.e., add
hash:/etc/mailman/aliases to alias_maps and remove
hash:/etc/mailman/virtual-mailman from virtual_alias_maps and also keep
hash:/var/lib/mailman/data/transport-mailman in transport_maps, I think
Postfix will deliver to Mailman.

If you are interested in solving your web server 500 error, show me the
relevant apache error log stuff.

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20150715/7f47cad3/attachment-0001.sig>

From mark at msapiro.net  Thu Jul 16 02:52:02 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 15 Jul 2015 17:52:02 -0700
Subject: [Mailman-Users] Mailman list mail for server loops back to
	myself
In-Reply-To: <55A6FBC0.4020904@susmilch.com>
References: <559FEEE0.2070706@susmilch.com> <55A14051.603@msapiro.net>
 <55A6FBC0.4020904@susmilch.com>
Message-ID: <55A70032.1080302@msapiro.net>

On 7/15/15 5:33 PM, Robert Susmilch wrote:
> By disabling the amavis filters in main.cf I get a successful delivery.
...
> By disabling content_filter = amavis:[127.0.0.1]:10024 it doesn't seem
> to double up and rewrite the address to test1 at server1.susmilch.com.


OK. The rewriting definitely seems to be part of the issue, but there
are probably other ways to deal with that without disabling amavis, if
you want to do that.

The virtual_to_transport script could be modified to write the domain as
server1.susmilch.com for example.

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20150715/c94f5901/attachment.sig>

From robert at susmilch.com  Thu Jul 16 03:32:32 2015
From: robert at susmilch.com (Robert Susmilch)
Date: Wed, 15 Jul 2015 20:32:32 -0500
Subject: [Mailman-Users] Mailman list mail for server loops back to
	myself
In-Reply-To: <55A70032.1080302@msapiro.net>
References: <559FEEE0.2070706@susmilch.com> <55A14051.603@msapiro.net>
 <55A6FBC0.4020904@susmilch.com> <55A70032.1080302@msapiro.net>
Message-ID: <55A709B0.7070509@susmilch.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

So... here's where I'm at. I took your suggestions to heart and tried
them. Didn't work. I reinstalled mailman from rpm and started with a
fresh mm_cfg.py.

Didn't work.

I reapplied my old config and changed my hostnames from my old
business domain to susmilch.com. I left the virtual_to_transport.sh line
.

If I remove virtual-mailman from main.cf, it complains rejecting my
email with an unknown recipient.

I restore virtual-mailman and postfix is happy. However, if I don't
run postmap on that after genaliases with a new list, the database is
out of date (obviously since genaliases doesn't run it).

If I leave out the virtual_to_transport script and create a new list,
it will not create the transport-mailman database.

I have edited the virtual_to_transport.sh to run postmap on
virtual-mailman and it seems to work.

At this point it seems to work. I have created two new lists and can sen
d.

My concern is I thought not having a FQDN as myhostname in main.cf of
postfix was bad karma.

Thanks for you time, if you have any suggestions I'd love to hear them.

On 07/15/2015 07:52 PM, Mark Sapiro wrote:
> On 7/15/15 5:33 PM, Robert Susmilch wrote:
>> By disabling the amavis filters in main.cf I get a successful
>> delivery.
> ...
>> By disabling content_filter = amavis:[127.0.0.1]:10024 it doesn't
>> seem to double up and rewrite the address to
>> test1 at server1.susmilch.com.
> 
> 
> OK. The rewriting definitely seems to be part of the issue, but
> there are probably other ways to deal with that without disabling
> amavis, if you want to do that.
> 
> The virtual_to_transport script could be modified to write the
> domain as server1.susmilch.com for example.
> 
> 
> 
> ------------------------------------------------------ 
> Mailman-Users mailing list Mailman-Users at 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/robert%40susmilc
h.com
>
> 
- -- 
Respectfully,

Robert Susmilch
===============
The "gobbledygook" in this email is due to this email having been
"signed" with PGP (or the free GPG). If both parties (sender and
receiver) had PGP key's the entire email could be encrypted (rendered
secure and unreadable except by the key holders) for confidentiality
and security.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJVpwmwAAoJEJvhIiLnDQ8qtbkP/iHdnZj+dg9a0t5Q3Gt78dnx
Z6CfrEbkKDbFK7M6ym181IDPrK5yRHJDcdUdQFaIDuYUljWeV4MrYNM5fXUIrTEW
D7fFd0p/iVoDrwd5y88trFNasRi8Oxh5Pv8umhHn7oyq8JQg3qcd7MyDtkPi4sE9
FfBB+aF3IhUh3scSTYXiRhhgCtZ9/z1YIF5CCzDRTYFrKa68iRiv9GZqQcArlW0/
bHcXguhbgLqrQhAwzhhcmzRoLItV9SQnRdVYhGxP7z0ZeKNt5HKnxEnca7nPLOzN
UDWXLVnZh2p7vcC5MN/Cyycf2zO4OT0Br3Gk/T5DdNO5NwnKZbV6GMvL1dfxK4ub
ZpqOEc8kfjTYsnGISGc8pmziIogXPp8AwJRAEwMGblu8KpQFWLWc9kc0gxvpjSLe
+6rMyvD7S+OWR6Y8xoilgQXrn6hG/bRmvWWGIqhGYAUgosttWaQBxrNBdvtNPpgN
Au2rl/DI6Kuok+8/D5fpCPl8UFcZqjTcHRb68OdiToqNBgRwdq6k7t3PGInt2kc9
3AIEYgeo8nexgQVXD1eJRUsQr8G7xhbtRTYCpyd0WUlnqF8blq0ATezIFa10B9on
5dQ7B/ETGmwSw48ieKo5gaiq8Td/icdQCZVSf+9Us0q9mpdQGFQ4mkMQfDsJo2Of
ok4234iNsVDxEMtYWdXm
=iHnC
-----END PGP SIGNATURE-----

From dmiller at nmap.com  Thu Jul 16 20:42:04 2015
From: dmiller at nmap.com (Daniel Miller)
Date: Thu, 16 Jul 2015 13:42:04 -0500
Subject: [Mailman-Users] How to stop mail-bombers from abusing web subscribe
	page
Message-ID: <CABmvJnMj_MYpsh7aDB9r6Ve23vYY3c4p3VsccjEVeqfFXgqMMw@mail.gmail.com>

Hi all,

We have discovered "mail bomber" programs like "boom mail" abusing the web
"subscribe" feature of Mailman 2.1.15 to send hundreds of subscription
confirmation messages to addresses that then complain to us and report us
as spammers. Is there a canonical way to deal with this? The ones we see
look like this in our web logs:

104.154.46.32 nmap.org - [29/Jun/2015:15:03:03 +0000] "GET
/mailman/subscribe/announce?email=ALLCAPS.EMAIL at EXAMPLE.COM&fullname=&pw=123456789&pw-conf=123456789&language=en&digest=0&email-button=Subscribe
HTTP/1.1" 504 323 "http://ugbox.club/boommail_bachdev/" "Mozilla/5.0
(Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko"

We ended up using this config in Apache:

  <Location /mailman/subscribe>
    # Stop spammers from sending tons of GET requests to mail-bomb victims
with subscription confirmations
    <LimitExcept POST>
    Deny from All
    </LimitExcept>
    # Those spammers never set referer correctly, either
    RewriteEngine On
    RewriteCond %{HTTP_HOST}@@%{HTTP_REFERER} !^([^@]*)@@https?://\1/.*
    RewriteRule .* [NC,F]
  </Location>

We'd love to hear if there's a better way to do this.

Dan

From mark at msapiro.net  Thu Jul 16 21:19:29 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 16 Jul 2015 12:19:29 -0700
Subject: [Mailman-Users] How to stop mail-bombers from abusing web
 subscribe page
In-Reply-To: <CABmvJnMj_MYpsh7aDB9r6Ve23vYY3c4p3VsccjEVeqfFXgqMMw@mail.gmail.com>
References: <CABmvJnMj_MYpsh7aDB9r6Ve23vYY3c4p3VsccjEVeqfFXgqMMw@mail.gmail.com>
Message-ID: <55A803C1.4080503@msapiro.net>

On 7/16/15 11:42 AM, Daniel Miller wrote:
> Hi all,
> 
> We have discovered "mail bomber" programs like "boom mail" abusing the web
> "subscribe" feature of Mailman 2.1.15 to send hundreds of subscription
> confirmation messages to addresses that then complain to us and report us
> as spammers.
...
> We'd love to hear if there's a better way to do this.


Upgrade to Mailman 2.1.16 or later and enable the SUBSCRIBE_FORM_SECRET
feature.

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

From dmiller at nmap.com  Thu Jul 16 23:05:58 2015
From: dmiller at nmap.com (Daniel Miller)
Date: Thu, 16 Jul 2015 16:05:58 -0500
Subject: [Mailman-Users] How to stop mail-bombers from abusing web
 subscribe page
In-Reply-To: <55A803C1.4080503@msapiro.net>
References: <CABmvJnMj_MYpsh7aDB9r6Ve23vYY3c4p3VsccjEVeqfFXgqMMw@mail.gmail.com>
 <55A803C1.4080503@msapiro.net>
Message-ID: <CABmvJnObsXFnNWct-OQ9kAxvtWDVcJU_ULNnKPJWMAqnwk0USA@mail.gmail.com>

On Thu, Jul 16, 2015 at 2:19 PM, Mark Sapiro <mark at msapiro.net> wrote:

> On 7/16/15 11:42 AM, Daniel Miller wrote:
> > Hi all,
> >
> > We have discovered "mail bomber" programs like "boom mail" abusing the
> web
> > "subscribe" feature of Mailman 2.1.15 to send hundreds of subscription
> > confirmation messages to addresses that then complain to us and report us
> > as spammers.
> ...
> > We'd love to hear if there's a better way to do this.
>
>
> Upgrade to Mailman 2.1.16 or later and enable the SUBSCRIBE_FORM_SECRET
> feature.
>

Thanks, Mark! We'll look into this option.

Dan

From danil at smirnov.la  Fri Jul 17 11:13:03 2015
From: danil at smirnov.la (Danil Smirnov)
Date: Fri, 17 Jul 2015 12:13:03 +0300
Subject: [Mailman-Users] newsgroup->mailman moderation
In-Reply-To: <55A3D3A1.2000801@msapiro.net>
References: <CAMrrXbqn1gGkuJFr0RYd=TZVi2RHMmtTe4Q5ZZucLtwVyWdXTQ@mail.gmail.com>
 <55A298D8.7080706@msapiro.net>
 <CAMrrXbqsy8c1yeEFGQLN7tgnfu2-SyBpHK=ppXYqP436-DUhLw@mail.gmail.com>
 <BF6552BD-1556-4B1E-A36B-3802A89061A8@msapiro.net>
 <CAMrrXbqx9wn70YSDbukQRZdF9mb5Cd+h9ccB4oHTSBJz3jBd6Q@mail.gmail.com>
 <CAMrrXbrwzSgj4P_BoD1dNCEvAO6hWV2-aJ8n7Danc+GE0zGrNw@mail.gmail.com>
 <55A3C9F2.9030304@msapiro.net>
 <CAMrrXbqioKTQO=xAExAtE5JxFykekkdAwMvKBaEdnVw+sLrnwA@mail.gmail.com>
 <55A3D3A1.2000801@msapiro.net>
Message-ID: <CAMrrXbqRq4fcdoa0rf166_KYbv5bAhHZsXhgJ7GH-QAEJt_X3g@mail.gmail.com>

2015-07-13 18:05 GMT+03:00 Mark Sapiro <mark at msapiro.net>:
> member_moderation action = Reject, a notice  will be sent. The moral
> here is never Reject non-member posts, either Hold them or Discard them.

Got it, Mark!

To complete the topic, I would like also to add Mailman footers to
messages, gatewayed to the group.
(They are not added by default...)
Could you please point me to the lines of code doing this?

Thanks,
Danil

From mark at msapiro.net  Fri Jul 17 17:24:49 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 17 Jul 2015 08:24:49 -0700
Subject: [Mailman-Users] newsgroup->mailman moderation
In-Reply-To: <CAMrrXbqRq4fcdoa0rf166_KYbv5bAhHZsXhgJ7GH-QAEJt_X3g@mail.gmail.com>
References: <CAMrrXbqn1gGkuJFr0RYd=TZVi2RHMmtTe4Q5ZZucLtwVyWdXTQ@mail.gmail.com>
 <55A298D8.7080706@msapiro.net>
 <CAMrrXbqsy8c1yeEFGQLN7tgnfu2-SyBpHK=ppXYqP436-DUhLw@mail.gmail.com>
 <BF6552BD-1556-4B1E-A36B-3802A89061A8@msapiro.net>
 <CAMrrXbqx9wn70YSDbukQRZdF9mb5Cd+h9ccB4oHTSBJz3jBd6Q@mail.gmail.com>
 <CAMrrXbrwzSgj4P_BoD1dNCEvAO6hWV2-aJ8n7Danc+GE0zGrNw@mail.gmail.com>
 <55A3C9F2.9030304@msapiro.net>
 <CAMrrXbqioKTQO=xAExAtE5JxFykekkdAwMvKBaEdnVw+sLrnwA@mail.gmail.com>
 <55A3D3A1.2000801@msapiro.net>
 <CAMrrXbqRq4fcdoa0rf166_KYbv5bAhHZsXhgJ7GH-QAEJt_X3g@mail.gmail.com>
Message-ID: <55A91E41.4060603@msapiro.net>

On 7/17/15 2:13 AM, Danil Smirnov wrote:
> 
> To complete the topic, I would like also to add Mailman footers to
> messages, gatewayed to the group.
> (They are not added by default...)
> Could you please point me to the lines of code doing this?


Headers/Footers are added by Mailman/Handlers/Decorate.py.
Decorate.process is called by Mailman/Handlers/SPTPDirect.py to apply
the replacements to msg_header and msg_footer and add them to the
message. You would need to do something similar in
Mailman/Handlers/ToUsenet.py.

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

From robert at susmilch.com  Fri Jul 17 19:16:42 2015
From: robert at susmilch.com (Robert Susmilch)
Date: Fri, 17 Jul 2015 12:16:42 -0500
Subject: [Mailman-Users] Editing already created list web address
Message-ID: <55A9387A.6030901@susmilch.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Dear List,

Is there a place to edit an already created list's web address. I have
finally gotten the web server working, however I have created a
virtualhost at lists.susmilch.com instead of www.susmilch.com. When I
created an active list I used the www, and have since changed the
mm_cfg.py to reflect that. New lists refer me internally to the
correct addresses, but old lists keep refering to www every time I
click a link.

- -- 
Respectfully,

Robert Susmilch
===============
The "gobbledygook" in this email is due to this email having been
"signed" with PGP (or the free GPG). If both parties (sender and
receiver) had PGP key's the entire email could be encrypted (rendered
secure and unreadable except by the key holders) for confidentiality
and security.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIbBAEBCAAGBQJVqTh6AAoJEJvhIiLnDQ8q8oUP9iEtqmfEVZL5MjG1mbI6t7QY
4aR+sbE2OUyNpFGIU4DQl7uQkIhC3C16deokJ2QFUzlsyq2y/ybJO79IYHjejnGt
qVEIfYMLMHjv5Pb9J/j83ztMbCl2zdaBiDoeclZTtyWH4seVICi6+sq4Obc+Xe4n
dqjTVdHEt8N2iC0AW/WOh7DsDLw2MkIrizuYk+S0all4kZ4vGHEagNj7/h/Tyuwy
Ox7smmZuzy6t276uCxzqOv0xetL6fN9YF/RTkgg5XWRyS7LSUE3wtlnVMm/N2lPZ
sGYUkbyb8PpGoX7Ac5VQt2znEXDHV/QW8BvS88oSXBCfyfxkdOFLzlQPEAMgKk+1
iWnd9hid0uAq15c0nS6/CAQ+Z/ucp3BxR4CQZe45WyQFCvYdsywokX6XhV52aCPa
Jne/MJDb/5mg3e/ll+6T+evwqiypzupS51FRiMehsfoOUY9Tfey5pg8tSRur3FCj
Hr3aEqNb5zrNjzEiTgOsBrdzlj7D8ntKHU91gZ2CoCgBI8p8uc1pFNtsNBjYB2me
uqUzWCpTDKBNbumKFROaA8IMBVJIgvLtGR6NoNKC3DJSruS4BNtgMeJltNZoPAAV
krbsetdA+uYGjtLuAh/jrmtI72D1zzI//0/2TfJKz32Lb9yBsbXv1iM6Jw8bsePk
ArsQLgr1quqgS3NGP7I=
=rOy0
-----END PGP SIGNATURE-----

From mark at msapiro.net  Fri Jul 17 19:20:12 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 17 Jul 2015 10:20:12 -0700
Subject: [Mailman-Users] Editing already created list web address
In-Reply-To: <55A9387A.6030901@susmilch.com>
References: <55A9387A.6030901@susmilch.com>
Message-ID: <55A9394C.5090501@msapiro.net>

On 7/17/15 10:16 AM, Robert Susmilch wrote:
> 
> Is there a place to edit an already created list's web address. I have
> finally gotten the web server working, however I have created a
> virtualhost at lists.susmilch.com instead of www.susmilch.com. When I
> created an active list I used the www, and have since changed the
> mm_cfg.py to reflect that. New lists refer me internally to the
> correct addresses, but old lists keep refering to www every time I
> click a link.


See the FAQ at <http://wiki.list.org/x/4030616>.

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20150717/ce5273b5/attachment.sig>

From cmupythia at cmu.edu  Fri Jul 17 19:29:00 2015
From: cmupythia at cmu.edu (Gretchen R Beck)
Date: Fri, 17 Jul 2015 17:29:00 +0000
Subject: [Mailman-Users] Expiring mailing lists
Message-ID: <56DDB644A1AF6E4CB5CF6CB8B50FCDB4028A7947@PGH-MSGMB-03.andrew.ad.cmu.edu>

I noticed that a couple of sites lists include expiration dates for their mailman lists.

I'm interested in using such a feature on my site; is there a particular version where this is available, or is it customized site-by-site?  Any pointers to information on implementation? [Also, if this is the wrong list to ask this question, please point me to the right one]

Thanks!

Gretchen Beck
Carnegie Mellon

From mark at msapiro.net  Fri Jul 17 20:10:24 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 17 Jul 2015 11:10:24 -0700
Subject: [Mailman-Users] Expiring mailing lists
In-Reply-To: <56DDB644A1AF6E4CB5CF6CB8B50FCDB4028A7947@PGH-MSGMB-03.andrew.ad.cmu.edu>
References: <56DDB644A1AF6E4CB5CF6CB8B50FCDB4028A7947@PGH-MSGMB-03.andrew.ad.cmu.edu>
Message-ID: <55A94510.4080008@msapiro.net>

On 7/17/15 10:29 AM, Gretchen R Beck wrote:
> I noticed that a couple of sites lists include expiration dates for their mailman lists.


This is not a feature in GNU Mailman as distributed by the Mailman project.


> I'm interested in using such a feature on my site; is there a particular version where this is available, or is it customized site-by-site?


This is the first I've heard of this. I have no information about the
implementation.


>  Any pointers to information on implementation? [Also, if this is the wrong list to ask this question, please point me to the right one]


I would ask the admins of the site(s) where you've seen this.

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

From skip.montanaro at gmail.com  Fri Jul 17 19:34:30 2015
From: skip.montanaro at gmail.com (Skip Montanaro)
Date: Fri, 17 Jul 2015 12:34:30 -0500
Subject: [Mailman-Users] MM doesn't really forward me the full message
Message-ID: <CANc-5UwAGQu0TN3ahmSCETt0YQkEMTpwtuQUbiOceELGurAqNg@mail.gmail.com>

Sometimes when I see a bit of held spam, I ask Mailman to forward it to me
with the intention of pumping it into SpamBayes for training purposes.
(This is on mail.python.org, where we are running 2.1.something.)
Unfortunately, it doesn't properly forward the entire message to me. It's
one of those crappy forwards like you get from Gmail, where the message
body and three or four user-visible headers are embedded in the message:


?

Am I missing something? Is MM the culprit here or Gmail? Is there some way
to get MM to forward me the complete message (including all headers) as an
attachment?

Thx,

Skip Montanaro

From mark at msapiro.net  Sat Jul 18 16:18:10 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 18 Jul 2015 07:18:10 -0700
Subject: [Mailman-Users] MM doesn't really forward me the full message
In-Reply-To: <CANc-5UwAGQu0TN3ahmSCETt0YQkEMTpwtuQUbiOceELGurAqNg@mail.gmail.com>
References: <CANc-5UwAGQu0TN3ahmSCETt0YQkEMTpwtuQUbiOceELGurAqNg@mail.gmail.com>
Message-ID: <55AA6022.10404@msapiro.net>

On 7/17/15 10:34 AM, Skip Montanaro wrote:
> Sometimes when I see a bit of held spam, I ask Mailman to forward it to me
> with the intention of pumping it into SpamBayes for training purposes.
> (This is on mail.python.org, where we are running 2.1.something.)
> Unfortunately, it doesn't properly forward the entire message to me. It's
> one of those crappy forwards like you get from Gmail, where the message
> body and three or four user-visible headers are embedded in the message:


I suspect this is gmail. The message mailman sends is a small "Forward
of moderated message" message with the original message attached as a
message/rfc822 part. I think if you use gmail's "show original" feature
to see the raw message, you will see the original message is there in
its entirety. Also, I tested this with gmail and downloading the
attached message to a file gets the original intact.

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

From danil at smirnov.la  Sun Jul 19 11:17:24 2015
From: danil at smirnov.la (Danil Smirnov)
Date: Sun, 19 Jul 2015 12:17:24 +0300
Subject: [Mailman-Users] newsgroup->mailman moderation
In-Reply-To: <55A91E41.4060603@msapiro.net>
References: <CAMrrXbqn1gGkuJFr0RYd=TZVi2RHMmtTe4Q5ZZucLtwVyWdXTQ@mail.gmail.com>
 <55A298D8.7080706@msapiro.net>
 <CAMrrXbqsy8c1yeEFGQLN7tgnfu2-SyBpHK=ppXYqP436-DUhLw@mail.gmail.com>
 <BF6552BD-1556-4B1E-A36B-3802A89061A8@msapiro.net>
 <CAMrrXbqx9wn70YSDbukQRZdF9mb5Cd+h9ccB4oHTSBJz3jBd6Q@mail.gmail.com>
 <CAMrrXbrwzSgj4P_BoD1dNCEvAO6hWV2-aJ8n7Danc+GE0zGrNw@mail.gmail.com>
 <55A3C9F2.9030304@msapiro.net>
 <CAMrrXbqioKTQO=xAExAtE5JxFykekkdAwMvKBaEdnVw+sLrnwA@mail.gmail.com>
 <55A3D3A1.2000801@msapiro.net>
 <CAMrrXbqRq4fcdoa0rf166_KYbv5bAhHZsXhgJ7GH-QAEJt_X3g@mail.gmail.com>
 <55A91E41.4060603@msapiro.net>
Message-ID: <CAMrrXbpLGqQShmEPp6zLX8nhZs4Aq5hGmCibra8v4E6sbx_d7A@mail.gmail.com>

2015-07-17 18:24 GMT+03:00 Mark Sapiro <mark at msapiro.net>:
> Headers/Footers are added by Mailman/Handlers/Decorate.py.
> Decorate.process is called by Mailman/Handlers/SPTPDirect.py to apply
> the replacements to msg_header and msg_footer and add them to the
> message. You would need to do something similar in
> Mailman/Handlers/ToUsenet.py.

Yes, it was quite easy. Attaching the patch for
Mailman/Handlers/ToUsenet.py for version 2.1.20.

From mark at msapiro.net  Mon Jul 20 03:39:55 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 19 Jul 2015 18:39:55 -0700
Subject: [Mailman-Users] newsgroup->mailman moderation
In-Reply-To: <CAMrrXbpLGqQShmEPp6zLX8nhZs4Aq5hGmCibra8v4E6sbx_d7A@mail.gmail.com>
References: <CAMrrXbqn1gGkuJFr0RYd=TZVi2RHMmtTe4Q5ZZucLtwVyWdXTQ@mail.gmail.com>
 <55A298D8.7080706@msapiro.net>
 <CAMrrXbqsy8c1yeEFGQLN7tgnfu2-SyBpHK=ppXYqP436-DUhLw@mail.gmail.com>
 <BF6552BD-1556-4B1E-A36B-3802A89061A8@msapiro.net>
 <CAMrrXbqx9wn70YSDbukQRZdF9mb5Cd+h9ccB4oHTSBJz3jBd6Q@mail.gmail.com>
 <CAMrrXbrwzSgj4P_BoD1dNCEvAO6hWV2-aJ8n7Danc+GE0zGrNw@mail.gmail.com>
 <55A3C9F2.9030304@msapiro.net>
 <CAMrrXbqioKTQO=xAExAtE5JxFykekkdAwMvKBaEdnVw+sLrnwA@mail.gmail.com>
 <55A3D3A1.2000801@msapiro.net>
 <CAMrrXbqRq4fcdoa0rf166_KYbv5bAhHZsXhgJ7GH-QAEJt_X3g@mail.gmail.com>
 <55A91E41.4060603@msapiro.net>
 <CAMrrXbpLGqQShmEPp6zLX8nhZs4Aq5hGmCibra8v4E6sbx_d7A@mail.gmail.com>
Message-ID: <55AC516B.7090509@msapiro.net>

On 7/19/15 2:17 AM, Danil Smirnov wrote:
> 2015-07-17 18:24 GMT+03:00 Mark Sapiro <mark at msapiro.net>:
>> Headers/Footers are added by Mailman/Handlers/Decorate.py.
>> Decorate.process is called by Mailman/Handlers/SPTPDirect.py to apply
>> the replacements to msg_header and msg_footer and add them to the
>> message. You would need to do something similar in
>> Mailman/Handlers/ToUsenet.py.
> 
> Yes, it was quite easy. Attaching the patch for
> Mailman/Handlers/ToUsenet.py for version 2.1.20.


Your patch didn't make it through this list's content filtering which
accepts only text/plain, text/x-diff and application/pgp-signature
elementary MIME types.

A better way to deal with this for MM 2.1 is to create an issue at
<https://bugs.launchpad.net/mailman/+filebug> and attach your patch or a
merge proposal.

For MM 3 the process is similar except the tracker is at
<https://gitlab.com/mailman/mailman/issues>.

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

From my_list_address at yahoo.no  Mon Jul 20 12:18:15 2015
From: my_list_address at yahoo.no (MLA)
Date: Mon, 20 Jul 2015 12:18:15 +0200
Subject: [Mailman-Users] Disabling the digest feature
Message-ID: <55ACCAE7.6000502@yahoo.no>

I have a low volume mailing list and would like to remove the digest 
option, so what I've done is (via the Mailman administrative interface):

- in "Membership management"-"Membership list": disabled "Digest" from 
those members who had this enabled
- in "Digest option": set Edit_digest to NO to disable the digest 
feature entirely
- posted a message to the list to tell about the change and that current 
digest-receiving members have had their subscriptions changed to non-digest.

This is all I have to do, right?

But for testing purposes I subscribed to the list with a new address and 
noticed that in my user's administration page ("options" section) 
there's a choice for "set digest mode" for on/off. How can I remove this 
and any other trace of the digest option which I might have missed?
Thanks.


M.

From asseline at telecom-paristech.fr  Sun Jul 19 22:13:33 2015
From: asseline at telecom-paristech.fr (Dominique Asselineau)
Date: Sun, 19 Jul 2015 22:13:33 +0200
Subject: [Mailman-Users] problem with accented characters,
	converting HTML to plain text
Message-ID: <20150719201333.GA22495@telecom-paristech.fr>

Hello,

When a e-mail in text/html content-type is converted in to plain text,
the accented characters are not treated correctly.

in configuration file 
    /usr/lib/mailman/Mailman/Defaults.py 
the variable
    HTML_TO_PLAIN_TEXT_COMMAND = '/usr/bin/lynx -dump %(filename)s'
and this variable is not overwritten in /usr/lib/mailman/Mailman/mm_cfg.py

/usr/bin/lynx -dump runs correctly.

Have you an idea why the accented characters cause problem?

Thanks

Dominique

-- 
+--------------------------------o--------------------------------------------+
| P-mail:                        | E-mail:                                    |
|   TELECOM ParisTech - Dep. TSI |  Dominique.Asselineau at telecom-paristech.fr |
|   Dominique Asselineau         | Phone: (33/0) 1 45 81 78 91                |
|   46, rue Barrault             |   Fax: (33/0) 1 45 81 37 94                |
|   75634 PARIS Cedex 13         |                                            |
| France                         |                                            |
+--------------------------------o--------------------------------------------+

From mark at msapiro.net  Mon Jul 20 16:04:28 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 20 Jul 2015 07:04:28 -0700
Subject: [Mailman-Users] Disabling the digest feature
In-Reply-To: <55ACCAE7.6000502@yahoo.no>
References: <55ACCAE7.6000502@yahoo.no>
Message-ID: <55ACFFEC.5030106@msapiro.net>

On 7/20/15 3:18 AM, MLA wrote:
> I have a low volume mailing list and would like to remove the digest
> option, so what I've done is (via the Mailman administrative interface):
> 
> - in "Membership management"-"Membership list": disabled "Digest" from
> those members who had this enabled
> - in "Digest option": set Edit_digest to NO to disable the digest
> feature entirely


Do you mean digestable as in
Can list members choose to receive list traffic bunched in digests?
(Edit digestable)?


> - posted a message to the list to tell about the change and that current
> digest-receiving members have had their subscriptions changed to
> non-digest.
> 
> This is all I have to do, right?


Assuming you meant 'digestable', yes.


> But for testing purposes I subscribed to the list with a new address and
> noticed that in my user's administration page ("options" section)
> there's a choice for "set digest mode" for on/off. How can I remove this
> and any other trace of the digest option which I might have missed?


The setting is there, but it can't be set to Yes if digestable is No.

If you have sufficient access to the server, you can copy
/path/to/templates/en/options.html to
/path/to/lists/LISTNAME/en/options.html and remove the part

    <tr><TD BGCOLOR="#cccccc">
        <strong>Set Digest Mode</strong><p>
        If you turn digest mode on, you'll get posts bundled together
        (usually one per day but possibly more on busy lists), instead
        of singly when they're sent.  If digest mode is changed from
        on to off, you may receive one last digest.
        </td><td bgcolor="#cccccc">
        <MM-Undigest-Radio-Button>Off<br>
        <MM-Digest-Radio-Button>On
        </td></tr>

and maybe the following part

    <tr><TD BGCOLOR="#cccccc">
        <strong>Get MIME or Plain Text Digests?</strong><p>
        Your mail reader may or may not support MIME digests.  In
        general MIME digests are preferred, but if you have a problem
        reading them, select plain text digests.
        </td><td bgcolor="#cccccc">
        <MM-Mime-Digests-Button>MIME<br>
        <MM-Plain-Digests-Button>Plain Text<p>
        <mm-global-mime-button><i>Set globally</i>
        </td></tr>


from the /path/to/lists/LISTNAME/en/options.html template (or place
'comment' tags around them). See the FAQ at
<http://wiki.list.org/x/4030605> for more on template editing.

It is arguably a bug to display these settings on the options page if
the list is not digestable and the user's digest setting is not Yes. If
you file a bug at <https://bugs.launchpad.net/mailman/+filebug>, I'll
consider fixing it.

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

From mark at tafn.org.uk  Mon Jul 20 16:19:52 2015
From: mark at tafn.org.uk (Mark T)
Date: Mon, 20 Jul 2015 15:19:52 +0100
Subject: [Mailman-Users] some mailman questions
Message-ID: <2010F09541E74405902315667794415F@PC>

Hi can any one help with the following
1 i have set all my mailing lists to private  
how do i get the list to show up in mailman only if i go to the page it ses no  public lists advertised witch is what i want only had non members trying to send messages
i have made a page in wordpress with all our lists on 
2. if i update my linode server will it break my mailman only i was told it would  
the version i am useing is 2.1.16rc2 witch i was also told is the most accessible for the blind
3 is there a way of changing all my passwords with out doing them one by one
mark.



From andrew at hodgsonfamily.org  Mon Jul 20 16:41:02 2015
From: andrew at hodgsonfamily.org (Andrew Hodgson)
Date: Mon, 20 Jul 2015 14:41:02 +0000
Subject: [Mailman-Users] some mailman questions
In-Reply-To: <2010F09541E74405902315667794415F@PC>
References: <2010F09541E74405902315667794415F@PC>
Message-ID: <DB5PR04MB1478DB1DF355174E2C406606C5850@DB5PR04MB1478.eurprd04.prod.outlook.com>

Mark T wrote:

>Hi can any one help with the following

>1 i have set all my mailing lists to private
>how do i get the list to show up in mailman only if i go to the page it ses no  public lists advertised witch is what i want only had non members trying to send messages
>i have made a page in wordpress with all our lists on

I am not sure what you are trying to do here, if you turn off the display of lists on the /listinfo page, people can still send emails to the list if they know about them from other means (I.e, Google searches, your Wordpress site etc).

>2. if i update my linode server will it break my mailman only i was told it would
>the version i am useing is 2.1.16rc2 witch i was also told is the most accessible for the blind

For what it's worth I run a load of lists on 2.1.20 which is the latest stable release and most if not all the users are blind and using it fine with assistive technology.  In terms of your version, you are using a pre-release/beta version, so depending on how you installed that would give you more ideas about whether updating the VM OS would break things.  What OS is the VM running now, is is being patched etc?

>3 is there a way of changing all my passwords with out doing them one by one

Do you mean your list admin passwords or something else?

Thanks.
Andrew.

From mark at msapiro.net  Mon Jul 20 16:55:12 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 20 Jul 2015 07:55:12 -0700
Subject: [Mailman-Users] some mailman questions
In-Reply-To: <2010F09541E74405902315667794415F@PC>
References: <2010F09541E74405902315667794415F@PC>
Message-ID: <55AD0BD0.4030008@msapiro.net>

On 7/20/15 7:19 AM, Mark T wrote:
> Hi can any one help with the following
> 1 i have set all my mailing lists to private  
> how do i get the list to show up in mailman only if i go to the page ...


If you mean you want lists that are not 'advertised' to show on the
admin and listinfo overview pages only if you and no one else goes to
the page, that would require modifications to the source code.

You could possibly implement your own CGI or PHP page that would run
Mailman's bin/list_lists command and display the results.


> 2. if i update my linode server will it break my mailman only i was told it would  
> the version i am useing is 2.1.16rc2 witch i was also told is the most accessible for the blind


There should be no difference in accessibility between Mailman 2.1.16rc2
and later versions.

I don't know why a server upgrade would break Mailman. I suppose there
could be issues resulting from an upgrade, but without knowing more
detail about both the current and upgraded configurations, I have no
idea what they might be.


> 3 is there a way of changing all my passwords with out doing them one by one


If you mean list member passwords, a list member can change her password
globally from her options page for any list of which she is a member.

If you mean list admin passwords, you can use Mailman's bin/change_pw
tool to change the admin password for all or selected lists.

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

From my_list_address at yahoo.no  Mon Jul 20 17:56:28 2015
From: my_list_address at yahoo.no (MLA)
Date: Mon, 20 Jul 2015 17:56:28 +0200
Subject: [Mailman-Users] Disabling the digest feature
In-Reply-To: <55ACFFEC.5030106@msapiro.net>
References: <55ACCAE7.6000502@yahoo.no> <55ACFFEC.5030106@msapiro.net>
Message-ID: <55AD1A2C.3050003@yahoo.no>

On 20/07/2015 16:04, Mark Sapiro wrote:
> On 7/20/15 3:18 AM, MLA wrote:
>> I have a low volume mailing list and would like to remove the digest
>> option, so what I've done is (via the Mailman administrative interface):
>>
>> - in "Membership management"-"Membership list": disabled "Digest" from
>> those members who had this enabled
>> - in "Digest option": set Edit_digest to NO to disable the digest
>> feature entirely
>
>
> Do you mean digestable as in
> Can list members choose to receive list traffic bunched in digests?
> (Edit digestable)?

Sorry, yes. I meant "Edit_digestable".



>> But for testing purposes I subscribed to the list with a new address and
>> noticed that in my user's administration page ("options" section)
>> there's a choice for "set digest mode" for on/off. How can I remove this
>> and any other trace of the digest option which I might have missed?


> The setting is there, but it can't be set to Yes if digestable is No.
>
> If you have sufficient access to the server, you can copy
> /path/to/templates/en/options.html to
> /path/to/lists/LISTNAME/en/options.html and remove the part

I'm not sure which rights I have to the server but I was able to edit it 
from the web user administration interface!
In the "Edit the public HTML pages and text files" I edited the "User 
specific options page". Works great now.



> It is arguably a bug to display these settings on the options page if
> the list is not digestable and the user's digest setting is not Yes. If
> you file a bug at <https://bugs.launchpad.net/mailman/+filebug>, I'll
> consider fixing it.

Done!


M.

From mark at msapiro.net  Mon Jul 20 18:28:48 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 20 Jul 2015 09:28:48 -0700
Subject: [Mailman-Users] Disabling the digest feature
In-Reply-To: <55AD1A2C.3050003@yahoo.no>
References: <55ACCAE7.6000502@yahoo.no> <55ACFFEC.5030106@msapiro.net>
 <55AD1A2C.3050003@yahoo.no>
Message-ID: <55AD21C0.4020207@msapiro.net>

On 7/20/15 8:56 AM, MLA wrote:
> On 20/07/2015 16:04, Mark Sapiro wrote:
>>
>> If you have sufficient access to the server, you can copy
>> /path/to/templates/en/options.html to
>> /path/to/lists/LISTNAME/en/options.html and remove the part
> 
> I'm not sure which rights I have to the server but I was able to edit it
> from the web user administration interface!
> In the "Edit the public HTML pages and text files" I edited the "User
> specific options page". Works great now.


Right. I forgot that this was one of the templates that can be edited
from the admin web UI. That's the easiest way to do it.


>> It is arguably a bug to display these settings on the options page if
>> the list is not digestable and the user's digest setting is not Yes. If
>> you file a bug at <https://bugs.launchpad.net/mailman/+filebug>, I'll
>> consider fixing it.
> 
> Done!


Thanks.

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

From dandrews at visi.com  Mon Jul 20 19:07:31 2015
From: dandrews at visi.com (David Andrews)
Date: Mon, 20 Jul 2015 12:07:31 -0500
Subject: [Mailman-Users] some mailman questions
In-Reply-To: <55AD0BD0.4030008@msapiro.net>
References: <2010F09541E74405902315667794415F@PC>
 <55AD0BD0.4030008@msapiro.net>
Message-ID: <auto-000030842457@mailfront2.g2host.com>

At 09:55 AM 7/20/2015, Mark Sapiro wrote:
>On 7/20/15 7:19 AM, Mark T wrote:
> > Hi can any one help with the following



> > 2. if i update my linode server will it break my mailman only i 
> was told it would
> > the version i am useing is 2.1.16rc2 witch i was also told is the 
> most accessible for the blind
>

I run Mailman through cPanel, but on Linode, and upgrading my OS has 
never caused any problems.  Also, I am a blind user, and there will 
be no accessibility problems by moving to 2.1.20.

Dave



>There should be no difference in accessibility between Mailman 2.1.16rc2
>and later versions.
>
>I don't know why a server upgrade would break Mailman. I suppose there
>could be issues resulting from an upgrade, but without knowing more
>detail about both the current and upgraded configurations, I have no
>idea what they might be.
>
>

         David Andrews and long white cane Harry.
E-Mail:  dandrews at visi.com or david.andrews at nfbnet.org


From mark at msapiro.net  Mon Jul 20 20:04:08 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 20 Jul 2015 11:04:08 -0700
Subject: [Mailman-Users] problem with accented characters,
 converting HTML to plain text
In-Reply-To: <20150719201333.GA22495@telecom-paristech.fr>
References: <20150719201333.GA22495@telecom-paristech.fr>
Message-ID: <55AD3818.5090109@msapiro.net>

On 7/19/15 1:13 PM, Dominique Asselineau wrote:
> Hello,
> 
> When a e-mail in text/html content-type is converted in to plain text,
> the accented characters are not treated correctly.


There are potential issues with this. Mailman gets the content of the
text/html part and calls HTML_TO_PLAINTEXT_COMMAND (lynx -dump in the
default case) to convert the HTML to a plain text rendering and replaces
the content of the part with that and changes the Content-Type: to
text/plain while maintaining any charset= parameter.

Lynx normally does not recode any characters, so the output of lynx
-dump should be in the same charset is the input and it should be OK.

Problems arise if the input has characters represented as HTML entities
such as &aacute; or &egrave;. In this case, lynx outputs the characters
encoded in a charset which may not match the messages encoding.

In order to say more, I would need to see a raw message as sent to the
list with all headers intact and the resultant raw message from the list
with all headers intact.

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

From robert at susmilch.com  Mon Jul 20 22:11:31 2015
From: robert at susmilch.com (Robert Susmilch)
Date: Mon, 20 Jul 2015 15:11:31 -0500
Subject: [Mailman-Users] Unsubscribe
In-Reply-To: <55AD3818.5090109@msapiro.net>
References: <20150719201333.GA22495@telecom-paristech.fr>
 <55AD3818.5090109@msapiro.net>
Message-ID: <11BE59AA-DD1D-42A8-B706-FCEE28496E9F@susmilch.com>



From sm at noisynotes.com  Tue Jul 21 01:13:06 2015
From: sm at noisynotes.com (Steve Matzura)
Date: Mon, 20 Jul 2015 19:13:06 -0400
Subject: [Mailman-Users] Phantom or unknown address for mailing lists
Message-ID: <ruvqqat8acp6ejdtrop7s4tv0uesiec6hk@4ax.com>

Finally got all my mail stuff straight. However, a strange and
untraceable thing has happened. It now seems all my mailing lists'
addresses begin with "mail." (list-name at mail.my-domain.com). There's
nothing in main.cf to explain this. My MX record is called "mail," but
should that affect Mailman?

From mark at msapiro.net  Tue Jul 21 02:23:00 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 20 Jul 2015 17:23:00 -0700
Subject: [Mailman-Users] Phantom or unknown address for mailing lists
In-Reply-To: <ruvqqat8acp6ejdtrop7s4tv0uesiec6hk@4ax.com>
References: <ruvqqat8acp6ejdtrop7s4tv0uesiec6hk@4ax.com>
Message-ID: <55AD90E4.4080906@msapiro.net>

On 7/20/15 4:13 PM, Steve Matzura wrote:
> Finally got all my mail stuff straight. However, a strange and
> untraceable thing has happened. It now seems all my mailing lists'
> addresses begin with "mail." (list-name at mail.my-domain.com). There's
> nothing in main.cf to explain this. My MX record is called "mail," but
> should that affect Mailman?


Where exactly do you see this? Is it in the list's admin General Options
-> host_name and the list posting address on the list's listinfo page?

If so, you can change the host_name and verify things like
DEFAULT_EMAIL_HOST and add_virtualhost email hosts in mm_cfg.py and
maybe run fix_url. See <http://wiki.list.org/x/4030616>.

If headers of email messages are being rewritten, see
<http://wiki.list.org/x/4030649>.

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

From lac at openend.se  Tue Jul 21 09:42:18 2015
From: lac at openend.se (Laura Creighton)
Date: Tue, 21 Jul 2015 09:42:18 +0200
Subject: [Mailman-Users] problem with accented characters,
	converting HTML to plain text
In-Reply-To: Message from Mark Sapiro <mark@msapiro.net>
 of "Mon, 20 Jul 2015 11:04:08 -0700." <55AD3818.5090109@msapiro.net>
References: <20150719201333.GA22495@telecom-paristech.fr><55AD3818.5090109@msapiro.net>
Message-ID: <201507210742.t6L7gISZ014491@fido.openend.se>

In a message of Mon, 20 Jul 2015 11:04:08 -0700, Mark Sapiro writes:
>On 7/19/15 1:13 PM, Dominique Asselineau wrote:
>> Hello,
>> 
>> When a e-mail in text/html content-type is converted in to plain text,
>> the accented characters are not treated correctly.
>
>
>There are potential issues with this. Mailman gets the content of the
>text/html part and calls HTML_TO_PLAINTEXT_COMMAND (lynx -dump in the
>default case) to convert the HTML to a plain text rendering and replaces
>the content of the part with that and changes the Content-Type: to
>text/plain while maintaining any charset= parameter.
>
>Lynx normally does not recode any characters, so the output of lynx
>-dump should be in the same charset is the input and it should be OK.
>
>Problems arise if the input has characters represented as HTML entities
>such as &aacute; or &egrave;. In this case, lynx outputs the characters
>encoded in a charset which may not match the messages encoding.
>
>In order to say more, I would need to see a raw message as sent to the
>list with all headers intact and the resultant raw message from the list
>with all headers intact.
>
>-- 
>Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
>San Francisco Bay Area, California    better use your sense - B. Dylan
>------------------------------------------------------

I had enough trouble with lynx over this -- it used to be how I
converted all html mail my mail reader saw, but such characters
are not rare in the mail I receive -- that I gave up on lynx.

My new rule in my mailer for how to display html text is:

w3m -dump -o display_link_number=1 -cols 78 -T text/html -
I "$(echo %a | sed -r 's/.*charset="?([-a-zA-Z0-9_]*).*/\1/')" -O utf-8 | less

which is one heck of a mouthful, but hasn't caused me any problems since.

Just in case somebody else wants to ditch lynx ...

Laura

From mark at msapiro.net  Tue Jul 21 20:01:40 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 21 Jul 2015 11:01:40 -0700
Subject: [Mailman-Users] problem with accented characters,
 converting HTML to plain text
In-Reply-To: <201507210742.t6L7gISZ014491@fido.openend.se>
References: <20150719201333.GA22495@telecom-paristech.fr><55AD3818.5090109@msapiro.net>
 <201507210742.t6L7gISZ014491@fido.openend.se>
Message-ID: <55AE8904.3050100@msapiro.net>

On 7/21/15 12:42 AM, Laura Creighton wrote:
> 
> My new rule in my mailer for how to display html text is:
> 
> w3m -dump -o display_link_number=1 -cols 78 -T text/html -I "$(echo %a | sed -r 's/.*charset="?([-a-zA-Z0-9_]*).*/\1/')" -O utf-8 | less
> 
> which is one heck of a mouthful, but hasn't caused me any problems since.
> 
> Just in case somebody else wants to ditch lynx ...


While I'm sure Laura's command above works well as an HTML viewer for an
MUA such as might be specified in a mutt mailcap file, there are issues
with trying to use this as a Mailman HTML_TO_PLAIN_TEXT_COMMAND because
it gets the input charset from the message's Content-Type: header and
none of the message's headers are passed to HTML_TO_PLAIN_TEXT_COMMAND.
Also, it specifies the output charset as utf-8, but Mailman will not
change the charset parameter in the converted MIME part. It only changes
the MIME type from text/html to text/plain so if the original HTML
charset is not utf-8, creating utf-8 output would be wrong.

While one could use some w3m command in HTML_TO_PLAIN_TEXT_COMMAND, the
appropriate command might be something like

w3m -dump -o display_link_number=1 -cols 78 -T text/html %(filename)s

without the -I and -O options, and this could wind up with the same
charset issues as lynx.

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

From ccordero at csusb.edu  Tue Jul 21 20:43:39 2015
From: ccordero at csusb.edu (Chad Cordero)
Date: Tue, 21 Jul 2015 18:43:39 +0000
Subject: [Mailman-Users] mail not delivered to a member
Message-ID: <D1D3E09B.113C15%ccordero@csusb.edu>

I have a member of a list that did not get a message to the list.  He was
a member of the list at the time (or I couldn?t find a
subscribe/unsubscribe request).  Please help.

sh-4.2# bin/list_members --regular --nomail=enabled libraryit | wc -l
10
sh-4.2# grep libraryit /var/log/mailman/smtp
Jul 20 13:11:36 2015 (2133)
<CA+cTe3anwP_90_U1yA93EH62W6fB6Bw=F3H1R+3WXZDidSr7AQ at mail.gmail.com> smtp
to libraryit for 9 recips, completed in 0.016 seconds
Jul 20 13:15:52 2015 (2133)
<CA+cTe3ZkT+rb60-gDLbkJMukEHmUu=nJ8APDF4dmZ3T=8O8Q6w at mail.gmail.com> smtp
to libraryit for 9 recips, completed in 0.017 seconds
Jul 20 13:57:48 2015 (2133)
<EC48F206-C1A9-440A-89DA-83961558110B at csusb.edu> smtp to libraryit for 10
recips, completed in 0.017 seconds
Jul 20 14:39:33 2015 (2133)
<CAEF1O5vvFsVBjpJ5Hchs4MpWAKM=TFeqhTVU5B0cDBwK1rQk=g at mail.gmail.com> smtp
to libraryit for 10 recips, completed in 0.018 seconds
Jul 20 16:16:28 2015 (2133)
<CAEF1O5uGaLPTW4_0et4x0mKS6kqyJJZAR59Dq9R6t16jPrJBMQ at mail.gmail.com> smtp
to libraryit for 10 recips, completed in 0.037 seconds
Jul 20 16:16:39 2015 (2133)
<CAG2=hRsegcR8AyiXK-yTMT94Wrddv0+POjEHJmDLMPR0iZ=_vg at mail.gmail.com> smtp
to libraryit for 10 recips, completed in 0.020 seconds
Jul 20 16:37:17 2015 (2133)
<CAG2=hRteQ0CHyKPFNQEW4znuPi1Rf=QwvONHA=gZV4jKJxZSaA at mail.gmail.com> smtp
to libraryit for 10 recips, completed in 0.017 seconds
Jul 20 16:52:17 2015 (2133)
<CAAie0gW0+1H5M-8pjaiHstsQm+bz=uyfzMEMVVe0f8zZ=mdDwg at mail.gmail.com> smtp
to libraryit for 9 recips, completed in 0.014 seconds
Jul 20 19:31:45 2015 (2133) <9acaed$kan9jt at ausxippc101.us.dell.com> smtp
to libraryit for 10 recips, completed in 0.053 seconds
Jul 21 08:09:10 2015 (2133)
<24eaa69267734ff7aa12314b5fde4737 at SN2PR0801MB0765.namprd08.prod.outlook.com
> smtp to libraryit for 10 recips, completed in 0.020 seconds
sh-4.2# grep libraryit /var/log/mailman/subscribe
sh-4.2#


---
Chad Cordero
Information Technology Consultant
Technology Support Center
Information Technology Services
California State University, San Bernardino
5500 University Pkwy
San Bernardino, CA 92407-2393
Main Line: 909/537-7677
Direct Line: 909/537-7281
Fax: 909/537-7141
http://support.csusb.edu/

---
Disclaimer: This e-mail message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information
protected from disclosure. If the reader of this message is not the
intended recipient, or an employee or agent responsible for delivering
this message to the intended recipient, you are hereby notified that any
dissemination, distribution or copying of this communication is strictly
prohibited. If you have received this communication in error, please
notify us immediately by replying to the message and deleting it from your
computer.


From mark at msapiro.net  Wed Jul 22 04:11:45 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 21 Jul 2015 19:11:45 -0700
Subject: [Mailman-Users] mail not delivered to a member
In-Reply-To: <D1D3E09B.113C15%ccordero@csusb.edu>
References: <D1D3E09B.113C15%ccordero@csusb.edu>
Message-ID: <55AEFBE1.3050209@msapiro.net>

On 7/21/15 11:43 AM, Chad Cordero wrote:
> I have a member of a list that did not get a message to the list.  He was
> a member of the list at the time (or I couldn?t find a
> subscribe/unsubscribe request).  Please help.
> 
> sh-4.2# bin/list_members --regular --nomail=enabled libraryit | wc -l
> 10


OK, the list has 10 members.


> sh-4.2# grep libraryit /var/log/mailman/smtp
> Jul 20 13:11:36 2015 (2133)
> <CA+cTe3anwP_90_U1yA93EH62W6fB6Bw=F3H1R+3WXZDidSr7AQ at mail.gmail.com> smtp
> to libraryit for 9 recips, completed in 0.016 seconds
...
> Jul 20 13:57:48 2015 (2133)
> <EC48F206-C1A9-440A-89DA-83961558110B at csusb.edu> smtp to libraryit for 10
> recips, completed in 0.017 seconds
...


and sometimes the list delivers to 9 recips and sometimes 10. The
difference is probably the poster's not metoo, or a Cc: to a list member
with nodups.

Your next step is to look at the MTA logs to see whether the specific
message was sent to the member.

On the other hand, this may be a case of what's in the FAQ at
<http://wiki.list.org/x/4030680>.

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

From ccordero at csusb.edu  Tue Jul 21 19:32:11 2015
From: ccordero at csusb.edu (Chad Cordero)
Date: Tue, 21 Jul 2015 17:32:11 +0000
Subject: [Mailman-Users] mail not delivered to a member
Message-ID: <D1D3D02A.113C0A%ccordero@csusb.edu>

I have a member of a list that did not get a message to the list.  He was a
member of the list at the time (or I couldn?t find a subscribe/unsubscribe
request).  Please help.

sh-4.2# bin/list_members --regular --nomail=enabled libraryit | wc -l

10

sh-4.2# bin/list_members --regular --nomail=enabled libraryit

003521244 at coyote.csusb.edu

003695665 at coyote.csusb.edu

003963205 at coyote.csusb.edu

004385237 at coyote.csusb.edu

004649969 at coyote.csusb.edu

004732675 at coyote.csusb.edu

004945833 at coyote.csusb.edu

004981700 at coyote.csusb.edu

alzahran at csusb.edu

jsmith at csusb.edu

sh-4.2# grep libraryit /var/log/mailman/smtp

Jul 20 13:11:36 2015 (2133)
<CA+cTe3anwP_90_U1yA93EH62W6fB6Bw=F3H1R+3WXZDidSr7AQ at mail.gmail.com> smtp to
libraryit for 9 recips, completed in 0.016 seconds

Jul 20 13:15:52 2015 (2133)
<CA+cTe3ZkT+rb60-gDLbkJMukEHmUu=nJ8APDF4dmZ3T=8O8Q6w at mail.gmail.com> smtp to
libraryit for 9 recips, completed in 0.017 seconds

Jul 20 13:57:48 2015 (2133) <EC48F206-C1A9-440A-89DA-83961558110B at csusb.edu>
smtp to libraryit for 10 recips, completed in 0.017 seconds

Jul 20 14:39:33 2015 (2133)
<CAEF1O5vvFsVBjpJ5Hchs4MpWAKM=TFeqhTVU5B0cDBwK1rQk=g at mail.gmail.com> smtp to
libraryit for 10 recips, completed in 0.018 seconds

Jul 20 16:16:28 2015 (2133)
<CAEF1O5uGaLPTW4_0et4x0mKS6kqyJJZAR59Dq9R6t16jPrJBMQ at mail.gmail.com> smtp to
libraryit for 10 recips, completed in 0.037 seconds

Jul 20 16:16:39 2015 (2133)
<CAG2=hRsegcR8AyiXK-yTMT94Wrddv0+POjEHJmDLMPR0iZ=_vg at mail.gmail.com> smtp to
libraryit for 10 recips, completed in 0.020 seconds

Jul 20 16:37:17 2015 (2133)
<CAG2=hRteQ0CHyKPFNQEW4znuPi1Rf=QwvONHA=gZV4jKJxZSaA at mail.gmail.com> smtp to
libraryit for 10 recips, completed in 0.017 seconds

Jul 20 16:52:17 2015 (2133)
<CAAie0gW0+1H5M-8pjaiHstsQm+bz=uyfzMEMVVe0f8zZ=mdDwg at mail.gmail.com> smtp to
libraryit for 9 recips, completed in 0.014 seconds

Jul 20 19:31:45 2015 (2133) <9acaed$kan9jt at ausxippc101.us.dell.com> smtp to
libraryit for 10 recips, completed in 0.053 seconds

Jul 21 08:09:10 2015 (2133)
<24eaa69267734ff7aa12314b5fde4737 at SN2PR0801MB0765.namprd08.prod.outlook.com>
smtp to libraryit for 10 recips, completed in 0.020 seconds

sh-4.2# grep libraryit /var/log/mailman/subscribe

sh-4.2#


---
Chad Cordero
Information Technology Consultant
Technology Support Center
Information Technology Services
California State University, San Bernardino
5500 University Pkwy
San Bernardino, CA 92407-2393
Main Line: 909/537-7677
Direct Line: 909/537-7281
Fax: 909/537-7141
http://support.csusb.edu/

---
Disclaimer: This e-mail message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information
protected from disclosure. If the reader of this message is not the intended
recipient, or an employee or agent responsible for delivering this message
to the intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited. If you
have received this communication in error, please notify us immediately by
replying to the message and deleting it from your computer.



From larry at acbradio.org  Tue Jul 21 22:01:38 2015
From: larry at acbradio.org (Larry Turnbull)
Date: Tue, 21 Jul 2015 20:01:38 +0000
Subject: [Mailman-Users] FW: (fwd) Re: Phantom or unknown address for
	mailing lists
In-Reply-To: <hpfsqadj1sdv3428pt31qelb8vmpk3sli9@4ax.com>
References: <hpfsqadj1sdv3428pt31qelb8vmpk3sli9@4ax.com>
Message-ID: <035501d0c3f0$0d7fa1a0$287ee4e0$@acbradio.org>

Hello all:

I am helping Steve work on the mailman and postfix setup on the new server.

Here is what is actually happening:

When I send an email directly to a user that exists in the alias or mailbox
table with username at theglobalvoice.info postfix delivers the email just
fine.

Now when I send an email to a mailman list such as
mailman at theglobalvoice.info I get no message back.

When I look in the maillog file I see an error that says user unknown
mailman at theglobalvoice.info.

When I send a message to mailman at mail.theglobalvoice.info mailman picks up
the message and delivers it  just fine.

In mm_cfg.py I added the following lines after mailman was installed:

MTA = 'Postfix'
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['theglobalvoice.info']

I added the references to the aliases and virtual-mailman files in main.cf
for postfix like so:
Alias_maps = hash:/etc/aliases, hash:/usr/local/mailman/data/aliases
Virtual_alias_maps = proxy:mysql:/etc/postfix/mysql_virtual_alias_maps.cf,
hash:/usr/local/mailman/data/virtual-mailman

I installed mailman by compiling its source code.

I ran configure with the following options:
./configure --with-mailhost=theglobalvoice.info
--with-urlhost=www.theglobalvoice.info

I did copy the lists over from the old server and ran bin/withlist -r -a -l
fix_url.

That script ran with out any errors.

I ran bin/genaliases and it created the aliases and virtual-mailman files.

Is there anything else I need to look at?

I administer a server for ACB and I have the same setup and it works fine.

The only major difference between the server administer and the one that
Steve administers is I am running Ubuntu 12.04 lts and he is running
fedora20.

I don't think it matters but thought I would share that bit of information
in case there is something with the OS I need to check out.

Thanks.

Larry



-----Original Message-----
From: Steve Matzura [mailto:number6 at noisynotes.com] 
Sent: Tuesday, July 21, 2015 7:47 AM
To: lt
Subject: (fwd) Re: [Mailman-Users] Phantom or unknown address for mailing
lists

On Mon, 20 Jul 2015 17:23:00 -0700, Mark Sapiro <mark at msapiro.net>
wrote:

On 7/20/15 4:13 PM, Steve Matzura wrote:
> Finally got all my mail stuff straight. However, a strange and 
> untraceable thing has happened. It now seems all my mailing lists'
> addresses begin with "mail." (list-name at mail.my-domain.com). There's 
> nothing in main.cf to explain this. My MX record is called "mail," but 
> should that affect Mailman?


Where exactly do you see this? Is it in the list's admin General Options
-> host_name and the list posting address on the list's listinfo page?

If so, you can change the host_name and verify things like
DEFAULT_EMAIL_HOST and add_virtualhost email hosts in mm_cfg.py and maybe
run fix_url. See <http://wiki.list.org/x/4030616>.

If headers of email messages are being rewritten, see
<http://wiki.list.org/x/4030649>.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan
------------------------------------------------------
Mailman-Users mailing list Mailman-Users at 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/sm%40noisynotes.com

From larry at acbradio.org  Wed Jul 22 16:17:24 2015
From: larry at acbradio.org (Larry Turnbull)
Date: Wed, 22 Jul 2015 14:17:24 +0000
Subject: [Mailman-Users] FW: (fwd) Re: Phantom or unknown address
	for?mailing lists
In-Reply-To: <035501d0c3f0$0d7fa1a0$287ee4e0$@acbradio.org>
References: <hpfsqadj1sdv3428pt31qelb8vmpk3sli9@4ax.com>
 <035501d0c3f0$0d7fa1a0$287ee4e0$@acbradio.org>
Message-ID: <005501d0c489$2241ddd0$66c59970$@acbradio.org>

I have figured out the problem.

I had to change the myorigin from $mydomain to $myhostname in the postfix
main.cf file.

Thanks.

Larry


-----Original Message-----
From: Mailman-Users
[mailto:mailman-users-bounces+larry=acbradio.org at python.org] On Behalf Of
Larry Turnbull
Sent: Tuesday, July 21, 2015 3:02 PM
To: mailman-users at python.org
Subject: [Mailman-Users] FW: (fwd) Re: Phantom or unknown address for
mailing lists

Hello all:

I am helping Steve work on the mailman and postfix setup on the new server.

Here is what is actually happening:

When I send an email directly to a user that exists in the alias or mailbox
table with username at theglobalvoice.info postfix delivers the email just
fine.

Now when I send an email to a mailman list such as
mailman at theglobalvoice.info I get no message back.

When I look in the maillog file I see an error that says user unknown
mailman at theglobalvoice.info.

When I send a message to mailman at mail.theglobalvoice.info mailman picks up
the message and delivers it  just fine.

In mm_cfg.py I added the following lines after mailman was installed:

MTA = 'Postfix'
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['theglobalvoice.info']

I added the references to the aliases and virtual-mailman files in main.cf
for postfix like so:
Alias_maps = hash:/etc/aliases, hash:/usr/local/mailman/data/aliases
Virtual_alias_maps = proxy:mysql:/etc/postfix/mysql_virtual_alias_maps.cf,
hash:/usr/local/mailman/data/virtual-mailman

I installed mailman by compiling its source code.

I ran configure with the following options:
./configure --with-mailhost=theglobalvoice.info
--with-urlhost=www.theglobalvoice.info

I did copy the lists over from the old server and ran bin/withlist -r -a -l
fix_url.

That script ran with out any errors.

I ran bin/genaliases and it created the aliases and virtual-mailman files.

Is there anything else I need to look at?

I administer a server for ACB and I have the same setup and it works fine.

The only major difference between the server administer and the one that
Steve administers is I am running Ubuntu 12.04 lts and he is running
fedora20.

I don't think it matters but thought I would share that bit of information
in case there is something with the OS I need to check out.

Thanks.

Larry



-----Original Message-----
From: Steve Matzura [mailto:number6 at noisynotes.com]
Sent: Tuesday, July 21, 2015 7:47 AM
To: lt
Subject: (fwd) Re: [Mailman-Users] Phantom or unknown address for mailing
lists

On Mon, 20 Jul 2015 17:23:00 -0700, Mark Sapiro <mark at msapiro.net>
wrote:

On 7/20/15 4:13 PM, Steve Matzura wrote:
> Finally got all my mail stuff straight. However, a strange and 
> untraceable thing has happened. It now seems all my mailing lists'
> addresses begin with "mail." (list-name at mail.my-domain.com). There's 
> nothing in main.cf to explain this. My MX record is called "mail," but 
> should that affect Mailman?


Where exactly do you see this? Is it in the list's admin General Options
-> host_name and the list posting address on the list's listinfo page?

If so, you can change the host_name and verify things like
DEFAULT_EMAIL_HOST and add_virtualhost email hosts in mm_cfg.py and maybe
run fix_url. See <http://wiki.list.org/x/4030616>.

If headers of email messages are being rewritten, see
<http://wiki.list.org/x/4030649>.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan
------------------------------------------------------
Mailman-Users mailing list Mailman-Users at 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/sm%40noisynotes.com
------------------------------------------------------
Mailman-Users mailing list Mailman-Users at 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/larry%40acbradio.org

From whilelm at doomfr.com  Sat Jul 25 12:56:24 2015
From: whilelm at doomfr.com (Christophe Moille)
Date: Sat, 25 Jul 2015 12:56:24 +0200
Subject: [Mailman-Users] KeyError: 'fr_FR' - return
	mm_cfg.LC_DESCRIPTIONS[lang][2]
Message-ID: <20150725105624.GB6376@localhost.localdomain>

Hello,

I can't get mailman home page displayed. And I can't figure what's wrong
with the log. Can you help me ? 


Jul 25 12:38:27 2015 admin(13187): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 
admin(13187): [----- Mailman Version: 2.1.15 -----] 
admin(13187): [----- Traceback ------] 
admin(13187): Traceback (most recent call last):
admin(13187):   File "/var/lib/mailman/scripts/driver", line 112, in run_main
admin(13187):     main()
admin(13187):   File "/var/lib/mailman/Mailman/Cgi/listinfo.py", line 43, in main
admin(13187):     listinfo_overview()
admin(13187):   File "/var/lib/mailman/Mailman/Cgi/listinfo.py", line 155, in listinfo_overview
admin(13187):     print doc.Format()
admin(13187):   File "/var/lib/mailman/Mailman/htmlformat.py", line 335, in Format
admin(13187):     direction = Utils.GetDirection(self.language)
admin(13187):   File "/var/lib/mailman/Mailman/Utils.py", line 710, in GetDirection
admin(13187):     return mm_cfg.LC_DESCRIPTIONS[lang][2]
admin(13187): KeyError: 'fr_FR'
admin(13187): [----- Python Information -----] 
admin(13187): sys.version     =   2.7.3 (default, Mar 13 2014, 11:03:55) 
[GCC 4.7.2] 
admin(13187): sys.executable  =   /usr/bin/python 
admin(13187): sys.prefix      =   /usr 
admin(13187): sys.exec_prefix =   /usr 
admin(13187): sys.path        =   ['/var/lib/mailman/pythonlib', '/var/lib/mailman', '/usr/lib/mailman/scripts', '/var/lib/mailman', '/usr/lib/python2.7/', '/usr/lib/python2.7/plat-linux2', '/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload', '/usr/lib/python2.7/site-packages'] 
admin(13187): sys.platform    =   linux2 
admin(13187): [----- Environment Variables -----] 
admin(13187):   SSL_VERSION_INTERFACE: mod_ssl/2.2.22 
admin(13187):   SSL_SERVER_I_DN_OU: http://www.CAcert.org 
admin(13187):   SSL_CIPHER_EXPORT: false 
admin(13187):   SERVER_SOFTWARE: Apache/2.2.22 (Debian) 
admin(13187):   SCRIPT_NAME: / 
admin(13187):   SSL_SERVER_A_KEY: rsaEncryption 
admin(13187):   QUERY_STRING:  
admin(13187):   SERVER_SIGNATURE: <address>Apache/2.2.22 (Debian) Server at listes.domaine.name Port 443</address>
admin(13187): 
admin(13187):   REQUEST_METHOD: GET 
admin(13187):   SERVER_PROTOCOL: HTTP/1.1 
admin(13187):   SSL_SERVER_S_DN: /CN=domaine.name 
admin(13187):   SSL_CIPHER: ECDHE-RSA-AES128-GCM-SHA256 
admin(13187):   SSL_SERVER_V_START: May  2 14:07:27 2014 GMT 
admin(13187):   SSL_TLS_SNI: listes.domaine.name 
admin(13187):   SSL_CLIENT_VERIFY: NONE 
admin(13187):   HTTP_USER_AGENT: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Iceweasel/31.8.0 
admin(13187):   HTTP_CONNECTION: keep-alive 
admin(13187):   SERVER_NAME: listes.domaine.name 
admin(13187):   REMOTE_ADDR: xxxxxxxxxxxxx 
admin(13187):   SSL_CIPHER_ALGKEYSIZE: 128 
admin(13187):   SSL_SECURE_RENEG: true 
admin(13187):   SERVER_PORT: 443 
admin(13187):   SSL_COMPRESS_METHOD: NULL 
admin(13187):   SSL_SERVER_M_VERSION: 3 
admin(13187):   SSL_SERVER_I_DN_O: CAcert Inc. 
admin(13187):   SERVER_ADDR: xxxxxxxxxxxxx 
admin(13187):   DOCUMENT_ROOT: /var/www 
admin(13187):   SSL_VERSION_LIBRARY: OpenSSL/1.0.1e 
admin(13187):   PYTHONPATH: /var/lib/mailman 
admin(13187):   SCRIPT_FILENAME: /usr/lib/cgi-bin/mailman/listinfo 
admin(13187):   SERVER_ADMIN: root at domaine.name 
admin(13187):   SSL_SERVER_M_SERIAL: 0234E9 
admin(13187):   SSL_SERVER_A_SIG: sha512WithRSAEncryption 
admin(13187):   HTTP_DNT: 1 
admin(13187):   HTTP_HOST: listes.domaine.name 
admin(13187):   HTTPS: on 
admin(13187):   HTTP_CACHE_CONTROL: max-age=0 
admin(13187):   REQUEST_URI: / 
admin(13187):   HTTP_ACCEPT: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 
admin(13187):   SSL_SERVER_S_DN_CN: domaine.name 
admin(13187):   GATEWAY_INTERFACE: CGI/1.1 
admin(13187):   SSL_SERVER_I_DN_CN: CAcert Class 3 Root 
admin(13187):   REMOTE_PORT: 55920 
admin(13187):   HTTP_ACCEPT_LANGUAGE: fr,fr-fr;q=0.8,en-us;q=0.5,en;q=0.3 
admin(13187):   SSL_SERVER_V_END: May  1 14:07:27 2016 GMT 
admin(13187):   SSL_PROTOCOL: TLSv1.2 
admin(13187):   SSL_CIPHER_USEKEYSIZE: 128 
admin(13187):   HTTP_ACCEPT_ENCODING: gzip, deflate 
admin(13187):   SSL_SERVER_I_DN: /O=CAcert Inc./OU=http://www.CAcert.org/CN=CAcert Class 3 Root 

-- 
C'est le passage ? l'action, et il y a plein de mani?res de le faire,
qui permet aussi l'acceptation et d'aller mieux.
Pablo Servigne, discutant de son ouvrage "intitul? Comment tout peut 
s?effondrer. Petit manuel de collapsologie ? l?usage des g?n?rations 
pr?sentes."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20150725/4d1e81c4/attachment.sig>

From michael.hierweck at hostsharing.net  Sat Jul 25 13:34:21 2015
From: michael.hierweck at hostsharing.net (Michael Hierweck)
Date: Sat, 25 Jul 2015 13:34:21 +0200
Subject: [Mailman-Users] Mailman 3: Deployment without LMTP
Message-ID: <55B3743D.9000201@hostsharing.net>

Hi all!

We are currently running Mailman 2 in an very low-traffic environment
without access to the mail server configuration. We can either use
.forward or aliases to forward mails directly to Mailman via pipe.
Fetching mails from POP3/IMAP mailboxes would be possible, too.

We would like to upgrade to Mailman 3 now. Thanks for lots of good work
over many years btw. However Mailman 3 only supports feeding mails via
LTMP. Is is possible to build a bridge between .forward/aliases and
Mailmans LMTP interface in a convenient and secure manner?

An option might be letting fetchmail fetch the mails from a mailbox and
forward them via LTMP. As the mails have already been successfully
delivered to the mailbox before Mailman might reject them I can't image
a chance of handling bounces due to rejects correctly in this setup.

Therefore I'm thinking of a small Python script that receives mail from
stdin and forwards them via LMTP but I'm unsure whether this would be a
correct way to achieve the goal because there might by problems with
bounces when Mailman rejects those mails. This script oughts to
terminate unsuccessfully when the LTMP delivery fails and should
therefore make Postfix bounce the mail itself.

Postfix -> .forward -> pipe --(stdin)--> script --(LMTP)--> Mailman 3

Any opinions or hints are appreciated. Thanks in advance.

Michael

From mark at msapiro.net  Sat Jul 25 18:05:18 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 25 Jul 2015 09:05:18 -0700
Subject: [Mailman-Users] KeyError: 'fr_FR' - return
 mm_cfg.LC_DESCRIPTIONS[lang][2]
In-Reply-To: <20150725105624.GB6376@localhost.localdomain>
References: <20150725105624.GB6376@localhost.localdomain>
Message-ID: <55B3B3BE.9000706@msapiro.net>

On 7/25/15 3:56 AM, Christophe Moille wrote:
> Hello,
> 
> I can't get mailman home page displayed. And I can't figure what's wrong
> with the log. Can you help me ? 
> 
> 
> Jul 25 12:38:27 2015 admin(13187): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 
> admin(13187): [----- Mailman Version: 2.1.15 -----] 
> admin(13187): [----- Traceback ------] 
> admin(13187): Traceback (most recent call last):
> admin(13187):   File "/var/lib/mailman/scripts/driver", line 112, in run_main
> admin(13187):     main()
> admin(13187):   File "/var/lib/mailman/Mailman/Cgi/listinfo.py", line 43, in main
> admin(13187):     listinfo_overview()
> admin(13187):   File "/var/lib/mailman/Mailman/Cgi/listinfo.py", line 155, in listinfo_overview
> admin(13187):     print doc.Format()
> admin(13187):   File "/var/lib/mailman/Mailman/htmlformat.py", line 335, in Format
> admin(13187):     direction = Utils.GetDirection(self.language)
> admin(13187):   File "/var/lib/mailman/Mailman/Utils.py", line 710, in GetDirection
> admin(13187):     return mm_cfg.LC_DESCRIPTIONS[lang][2]
> admin(13187): KeyError: 'fr_FR'


It appears that you have set

DEFAULT_SERVER_LANGUAGE = 'fr_FR'

in mm_cfg.py. This locale is not known to Mailman. You need

DEFAULT_SERVER_LANGUAGE = 'fr'

instead.

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20150725/1ac9a634/attachment.sig>

From shivams at one.com  Tue Jul 28 06:17:30 2015
From: shivams at one.com (Shivam Shukla)
Date: Tue, 28 Jul 2015 09:47:30 +0530
Subject: [Mailman-Users] Hyperkitty search not working
Message-ID: <55B7025A.4090900@one.com>

Hi,

I am using mailman3 in development mode. I have all components working 
and properly running. I have setup some test mailing lists and send mails.
The issue is that i am not able to use the search feature of hyperkitty 
properly. I am inserting subject and some part of body in search field 
but it never give any result. Please suggest am i doing something wrong 
or search feature does not work the way i am trying to use it.

Thanks

From gaja.php at gmail.com  Wed Jul 29 11:49:31 2015
From: gaja.php at gmail.com (Selva Gaja)
Date: Wed, 29 Jul 2015 15:19:31 +0530
Subject: [Mailman-Users] Cpanel, Auto change the mailman create file perm
Message-ID: <CAAzGjDTL8p6HrXeMN1dL17+SuHvxWfvi0wn6Y7oChMVO-EnW5Q@mail.gmail.com>

Hi,

I am using Cpanel third party mailman.

In my site  http://demo.com/*mailman/create* unable to access. But I can
access the other mailman pages (http://demo.com/mailman/admin) from my site.

So, I give the 2755 permission for cgi-bin/create file
  sudo chmod 2755 /usr/local/cpanel/3rdparty/mailman/cgi-bin/create

After that I can access the mailman create page from my site.

But some days later create file perm automatically changed  to 0. Again and
again create file perm automatically changed  to 0.

I want create file perm always to 2755. How can i fix this issue.

Please help me.


-- 
Thanks and Regards,
Selva Gajendran.S

From stephen at xemacs.org  Wed Jul 29 15:01:09 2015
From: stephen at xemacs.org (Stephen J. Turnbull)
Date: Wed, 29 Jul 2015 22:01:09 +0900
Subject: [Mailman-Users]  Cpanel, Auto change the mailman create file perm
In-Reply-To: <CAAzGjDTL8p6HrXeMN1dL17+SuHvxWfvi0wn6Y7oChMVO-EnW5Q@mail.gmail.com>
References: <CAAzGjDTL8p6HrXeMN1dL17+SuHvxWfvi0wn6Y7oChMVO-EnW5Q@mail.gmail.com>
Message-ID: <87mvyfce3u.fsf@uwakimon.sk.tsukuba.ac.jp>

Selva Gaja writes:

 > I am using Cpanel third party mailman.

You're going to need to get help from your host and/or from cPanel.
This is a system-level issue.  Mailman as we distribute it doesn't
change permissions on executable files after installation.  Even the
"fix permissions" script only touches data directories, and that must
be invoked by the system administrator.


From Krinetzki at itc.rwth-aachen.de  Tue Jul 28 12:08:26 2015
From: Krinetzki at itc.rwth-aachen.de (Krinetzki, Stephan)
Date: Tue, 28 Jul 2015 10:08:26 +0000
Subject: [Mailman-Users] Mailman 3 - Some questions
Message-ID: <594A67F0BEDB4A49AAF8B765EFB7482F3C62AC@MBX-S1.rwth-ad.de>

Hello,

I am planning to migrate from mailman 2.1.14 to mailman 3. At the moment
mailman 3 is running on a new CentOS 7 server with postfix as MTA. But I
have some questions and problems:

1. I have an error with hyperkitty. After receiving an mail I'm getting this
error:

Jul 28 11:31:06 2015 (3227) ACCEPT:
<DAF46B4691C451439746B086FB8AA4FFA33CB9 at MBX-S1.rwth-ad.de>
Jul 28 11:31:07 2015 (3221) HyperKitty failure on
http://127.0.0.1/archives/api/mailman/urls: <h1>Bad Request (400)</h1> (400)
Jul 28 11:31:07 2015 (3221) HyperKitty failure on
http://127.0.0.1/archives/api/mailman/urls: <h1>Bad Request (400)</h1> (400)
Jul 28 11:31:08 2015 (3231) HyperKitty failure on
http://127.0.0.1/archives/api/mailman/archive: <h1>Bad Request (400)</h1>
(400)
Jul 28 11:31:08 2015 (3231) Broken archiver: hyperkitty
Traceback (most recent call last):
  File
"/opt/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/r
unners/archive.py", line 107, in _dispose
    archiver.system_archiver.archive_message(mlist, msg_copy)
  File
"/opt/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman_h
yperkitty/__init__.py", line 132, in archive_message
    raise ValueError(result.text)
ValueError: <h1>Bad Request (400)</h1>

So the mail is delivered to the list, but not in the archive. I'm no python
expert, so I can't say what's wrong. Any kind of help is appreciated.

2. In mailman 2, I've created a list and added a new owner. Then the owner
get an email, with his password and a link to the admin page of the list.
How does this work in mailman3? If I create an list in mailman3 and set the
owner, then the email address is the owner, but he isn't noticed. So what
steps are needed to get an password for the new owner and admin of the list?

3. Is it possible to get Shibboleth (https://www.shibboleth.net) working
with mailman3?

4. The link in the welcome mail to the info page of the list is wrong. It
says   http://lists.example.com/listinfo/list at lists.example.com and if I
visit this link, I get an 404 error. (example.com is here a real domain).
The Second link says http://example.com/me at host.com where the example.com
part seems to be hardcoded.

Thank you for your help and I hope my English is not too bad (I'm just a
German IT Administrator...)

Greetings from Germany

Stephan Krinetzki

From Krinetzki at itc.rwth-aachen.de  Wed Jul 29 08:17:23 2015
From: Krinetzki at itc.rwth-aachen.de (Krinetzki, Stephan)
Date: Wed, 29 Jul 2015 06:17:23 +0000
Subject: [Mailman-Users] Mailman 3 - Some questions (addition)
Message-ID: <594A67F0BEDB4A49AAF8B765EFB7482F3C682F@MBX-S1.rwth-ad.de>

Hello,

The last error in hyperkitty was because the https:// URL was missing in the
BROWSER_AUDIENCE variable. Now I'm getting a new error:

ERROR 2015-07-29 08:11:02,287 update_index 7216 140406344681280 Failed to
update the fulltext index: 'Command' object has no attribute 'commit'
Traceback (most recent call last):
  File
"/opt/mailman/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/job
s/update_index.py", line 58, in execute
    update_index()
  File
"/opt/mailman/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/sea
rch_indexes.py", line 73, in update_index
    update_cmd.update_backend("hyperkitty", "default")
  File
"/opt/mailman/mailman-bundler/eggs/django_haystack-2.4.0-py2.7.egg/haystack/
management/commands/update_index.py", line 233, in update_backend
    do_update(backend, index, qs, start, end, total,
verbosity=self.verbosity, commit=self.commit)
AttributeError: 'Command' object has no attribute 'commit'

As far as I can tell, there is an error with the haystack indexing of
archived mails. But how to fix this? I'm clueless.

And the questions from the first mail:

In mailman 2, I've created a list and added a new owner. Then the owner
get an email, with his password and a link to the admin page of the list.
How does this work in mailman3? If I create an list in mailman3 and set the
owner, then the email address is the owner, but he isn't noticed. So what
steps are needed to get an password for the new owner and admin of the list?

Is it possible to get Shibboleth (https://www.shibboleth.net) working
with mailman3?

The link in the welcome mail to the info page of the list is wrong. It
says   http://lists.example.com/listinfo/list at lists.example.com and if I
visit this link, I get an 404 error. (example.com is here a real domain).
The Second link says http://example.com/me at host.com where the example.com
part seems to be hardcoded.

Thank you for your help and I hope my English is not too bad (I'm just a
German IT Administrator...)

Greetings from Germany

Stephan Krinetzki

From mark at msapiro.net  Wed Jul 29 16:01:22 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 29 Jul 2015 07:01:22 -0700
Subject: [Mailman-Users] Cpanel, Auto change the mailman create file perm
In-Reply-To: <87mvyfce3u.fsf@uwakimon.sk.tsukuba.ac.jp>
References: <CAAzGjDTL8p6HrXeMN1dL17+SuHvxWfvi0wn6Y7oChMVO-EnW5Q@mail.gmail.com>
 <87mvyfce3u.fsf@uwakimon.sk.tsukuba.ac.jp>
Message-ID: <55B8DCB2.8000206@msapiro.net>

On 7/29/15 6:01 AM, Stephen J. Turnbull wrote:
> Selva Gaja writes:
> 
>  > I am using Cpanel third party mailman.
> 
> You're going to need to get help from your host and/or from cPanel.
> This is a system-level issue.  Mailman as we distribute it doesn't
> change permissions on executable files after installation.  Even the
> "fix permissions" script only touches data directories, and that must
> be invoked by the system administrator.


Also, this probably occurs because cPanel has it's own Mailman list
creation and deletion process and you should be using that rather than
Mailman's create CGI.

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

From mark at msapiro.net  Wed Jul 29 17:33:14 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 29 Jul 2015 08:33:14 -0700
Subject: [Mailman-Users] Mailman 3 - Some questions (addition)
In-Reply-To: <594A67F0BEDB4A49AAF8B765EFB7482F3C682F@MBX-S1.rwth-ad.de>
References: <594A67F0BEDB4A49AAF8B765EFB7482F3C682F@MBX-S1.rwth-ad.de>
Message-ID: <55B8F23A.7030903@msapiro.net>

On 7/28/15 11:17 PM, Krinetzki, Stephan wrote:
> Hello,
> 
> The last error in hyperkitty was because the https:// URL was missing in the
> BROWSER_AUDIENCE variable. Now I'm getting a new error:
...
> And the questions from the first mail:
...


Questions about Mailman 3 and particularly Postorius and Hyperkitty are
better posted to the mailman-developers at python.org list
<http://mail.python.org/mailman/listinfo/mailman-developers>. Please
join that list if you are not already a member and post there.

The people working most closely with MM 3 are much more likely to read
your post on mailman-developers. We will soon have a
mailman3-users at mailman3.org list (running on MM 3 of course), but there
are still infrastructure issues to work out before that list will be
operational.

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

From mark at msapiro.net  Wed Jul 29 17:43:40 2015
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 29 Jul 2015 08:43:40 -0700
Subject: [Mailman-Users] Hyperkitty search not working
In-Reply-To: <55B7025A.4090900@one.com>
References: <55B7025A.4090900@one.com>
Message-ID: <55B8F4AC.8030408@msapiro.net>

On 7/27/15 9:17 PM, Shivam Shukla wrote:
> 
> I am using mailman3 in development mode. I have all components working
> and properly running. I have setup some test mailing lists and send mails.
> The issue is that i am not able to use the search feature of hyperkitty
> properly. I am inserting subject and some part of body in search field
> but it never give any result. Please suggest am i doing something wrong
> or search feature does not work the way i am trying to use it.


Questions about Mailman 3 and particularly Postorius and Hyperkitty are
better posted to the mailman-developers at python.org list
<http://mail.python.org/mailman/listinfo/mailman-developers>. Please
join that list if you are not already a member and post there.

The people working most closely with MM 3 are much more likely to read
your post on mailman-developers. We will soon have a
mailman3-users at mailman3.org list (running on MM 3 of course), but there
are still infrastructure issues to work out before that list will be
operational.

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