From mark at msapiro.net  Sun Jul  1 16:27:33 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 1 Jul 2012 07:27:33 -0700
Subject: [Mailman-Users] Mailman / Postfix new list issue
In-Reply-To: <CA+wvyiuP1f+9=DBWwuXYRvKWjeaQ8cQfwysP85jAtp54_vNtKg@mail.gmail.com>
Message-ID: <PC19520120701072733053733e8c63a@Notebook-09>

Dan Offord wrote:
>
>I'm having an issue with any new lists created in Mailman, it appears
>to be forcing each mailing lists host_name to: multiplay.co.uk
>
>So any welcome emails specifically states:
>
>"To post to this list, send your message to:
>
> newlist at multiplay.co.uk"
>
>Where the host/domain for Mailman is set to lists.multiplay.co.uk
>
>My mm_cfg.py is at http://pastie.org/4178388


The relevant lines of which are:

DEFAULT_URL_HOST = 'lists.multiplay.co.uk'
add_virtualhost('lists.multiplay.co.uk')
DEFAULT_EMAIL_HOST = 'lists.multiplay.co.uk'
host_name = 'lists.multiplay.co.uk'

The assignment to host_name in mm_cfg.py does nothing useful. remove it.

add_virtualhost() takes one or two arguments and creates a mapping from
a url host (web host) to an email host. If the email host argument is
ommitted, it is determined by stripping everything up to the first dot
'.' from the url host argument. This is documented in Defaults.py

# ...  If optional emailhost is
# omitted it defaults to urlhost with the first name stripped off, e.g.
#
# add_virtualhost('www.dom.ain')
# VIRTUAL_HOST['www.dom.ain']
# ==> 'dom.ain'

Thus,

add_virtualhost('lists.multiplay.co.uk')

is the same as

add_virtualhost('lists.multiplay.co.uk', 'multiplay.co.uk')

What you want in mm_cfg.py are these 3 lines in this order

DEFAULT_URL_HOST = 'lists.multiplay.co.uk'
DEFAULT_EMAIL_HOST = 'lists.multiplay.co.uk'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

Then, you can fix the host_name of the already created list either from
the web UI General Options page or by running fix_url {see
<http://wiki.list.org/x/mIA9>).

-- 
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  Sun Jul  1 21:12:29 2012
From: dandrews at visi.com (David Andrews)
Date: Sun, 01 Jul 2012 14:12:29 -0500
Subject: [Mailman-Users] Duplicate Messages
Message-ID: <auto-000067350019@mailfront3.g2host.com>

I am getting duplicate messages once a day, the 8:00 a.m. messages 
sent out by every list telling of what messages pending.  My users 
also get two copies of the password reminder once a month.  And ... 
not sure if it is related, but probably, I get two copies of a 
message each morning at 8:00 a.m. from the "Mailman" list telling of 
pending messages.  You can't get at this list to eliminate, so not 
sure what is going on.

Thanks in advance!

Dave


From bsfinkel at att.net  Sun Jul  1 22:31:38 2012
From: bsfinkel at att.net (Barry S, Finkel)
Date: Sun, 01 Jul 2012 15:31:38 -0500
Subject: [Mailman-Users] Duplicate Messages
In-Reply-To: <auto-000067350019@mailfront3.g2host.com>
References: <auto-000067350019@mailfront3.g2host.com>
Message-ID: <4FF0B3AA.5000107@att.net>

On 7/1/2012 2:12 PM, David Andrews wrote:
> I am getting duplicate messages once a day, the 8:00 a.m. messages 
> sent out by every list telling of what messages pending.  My users 
> also get two copies of the password reminder once a month.  And ... 
> not sure if it is related, but probably, I get two copies of a message 
> each morning at 8:00 a.m. from the "Mailman" list telling of pending 
> messages.  You can't get at this list to eliminate, so not sure what 
> is going on.
>
> Thanks in advance!
>
> Dave
>

It sound like you have two crontab entries for some Mailman crons, or 
you have two
crontabs - one in the old style as root and one in the new style as mailman.
--Barry Finkel


From liv3d at multiplay.co.uk  Mon Jul  2 07:12:27 2012
From: liv3d at multiplay.co.uk (Dan Offord)
Date: Mon, 2 Jul 2012 06:12:27 +0100
Subject: [Mailman-Users] Mailman / Postfix new list issue
In-Reply-To: <PC19520120701072733053733e8c63a@Notebook-09>
References: <CA+wvyiuP1f+9=DBWwuXYRvKWjeaQ8cQfwysP85jAtp54_vNtKg@mail.gmail.com>
	<PC19520120701072733053733e8c63a@Notebook-09>
Message-ID: <CA+wvyis8fS4PHuwm3v1zhTVYseHEj+CxhPJR_iagDYQFoWOAtw@mail.gmail.com>

On 1 July 2012 15:27, Mark Sapiro <mark at msapiro.net> wrote:
>
> The relevant lines of which are:
>
> DEFAULT_URL_HOST = 'lists.multiplay.co.uk'
> add_virtualhost('lists.multiplay.co.uk')
> DEFAULT_EMAIL_HOST = 'lists.multiplay.co.uk'
> host_name = 'lists.multiplay.co.uk'
>
> The assignment to host_name in mm_cfg.py does nothing useful. remove it.
>
> add_virtualhost() takes one or two arguments and creates a mapping from
> a url host (web host) to an email host. If the email host argument is
> ommitted, it is determined by stripping everything up to the first dot
> '.' from the url host argument. This is documented in Defaults.py
>
> # ...  If optional emailhost is
> # omitted it defaults to urlhost with the first name stripped off, e.g.
> #
> # add_virtualhost('www.dom.ain')
> # VIRTUAL_HOST['www.dom.ain']
> # ==> 'dom.ain'
>
> Thus,
>
> add_virtualhost('lists.multiplay.co.uk')
>
> is the same as
>
> add_virtualhost('lists.multiplay.co.uk', 'multiplay.co.uk')
>
> What you want in mm_cfg.py are these 3 lines in this order
>
> DEFAULT_URL_HOST = 'lists.multiplay.co.uk'
> DEFAULT_EMAIL_HOST = 'lists.multiplay.co.uk'
> add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
>
> Then, you can fix the host_name of the already created list either from
> the web UI General Options page or by running fix_url {see
> <http://wiki.list.org/x/mIA9>).
>
> --
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
>

Thank you Mark,

That fixed the issue I was seeing :)

Kind Regards,

Dan Offord

Technical Systems Administrator

Multiplay (UK) Ltd, Unit 7 Whitefield, Lepe Road, Blackfield
Southampton, Hampshire, SO45 1XR

Registered in England & Wales No. 3370594

Phone: +44 (0) 845 868 1337 | Direct: +44 (0) 56 000 36985
Twitter: @liv3d | Skype: mpukliv3d
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.

In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster at multiplay.co.uk.


From geoff at QuiteLikely.com  Mon Jul  2 17:02:42 2012
From: geoff at QuiteLikely.com (Geoff Shang)
Date: Mon, 2 Jul 2012 18:02:42 +0300 (IDT)
Subject: [Mailman-Users] Help! How to quell list address in personalised
	messages
Message-ID: <alpine.DEB.2.00.1207021758011.2144@data.home>

Hi,

A bit urgent.

I thought I'd turn on personalisation for an announce list I'm putting 
together, in order to have the person's address in the To field instead of 
the list address.  The box will only be used for this list and messages 
wil only go out about once a month, so performance isn't an issue.

But when I turned on full personalisation and got my Email address in the 
To field, the list address got sent in the Cc field.

Is there any way I can stop this?   I want to keep people from trying to 
post to the list.  I will close other doors as well but there's really no 
need for people to see the list address.

Geoff.


From mark at msapiro.net  Mon Jul  2 17:16:21 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 02 Jul 2012 08:16:21 -0700
Subject: [Mailman-Users] Help! How to quell list address in personalised
 messages
In-Reply-To: <alpine.DEB.2.00.1207021758011.2144@data.home>
References: <alpine.DEB.2.00.1207021758011.2144@data.home>
Message-ID: <4FF1BB45.9020105@msapiro.net>

On 7/2/2012 8:02 AM, Geoff Shang wrote:
> 
> But when I turned on full personalisation and got my Email address in
> the To field, the list address got sent in the Cc field.
> 
> Is there any way I can stop this?   I want to keep people from trying to
> post to the list.  I will close other doors as well but there's really
> no need for people to see the list address.


This is intentional and by design to facilitate people replying to the
list even with full personalization.

If you don't want this, you need to modify
Mailman/Handlers/CookHeaders.py to not add the list posting address to
Cc: or add a custom handler following CookHeaders to remove it.

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




From geoff at QuiteLikely.com  Mon Jul  2 17:42:09 2012
From: geoff at QuiteLikely.com (Geoff Shang)
Date: Mon, 2 Jul 2012 18:42:09 +0300 (IDT)
Subject: [Mailman-Users] Help! How to quell list address in personalised
 messages
In-Reply-To: <4FF1BB45.9020105@msapiro.net>
References: <alpine.DEB.2.00.1207021758011.2144@data.home>
	<4FF1BB45.9020105@msapiro.net>
Message-ID: <alpine.DEB.2.00.1207021839390.2144@data.home>

On Mon, 2 Jul 2012, Mark Sapiro wrote:

> This is intentional and by design to facilitate people replying to the
> list even with full personalization.

Yes but for an announcement-type list you don't want this.

> If you don't want this, you need to modify
> Mailman/Handlers/CookHeaders.py to not add the list posting address to
> Cc: or add a custom handler following CookHeaders to remove it.

Thanks very much.  I just found the same advice you wrote two years ago at 
http://mail.python.org/pipermail/mailman-users/2010-April/069241.html

Lets see if I can do this without serious breakage.

Geoff.


From mark at msapiro.net  Mon Jul  2 19:15:20 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 02 Jul 2012 10:15:20 -0700
Subject: [Mailman-Users] Help! How to quell list address in personalised
	messages
In-Reply-To: <alpine.DEB.2.00.1207021839390.2144@data.home>
References: <alpine.DEB.2.00.1207021758011.2144@data.home>
	<4FF1BB45.9020105@msapiro.net>
	<alpine.DEB.2.00.1207021839390.2144@data.home>
Message-ID: <c785f535-02d1-4712-b315-2d81d549126c@email.android.com>

Geoff Shang <geoff at QuiteLikely.com> wrote:

>On Mon, 2 Jul 2012, Mark Sapiro wrote:
>
>Lets see if I can do this without serious breakage.
>
>Geoff.


If you need help, let me know.


-- 
Mark Sapiro <mark at msapiro.net>
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

From geoff at QuiteLikely.com  Mon Jul  2 19:26:27 2012
From: geoff at QuiteLikely.com (Geoff Shang)
Date: Mon, 2 Jul 2012 20:26:27 +0300 (IDT)
Subject: [Mailman-Users] Help! How to quell list address in personalised
 messages
In-Reply-To: <c785f535-02d1-4712-b315-2d81d549126c@email.android.com>
References: <alpine.DEB.2.00.1207021758011.2144@data.home>
	<4FF1BB45.9020105@msapiro.net>
	<alpine.DEB.2.00.1207021839390.2144@data.home>
	<c785f535-02d1-4712-b315-2d81d549126c@email.android.com>
Message-ID: <alpine.DEB.2.00.1207022025060.2144@data.home>

On Mon, 2 Jul 2012, Mark Sapiro wrote:

> If you need help, let me know.

Think I got it.  Commenting out the block at line 161 (Mailman 2.1.13) 
seems to have done the trick.

Thanks again,
Geoff.


From jdanield at free.fr  Mon Jul  2 20:10:56 2012
From: jdanield at free.fr (jdd)
Date: Mon, 02 Jul 2012 20:10:56 +0200
Subject: [Mailman-Users] remainder post bounce
Message-ID: <4FF1E430.40600@free.fr>

I have a curious situation. I could fix it, so there is no hurry to 
find a better solution, but I wonder where I failed :-).

I have a domain name (culte.org) that hold a mailman mailing lists server.

Under this domain, there is a (virtual) network. The real server is 
savage-reborn.culte.org

When mailman send the messages to the lists, no problem at all, the 
return path is <list-name>@culte.org

but when mailman send the monthly reminder, the return path is 
<listname>@savage-reborn.culte.org.

some recipients do not like to have the extra "savage-reborn" part and 
refuse the mail.

I don't know where I could change this without disturbing the server's 
working.

The MTA is postfix.

I could solve the problem adding savage-reborn in culte.org zone 
definitions.

any idea?

thanks
jd

From mark at msapiro.net  Tue Jul  3 05:22:10 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 2 Jul 2012 20:22:10 -0700
Subject: [Mailman-Users] remainder post bounce
In-Reply-To: <4FF1E430.40600@free.fr>
Message-ID: <PC195201207022022100650a838dbd4@MSAPIRO>

jdd wrote:
>
>When mailman send the messages to the lists, no problem at all, the 
>return path is <list-name>@culte.org
>
>but when mailman send the monthly reminder, the return path is 
><listname>@savage-reborn.culte.org.
>
>some recipients do not like to have the extra "savage-reborn" part and 
>refuse the mail.
>
>I don't know where I could change this without disturbing the server's 
>working.



I'm a bit confused as to what you mean by return path. If you actually
mean the Return-Path: header, it should be <list-name>-bounces at ... in
the case of list posts and mailman-bounces at ... in the case of password
reminders.

In any case, look at the host_name attribute of the 'mailman' site list
on the list's General Options page and if it is
savage-reborn.culte.org, change it to culte.org.

If this is not the issue, I think I'd need to see the full headers from
a password reminder to understand the problem.

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


From andrew.b.watson at nasa.gov  Tue Jul  3 05:54:34 2012
From: andrew.b.watson at nasa.gov (Andrew Watson)
Date: Mon, 2 Jul 2012 20:54:34 -0700
Subject: [Mailman-Users] google tracking code
Message-ID: <BE32444A-90DC-49B8-9458-4272C93D9186@nasa.gov>

How can I put google tracking code in archived email messages?
I am using pipermail.

From jdanield at free.fr  Tue Jul  3 08:26:05 2012
From: jdanield at free.fr (jdd)
Date: Tue, 03 Jul 2012 08:26:05 +0200
Subject: [Mailman-Users] remainder post bounce
In-Reply-To: <PC195201207022022100650a838dbd4@MSAPIRO>
References: <PC195201207022022100650a838dbd4@MSAPIRO>
Message-ID: <4FF2907D.2030400@free.fr>

Le 03/07/2012 05:22, Mark Sapiro a ?crit :

> I'm a bit confused as to what you mean by return path. If you actually
> mean the Return-Path: header,

yes

  it should be<list-name>-bounces at ... in
> the case of list posts and mailman-bounces at ... in the case of password
> reminders.
>

yes it's

linux-31-bounces at culte.org for usual messages

and

mailman-bounces at savage-reborn.culte.org

for the reminder message

> In any case, look at the host_name attribute of the 'mailman' site list
> on the list's General Options page and if it is
> savage-reborn.culte.org, change it to culte.org.

it is culte.org

>
> If this is not the issue, I think I'd need to see the full headers from
> a password reminder to understand the problem.
>

below one of the return message (less the user adress). I guess I 
misconfigured some of the internal mailman (or postfix) config file :-(.

thanks
jdd


Return-Path: <mailman-loop at culte.org>
X-Original-To: jdd at dodin.org
Delivered-To: jdd at dodin.org
Received: from savage-reborn.culte.org 
(ram31-1-82-234-76-241.fbx.proxad.net [82.234.76.241])
     by dodin.org (Postfix) with ESMTP id BDA65252A
     for <jdd at dodin.org>; Sun,  1 Jul 2012 05:00:29 +0200 (CEST)
Received: from savage-reborn.culte.org (localhost [127.0.0.1])
     by savage-reborn.culte.org (Postfix) with ESMTP id 53DFE402A3
     for <jdd at dodin.org>; Sun,  1 Jul 2012 05:01:17 +0200 (CEST)
X-Original-To: mailman-bounces at savage-reborn.culte.org
Delivered-To: mailman-bounces at savage-reborn.culte.org
Received: by savage-reborn.culte.org (Postfix)
  id 4812B402FA; Sun,  1 Jul 2012 05:00:50 +0200 (CEST)
Date: Sun,  1 Jul 2012 05:00:50 +0200 (CEST)
From: MAILER-DAEMON at culte.org (Mail Delivery System)
Subject: Undelivered Mail Returned to Sender
To: mailman-bounces at savage-reborn.culte.org
Auto-Submitted: auto-replied
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
  boundary="8CFA740307.1341111650/savage-reborn.culte.org"
Message-Id: <20120701030050.4812B402FA at savage-reborn.culte.org>
Errors-To: mailman-loop at culte.org
Sender: mailman-loop at culte.org

This is a MIME-encapsulated message.

--8CFA740307.1341111650/savage-reborn.culte.org
Content-Description: Notification
Content-Type: text/plain; charset=us-ascii

This is the mail system at host savage-reborn.culte.org.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                    The mail system

<emmXXXXXXX at enseeiht.fr>: host n7smtp2.enseeiht.fr[147.127.176.23] said:
     553 5.1.8 <emmXXXXXXX at enseeiht.fr>... Domain of sender address
     mailman-bounces at savage-reborn.culte.org does not exist (in reply 
to RCPT TO
     command)

--8CFA740307.1341111650/savage-reborn.culte.org
Content-Description: Delivery report
Content-Type: message/delivery-status

Reporting-MTA: dns; savage-reborn.culte.org
X-Postfix-Queue-ID: 8CFA740307
X-Postfix-Sender: rfc822; mailman-bounces at savage-reborn.culte.org
Arrival-Date: Sun,  1 Jul 2012 05:00:39 +0200 (CEST)

Final-Recipient: rfc822; emXXXXX at enseeiht.fr
Original-Recipient: rfc822;emmXXXXXX at enseeiht.fr
Action: failed
Status: 5.1.8
Remote-MTA: dns; n7smtp2.enseeiht.fr
Diagnostic-Code: smtp; 553 5.1.8 <emmaXXXXXX at enseeiht.fr>... Domain of
     sender address mailman-bounces at savage-reborn.culte.org does not exist

--8CFA740307.1341111650/savage-reborn.culte.org
Content-Description: Undelivered Message
Content-Type: message/rfc822

Return-Path: <mailman-bounces at savage-reborn.culte.org>
Received: from savage-reborn.culte.org (localhost [127.0.0.1])
     by savage-reborn.culte.org (Postfix) with ESMTP id 8CFA740307
     for <emXXXXXX at enseeiht.fr>; Sun,  1 Jul 2012 05:00:39 +0200 (CEST)
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: =?iso-8859-1?q?Rappel_pour_les_abonnements_aux_listes_sur_culte?=
  =?iso-8859-1?q?=2Eorg?=
From: mailman-owner at culte.org
To: emXXXXXX at enseeiht.fr
X-No-Archive: yes
Message-ID: <mailman.109.1341111612.16543.mailman at savage-reborn.culte.org>
Date: Sun, 01 Jul 2012 05:00:12 +0200
Precedence: bulk
X-BeenThere: mailman at savage-reborn.culte.org
X-Mailman-Version: 2.1.14
List-Id: <mailman.savage-reborn.culte.org>
X-List-Administrivia: yes
Errors-To: mailman-bounces at savage-reborn.culte.org
Sender: mailman-bounces at savage-reborn.culte.org

Ceci est un rappel, envoy=E9 une fois par mois, concernant vos
abonnements aux listes de culte.org.  Il contient vos param=E8tres
d'abonnement et la marche =E0 suivre pour les changer ou r=E9silier votre
abonnement =E0 une liste.

Vous pouvez utiliser l'interface web pour changer votre statut ou vos
param=E8tres d'abonnement, vous pouvez aussi y r=E9silier votre
abonnement, choisir de recevoir les messages en mode group=E9 ou encore
d=E9sactiver toute r=E9ception de messages (par exemple si vous partez en
vacances), etc.

En plus de l'interface web, vous pouvez proc=E9der =E0 ces modifications
par courrier =E9lectronique. Pour plus d'information, envoyez un message
=E0 l'adresse '-request' de la liste (par exemple
mailman-request at culte.org) contenant uniquement le mot 'help' dans le
corps du message, vous recevrez alors un courrier vous indiquant la
marche =E0 suivre.

Si vous avez des questions, des probl=E8mes, des commentaires, etc.,
envoyez-les =E0 mailman-owner at culte.org. Merci !

Mots de passe pour emmXXXXXX at enseeiht.fr: =

Liste                                    Mot de passe // URL
----                                     --------  =

linux-31 at culte.org                      YYYYYYY  =

http://culte.org/mailman/options/linux-31/eXXXXXXX%40enseeiht.fr

--8CFA740307.1341111650/savage-reborn.culte.org--

From mark at msapiro.net  Tue Jul  3 09:08:04 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 03 Jul 2012 00:08:04 -0700
Subject: [Mailman-Users] remainder post bounce
In-Reply-To: <4FF2907D.2030400@free.fr>
References: <PC195201207022022100650a838dbd4@MSAPIRO>
	<4FF2907D.2030400@free.fr>
Message-ID: <4FF29A54.6030803@msapiro.net>

On 7/2/2012 11:26 PM, jdd wrote:
> Le 03/07/2012 05:22, Mark Sapiro a ?crit :
> 
>> In any case, look at the host_name attribute of the 'mailman' site list
>> on the list's General Options page and if it is
>> savage-reborn.culte.org, change it to culte.org.
> 
> it is culte.org


There are several things in the message below that say that is not the
case and that the host_name of the 'mailman' list is savage-reborn.culte.org



> below one of the return message (less the user adress). I guess I
> misconfigured some of the internal mailman (or postfix) config file :-(.


Note that there are two messages involved here. There is the original
password reminder that was undeliverable and there is the DSN to you
notifying you of the undeliverable message

> Return-Path: <mailman-loop at culte.org>

The above domain is normally the result of looking up DEFAULT_URL_HOST
in VIRTUAL_HOSTS which in turn is normally DEFAULT_EMAIL_HOST.


> X-Original-To: jdd at dodin.org
> Delivered-To: jdd at dodin.org
> Received: from savage-reborn.culte.org
> (ram31-1-82-234-76-241.fbx.proxad.net [82.234.76.241])
>     by dodin.org (Postfix) with ESMTP id BDA65252A
>     for <jdd at dodin.org>; Sun,  1 Jul 2012 05:00:29 +0200 (CEST)
> Received: from savage-reborn.culte.org (localhost [127.0.0.1])
>     by savage-reborn.culte.org (Postfix) with ESMTP id 53DFE402A3
>     for <jdd at dodin.org>; Sun,  1 Jul 2012 05:01:17 +0200 (CEST)
> X-Original-To: mailman-bounces at savage-reborn.culte.org


The above indicates the envelope sender of the original reminder was
mailman-bounces at savage-reborn.culte.org.


> Delivered-To: mailman-bounces at savage-reborn.culte.org
> Received: by savage-reborn.culte.org (Postfix)
>  id 4812B402FA; Sun,  1 Jul 2012 05:00:50 +0200 (CEST)
> Date: Sun,  1 Jul 2012 05:00:50 +0200 (CEST)
> From: MAILER-DAEMON at culte.org (Mail Delivery System)
> Subject: Undelivered Mail Returned to Sender
> To: mailman-bounces at savage-reborn.culte.org
> Auto-Submitted: auto-replied
> MIME-Version: 1.0
> Content-Type: multipart/report; report-type=delivery-status;
>  boundary="8CFA740307.1341111650/savage-reborn.culte.org"
> Message-Id: <20120701030050.4812B402FA at savage-reborn.culte.org>
> Errors-To: mailman-loop at culte.org
> Sender: mailman-loop at culte.org
> 
> This is a MIME-encapsulated message.
> 
> --8CFA740307.1341111650/savage-reborn.culte.org
> Content-Description: Notification
> Content-Type: text/plain; charset=us-ascii
> 
> This is the mail system at host savage-reborn.culte.org.
> 
> I'm sorry to have to inform you that your message could not
> be delivered to one or more recipients. It's attached below.
> 
> For further assistance, please send mail to postmaster.
> 
> If you do so, please include this problem report. You can
> delete your own text from the attached returned message.
> 
>                    The mail system
> 
> <emmXXXXXXX at enseeiht.fr>: host n7smtp2.enseeiht.fr[147.127.176.23] said:
>     553 5.1.8 <emmXXXXXXX at enseeiht.fr>... Domain of sender address
>     mailman-bounces at savage-reborn.culte.org does not exist (in reply to
> RCPT TO
>     command)
> 
> --8CFA740307.1341111650/savage-reborn.culte.org
> Content-Description: Delivery report
> Content-Type: message/delivery-status
> 
> Reporting-MTA: dns; savage-reborn.culte.org
> X-Postfix-Queue-ID: 8CFA740307
> X-Postfix-Sender: rfc822; mailman-bounces at savage-reborn.culte.org
> Arrival-Date: Sun,  1 Jul 2012 05:00:39 +0200 (CEST)
> 
> Final-Recipient: rfc822; emXXXXX at enseeiht.fr
> Original-Recipient: rfc822;emmXXXXXX at enseeiht.fr
> Action: failed
> Status: 5.1.8
> Remote-MTA: dns; n7smtp2.enseeiht.fr
> Diagnostic-Code: smtp; 553 5.1.8 <emmaXXXXXX at enseeiht.fr>... Domain of
>     sender address mailman-bounces at savage-reborn.culte.org does not exist
> 
> --8CFA740307.1341111650/savage-reborn.culte.org
> Content-Description: Undelivered Message
> Content-Type: message/rfc822


The original reminder follows.

There are several occurrences of savage-reborn.culte.org, some of which
(List-ID: in particular) would not have been rewritten by Postfix and
all of which originate from the host_name of the 'mailman' list.

Please note I am talking about the host_name of the list named
'mailman', not the list named 'linux-31'


> Return-Path: <mailman-bounces at savage-reborn.culte.org>
                                ^^^^^^^^^^^^^^^^^^^^^^^

> Received: from savage-reborn.culte.org (localhost [127.0.0.1])
>     by savage-reborn.culte.org (Postfix) with ESMTP id 8CFA740307
>     for <emXXXXXX at enseeiht.fr>; Sun,  1 Jul 2012 05:00:39 +0200 (CEST)
> MIME-Version: 1.0
> Content-Type: text/plain; charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> Subject: =?iso-8859-1?q?Rappel_pour_les_abonnements_aux_listes_sur_culte?=
>  =?iso-8859-1?q?=2Eorg?=
> From: mailman-owner at culte.org
> To: emXXXXXX at enseeiht.fr
> X-No-Archive: yes
> Message-ID: <mailman.109.1341111612.16543.mailman at savage-reborn.culte.org>
                                                    ^^^^^^^^^^^^^^^^^^^^

> Date: Sun, 01 Jul 2012 05:00:12 +0200
> Precedence: bulk
> X-BeenThere: mailman at savage-reborn.culte.org
                       ^^^^^^^^^^^^^^^^^^^^^^^

> X-Mailman-Version: 2.1.14
> List-Id: <mailman.savage-reborn.culte.org>
                    ^^^^^^^^^^^^^^^^^^^^^^^

> X-List-Administrivia: yes
> Errors-To: mailman-bounces at savage-reborn.culte.org
                             ^^^^^^^^^^^^^^^^^^^^^^^

> Sender: mailman-bounces at savage-reborn.culte.org
                          ^^^^^^^^^^^^^^^^^^^^^^^

> 
> Ceci est un rappel, envoy=E9 une fois par mois, concernant vos
> abonnements aux listes de culte.org.  Il contient vos param=E8tres
> d'abonnement et la marche =E0 suivre pour les changer ou r=E9silier votre
> abonnement =E0 une liste.
> 
> Vous pouvez utiliser l'interface web pour changer votre statut ou vos
> param=E8tres d'abonnement, vous pouvez aussi y r=E9silier votre
> abonnement, choisir de recevoir les messages en mode group=E9 ou encore
> d=E9sactiver toute r=E9ception de messages (par exemple si vous partez en
> vacances), etc.
> 
> En plus de l'interface web, vous pouvez proc=E9der =E0 ces modifications
> par courrier =E9lectronique. Pour plus d'information, envoyez un message
> =E0 l'adresse '-request' de la liste (par exemple
> mailman-request at culte.org) contenant uniquement le mot 'help' dans le
> corps du message, vous recevrez alors un courrier vous indiquant la
> marche =E0 suivre.
> 
> Si vous avez des questions, des probl=E8mes, des commentaires, etc.,
> envoyez-les =E0 mailman-owner at culte.org. Merci !
> 
> Mots de passe pour emmXXXXXX at enseeiht.fr: =
> 
> Liste                                    Mot de passe // URL
> ----                                     --------  =
> 
> linux-31 at culte.org                      YYYYYYY  =
> 
> http://culte.org/mailman/options/linux-31/eXXXXXXX%40enseeiht.fr
> 
> --8CFA740307.1341111650/savage-reborn.culte.org--

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




From jdanield at free.fr  Tue Jul  3 10:10:09 2012
From: jdanield at free.fr (jdd)
Date: Tue, 03 Jul 2012 10:10:09 +0200
Subject: [Mailman-Users] remainder post bounce
In-Reply-To: <4FF29A54.6030803@msapiro.net>
References: <PC195201207022022100650a838dbd4@MSAPIRO>
	<4FF2907D.2030400@free.fr> <4FF29A54.6030803@msapiro.net>
Message-ID: <4FF2A8E1.70803@free.fr>

Le 03/07/2012 09:08, Mark Sapiro a ?crit :

> Please note I am talking about the host_name of the list named
> 'mailman', not the list named 'linux-31'

got it!!!

this list is not listed in the web sreeen, so I even forgot it existed!

of course there where the error (probably because it was the first 
configured one, when my knowledge was even lower than now :-()

thanks a lot.

Your work for mailman is an example of what can be done for the best. 
Impressive. Thanks again

jdd

From mark at msapiro.net  Tue Jul  3 21:29:57 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 3 Jul 2012 12:29:57 -0700
Subject: [Mailman-Users] google tracking code
In-Reply-To: <BE32444A-90DC-49B8-9458-4272C93D9186@nasa.gov>
Message-ID: <PC195201207031229570687e7610ea8@MSAPIRO>

Andrew Watson wrote:

>How can I put google tracking code in archived email messages?
>I am using pipermail.


Existing archived messages or new messages as they are archived?

For new messages it's trivial. Just make a sitewide version of the
article.html template for each supported language that includes the
tracking code. See the FAQ at <http://wiki.list.org/x/jYA9>.

For existing archived messages there are a couple of ways. The easiest
is just run "bin/arch --wipe LISTNAME" on each list after installing
the edited article.html template, but this can be time consuming and
have undesirable side effects if your LISTNAME.mbox files go back a
long way.

The other way is to just write a script to add the tracking code to
every archives/private/*/*/+([0-9]).html file.

In either case, you may then want to fix the change date of the files.
See <http://www.msapiro.net/scripts/update_archive_mtime> for the
rationale and a script to do this. In fact, you could modify that
script to add the tracking code too.

-- 
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  Wed Jul  4 09:57:12 2012
From: stephen at xemacs.org (Stephen J. Turnbull)
Date: Wed, 04 Jul 2012 16:57:12 +0900
Subject: [Mailman-Users] google tracking code
In-Reply-To: <PC195201207031229570687e7610ea8@MSAPIRO>
References: <BE32444A-90DC-49B8-9458-4272C93D9186@nasa.gov>
	<PC195201207031229570687e7610ea8@MSAPIRO>
Message-ID: <87sjd86js7.fsf@uwakimon.sk.tsukuba.ac.jp>

Mark Sapiro writes:

 > The other way is to just write a script to add the tracking code to
 > every archives/private/*/*/+([0-9]).html file.

Shouldn't that be "archives/private/*/*/[0-9]+\.html"?

Steve

From mark at msapiro.net  Wed Jul  4 18:42:36 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 4 Jul 2012 09:42:36 -0700
Subject: [Mailman-Users] google tracking code
In-Reply-To: <87sjd86js7.fsf@uwakimon.sk.tsukuba.ac.jp>
Message-ID: <PC195201207040942360062d00beda2@MSAPIRO>

Stephen J. Turnbullwrote:

>Mark Sapiro writes:
>
> > The other way is to just write a script to add the tracking code to
> > every archives/private/*/*/+([0-9]).html file.
>
>Shouldn't that be "archives/private/*/*/[0-9]+\.html"?


No. What I wrote is a bash extglob, not a regular expression (note '*',
not '.*'). If it were an re it might be something like
"archives/private/[^/]*/[^/]*/[0-9]+\.html".

-- 
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  5 01:58:29 2012
From: stephen at xemacs.org (Stephen J. Turnbull)
Date: Thu, 05 Jul 2012 08:58:29 +0900
Subject: [Mailman-Users] google tracking code
In-Reply-To: <PC195201207040942360062d00beda2@MSAPIRO>
References: <87sjd86js7.fsf@uwakimon.sk.tsukuba.ac.jp>
	<PC195201207040942360062d00beda2@MSAPIRO>
Message-ID: <87liiz6pui.fsf@uwakimon.sk.tsukuba.ac.jp>

Mark Sapiro writes:
 > No.

Sorry!  Gotta stop writing non-urgent mail on planes (especially when
flying out of a disaster area....)

 > What I wrote is a bash extglob

*sigh* Yet another reason to hate bash....  (YMMV of course, not a
criticism of you for using it!)



From rmcleran at yahoo.com  Tue Jul 10 15:50:47 2012
From: rmcleran at yahoo.com (Bob McLeran)
Date: Tue, 10 Jul 2012 06:50:47 -0700 (PDT)
Subject: [Mailman-Users] Subscriber email doesn't post
Message-ID: <1341928247.97359.YahooMailNeo@web113603.mail.gq1.yahoo.com>

On a list which I administer as owner, we have a subscribed address 
ending in "@mail.com" whose email to the list will not post. Originally, 
his posts were returned to him with a "Delivery Status Notification" 
subject line, stating: 
----------
????? This is an automatically generated Delivery Status Notification. 

Delivery to the following recipients was aborted after 0 second(s): 
-----------
Initially, I did not receive a bounce notification as owner when this 
occurred. 

After determining that his ISP was releasing his email to our list 
address, I added his email address to the section of the admin interface 
Privacy Options/Sender Filters/List of non-member addresses whose 
postings should be automatically accepted. After doing that, I received 
bounce notifications when he sent an email to be posted, but the email 
would still not post. 

There are no spam filters which we have implemented that would cause 
this to occur. 

Any ideas what might be occurring and how to fix it? 

From bcanty at apsa.org  Thu Jul 19 16:33:16 2012
From: bcanty at apsa.org (Brian Canty)
Date: Thu, 19 Jul 2012 10:33:16 -0400
Subject: [Mailman-Users] Changing Code and Looks
Message-ID: <6B3A7025196C1A49AABB0E6C80AD5AE2015B4CAB@apsaserv.APSA.local>

Hello - I posted a questions last week about the ability to unsubscribe,
but found out that was not available.

 

Now I ask, it there a way where you can change the language that appears
when you use the following statements?:

 

<MM-Options-Form-Start>

<MM-Editing-Options>

<MM-Form-End>

 

And if you can edit this fields, where do you find them?

 

Thanks for any help.

 

Sincerely,

 

 

Brian Canty

Manager, Computer Information Services

American Psychoanalytic Associaiton

(212) 752-0450 x17

 

www.apsa.org

 


From ml at smtp.fakessh.eu  Sat Jul 21 02:12:58 2012
From: ml at smtp.fakessh.eu (ml)
Date: Sat, 21 Jul 2012 02:12:58 +0200
Subject: [Mailman-Users] mailman force all httpd ssl
Message-ID: <5009F40A.1050701@smtp.fakessh.eu>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

hello guys


I come to you to submit an application problem already

i read this page
http://wiki.list.org/display/DOC/4.27+Securing+Mailman%27s+web+GUI+by+using+Secure+HTTP-SSL
I applied in my setup

force ssl  work only for this url
http://lists.fakessh.eu/mailman/

my config not work for other url
http://lists.fakessh.eu/mailman/listinfo/news

trying to find a solution I'm searching on google is my friend

but not solve my problem

- -- 
  http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC2626742
  gpg --keyserver pgp.mit.edu --recv-key C2626742

  http://urlshort.eu fakessh @
  http://gplus.to/sshfake
  http://gplus.to/sshswilting
  http://gplus.to/john.swilting
  https://lists.fakessh.eu/mailman/
  This list is moderated by me, but all applications will be accepted
  provided they receive a note of presentation
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlAJ9AoACgkQNgqL0sJiZ0JtcwCgsjww6BDiaMedg0tdxmLC35Tc
AL0AnidrqKHqqYj78ngqrGtAmyC+8Zfs
=JrQv
-----END PGP SIGNATURE-----

From ml at smtp.fakessh.eu  Sat Jul 21 03:51:26 2012
From: ml at smtp.fakessh.eu (ml)
Date: Sat, 21 Jul 2012 03:51:26 +0200
Subject: [Mailman-Users] mailman force all httpd ssl
In-Reply-To: <5009F40A.1050701@smtp.fakessh.eu>
References: <5009F40A.1050701@smtp.fakessh.eu>
Message-ID: <500A0B1E.4000105@smtp.fakessh.eu>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Le 21/07/2012 02:12, ml a ?crit :
> hello guys
> 
> 
> I come to you to submit an application problem already
> 
> i read this page 
> http://wiki.list.org/display/DOC/4.27+Securing+Mailman%27s+web+GUI+by+using+Secure+HTTP-SSL
>
> 
I applied in my setup
> 
> force ssl  work only for this url http://lists.fakessh.eu/mailman/
> 
> my config not work for other url 
> http://lists.fakessh.eu/mailman/listinfo/news
> 
> trying to find a solution I'm searching on google is my friend
> 
> but not solve my problem
> 

I tested the various config available with google search

on my centos 6.3 the ssl redirect works only for this url
http://lists.fakessh.eu/mailman


fail other url


- -- 
  http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC2626742
  gpg --keyserver pgp.mit.edu --recv-key C2626742

  http://urlshort.eu fakessh @
  http://gplus.to/sshfake
  http://gplus.to/sshswilting
  http://gplus.to/john.swilting
  https://lists.fakessh.eu/mailman/
  This list is moderated by me, but all applications will be accepted
  provided they receive a note of presentation
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlAKCx4ACgkQNgqL0sJiZ0IGaACdHXSL0glbecKxkp2mFu72GD29
95kAoNvN4oyUv/2qt+1vKN14iu44rIHm
=X+Wb
-----END PGP SIGNATURE-----

From ml at smtp.fakessh.eu  Sat Jul 21 09:10:18 2012
From: ml at smtp.fakessh.eu (ml)
Date: Sat, 21 Jul 2012 09:10:18 +0200
Subject: [Mailman-Users] mailman force all httpd ssl
In-Reply-To: <500A0B1E.4000105@smtp.fakessh.eu>
References: <5009F40A.1050701@smtp.fakessh.eu>
	<500A0B1E.4000105@smtp.fakessh.eu>
Message-ID: <179330fa4f2a60508e77a9481e496e7b@smtp.fakessh.eu>

Le 21/07/2012 03:51, ml a ?crit :
> Le 21/07/2012 02:12, ml a ?crit :
>> hello guys
>
>
>> I come to you to submit an application problem already
>
>> i read this page
>> 
>> http://wiki.list.org/display/DOC/4.27+Securing+Mailman%27s+web+GUI+by+using+Secure+HTTP-SSL
>
>
> I applied in my setup
>
>> force ssl  work only for this url http://lists.fakessh.eu/mailman/
>
>> my config not work for other url
>> http://lists.fakessh.eu/mailman/listinfo/news
>
>> trying to find a solution I'm searching on google is my friend
>
>> but not solve my problem
>
>
> I tested the various config available with google search
>
> on my centos 6.3 the ssl redirect works only for this url
> http://lists.fakessh.eu/mailman
>
>
> fail other url
>



this sample
http://wiki.list.org/display/DOC/4.27+Securing+Mailman%27s+web+GUI+by+using+Secure+HTTP-SSL

not work on my machine
I am obliged to write a config like this


RewriteEngine On
Options +FollowSymlinks
RewriteCond %{HTTPS}        off [NC]
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [L,R=permanent]
RedirectMatch  ^/mailman[/]*$  
https://lists.fakessh.eu/mailman/listinfo

RewriteRule ^/mailman(/.*)  https://%{HTTP_HOST}/mailman$1 
[L,R=permanent]



same issue as provided
only http://lists.fakessh.eu/mailman/
correctly only with ssl redirect
-- 
   http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC2626742
   gpg --keyserver pgp.mit.edu --recv-key C2626742

   http://urlshort.eu fakessh @
   http://gplus.to/sshfake
   http://gplus.to/sshswilting
   http://gplus.to/john.swilting
   https://lists.fakessh.eu/mailman/
   This list is moderated by me, but all applications will be accepted
   provided they receive a note of presentation

-- 
   http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC2626742
   gpg --keyserver pgp.mit.edu --recv-key C2626742

   http://urlshort.eu fakessh @
   http://gplus.to/sshfake
   http://gplus.to/sshswilting
   http://gplus.to/john.swilting
   https://lists.fakessh.eu/mailman/
   This list is moderated by me, but all applications will be accepted
   provided they receive a note of presentation

From ml at smtp.fakessh.eu  Sun Jul 22 04:46:13 2012
From: ml at smtp.fakessh.eu (ml)
Date: Sun, 22 Jul 2012 04:46:13 +0200
Subject: [Mailman-Users] mailman force all httpd ssl
In-Reply-To: <179330fa4f2a60508e77a9481e496e7b@smtp.fakessh.eu>
References: <5009F40A.1050701@smtp.fakessh.eu>
	<500A0B1E.4000105@smtp.fakessh.eu>
	<179330fa4f2a60508e77a9481e496e7b@smtp.fakessh.eu>
Message-ID: <dc9bbe2e1ddf685f1850d1ccf05b5224@smtp.fakessh.eu>



Le 2012-07-21 09:10, ml a ?crit?:
> Le 21/07/2012 03:51, ml a ?crit :
>> Le 21/07/2012 02:12, ml a ?crit :
>>> hello guys
>>
>>
>>> I come to you to submit an application problem already
>>
>>> i read this page
>>> 
>>> http://wiki.list.org/display/DOC/4.27+Securing+Mailman%27s+web+GUI+by+using+Secure+HTTP-SSL
>>
>>
>> I applied in my setup
>>
>>> force ssl  work only for this url http://lists.fakessh.eu/mailman/
>>
>>> my config not work for other url
>>> http://lists.fakessh.eu/mailman/listinfo/news
>>
>>> trying to find a solution I'm searching on google is my friend
>>
>>> but not solve my problem
>>
>>
>> I tested the various config available with google search
>>
>> on my centos 6.3 the ssl redirect works only for this url
>> http://lists.fakessh.eu/mailman
>>
>>
>> fail other url
>>
>
>
>
> this sample
> 
> http://wiki.list.org/display/DOC/4.27+Securing+Mailman%27s+web+GUI+by+using+Secure+HTTP-SSL
>
> not work on my machine
> I am obliged to write a config like this
>
>
> RewriteEngine On
> Options +FollowSymlinks
> RewriteCond %{HTTPS}        off [NC]
> RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [L,R=permanent]
> RedirectMatch  ^/mailman[/]*$  
> https://lists.fakessh.eu/mailman/listinfo
>
> RewriteRule ^/mailman(/.*)  https://%{HTTP_HOST}/mailman$1 
> [L,R=permanent]
>
>
>
> same issue as provided
> only http://lists.fakessh.eu/mailman/
> correctly only with ssl redirect



despite my efforts during these past few days I do not manage to do 
what I want

only http://lists.fakessh.eu/mailman/ correctly redirect



-- 
   http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC2626742
   gpg --keyserver pgp.mit.edu --recv-key C2626742

   http://urlshort.eu fakessh @
   http://gplus.to/sshfake
   http://gplus.to/sshswilting
   http://gplus.to/john.swilting
   https://lists.fakessh.eu/mailman/
   This list is moderated by me, but all applications will be accepted
   provided they receive a note of presentation

From mark at msapiro.net  Sun Jul 22 20:33:43 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 22 Jul 2012 11:33:43 -0700
Subject: [Mailman-Users] mailman force all httpd ssl
In-Reply-To: <dc9bbe2e1ddf685f1850d1ccf05b5224@smtp.fakessh.eu>
References: <5009F40A.1050701@smtp.fakessh.eu>
	<500A0B1E.4000105@smtp.fakessh.eu>
	<179330fa4f2a60508e77a9481e496e7b@smtp.fakessh.eu>
	<dc9bbe2e1ddf685f1850d1ccf05b5224@smtp.fakessh.eu>
Message-ID: <500C4787.5050700@msapiro.net>

On 7/21/2012 7:46 PM, ml wrote:

>> I am obliged to write a config like this
>>
>>
>> RewriteEngine On
>> Options +FollowSymlinks
>> RewriteCond %{HTTPS}        off [NC]
>> RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [L,R=permanent]
>> RedirectMatch  ^/mailman[/]*$  https://lists.fakessh.eu/mailman/listinfo
>>
>> RewriteRule ^/mailman(/.*)  https://%{HTTP_HOST}/mailman$1
>> [L,R=permanent]
>>
>>
>>
>> same issue as provided
>> only http://lists.fakessh.eu/mailman/
>> correctly only with ssl redirect
> 
> 
> 
> despite my efforts during these past few days I do not manage to do what
> I want
> 
> only http://lists.fakessh.eu/mailman/ correctly redirect



So it appears that your RedirectMatch works, but your RewriteRule
directives do not. I don't offhand know why. This is an Apache question,
not a Mailman question. See <http://httpd.apache.org/docs/2.X/rewrite/>
where X is 0, 2 or 4 depending on your Apache version, and/or see
<http://httpd.apache.org/userslist.html>.

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


From adamsca at gmail.com  Mon Jul 23 22:17:10 2012
From: adamsca at gmail.com (Christopher Adams)
Date: Mon, 23 Jul 2012 13:17:10 -0700
Subject: [Mailman-Users] upgrade path from 2.1.13 to 2.1.15
Message-ID: <CAA13W+8ab407Jdj-Cngb_Xr1t64VKgUEofEdzzNLOzCQhnt1XQ@mail.gmail.com>

Hello,

I am finally getting around to to upgrading Mailman 2.1.13. Should I
upgrade to 2.1.14 and then upgrade to 2.1.15, or just go directly to 2.1.15?

It sounds like 2.1.15 changes some files significantly, but the process
remains the same. Basically, do as if installing mailman initially, using
all parameters that were previously used.

Am I correct in my assumptions and is there anything else that I should
know. based on what others experiences when upgrading.

Many thanks,

-- 
Christopher Adams
adamsca at gmail.com

From mark at msapiro.net  Tue Jul 24 03:53:24 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 23 Jul 2012 18:53:24 -0700
Subject: [Mailman-Users] Subscriber email doesn't post
In-Reply-To: <1341928247.97359.YahooMailNeo@web113603.mail.gq1.yahoo.com>
References: <1341928247.97359.YahooMailNeo@web113603.mail.gq1.yahoo.com>
Message-ID: <500E0014.1060704@msapiro.net>

On 7/10/2012 6:50 AM, Bob McLeran wrote:
> On a list which I administer as owner, we have a subscribed address 
> ending in "@mail dot com" whose email to the list will not post. Originally, 
> his posts were returned to him with a "Delivery Status Notification" 
> subject line, stating: 
> ----------
>       This is an automatically generated Delivery Status Notification. 
> 
> Delivery to the following recipients was aborted after 0 second(s): 
> -----------


And what was the recipient address?


> Initially, I did not receive a bounce notification as owner when this 
> occurred. 


You only receive a notice when a bounce triggers disabling delivery. In
any case, this is apparently not a bounce of a message from Mailman to
the user, but a bounce of the user's post to Mailman, so you wouldn't
see anything from Mailman because Mailman never saw the post.


> After determining that his ISP was releasing his email to our list 
> address, I added his email address to the section of the admin interface 
> Privacy Options/Sender Filters/List of non-member addresses whose 
> postings should be automatically accepted. After doing that, I received 
> bounce notifications when he sent an email to be posted, but the email 
> would still not post. 


And what do these notices say? Note that if user at mail dot com is a list
member, adding user at mail dot com to accept_these_nonmembers should make no
difference.


> Any ideas what might be occurring and how to fix it? 


Not without more information such as MTA log entries and Mailman log
entries.

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


From tim at IntegraStrategic.com  Mon Jul 16 15:10:09 2012
From: tim at IntegraStrategic.com (Tim Brooks)
Date: Mon, 16 Jul 2012 09:10:09 -0400
Subject: [Mailman-Users] Unwanted Blank Attachments
Message-ID: <008501cd6354$542efa60$fc8cef20$@com>

I've recently switched servers so had to re-set up all of my mail lists.  I
set them up on the new server exactly how they were set up on the old
server.  However, new messages now include a blank .txt file (ATT00115.txt).

 

Under Non-digest options, both the Header and Footer are blank (including no
extra spaces).  

 

I do need to allow attachments, but I'd like to remove these blank ones.  

 

Can anyone help?

 

Thanks.

 

Tim Brooks

 

 

 

Integra Strategic Technologies Consulting, LLC

30 Danforth Street, Suite 305

Portland, Maine 04101

207.871.8008

http://www.IntegraStrategic.com

 


From mark at msapiro.net  Tue Jul 24 04:15:41 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 23 Jul 2012 19:15:41 -0700
Subject: [Mailman-Users] Unwanted Blank Attachments
In-Reply-To: <008501cd6354$542efa60$fc8cef20$@com>
References: <008501cd6354$542efa60$fc8cef20$@com>
Message-ID: <500E054D.9000900@msapiro.net>

On 7/16/2012 6:10 AM, Tim Brooks wrote:
> I've recently switched servers so had to re-set up all of my mail lists.  I
> set them up on the new server exactly how they were set up on the old
> server.  However, new messages now include a blank .txt file (ATT00115.txt).
> 
>  
> 
> Under Non-digest options, both the Header and Footer are blank (including no
> extra spaces).  


Please send a test post to your list and then post the raw message
including all headers and sub-part headers for the message as sent to
the list and the message as received from the 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  Tue Jul 24 04:48:56 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 23 Jul 2012 19:48:56 -0700
Subject: [Mailman-Users] Changing Code and Looks
In-Reply-To: <6B3A7025196C1A49AABB0E6C80AD5AE2015B4CAB@apsaserv.APSA.local>
References: <6B3A7025196C1A49AABB0E6C80AD5AE2015B4CAB@apsaserv.APSA.local>
Message-ID: <500E0D18.2080606@msapiro.net>

On 7/19/2012 7:33 AM, Brian Canty wrote:
> Hello - I posted a questions last week about the ability to unsubscribe,
> but found out that was not available.
> 
>  
> 
> Now I ask, it there a way where you can change the language that appears
> when you use the following statements?:
> 
>  
> 
> <MM-Options-Form-Start>
> 
> <MM-Editing-Options>
> 
> <MM-Form-End>


Those tags appear only in the listinfo.html template for a list. The
<MM-Options-Form-Start> and <MM-Form-End> tags generate only HTML <FORM
...> and </FORM> tags respectively and require no translation.

The text generated by the <MM-Editing-Options> tag should be translated
to the list's preferred_language or the language selected by the user at
the top of the listinfo page.


> And if you can edit this fields, where do you find them?


See the definition of FormatEditingOption in Mailman/HTMLFormatter.py
and also the definition of list_listinfo in Mailman/Cgi/listinfo.py.

Note that if you change the English text in FormatEditingOption(), you
will break all the i18n translations of this text unless you update the
respective message catalogs.

Probably a better way to deal with this is to just replace the
<MM-Editing-Options> tag in the listinfo.html template with the desired
result. See the FAQ at <http://wiki.list.org/x/jYA9> for info on where
to put edited templates.

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


From turnbull at sk.tsukuba.ac.jp  Tue Jul 24 05:42:52 2012
From: turnbull at sk.tsukuba.ac.jp (Stephen J. Turnbull)
Date: Tue, 24 Jul 2012 12:42:52 +0900
Subject: [Mailman-Users]  upgrade path from 2.1.13 to 2.1.15
In-Reply-To: <CAA13W+8ab407Jdj-Cngb_Xr1t64VKgUEofEdzzNLOzCQhnt1XQ@mail.gmail.com>
References: <CAA13W+8ab407Jdj-Cngb_Xr1t64VKgUEofEdzzNLOzCQhnt1XQ@mail.gmail.com>
Message-ID: <87zk6p25ab.fsf@uwakimon.sk.tsukuba.ac.jp>

Christopher Adams writes:

 > I am finally getting around to to upgrading Mailman 2.1.13. Should
 > I upgrade to 2.1.14 and then upgrade to 2.1.15, or just go directly
 > to 2.1.15?

You can just go directly.  Of course check the "UPGRADING" document
for a refresher, but there are no particular tasks since 2.1.5.  So I
don't think list configs or site configs changed in any way you need
to worry about (ie, new options will have reasonable settings in
Defaults.py).  Review the "NEWS" document to see if any of the changes
in available options are things you would like to take advantage of.

Most important, check "NEWS" to see if any defaults have changed in ways
you don't like.  (I don't see any in a quick look, but I only looked
hard enough to verify the names of the documents you need to look at.)


From mark at msapiro.net  Tue Jul 24 05:59:00 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 23 Jul 2012 20:59:00 -0700
Subject: [Mailman-Users] upgrade path from 2.1.13 to 2.1.15
In-Reply-To: <CAA13W+8ab407Jdj-Cngb_Xr1t64VKgUEofEdzzNLOzCQhnt1XQ@mail.gmail.com>
References: <CAA13W+8ab407Jdj-Cngb_Xr1t64VKgUEofEdzzNLOzCQhnt1XQ@mail.gmail.com>
Message-ID: <500E1D84.9010406@msapiro.net>

On 7/23/2012 1:17 PM, Christopher Adams wrote:
> Hello,
> 
> I am finally getting around to to upgrading Mailman 2.1.13. Should I
> upgrade to 2.1.14 and then upgrade to 2.1.15, or just go directly to 2.1.15?


Just upgrade directly to 2.1.15. There's no need to do any intermediate
upgrades.


> It sounds like 2.1.15 changes some files significantly, but the process
> remains the same. Basically, do as if installing mailman initially, using
> all parameters that were previously used.


That's correct.

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


From tim at IntegraStrategic.com  Tue Jul 24 15:16:27 2012
From: tim at IntegraStrategic.com (Tim Brooks)
Date: Tue, 24 Jul 2012 09:16:27 -0400
Subject: [Mailman-Users] Unwanted Blank Attachments
In-Reply-To: <500E054D.9000900@msapiro.net>
References: <008501cd6354$542efa60$fc8cef20$@com>
	<500E054D.9000900@msapiro.net>
Message-ID: <0db401cd699e$88754b30$995fe190$@com>

>On 7/16/2012 6:10 AM, Tim Brooks wrote:
>> I've recently switched servers so had to re-set up all of my mail 
>> lists.  I set them up on the new server exactly how they were set up 
>> on the old server.  However, new messages now include a blank .txt file
(ATT00115.txt).
>> 
>>  
>> 
>> Under Non-digest options, both the Header and Footer are blank 
>> (including no extra spaces).

On 7/23/2012 10:16 PM, Mark Sapiro wrote:

>Please send a test post to your list and then post the raw message
>including all headers and sub-part headers for the message as sent to
>the list and the message as received from the list.



Below is the email, complete with headers, I sent to the list when I first
moved it to the new server.  I have replaced the domain name of the list
with ********** as it's a private list.

I've compared the settings from the original list with the new list, and
they're the same, but for the fact that the new list is using an upgraded
version of mailman and has a couple of additional settings.

Thanks.

Tim


Return-Path: <crust-bounces@**********.com>
Delivered-To: tim at MYDOMAIN.com
Received: from smtp47.gate.dfw1a (smtp47.gate.dfw1a.rsapps.net
[172.20.100.47])
	by store81a.mail.dfw1a (SMTP Server) with ESMTP id 548403F0001
	for <tim at MYDOMAIN.com>; Mon, 16 Jul 2012 08:44:51 -0400 (EDT)
X-Virus-Scanned: OK
X-MessageSniffer-Scan-Result: 0
X-MessageSniffer-Rules: 0-0-0-8994-c
X-CMAE-Scan-Result: 0
X-CNFS-Analysis: v=1.0 c=1 a=wTWYLeKZ-VwA:10 a=htW1509WfwoA:10
a=EOsq1xBmYeUA:10 a=wPDyFdB5xvgA:10 a=siZhNAJ/1NhgFXJ/OGxQSg==:17
a=M_2BNmdbAAAA:8 a=IIiOoWDVaXiRcrJEK2gA:9 a=CjuIK1q_8ugA:10
a=MO3UcEST6AUA:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=EpTU8DL7xl5Q5M-dp4IA:9
a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10
Received: from [50.57.0.7] ([50.57.0.7:37760] helo=smtp27.gate.ord1b)
	by smtp47.gate.dfw1a.rsapps.net (envelope-from
<crust-bounces@**********.com>)
	(ecelerity 2.2.3.49 r(42060/42061)) with ESMTPS (cipher=AES256-SHA) 
	id CD/5E-16975-3CC04005; Mon, 16 Jul 2012 08:44:51 -0400
X-Spam-Exception: WHITELISTED
X-Spam-Threshold: 95
X-Spam-Score: 0
X-Spam-Flag: NO
X-Virus-Scanned: OK
Authentication-Results:  smtp27.gate.ord1b.rsapps.net
x-tls.subject="/C=US/ST=Virginia/L=Herndon/O=Parallels/OU=Parallels
Panel/CN=Parallels Panel/emailAddress=info at parallels.com"; auth=fail
(cipher=AES256-SHA)
X-MessageSniffer-Scan-Result: 0
X-MessageSniffer-Rules: 0-0-0-7973-c
X-CMAE-Scan-Result: 0
X-CNFS-Analysis: v=1.0 c=1 a=htW1509WfwoA:10 a=EOsq1xBmYeUA:10
a=wPDyFdB5xvgA:10 a=M_2BNmdbAAAA:8 a=IIiOoWDVaXiRcrJEK2gA:9
a=CjuIK1q_8ugA:10 a=MO3UcEST6AUA:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8
a=EpTU8DL7xl5Q5M-dp4IA:9 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10
a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10
X-Orig-To: tim at MYDOMAIN.com
X-Originating-Ip: [216.70.82.193]
Received: from [216.70.82.193] ([216.70.82.193:50693]
helo=SERVERNAME.MYDOMAIN.com)
	by smtp27.gate.ord1b.rsapps.net (envelope-from
<crust-bounces@***********.com>)
	(ecelerity 2.2.3.49 r(42060/42061)) with ESMTPS (cipher=AES256-SHA
	subject="/C=US/ST=Virginia/L=Herndon/O=Parallels/OU=Parallels
Panel/CN=Parallels Panel/emailAddress=info at parallels.com") 
	id 59/48-09305-2CC04005; Mon, 16 Jul 2012 08:44:50 -0400
Received: (qmail 7492 invoked from network); 16 Jul 2012 08:44:43 -0400
Received: from localhost (HELO MYDOMAIN.com) (127.0.0.1)
  by localhost with ESMTPA; 16 Jul 2012 08:44:43 -0400
Delivered-To: 14-crust@***********.com
Received: (qmail 7307 invoked from network); 16 Jul 2012 08:44:42 -0400
Received-SPF: none (no valid SPF record)
Received: from smtp166.dfw.emailsrvr.com (67.192.241.166)
	by MYDOMAIN.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
	16 Jul 2012 08:44:42 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by smtp6.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id
	A83DD2708AD
	for <crust@***********.com>; Mon, 16 Jul 2012 08:44:41 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp6.relay.dfw1a.emailsrvr.com (Authenticated sender:
	tim-AT-MYDOMAIN.com) with ESMTPA id 61BD22708A9
	for <crust@**********.com>; Mon, 16 Jul 2012 08:44:41 -0400 (EDT)
From: "Tim Brooks" <tim at MYDOMAIN.com>
To: "'Crust'" <crust@***********.com>
Subject: This morning in Portland
Date: Mon, 16 Jul 2012 08:44:26 -0400
Organization: MY COMPANY
Message-ID: <006401cd6350$bc2fdfc0$348f9f40$@com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac1jULullQ9zILKWSYOkP/UGAwF8Hg==
Content-Language: en-us
X-BeenThere: crust@***********.com
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tim at MYDOMAIN.com
List-Id: <crust. ***********.com>
List-Unsubscribe: <http://lists. ***********.com/mailman/listinfo/crust>,
	<mailto:crust-request@***********.com?subject=unsubscribe>
List-Archive: <http://lists. ***********.com/pipermail/crust>
List-Post: <mailto:crust@***********.com>
List-Help: <mailto:crust-request@***********.com?subject=help>
List-Subscribe: <http://lists. ***********.com/mailman/listinfo/crust>,
	<mailto:crust-request@***********.com?subject=subscribe>
Content-Type: multipart/mixed;
boundary="===============3440022683609731601=="
Sender: crust-bounces@***********.com
Errors-To: crust-bounces@***********.com 

Good morning, Crust.  I have moved all mailing lists from one server to
another, so I'm just sending a test message.  You don't need to reply.

Tim


From mark at msapiro.net  Wed Jul 25 05:54:38 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 24 Jul 2012 20:54:38 -0700
Subject: [Mailman-Users] Unwanted Blank Attachments
In-Reply-To: <0db401cd699e$88754b30$995fe190$@com>
References: <008501cd6354$542efa60$fc8cef20$@com>
	<500E054D.9000900@msapiro.net>
	<0db401cd699e$88754b30$995fe190$@com>
Message-ID: <500F6DFE.8080007@msapiro.net>

On 7/24/2012 6:16 AM, Tim Brooks wrote:
> 
> Below is the email, complete with headers, I sent to the list when I first
> moved it to the new server.  I have replaced the domain name of the list
> with ********** as it's a private list.


This is either not the complete email or it is somehow defective. The
message headers show:

Content-Type: multipart/mixed;
 boundary="===============3440022683609731601=="

but there are no message boundaries or sub-part headers in the message
body. This appears to be a message as received from the list.

1) Are you certain this is the complete, raw message as received from
the list?

2) Do you have the complete, raw message that you sent to the list,
e.g., from a "sent" folder?

What I want to see is the complete MIME structure of a message as sent
to the list and that of the same message as received from the list.


> I've compared the settings from the original list with the new list, and
> they're the same, but for the fact that the new list is using an upgraded
> version of mailman and has a couple of additional settings.
[...]
> X-Mailman-Version: 2.1.9


Perhaps an upgrade for you, but still old. 2.1.9 was released in Sept,
2006. The current version is 2.1.15, released last month.

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


From es at fruitcom.com  Wed Jul 25 12:53:56 2012
From: es at fruitcom.com (Eric Smith)
Date: Wed, 25 Jul 2012 12:53:56 +0200
Subject: [Mailman-Users] configuration of mailman with postfix
Message-ID: <mailbox-11730-1343209859-252216@pepper>

Hi

I have the following versions mailman 1:2.1.14-3 on postfix 2.9.1-5 and Ubuntu 12.04 LTS

When I configure post install with the following instructionsi such as this one:
http://free-electrons.com/blog/mailman-howto-ubuntu-10-04/

My installation is for lists on virtual domains
NOT foobar.fruitcom.com
but complete virtual domains, in  this example
foobar.com

Postfix reports a warning:
warning: /etc/postfix/main.cf: unused parameter: mailman_destination_recipient_limit=1

Mails sent to one of the list committee at foobar.com give the following error:
<"|/var/lib/mailman/mail/mailman post committee"@fruitcom.com>
(expanded from
    <committee at foobar.com>): unknown user: "|/var/lib/mailman/mail/mailman post committee"

Is there a suggestion to address this particular issue which I
think is the expansion to `committee"@fruitcom.com' ,
alternatively, are there other instructions 

Thanks.

-- 
Best regards,
Eric Smith
Mobile: 00 31 6 455 09313 - Tel Wageningen: +31 317 728888

From mark at msapiro.net  Thu Jul 26 07:11:15 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 25 Jul 2012 22:11:15 -0700
Subject: [Mailman-Users] configuration of mailman with postfix
In-Reply-To: <mailbox-11730-1343209859-252216@pepper>
Message-ID: <PC195201207252211150968a9fc6997@MSAPIRO>

Eric Smith wrote:
>
>When I configure post install with the following instructionsi such as this one:
>http://free-electrons.com/blog/mailman-howto-ubuntu-10-04/


Please see the FAQ at <http://wiki.list.org/x/OIDD>.


>My installation is for lists on virtual domains
>NOT foobar.fruitcom.com
>but complete virtual domains, in  this example
>foobar.com
>
>Postfix reports a warning:
>warning: /etc/postfix/main.cf: unused parameter: mailman_destination_recipient_limit=1


This is only applicable if you are using a 'mailman' transport with
postfix_to_mailman.py. It should not be included in main.cf if you are
delivering via aliases.


>Mails sent to one of the list committee at foobar.com give the following error:
><"|/var/lib/mailman/mail/mailman post committee"@fruitcom.com>
>(expanded from
>    <committee at foobar.com>): unknown user: "|/var/lib/mailman/mail/mailman post committee"
>
>Is there a suggestion to address this particular issue which I
>think is the expansion to `committee"@fruitcom.com' ,
>alternatively, are there other instructions 


The actual alias should not have the '@fruitcom.com' bit. Where does
this come from? Did Mailman generate it in data/aliases or did you
manually edit Mailman's data/aliases or /etc/aliases?

See the installation manual at
<http://www.list.org/mailman-install/node12.html>.


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


From gary at roksw.com  Fri Jul 27 21:20:14 2012
From: gary at roksw.com (Gary Kopp)
Date: Fri, 27 Jul 2012 13:20:14 -0600
Subject: [Mailman-Users] txt.gz character encoding
Message-ID: <002801cd6c2c$daef0230$90cd0690$@roksw.com>

I am trying to download Pipermail archives from
http://lists.xwiki.org/pipermail/users/. They are offered in txt.gz files. I
now understand that even though it is not immediately obvious, I can
download the uncompressed .txt versions by modifying the URL, and the
resulting files are fine. But if I download one of the txt.gz files and
unzip it to create a .txt file the results are undecipherable. It looks like
a different character encoding was used. The beginning of the unzipped file
has the host server's path in clear text at the top (information that is not
in the .txt file downloaded directly, BTW), but the rest is gibberish. Is
there something special about the process that Pipermail uses to produce the
.gz files, or is this something xwiki.org might have changed?

--Gary


From mark at msapiro.net  Sat Jul 28 18:28:18 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 28 Jul 2012 09:28:18 -0700
Subject: [Mailman-Users] txt.gz character encoding
In-Reply-To: <002801cd6c2c$daef0230$90cd0690$@roksw.com>
Message-ID: <PC1952012072809281709848003bbe9@MSAPIRO>

Gary Kopp wrote:

>I am trying to download Pipermail archives from
>http://lists.xwiki.org/pipermail/users/. They are offered in txt.gz files. I
>now understand that even though it is not immediately obvious, I can
>download the uncompressed .txt versions by modifying the URL, and the
>resulting files are fine. But if I download one of the txt.gz files and
>unzip it to create a .txt file the results are undecipherable. It looks like
>a different character encoding was used. The beginning of the unzipped file
>has the host server's path in clear text at the top (information that is not
>in the .txt file downloaded directly, BTW), but the rest is gibberish. Is
>there something special about the process that Pipermail uses to produce the
>.gz files, or is this something xwiki.org might have changed?


Mailman/pipermail creates the .txt.gz files in one of two ways
depending on configuration, but both use the same underlying process.
In either case, the message being archived is appended to the .txt
text file.

In the default case, that's all that's done, but Mailman's
cron/nightly_gzip is run overnight to (re)create the .txt.gz file from
the .txt file.

If the installation has set GZIP_ARCHIVE_TXT_FILES to a true value in
mm_cfg.py, when the message is added to the .txt file, the .txt.gz is
(re)created from the .txt file at that time. This involves more
overhead than the default but avoids the issue of messages added
during a day not being in the .txt.gz file until the next day.

In my case, I avoid both the overhead and the delay issue by just not
running cron/nightly_gzip. Then the files served from the archive TOC
page are the .txt files as there are no .txt.gz files.

None of the above addresses your question however. To answer your
question, whether the gzipping is done on the fly by pipermail or
nightly by cron/nightly_gzip or both, it is done via the Python gzip
module which in turn relies on the Python zlib module to do the actual
comperssion.

It appears that there is something in this process in the xwiki.org
installation that actually gzips the file twice.

[msapiro at MSAPIRO ~/Desktop]$ file 2012-July.txt.gz
2012-July.txt.gz: gzip compressed data, from Unix
[msapiro at MSAPIRO ~/Desktop]$ gunzip 2012-July.txt.gz
[msapiro at MSAPIRO ~/Desktop]$ file 2012-July.txt
2012-July.txt: gzip compressed data, was
"/var/lib/mailman/archives/private/users/2012-July.txt", last
modified: Fri Jul 27 20:27:03 2012, max compression


I.e., it appears the
/var/lib/mailman/archives/private/users/2012-July.txt was compressed
by gzip with it's (default) --name option and then the result was
gzipped again.

You can recover the original .txt file from the .txt.gz file in this
case by, e.g.

[msapiro at MSAPIRO ~/Desktop]$ gunzip 2012-July.txt.gz
[msapiro at MSAPIRO ~/Desktop]$ mv 2012-July.txt 2012-July.txt.gz
[msapiro at MSAPIRO ~/Desktop]$ gunzip --no-name 2012-July.txt.gz


This situation is specific to the xwiki.org installation.

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


From mailman at veggiechinese.net  Sat Jul 28 18:38:06 2012
From: mailman at veggiechinese.net (William Yardley)
Date: Sat, 28 Jul 2012 09:38:06 -0700
Subject: [Mailman-Users] A simple unsubscribe
In-Reply-To: <20120629183906.0b398c1a@abydos.stargate.org.uk>
References: <6B3A7025196C1A49AABB0E6C80AD5AE2015B4BC3@apsaserv.APSA.local>
	<20120629183906.0b398c1a@abydos.stargate.org.uk>
Message-ID: <20120728163806.GB18588@mitch.veggiechinese.net>

On Fri, Jun 29, 2012 at 06:39:06PM +0100, Brad Rogers wrote:
> On Fri, 29 Jun 2012 11:51:51 -0400 "Brian Canty" <bcanty at apsa.org> wrote:
> 
> > Hello - I was wondering if anyone has a way to provide subscribers a
> > simple and easy way to unsubscribe from a mailing list.  I do not

> What's wrong with the current challenge and response method?  Stops
> people from maliciously (un)subscribing others.

Even if it's not primarily intended for that purpose, Mailman is used
extensively as (and can be configured as) an announcement list, vs. a
traditional discussion list. In that context (where none of the members
can post, or learn the email address of other members, and therefore
won't accidentally post their unsub link to the list), it makes sense to
have a one-click unsubscribe. While you might "maliciously" try to
unsubscribe someone you don't like on a discussion list, there are good
policy or legal reasons in certain cases to make *subscription*
difficult, and *unsubscription* easy.

[Yes, I understand that it's possible to do this already; just
responding to the "why" of your question]

While I don't use Mailman for this purpose, I do think that it would be
great if the new version had a way to unsubscribe users via some kind of
goop, rather than via their password.

w


From khillo100 at hotmail.com  Sun Jul 29 15:01:56 2012
From: khillo100 at hotmail.com (Khalil Abbas)
Date: Sun, 29 Jul 2012 16:01:56 +0300
Subject: [Mailman-Users] postsuper
Message-ID: <BLU171-DS30752A7E538D49442FB646FBC70@phx.gbl>

Hello, it?s been quite a while since I posted here, I kinda miss u guyz:)

I?m running a list of 3 Mil. subscribers for a local news agency as follows:

the whole list is hosted on a 32GBs Ram server, 10 domains, 30 lists, 100,000 subscribers each list..

the mail is distributed thru a relay of 120 servers identified as MX records in the main server?s domains? DNS zones.. 

the question is, I noticed that mail delivery is slow, and it gets faster when I use: ?postsuper ?r ALL? .. do u think it?s a good idea if I added it as a cronjob that runs every minute? or better split the list into several servers??

Thanks..

From mark at msapiro.net  Sun Jul 29 16:38:42 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 29 Jul 2012 07:38:42 -0700
Subject: [Mailman-Users] postsuper
In-Reply-To: <BLU171-DS30752A7E538D49442FB646FBC70@phx.gbl>
References: <BLU171-DS30752A7E538D49442FB646FBC70@phx.gbl>
Message-ID: <50154AF2.9090402@msapiro.net>

On 7/29/2012 6:01 AM, Khalil Abbas wrote:
> 
> the question is, I noticed that mail delivery is slow, and it gets faster when I use: postsuper r ALL .. do u think its a good idea if I added it as a cronjob that runs every minute? or better split the list into several servers??


See <http://www.postfix.org/TUNING_README.html#hammer>

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


From khillo100 at hotmail.com  Sun Jul 29 20:20:39 2012
From: khillo100 at hotmail.com (Khalil Abbas)
Date: Sun, 29 Jul 2012 21:20:39 +0300
Subject: [Mailman-Users] postsuper
In-Reply-To: <50154AF2.9090402@msapiro.net>
References: <BLU171-DS30752A7E538D49442FB646FBC70@phx.gbl>
	<50154AF2.9090402@msapiro.net>
Message-ID: <BLU171-DS14C493E850CB2FE3301846FBC70@phx.gbl>

Hi, Thanks for the tip, but my problem isn?t with deferred mail, no mail is 
getting rejected from the remote MTA's.. but my problem is that the main 
hardware node is distributing the mail over the 120 MX nodes slowly.. I have 
set the SMTP_MAX_RCPTS to 5 per message for better delivery to several MTA's 
, which means 3 million subscribers are delivered in groups of 5.. resulting 
600,000 messages to be distributed by the main hardware node.. is that too 
much? should I split them to several servers??

Thanks..


-----Original Message----- 
From: Mark Sapiro
Sent: Sunday, July 29, 2012 5:38 PM
To: Khalil Abbas
Cc: mailman-users at python.org
Subject: Re: [Mailman-Users] postsuper

On 7/29/2012 6:01 AM, Khalil Abbas wrote:
>
> the question is, I noticed that mail delivery is slow, and it gets faster 
> when I use: 
postsuper r ALL
 .. do u think its a good idea if I added 
> it as a cronjob that runs every minute? or better split the list into 
> several servers??


See <http://www.postfix.org/TUNING_README.html#hammer>

-- 
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 30 01:17:01 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 29 Jul 2012 16:17:01 -0700
Subject: [Mailman-Users] postsuper
In-Reply-To: <BLU171-DS14C493E850CB2FE3301846FBC70@phx.gbl>
References: <BLU171-DS30752A7E538D49442FB646FBC70@phx.gbl>
	<50154AF2.9090402@msapiro.net>
	<BLU171-DS14C493E850CB2FE3301846FBC70@phx.gbl>
Message-ID: <5015C46D.3050501@msapiro.net>

On 7/29/2012 11:20 AM, Khalil Abbas wrote:
> Hi, Thanks for the tip, but my problem isn?t with deferred mail,


Then why would "postsuper -r ALL" have any effect?


> no mail
> is getting rejected from the remote MTA's.. but my problem is that the
> main hardware node is distributing the mail over the 120 MX nodes
> slowly.. I have set the SMTP_MAX_RCPTS to 5 per message for better
> delivery to several MTA's , which means 3 million subscribers are
> delivered in groups of 5.. resulting 600,000 messages to be distributed
> by the main hardware node.. is that too much? should I split them to
> several servers??


Perhaps if you asked your question on a list or forum devoted to
configuring hardware and MTAs for delivering large volumes of mail,
you'd get a better response. This list is for support of Mailman. As far
as I can tell, your issue is downstream of Mailman after Mailman has
successfully delivered your mail to your main outgoing MTA and is
therefore, not a Mailman issue.

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


From khillo100 at hotmail.com  Mon Jul 30 02:57:51 2012
From: khillo100 at hotmail.com (Khalil Abbas)
Date: Mon, 30 Jul 2012 03:57:51 +0300
Subject: [Mailman-Users] postsuper
In-Reply-To: <5015C46D.3050501@msapiro.net>
References: <BLU171-DS30752A7E538D49442FB646FBC70@phx.gbl>
	<50154AF2.9090402@msapiro.net>
	<BLU171-DS14C493E850CB2FE3301846FBC70@phx.gbl>
	<5015C46D.3050501@msapiro.net>
Message-ID: <BLU171-DS34028F84742946EF7B44F4FBC60@phx.gbl>

you're the man :)

-----Original Message----- 
From: Mark Sapiro
Sent: Monday, July 30, 2012 2:17 AM
To: Khalil Abbas
Cc: mailman-users at python.org
Subject: Re: [Mailman-Users] postsuper

On 7/29/2012 11:20 AM, Khalil Abbas wrote:
> Hi, Thanks for the tip, but my problem isn?t with deferred mail,


Then why would "postsuper -r ALL" have any effect?


> no mail
> is getting rejected from the remote MTA's.. but my problem is that the
> main hardware node is distributing the mail over the 120 MX nodes
> slowly.. I have set the SMTP_MAX_RCPTS to 5 per message for better
> delivery to several MTA's , which means 3 million subscribers are
> delivered in groups of 5.. resulting 600,000 messages to be distributed
> by the main hardware node.. is that too much? should I split them to
> several servers??


Perhaps if you asked your question on a list or forum devoted to
configuring hardware and MTAs for delivering large volumes of mail,
you'd get a better response. This list is for support of Mailman. As far
as I can tell, your issue is downstream of Mailman after Mailman has
successfully delivered your mail to your main outgoing MTA and is
therefore, not a Mailman issue.

-- 
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  Mon Jul 30 04:11:47 2012
From: stephen at xemacs.org (Stephen J. Turnbull)
Date: Mon, 30 Jul 2012 11:11:47 +0900
Subject: [Mailman-Users] postsuper
In-Reply-To: <BLU171-DS14C493E850CB2FE3301846FBC70@phx.gbl>
References: <BLU171-DS30752A7E538D49442FB646FBC70@phx.gbl>
	<50154AF2.9090402@msapiro.net>
	<BLU171-DS14C493E850CB2FE3301846FBC70@phx.gbl>
Message-ID: <87wr1myp3w.fsf@uwakimon.sk.tsukuba.ac.jp>

Khalil Abbas writes:

 > Hi, Thanks for the tip, but my problem isn?t with deferred mail, no mail is 
 > getting rejected from the remote MTA's.. but my problem is that the main 
 > hardware node is distributing the mail over the 120 MX nodes slowly.. I have 
 > set the SMTP_MAX_RCPTS to 5 per message for better delivery to
 > several MTA's 

That seems way too low in your configuration.  You control the peers
of the originating node, so a high SPMT_MAX_RCPTS should not be a
problem within your network.  What you need to do is make sure that
the MX nodes are throttled so that they don't get blackballed by the
remotes.


From tanstaafl at libertytrek.org  Mon Jul 30 13:39:33 2012
From: tanstaafl at libertytrek.org (Tanstaafl)
Date: Mon, 30 Jul 2012 07:39:33 -0400
Subject: [Mailman-Users] A simple unsubscribe
In-Reply-To: <20120728163806.GB18588@mitch.veggiechinese.net>
References: <6B3A7025196C1A49AABB0E6C80AD5AE2015B4BC3@apsaserv.APSA.local>
	<20120629183906.0b398c1a@abydos.stargate.org.uk>
	<20120728163806.GB18588@mitch.veggiechinese.net>
Message-ID: <50167275.1090509@libertytrek.org>

On 2012-07-28 12:38 PM, William Yardley <mailman at veggiechinese.net> wrote:
> Even if it's not primarily intended for that purpose, Mailman is used
> extensively as (and can be configured as) an announcement list, vs. a
> traditional discussion list. In that context (where none of the members
> can post, or learn the email address of other members, and therefore
> won't accidentally post their unsub link to the list), it makes sense to
> have a one-click unsubscribe. While you might "maliciously" try to
> unsubscribe someone you don't like on a discussion list, there are good
> policy or legal reasons in certain cases to make *subscription*
> difficult, and *unsubscription* easy.

And as long as a 'Goodbye' message was mailed to the former subscriber, 
they would at least know they were unsubscribed... and if this happens 
and the former subscriber resubscribes, some kind of time based security 
measure could be used to prevent anyone from being one-click 
unsubscribed more than x times per [week][month][quarter][year][whatever]...

From Eric.Smith at trustfood.org  Sun Jul 29 23:01:35 2012
From: Eric.Smith at trustfood.org (Eric Smith)
Date: Sun, 29 Jul 2012 23:01:35 +0200
Subject: [Mailman-Users] configuration of mailman with postfix - SOLVED
In-Reply-To: <1484963.JU2Sa3Vonm@scott-latitude-e6320>
References: <mailbox-3938-1343219300-986698@pepper>
	<500FE858.2000802@schetterer.org>
	<mailbox-20122-1343239238-346300@pepper>
	<1484963.JU2Sa3Vonm@scott-latitude-e6320>
Message-ID: <mailbox-14067-1343595301-368666@pepper>

The issue was that as of 12.04 ubuntu upgraded to ipv6 support.
My mailman install required relaying of mails by postfix but
because the system was now ipv6 enabled, this 
was not possible until add following to mynetworks
 [::1]/128
Thanks to Mark Sapiro on the mailman list for persisting
and finding the answer. 

Maybe this will save someone else the time that it cost me.

Is the cause of this type of issue my ignorance alone?
Why (else) do these things happen?

-- 
Best regards,
Eric Smith

Scott Kitterman wrote on Wed-25-Jul 12  9:07PM
> On Wednesday, July 25, 2012 08:55:52 PM Eric Smith wrote:
> > Thanks Robert (Scott)
> > 
> > I have upgraded, checked and followed the Ubuntu docs.
> > transport in master.cf corrected (I had a typo that gave the
> > error with the user expansion), now it is like this;
> > 
> > [root at pepper ~] $ grep -A1 mailman  /etc/postfix/master.cf
> > mailman   unix  -       n       n       -       -       pipe
> >  flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
> >  ${nexthop} ${user}
> > 
> > $ mutt fresher at fresher2.nl -stest</dev/null;sleep 2;\
> > sudo sh -c "find /var/log/ -mmin -1; grep fresher  /var/log/mail.log|tail
> > -1" /var/log/syslog
> > /var/log/mail.log
> > /var/log/auth.log
> > Jul 25 20:45:53 localhost postfix/local[10429]: 70E4329020F: \
> > to=<|/var/lib/mailman/mail/mailman post fresher at fruitcom.com>, \
> > orig_to=<fresher at fresher2.nl>, relay=local, delay=0.17, \
> > delays=0.11/0/0/0.06, dsn=5.1.1, status=bounced (unknown user: \
> > "|/var/lib/mailman/mail/mailman post fresher")
> > 
> > FWIW:
> > [eric at pepper ~] $ echo $HOSTNAME
> > pepper.fruitcom.com
> > 
> > (Tooth enamel wearing a bit thin)
> > 
> > Any ideas where I could look?
> 
> I've never used mailman, so I don't know for sure about this, but I note 
> you're using "user=list" in the flags for the mailman service, but I see 
> "/var/lib/mailman/mail/mailman post fresher" in the logs.  Is fresher a valid 
> address in your domain?
> 
> Scott K

From bcanty at apsa.org  Tue Jul 31 16:11:31 2012
From: bcanty at apsa.org (Brian Canty)
Date: Tue, 31 Jul 2012 10:11:31 -0400
Subject: [Mailman-Users] Changing form codes
Message-ID: <6B3A7025196C1A49AABB0E6C80AD5AE2015B4D3A@apsaserv.APSA.local>

Hello Everyone - 

 

I sent this message a couple of weeks ago and did not hear from anyone
so I am trying  again.

 

Does anyone know if there is a way to change the way the preformatted
forms from mailman look.

 

I would like to change the editing-options form but cannot figure out
how to do that.  The Mailman code is

 

<MM-Editing-Options>

 

Any help would be appreciated.

 

Thanks in advance.

Brian

 

 

Brian Canty

Manager, Computer Information Services

American Psychoanalytic Associaiton

(212) 752-0450 x17

 

www.apsa.org

 


From mark at msapiro.net  Tue Jul 31 19:26:45 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 31 Jul 2012 10:26:45 -0700
Subject: [Mailman-Users] Changing form codes
In-Reply-To: <6B3A7025196C1A49AABB0E6C80AD5AE2015B4D3A@apsaserv.APSA.local>
Message-ID: <PC195201207311026450671a9fc688c@MSAPIRO>

Brian Canty wrote:
>
>I sent this message a couple of weeks ago and did not hear from anyone
>so I am trying  again.
>
> 
>
>Does anyone know if there is a way to change the way the preformatted
>forms from mailman look.


See my reply at
<http://mail.python.org/pipermail/mailman-users/2012-July/073857.html>.

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