From mark at msapiro.net  Fri Feb  1 02:31:48 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 31 Jan 2013 17:31:48 -0800
Subject: [Mailman-Users] Links showing up twice in posted messages
In-Reply-To: <1359587105.6491.YahooMailNeo@web160802.mail.bf1.yahoo.com>
References: <1359587105.6491.YahooMailNeo@web160802.mail.bf1.yahoo.com>
Message-ID: <510B1B04.7020402@msapiro.net>

On 1/30/2013 3:05 PM, Heather Ben? Dubin wrote:
> 
> Whenever members post messages to this particular list using any kind of URL, the URL comes through twice, for example: 
> 
> heather_dubin at yahoo.com<mailto:heather_dubin at yahoo.com>
> http://www.cce-usa.org/<http://www.cce-usa.org/>
> 
> I have looked through all of the settings and compared them to the settings of the lists that are working properly, but I don't see anything that's different. 
> 
> 
> Does anyone have ANY idea why this is happening and what I can do to fix it?


Since it only occurs with one list and not others with similar settings
(although Mailman wouldn't do this anyway), I suspect it has to do with
the mail clients of the people posting to the list.

Also, as suggested by Stucki, check the archives and see if they show
these artifacts.

It may also have to do with content filtering if that is different for
this list than others.

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


From cnulk at scu.edu  Sat Feb  2 00:41:50 2013
From: cnulk at scu.edu (Chris Nulk)
Date: Fri, 01 Feb 2013 15:41:50 -0800
Subject: [Mailman-Users] Using set_mod.py
Message-ID: <510C52BE.1060509@scu.edu>

Hello all,

I am trying to change moderation settings on some lists via a script so 
I can automate the list management for several lists (approx. 30 lists).

In the script I use the following to run set_mod.py:

   /usr/lib/mailman/bin/withlist --run /usr/lib/mailman/bin/set_mod 
LISTNAME --unset address at example.com

however, I get the following error back:

      Importing /usr/lib/mailman/bin/set_mod...
      Traceback (most recent call last):
        File "/usr/lib/mailman/bin/withlist", line 297, in ?
          main()
        File "/usr/lib/mailman/bin/withlist", line 266, in main
          mod = __import__(module)
      ImportError: No module named /usr/lib/mailman/bin/set_mod

Just to make sure I am running withlist and set_mod correctly, I did 
change into the mailman directory (/usr/lib/mailman) and run the command 
as recommended in the documentation:

   bin/withlist --run bin/set_mod LISTNAME --unset address at example.com

and, I get back the following error:

      Importing bin/set_mod...
      Running bin/set_mod.bin/set_mod()...
      Traceback (most recent call last):
        File "bin/withlist", line 297, in ?
          main()
        File "bin/withlist", line 269, in main
          func = getattr(mod, callable)
      AttributeError: 'module' object has no attribute 'bin/set_mod'

I tried adding the .py at the end of set_mod but I get a different error.

As a matter of fact, things went from bad to worse.  All the different 
trys I did may have corrupted my test list.  I had to delete the list 
and recreate it.

Is there a magic incantation so I can run set_mod.py in a script like my 
first command above?
Is there an easy way to modify set_mod.py so I can run it without using 
withlist (like add_members, remove_members, etc.)?

Thanks for an help and any advice,
Chris

From mark at msapiro.net  Sat Feb  2 02:01:28 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 01 Feb 2013 17:01:28 -0800
Subject: [Mailman-Users] Using set_mod.py
In-Reply-To: <510C52BE.1060509@scu.edu>
References: <510C52BE.1060509@scu.edu>
Message-ID: <510C6568.5010901@msapiro.net>

On 2/1/2013 3:41 PM, Chris Nulk wrote:

> 
> In the script I use the following to run set_mod.py:
> 
>   /usr/lib/mailman/bin/withlist --run /usr/lib/mailman/bin/set_mod
> LISTNAME --unset address at example.com


/usr/lib/mailman/bin/withlist --help

might help, but the argument to --run is a module name, not a path. The
module must be in a directory in Python's sys.path which is why the
script says "Save as bin/set_mod.py" which you have correctly done, but
the command you need is

/usr/lib/mailman/bin/withlist --run set_mod LISTNAME --unset
address at example.com

> [...]
> Just to make sure I am running withlist and set_mod correctly, I did
> change into the mailman directory (/usr/lib/mailman) and run the command
> as recommended in the documentation:
> 
>   bin/withlist --run bin/set_mod LISTNAME --unset address at example.com


That is not the command recommended in the documentation which says:

Save as bin/set_mod.py

Run via

   bin/withlist -r set_mod <listname> <option> <member> ...
[...]
> As a matter of fact, things went from bad to worse.  All the different
> trys I did may have corrupted my test list.  I had to delete the list
> and recreate it.


Those errors from withlist should not have corrupted your list. The
script never got far enough to save any changes. However, if at any
point you gave the '-l' option to withlist, withlist might have left the
list locked. It shouldn't, but it's hard to say without more info.


> Is there a magic incantation so I can run set_mod.py in a script like my
> first command above?


It's not magic. See above.


> Is there an easy way to modify set_mod.py so I can run it without using
> withlist (like add_members, remove_members, etc.)?


Easy for me, yes.

There is a moral here. Before handling loaded guns, you need to take the
gun safety class or you might shoot yourself in the foot. The analogy to
the gun safety class here is perhaps
<http://wiki.python.org/moin/BeginnersGuide>.

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


From webmaster at hullcamra.org.uk  Fri Feb  1 14:07:26 2013
From: webmaster at hullcamra.org.uk (Webmaster @ Hull CAMRA)
Date: Fri, 1 Feb 2013 13:07:26 -0000
Subject: [Mailman-Users] Special Characters
Message-ID: <002a01ce007d$156efbb0$404cf310$@org.uk>

Hi All

 

I've been searching FAQs and messages for references to using special
characters but the information I found only relates to headers and footers.
My problem is that Mailman is not recognising characters such as the British
Pound symbol in the body of messages, so when a subscriber posts something
with a ? symbol in it 's appearing as a question mark? Is there any way I
can change how Mailman sees these symbols and interprets them correctly
without having to resort to HTML which most of my subscribers would be
clueless about?

 

 

Regards

Patrick

webmaster at hullcamra.org.uk

http://www.hullcamra.org.uk

http://www.imaginewebsites.co.uk

 

 


From vickib at wcadv.org  Fri Feb  1 20:34:03 2013
From: vickib at wcadv.org (Vicki Berenson)
Date: Fri, 1 Feb 2013 19:34:03 +0000
Subject: [Mailman-Users] Sibling lists and senders - regular_include
Message-ID: <1B887789A6C22B43A75CEA81F103E0A50930ECD0@WCADVSERVER.office.wcadv.org>

Hi, I've looked at all the posts I can find about this but I'm still unclear.

I have created an announcements list that includes several sublists in regular_include_lists.

There are also a number of individual subscribers (staff at our agency). I have set all but two of them to be moderated. The idea is that I want 2 of us (Vicki and Colleen) to be able to send to the announcements list, and the others to just receive posts.

What I'm unclear about is, if Vicki or Colleen are not members of one of the sublists in regular_include_lists, will our posts to announcements still get to the people who are only on those lists?

If someone is an announcements list administrator, will they be able to send to the announcements list and thus to all the sublist subscribers? Do we need to be announcement list members to post?

And just to clarify: if we want to be sure that digest members receive these posts but not duplicates, we should include all the lists in regular_exclude_lists (as well as includes) and include all the lists in To or Cc?

Thanks much!

Vicki Berenson
Technology Coordinator
Wisconsin Coalition Against Domestic Violence
307 South Paterson Street, Suite 1
Madison, Wisconsin 53703
Phone: (608) 255-0539  Fax/TTY: (608) 255-3560
www.wcadv.org<http://www.wcadv.org/>
vickib at wcadv.org<mailto:vickib at wcadv.org>

"Open your arms to change, but don't let go of your values." - Dalai Lama



From mark at msapiro.net  Sat Feb  2 09:39:31 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 2 Feb 2013 00:39:31 -0800
Subject: [Mailman-Users] Sibling lists and senders - regular_include
In-Reply-To: <1B887789A6C22B43A75CEA81F103E0A50930ECD0@WCADVSERVER.office.wcadv.org>
Message-ID: <PC19932013020200393102182a9674f9@MSAPIRO>

Vicki Berenson wrote:
>
>I have created an announcements list that includes several sublists in regular_include_lists.
>
>There are also a number of individual subscribers (staff at our agency). I have set all but two of them to be moderated. The idea is that I want 2 of us (Vicki and Colleen) to be able to send to the announcements list, and the others to just receive posts.


The safer way to do this that prevents posting by spoofing Vicki or
Colleen in the From: header is to moderate everyone on the
announcements list and post using an Approved: password header or
pseudo-header. See the FAQ at <http://wiki.list.org/x/3YA9>.


>What I'm unclear about is, if Vicki or Colleen are not members of one of the sublists in regular_include_lists, will our posts to announcements still get to the people who are only on those lists?


Yes.


>If someone is an announcements list administrator, will they be able to send to the announcements list and thus to all the sublist subscribers? Do we need to be announcement list members to post?


Any unmoderated member can post and anyone who knows the list admin or
moderator or in 2.1.15 poster password can post with an Approved:
password header.

Having one's address listed as an owner or moderator only results in
one's receiving certain emailed notices and messages to -owner, it
conveys no posting priviledge. See the FAQ at
<http://wiki.list.org/x/5YA9>.


>And just to clarify: if we want to be sure that digest members receive these posts but not duplicates, we should include all the lists in regular_exclude_lists (as well as includes) and include all the lists in To or Cc?


In this case, people who are members of more than one sub-list will
receive dups from the sub-lists, they just won't receive a dup from
the announce list if they happen to be a regular member of one or more
sub-lists.

Or maybe just mail to all the lists without using regular_include_lists
or regular_exclude_lists at all or use an umbrella list. See the FAQs
at <http://wiki.list.org/x/TIA9> and <http://wiki.list.org/x/boA9>.

-- 
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 Feb  2 09:57:02 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 02 Feb 2013 00:57:02 -0800
Subject: [Mailman-Users] Special Characters
In-Reply-To: <002a01ce007d$156efbb0$404cf310$@org.uk>
References: <002a01ce007d$156efbb0$404cf310$@org.uk>
Message-ID: <510CD4DE.7070703@msapiro.net>

On 2/1/2013 5:07 AM, Webmaster @ Hull CAMRA wrote:
> 
> I've been searching FAQs and messages for references to using special
> characters but the information I found only relates to headers and footers.
> My problem is that Mailman is not recognising characters such as the British
> Pound symbol in the body of messages, so when a subscriber posts something
> with a ? symbol in it 's appearing as a question mark? Is there any way I
> can change how Mailman sees these symbols and interprets them correctly
> without having to resort to HTML which most of my subscribers would be
> clueless about?


I'm confused. At first I thought you must be talking about '?' appearing
in the list's archives, since Mailman should not be munging message
bodies other than via content filtering's removing unwanted parts in
their entirety, but your reference to HTML makes me think you're talking
about 'plain' format digests.

So, is it archives, plain format digests, both or somewhere else that
you see the problem?

If you're only concerned about plain format digests, you might try
switching to MIME as default and switching the current plain digest
subscribers. MIME digests are not something users need a clue about. It
is an MUA thing much more than a user thing, and a majority (but not all
depending on their MUA) of your users will be as happy or happier with MIME.

The alternative is to change the default character set for English to
utf-8 or iso-8859-1. The first few hits from this search
<http://www.google.com/search?q=site:mail.python.org+inurl%3Amailman-users+add_language+english>
should tell you how this is done

-- 
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 Feb  2 10:36:17 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 02 Feb 2013 01:36:17 -0800
Subject: [Mailman-Users] About Spam Filtering
In-Reply-To: <510A206C.4050805@metu.edu.tr>
References: <PC19932013013008063203328854c16c@MSAPIRO>
	<510A206C.4050805@metu.edu.tr>
Message-ID: <510CDE11.60300@msapiro.net>

On 1/30/2013 11:42 PM, METU E-List Admin wrote:
> 
> The message was addressed to the list address. The email address I have
> registered is not the owner of the list.
> 
> The message headers are:
> 
> ------------------------------------------------
[...]
> X-BeenThere: fethiyede at googlegroups.com


I don't know why it would matter, but it seems your register at metu.edu.tr
list a member of this fethiyede at googlegroups.com google group. Do you
want that? Is all the problem mail coming via that google group? Do you
have any list settings to allow mail from that group?

However, if you haven't reordered the pipeline for this list, SpamDetect
which processes header_filter_rules comes first and should take precedence.


[...]
> X-Mailer: Microsoft CDO for Windows 2000


It's hard to see from your jpeg image, but is it possible that your

^X-Mailer: (?!Microsoft Outlook .*)$

actually contains more than one space after the colon?


[...]
> X-Mailman-Version:


Odd that this is empty ...


> Reply-To: fethiyede at googlegroups.com
[...]

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


From jesus at evangelizacion.org.mx  Tue Feb  5 22:48:43 2013
From: jesus at evangelizacion.org.mx (Jesus Rivas)
Date: Tue, 05 Feb 2013 15:48:43 -0600
Subject: [Mailman-Users] Fwd: get bounced mails
In-Reply-To: <5111300E.1020001@evangelizacion.org.mx>
References: <5111300E.1020001@evangelizacion.org.mx>
Message-ID: <51117E3B.9040503@evangelizacion.org.mx>

get a list of members who's delivery is
currently disabled by bounce


*Jes?s Rivas*
Sistemas
<http://www.evangelizacion.org.mx>
T. (01 81) 8123-1293
01 800 836 9407
website <http://www.evangelizacion.org.mx> | vCard 
<http://www.evangelizacion.org.mx/firma/jesus_rivas.vcf> | facebook 
<https://www.facebook.com/evangelizacionactiva> | twitter 
<https://twitter.com/evangelizaciona>



-------- Mensaje original --------
Asunto: 	get bounced mails
Fecha: 	Tue, 05 Feb 2013 10:15:10 -0600
De: 	Jesus Rivas <jesus at evangelizacion.org.mx>
Responder a: 	jesus at evangelizacion.org.mx
Organizaci?n: 	Evangelizacion Activa
Para: 	Mark Sapiro <mark at msapiro.net>



Hi list.

is there any way to get the bounced mailing list?

Best regards

*Jes?s Rivas*
Sistemas
<http://www.evangelizacion.org.mx>
T. (01 81) 8123-1293
01 800 836 9407
website <http://www.evangelizacion.org.mx> | vCard 
<http://www.evangelizacion.org.mx/firma/jesus_rivas.vcf> | facebook 
<https://www.facebook.com/evangelizacionactiva> | twitter 
<https://twitter.com/evangelizaciona>






From jesus at evangelizacion.org.mx  Tue Feb  5 22:08:16 2013
From: jesus at evangelizacion.org.mx (Jesus Rivas)
Date: Tue, 05 Feb 2013 15:08:16 -0600
Subject: [Mailman-Users] Bounced mailling list.
Message-ID: <511174C0.1030400@evangelizacion.org.mx>

Hi list.

is there any way to get the bounced mailing list?

Best regards
-- 
*Jes?s Rivas*
Sistemas
<http://www.evangelizacion.org.mx>
T. (01 81) 8123-1293
01 800 836 9407
website <http://www.evangelizacion.org.mx> | vCard 
<http://www.evangelizacion.org.mx/firma/jesus_rivas.vcf> | facebook 
<https://www.facebook.com/evangelizacionactiva> | twitter 
<https://twitter.com/evangelizaciona>


From mark at msapiro.net  Wed Feb  6 01:36:08 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 5 Feb 2013 16:36:08 -0800
Subject: [Mailman-Users] Fwd: get bounced mails
In-Reply-To: <51117E3B.9040503@evangelizacion.org.mx>
Message-ID: <PC1993201302051636080359efafe76f@MSAPIRO>

Jesus Rivas wrote:

>get a list of members who's delivery is
>currently disabled by bounce


Mailman's

  bin/list_members --nomail=bybounce LISTNAME

is the preferred way. If you don't have command line access to the
server, the script at
<http://www.msapiro.net/scripts/mailman-subscribers.py> can give the
same result by screen scraping the web admin membership list. Read the
beginning of the script for usage information.

-- 
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 Feb  6 01:39:25 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 5 Feb 2013 16:39:25 -0800
Subject: [Mailman-Users] Bounced mailling list.
In-Reply-To: <511174C0.1030400@evangelizacion.org.mx>
Message-ID: <PC1993201302051639250875efafe984@MSAPIRO>

Jesus Rivas wrote:
>
>is there any way to get the bounced mailing list?


If this is the same question asked in your post at
<http://mail.python.org/pipermail/mailman-users/2013-February/074680.html>,
that is answered at
<http://mail.python.org/pipermail/mailman-users/2013-February/074682.html>.

If it is a different question, please clarify exactly what is wanted.

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


From listeyon at metu.edu.tr  Wed Feb  6 13:26:38 2013
From: listeyon at metu.edu.tr (METU E-List Admin)
Date: Wed, 06 Feb 2013 14:26:38 +0200
Subject: [Mailman-Users] About Spam Filtering
In-Reply-To: <510CDE11.60300@msapiro.net>
References: <PC19932013013008063203328854c16c@MSAPIRO>
	<510A206C.4050805@metu.edu.tr> <510CDE11.60300@msapiro.net>
Message-ID: <51124BFE.5070905@metu.edu.tr>

Hello,

This mail address is not registered to any mailing lists officially. I 
think we have to request a manual unsubscribe from the owner of the 
list. However, there are lots of mails like this and blocking them is 
much easier and better method.

"^X-Mailer: (?!Microsoft Outlook .*)$" has single spacing between the 
colon and the parenthesis. The screenshot is taken using Chrome on Ubuntu.

We have removed the Mailman version number using the configuration file. 
I think that configuration also removes the version number from the 
headers. If it is a problem, we can convert it to the original state.

Thanks,


On 02/02/2013 11:36 AM, Mark Sapiro wrote:
> On 1/30/2013 11:42 PM, METU E-List Admin wrote:
>> The message was addressed to the list address. The email address I have
>> registered is not the owner of the list.
>>
>> The message headers are:
>>
>> ------------------------------------------------
> [...]
>> X-BeenThere: fethiyede at googlegroups.com
>
> I don't know why it would matter, but it seems your register at metu.edu.tr
> list a member of this fethiyede at googlegroups.com google group. Do you
> want that? Is all the problem mail coming via that google group? Do you
> have any list settings to allow mail from that group?
>
> However, if you haven't reordered the pipeline for this list, SpamDetect
> which processes header_filter_rules comes first and should take precedence.
>
>
> [...]
>> X-Mailer: Microsoft CDO for Windows 2000
>
> It's hard to see from your jpeg image, but is it possible that your
>
> ^X-Mailer: (?!Microsoft Outlook .*)$
>
> actually contains more than one space after the colon?
>
>
> [...]
>> X-Mailman-Version:
>
> Odd that this is empty ...
>
>
>> Reply-To: fethiyede at googlegroups.com
> [...]
>


From mark at msapiro.net  Wed Feb  6 17:24:16 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 6 Feb 2013 08:24:16 -0800
Subject: [Mailman-Users] About Spam Filtering
In-Reply-To: <51124BFE.5070905@metu.edu.tr>
Message-ID: <PC19932013020608241606404c482690@MSAPIRO>

METU E-List Admin wrote:
>
>"^X-Mailer: (?!Microsoft Outlook .*)$" has single spacing between the 
>colon and the parenthesis. The screenshot is taken using Chrome on Ubuntu.


The screenshot is problematic for the reason that it is incomplete. The
whole page is not shown and the content of some of the text boxes is
longer than the box. It would be much better to post something like
the relevant part of

 bin/config_list -o - LISTNAME | grep -A20 header_filter_rules

to provide this information.


>We have removed the Mailman version number using the configuration file. 
>I think that configuration also removes the version number from the 
>headers. If it is a problem, we can convert it to the original state.


I don't think this would be a problem. The question still remains as to
why your header_filter_rules rule is apparently not working.

You could try applying the attached patch to
Mailman/Handlers/SpamDetect.py and restarting Mailman. This will
produce a 'debug' log in Mailman's logs/ directory with information
about all the header_filter_rules hits which may help find what's
going wrong.

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

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: SpamDetect.patch.txt
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20130206/742c5f26/attachment.txt>

From cnulk at scu.edu  Fri Feb  8 18:52:26 2013
From: cnulk at scu.edu (Chris Nulk)
Date: Fri, 08 Feb 2013 09:52:26 -0800
Subject: [Mailman-Users] Subject line message filtering
Message-ID: <51153B5A.90401@scu.edu>

Hello all,

I am trying to stop a particular group of messages from going to several 
of my lists.  I am looking at the Subject line of the message to do the 
filtering and I am using the header_filter_rules in Spam Filtering.  My 
regex filter is:

      ^Subject:[\s\+]*\[.*\]\s+(Invitation|Canceled Event):.*

and the Subject lines I am trying to catch and reject the message look like:

      Subject: [MYLIST] Invitation: Test event @ Thu Feb 28,
	     2013 10:00 - 11:00 (mylistg at example.com)

or

      Subject: [MYLIST] Canceled Event: Test event @ Thu Feb 28,
	     2013 10:00 - 11:00 (mylist at example.com)


I have set the action for the rule to reject, however, the messages still get posted to the list.

I have tested the regex above using the python interactive interpreter and the regex does match the various inputs used.

Can anyone tell me what the problem is with my regex?

Also, can any of the sender/recipient filters cause the message to bypass the spam filters?  The message pipeline is unchanged.

Thanks,
Chris


From cwieland at uci.edu  Fri Feb  8 19:41:03 2013
From: cwieland at uci.edu (Con Wieland)
Date: Fri, 8 Feb 2013 10:41:03 -0800
Subject: [Mailman-Users] Solaris 10 and Mailman
Message-ID: <1920D254-9007-4313-95C8-5489ED9427D1@uci.edu>

Hello,

Does anyone happen to have a SMF script for mailman they would care to share.

Thanks in advance.
Con Wieland
Office of Information Technology
University of California at Irvine

From Richard at Damon-Family.org  Fri Feb  8 20:44:19 2013
From: Richard at Damon-Family.org (Richard Damon)
Date: Fri, 08 Feb 2013 14:44:19 -0500
Subject: [Mailman-Users] Subject line message filtering
In-Reply-To: <51153B5A.90401@scu.edu>
References: <51153B5A.90401@scu.edu>
Message-ID: <51155593.4090506@Damon-Family.org>

On 2/8/13 12:52 PM, Chris Nulk wrote:
> Hello all,
>
> I am trying to stop a particular group of messages from going to
> several of my lists.  I am looking at the Subject line of the message
> to do the filtering and I am using the header_filter_rules in Spam
> Filtering.  My regex filter is:
>
>      ^Subject:[\s\+]*\[.*\]\s+(Invitation|Canceled Event):.*
>
> and the Subject lines I am trying to catch and reject the message look
> like:
>
>      Subject: [MYLIST] Invitation: Test event @ Thu Feb 28,
>          2013 10:00 - 11:00 (mylistg at example.com)
>
> or
>
>      Subject: [MYLIST] Canceled Event: Test event @ Thu Feb 28,
>          2013 10:00 - 11:00 (mylist at example.com)
>
>
> I have set the action for the rule to reject, however, the messages
> still get posted to the list.
>
> I have tested the regex above using the python interactive interpreter
> and the regex does match the various inputs used.
>
> Can anyone tell me what the problem is with my regex?
>
> Also, can any of the sender/recipient filters cause the message to
> bypass the spam filters?  The message pipeline is unchanged.
>
> Thanks,
> Chris
Make sure you have set the "Action" for the filter to some other than
Defer or Accept.

A previous Accept that matches the message will override this filter.

Also, note that I think the filter it tested BEFORE the [MYLIST] is
added to the subject by the list, so is only there to be matched if it
was in the original email.

-- 
Richard Damon


From cnulk at scu.edu  Fri Feb  8 22:21:34 2013
From: cnulk at scu.edu (Chris Nulk)
Date: Fri, 08 Feb 2013 13:21:34 -0800
Subject: [Mailman-Users] Subject line message filtering
In-Reply-To: <51155593.4090506@Damon-Family.org>
References: <51153B5A.90401@scu.edu> <51155593.4090506@Damon-Family.org>
Message-ID: <51156C5E.3020006@scu.edu>

On 2/8/2013 11:44 AM, Richard Damon wrote:
> On 2/8/13 12:52 PM, Chris Nulk wrote:
>> Hello all,
>>
>> I am trying to stop a particular group of messages from going to
>> several of my lists.  I am looking at the Subject line of the message
>> to do the filtering and I am using the header_filter_rules in Spam
>> Filtering.  My regex filter is:
>>
>>       ^Subject:[\s\+]*\[.*\]\s+(Invitation|Canceled Event):.*
>>
>> and the Subject lines I am trying to catch and reject the message look
>> like:
>>
>>       Subject: [MYLIST] Invitation: Test event @ Thu Feb 28,
>>           2013 10:00 - 11:00 (mylistg at example.com)
>>
>> or
>>
>>       Subject: [MYLIST] Canceled Event: Test event @ Thu Feb 28,
>>           2013 10:00 - 11:00 (mylist at example.com)
>>
>>
>> I have set the action for the rule to reject, however, the messages
>> still get posted to the list.
>>
>> I have tested the regex above using the python interactive interpreter
>> and the regex does match the various inputs used.
>>
>> Can anyone tell me what the problem is with my regex?
>>
>> Also, can any of the sender/recipient filters cause the message to
>> bypass the spam filters?  The message pipeline is unchanged.
>>
>> Thanks,
>> Chris
> Make sure you have set the "Action" for the filter to some other than
> Defer or Accept.

I did set the "Action" to "Reject".

>
> A previous Accept that matches the message will override this filter.

Not a problem.  Yet.  I only have the one filter.

>
> Also, note that I think the filter it tested BEFORE the [MYLIST] is
> added to the subject by the list, so is only there to be matched if it
> was in the original email.
>
This was the answer.  Thank you.  I should have realized that but I just 
wanted to get it done so I can move on to other critical work. Taking 
out the [MYLIST] check from the regex worked and I could add back in 
addition constraints to the regex to make it more targeted.

Thanks again Richard.

Chris

From mark at msapiro.net  Sat Feb  9 01:28:23 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 08 Feb 2013 16:28:23 -0800
Subject: [Mailman-Users] Subject line message filtering
In-Reply-To: <51153B5A.90401@scu.edu>
References: <51153B5A.90401@scu.edu>
Message-ID: <51159827.2060101@msapiro.net>

Chris Nulk wrote:

> My regex filter is:
> 
>       ^Subject:[\s\+]*\[.*\]\s+(Invitation|Canceled Event):.*


I know you've resolved this and that the issue was that
header_filter_rules are processed way before the subject_prefix is added
so you didn't want the '\[.*\]'part of the pattern, but I'm confused by
the '[\s\+]*' part of the pattern which says match 0 or more occurrences
of the character class consisting of any white space character (\s) and
the plus sign (either \+ or just + would be equivalent here, + loses its
special meaning inside []).

So, is [\s\+]* a typo or did you just mean \s+ or \s*?


> Also, can any of the sender/recipient filters cause the message to bypass the spam filters?  The message pipeline is unchanged.


No. header_filter_rules are processed by SpamDetect which is the first
module in the pipeline. As you discovered, the CookHeaders module which
adds the subject_prefix comes much later, and the sender/recipient
filters are processed by Moderate which also comes later.

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


From pyz at brama.com  Sun Feb 10 22:53:54 2013
From: pyz at brama.com (Max Pyziur)
Date: Sun, 10 Feb 2013 16:53:54 -0500 (EST)
Subject: [Mailman-Users] ISP policies, specifically AOL
Message-ID: <alpine.LRH.2.02.1302101646350.1683@brama.com>


Greetings,

We've been using mailman for almost ten years (thank you). At our peak we 
have run about ten email lists: some discussion-oriented w/ small 
membership, and very low frequency; others that have had higher frequency 
and membership. In addition, two of them have been used to distribute 
monthly newsletters/announcements to a large membership (5,000 to 10,000 
subscribers).

Recently (in the last six months to a year), some ISPs have begun blocking 
these high volume/low-frequency distributions, in particular AOL. While 
AOL emails make up about 10% of the constituency of these lists, for us 
and our lists it is important that distributions reach these subscribers.

It seems that AOL, among others, has insisted on some sort of 
pre-authentication procedures, so that large distributions from servers 
such as ours are effectively whitelisted.

Have other mailman admins encountered these issues?

Is this a foreshadowing of things to come?

Much thanks.

Max Pyziur
pyz at brama.com

From fmouse-mailman at fmp.com  Mon Feb 11 01:13:56 2013
From: fmouse-mailman at fmp.com (Lindsay Haisley)
Date: Sun, 10 Feb 2013 18:13:56 -0600
Subject: [Mailman-Users] ISP policies, specifically AOL
In-Reply-To: <alpine.LRH.2.02.1302101646350.1683@brama.com>
References: <alpine.LRH.2.02.1302101646350.1683@brama.com>
Message-ID: <1360541636.11774.76.camel@pudina.fmp.com>

I've had some experience dealing with AOL's issues.  Their policies and
techniques are shared by earthlink and probably a couple of other mail
hosting providers.

This has been going on for some years, and AOL had been fairly
consistent about it.  AOL's mail UI contains a "Report Spam" button, and
accumulates statistics on the sending IPs of email to which their users
object, and if an IP address accumulates too many complaints, it gets
blocked.

These URLs will be helpful to you:

http://postmaster.aol.com/Postmaster.FeedbackLoop.php

http://postmaster.aol.com/Postmaster.Guidelines.php

If you're subscribed to AOL's FBL abuse reports you'll get a notice
whenever an AOL (or other IPP host using this same system) subscriber
presses the "Report Spam" button, and AOL considers it your
responsibility to see that this address is deleted from your mailing
list in the future.  Ironically, AOL does its best to redact any
information from the problem emails (returned with FBL abuse reports)
which would enable you to easily identify the complaining AOL
subscriber, although if you manage to pull this information from a VERP
address in the message headers, AOL has no problem with this.

What I've been doing here is directing AOL's FBL abuse reports through a
custom python script which extracts the list name and the subscriber
address, unsubscribes the address from the list and notifies the list
owner (withlist is your friend!).  To this end, I've also hacked Mailman
to insert a Resent-message-id header into outgoing posts containing the
subscriber address, AES-encrypted.  According to a discussion on this
list several months ago, AOL has no problem with this, as long as the
subscriber address isn't in plain text in the returned list post in the
FBL abuse report.

In the meantime, you'll need to contact the AOL postmaster
(postmaster at aol.com) and get the blocks removed, and sign up for FBL
abuse reports.

AOL also has a "Certified Email" service to which you can subscribe,
once you've cleared the blocks against your server.  I'm not sure if
this is a commercial service, but if you sign up for it, it does provide
you with some insurance against blocks.  See the pages I cite above.

On Sun, 2013-02-10 at 16:53 -0500, Max Pyziur wrote:
> We've been using mailman for almost ten years (thank you). At our peak we 
> have run about ten email lists: some discussion-oriented w/ small 
> membership, and very low frequency; others that have had higher frequency 
> and membership. In addition, two of them have been used to distribute 
> monthly newsletters/announcements to a large membership (5,000 to 10,000 
> subscribers).
> 
> Recently (in the last six months to a year), some ISPs have begun blocking 
> these high volume/low-frequency distributions, in particular AOL. While 
> AOL emails make up about 10% of the constituency of these lists, for us 
> and our lists it is important that distributions reach these subscribers.
> 
> It seems that AOL, among others, has insisted on some sort of 
> pre-authentication procedures, so that large distributions from
> servers 
> such as ours are effectively whitelisted.
> 
> Have other mailman admins encountered these issues?
> 
> Is this a foreshadowing of things to come?
> 
> Much thanks.
> 
> Max Pyziur
> 



From listeyon at metu.edu.tr  Mon Feb 11 10:00:22 2013
From: listeyon at metu.edu.tr (METU E-List Admin)
Date: Mon, 11 Feb 2013 11:00:22 +0200
Subject: [Mailman-Users] About Spam Filtering
In-Reply-To: <PC19932013020608241606404c482690@MSAPIRO>
References: <PC19932013020608241606404c482690@MSAPIRO>
Message-ID: <5118B326.8060804@metu.edu.tr>

Hello,

--------------------------------------------
$ bin/config_list -o - REGISTER | grep -A20 header_filter_rules
header_filter_rules = [('^X-Mailer: (?!Microsoft Outlook .*)$', 7, 
False), ('^X-Mailer-LID: .*$', 3, False), ('^X-Mailer-RecptId: .*$', 3, 
False), ('^X-Mailer-SID: .*$', 3, False), ('^X-Mailer-Sent-By: .*$', 3, 
False), ('^X-Spam-Status: Yes.*$', 3, False), ('^X-Spam-Flag: YES', 3, 
False), ('^X-Virus-Status: Yes', 3, False), ('^X-Bogosity-Metu: Yes', 3, 
False)]

# Use this option to prohibit posts according to specific header values.
# The target value is a regular-expression for matching against the
# specified header.  The match is done disregarding letter case. Lines
# beginning with '#' are ignored as comments.
#
# For example:to: .*@public.com  says to hold all postings with a To:
# mail header containing '@public.com' anywhere among the addresses.
#
# Note that leading whitespace is trimmed from the regexp.  This can be
# circumvented in a number of ways, e.g. by escaping or bracketing it.
bounce_matching_headers = ''

## Bounce options
#
# These policies control the automatic bounce processing system in
# Mailman.  Here's an overview of how it works.
#
# <p>When a bounce is received, Mailman tries to extract two pieces of
# information from the message: the address of the member the message

-------------------------------------------

I will post the logs a few days later, just to make sure that it has the 
needed info.

Thanks,



On 02/06/2013 06:24 PM, Mark Sapiro wrote:
> METU E-List Admin wrote:
>> "^X-Mailer: (?!Microsoft Outlook .*)$" has single spacing between the
>> colon and the parenthesis. The screenshot is taken using Chrome on Ubuntu.
>
> The screenshot is problematic for the reason that it is incomplete. The
> whole page is not shown and the content of some of the text boxes is
> longer than the box. It would be much better to post something like
> the relevant part of
>
>   bin/config_list -o - LISTNAME | grep -A20 header_filter_rules
>
> to provide this information.
>
>
>> We have removed the Mailman version number using the configuration file.
>> I think that configuration also removes the version number from the
>> headers. If it is a problem, we can convert it to the original state.
>
> I don't think this would be a problem. The question still remains as to
> why your header_filter_rules rule is apparently not working.
>
> You could try applying the attached patch to
> Mailman/Handlers/SpamDetect.py and restarting Mailman. This will
> produce a 'debug' log in Mailman's logs/ directory with information
> about all the header_filter_rules hits which may help find what's
> going wrong.
>


From aspamkiller at yandex.ru  Mon Feb 11 11:02:09 2013
From: aspamkiller at yandex.ru (Dimytch)
Date: Mon, 11 Feb 2013 12:02:09 +0200
Subject: [Mailman-Users] To divide the mail sending by portions in time
Message-ID: <2514801360576929@web4d.yandex.ru>

Hi, all

We are using our list mostly for sending some actual info from one email.
Could I divide mail messages sending by portions like 300 msg per 10 minutes or so?
Any help would be appreciate.

//Dimitri

From mark at msapiro.net  Mon Feb 11 15:01:24 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 11 Feb 2013 06:01:24 -0800
Subject: [Mailman-Users] To divide the mail sending by portions in time
In-Reply-To: <2514801360576929@web4d.yandex.ru>
Message-ID: <PC1993201302110601240937309713c1@MSAPIRO>

Dimytch wrote:

>Could I divide mail messages sending by portions like 300 msg per 10 minutes or so?


See the FAQ at <http://wiki.list.org/x/j4A9> and the throttle.patch
linked therefrom.

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


From cnulk at scu.edu  Mon Feb 11 18:01:54 2013
From: cnulk at scu.edu (Chris Nulk)
Date: Mon, 11 Feb 2013 09:01:54 -0800
Subject: [Mailman-Users] Subject line message filtering
In-Reply-To: <51159827.2060101@msapiro.net>
References: <51153B5A.90401@scu.edu> <51159827.2060101@msapiro.net>
Message-ID: <51192402.6010804@scu.edu>

On 2/8/2013 4:28 PM, Mark Sapiro wrote:
> Chris Nulk wrote:
>
>> My regex filter is:
>>
>>        ^Subject:[\s\+]*\[.*\]\s+(Invitation|Canceled Event):.*
>
> I know you've resolved this and that the issue was that
> header_filter_rules are processed way before the subject_prefix is added
> so you didn't want the '\[.*\]'part of the pattern, but I'm confused by
> the '[\s\+]*' part of the pattern which says match 0 or more occurrences
> of the character class consisting of any white space character (\s) and
> the plus sign (either \+ or just + would be equivalent here, + loses its
> special meaning inside []).
>
> So, is [\s\+]* a typo or did you just mean \s+ or \s*?


The [\s\+]* was deliberate.  Most of our lists but the list name in 
brackets ('[', ']'), however, we have a few lists that are members of 
another list.  For those lists the list subject prefix is a plus-sign 
('+').   For example, we have a student list that has the [Student] 
prefix when the messages go out.  Faculty and staff are not members of 
the list and don't receive those messages.  Yet, there are a few faculty 
and staff who have an interest in seeing the messages so those 
faculty/staff are put on a "listening" list which is a member of the 
student list.  When a message goes to the student list, the prefix 
[Student] is added to the subject line.  The message is then sent to the 
"listening" list and it adds its own subject prefix.  Instead of having 
'[Student-Listen][Student]' show in the subject line, I changed it to a 
'+'.  The long and short of it is that I was trying to match both types 
of lines and the [\s\+]* was the bit for matching the "listening" list's 
subject prefix.

>
>
>> Also, can any of the sender/recipient filters cause the message to bypass the spam filters?  The message pipeline is unchanged.
>
> No. header_filter_rules are processed by SpamDetect which is the first
> module in the pipeline. As you discovered, the CookHeaders module which
> adds the subject_prefix comes much later, and the sender/recipient
> filters are processed by Moderate which also comes later.
>
Great information to know, thanks.

The only issue I have now is the boss wants to be able to send a reject 
message if a message is rejected when it matches a rule.  The only 
option I have is to hold the message and let the moderator send the 
rejection notice.  And since, the header rule is for our global lists, I 
am the lucky moderator.


Thanks for all the great help,
Chris

From mark at msapiro.net  Tue Feb 12 03:40:03 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 11 Feb 2013 18:40:03 -0800
Subject: [Mailman-Users] Subject line message filtering
In-Reply-To: <51192402.6010804@scu.edu>
Message-ID: <PC1993201302111839590203f63c1d06@MSAPIRO>

Chris Nulk wrote:

>On 2/8/2013 4:28 PM, Mark Sapiro wrote:
>> Chris Nulk wrote:
>>
>>> My regex filter is:
>>>
>>>        ^Subject:[\s\+]*\[.*\]\s+(Invitation|Canceled Event):.*
[...]
>The [\s\+]* was deliberate.  Most of our lists but the list name in 
>brackets ('[', ']'), however, we have a few lists that are members of 
>another list.  For those lists the list subject prefix is a plus-sign 
>('+').


OK, I get it


>The only issue I have now is the boss wants to be able to send a reject 
>message if a message is rejected when it matches a rule.  The only 
>option I have is to hold the message and let the moderator send the 
>rejection notice.  And since, the header rule is for our global lists, I 
>am the lucky moderator.


If you mean you want to reject the message with something other than
the "Message rejected by filter rule match" message, then you are
correct unless you want to modify the message in the SpamDetect.py
module, i.e. change the message in

                    raise Errors.RejectMessage(
                        _('Message rejected by filter rule match'))

Making it something like:

                    raise Errors.RejectMessage(
                        _("""Some long winded,
                          Multiple line
                          Rejection message
                          """))

However, I hope these are just legitimate notifications that shouldn't
have been sent to a list and not spam. It is a very bad idea to reject
anything that might be spam because the rejection almost certainly
goes to some innocent 3rd party whose address was spoofed in the
message's headers. This is known as backscatter and is bad.


-- 
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 Feb 12 07:37:29 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 11 Feb 2013 22:37:29 -0800
Subject: [Mailman-Users] About Spam Filtering
In-Reply-To: <5118B326.8060804@metu.edu.tr>
Message-ID: <PC19932013021122372900936ad4507a@MSAPIRO>

METU E-List Admin wrote:
>
>--------------------------------------------
>$ bin/config_list -o - REGISTER | grep -A20 header_filter_rules
>header_filter_rules = [('^X-Mailer: (?!Microsoft Outlook .*)$', 7, 


This regexp won't work. The negative lookahead does not advance the
current position so your regexp says look for 'X-Mailer: ' at the
beginning of the line not followed by 'Microsoft Outlook .*' but
followed immediately by the end of the line, so it will only match a
header like 'X-Mailer: ' not followed by anything.

What you want is

^X-Mailer: (?!Microsoft Outlook .*).*$

or just

^X-Mailer: (?!Microsoft Outlook .*)

or maybe even just

^X-Mailer: (?!Microsoft Outlook )

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


From listeyon at metu.edu.tr  Tue Feb 12 08:25:48 2013
From: listeyon at metu.edu.tr (METU E-List Admin)
Date: Tue, 12 Feb 2013 09:25:48 +0200
Subject: [Mailman-Users] About Spam Filtering
In-Reply-To: <PC19932013021122372900936ad4507a@MSAPIRO>
References: <PC19932013021122372900936ad4507a@MSAPIRO>
Message-ID: <5119EE7C.7050203@metu.edu.tr>

Thank you for your support. I have changed the regexp to

^X-Mailer: (?!Microsoft Outlook .*).*$

and I will watch for the next emails. I will also watch for the logs for 
a few days, then revert back to original file.

Thanks

On 02/12/2013 08:37 AM, Mark Sapiro wrote:
> METU E-List Admin wrote:
>> --------------------------------------------
>> $ bin/config_list -o - REGISTER | grep -A20 header_filter_rules
>> header_filter_rules = [('^X-Mailer: (?!Microsoft Outlook .*)$', 7,
>
> This regexp won't work. The negative lookahead does not advance the
> current position so your regexp says look for 'X-Mailer: ' at the
> beginning of the line not followed by 'Microsoft Outlook .*' but
> followed immediately by the end of the line, so it will only match a
> header like 'X-Mailer: ' not followed by anything.
>
> What you want is
>
> ^X-Mailer: (?!Microsoft Outlook .*).*$
>
> or just
>
> ^X-Mailer: (?!Microsoft Outlook .*)
>
> or maybe even just
>
> ^X-Mailer: (?!Microsoft Outlook )
>


From s.watkins at nhm.ac.uk  Tue Feb 12 11:25:28 2013
From: s.watkins at nhm.ac.uk (Steff Watkins)
Date: Tue, 12 Feb 2013 10:25:28 +0000
Subject: [Mailman-Users] Solaris 10 and Mailman
In-Reply-To: <1920D254-9007-4313-95C8-5489ED9427D1@uci.edu>
References: <1920D254-9007-4313-95C8-5489ED9427D1@uci.edu>
Message-ID: <A5516D1928EF5B46BFE2E3A626B322CE66A0C8C0@EXC-JONES.nhm.ac.uk>

> -----Original Message-----
> Sent: Friday, February 08, 2013 6:41 PM
> Subject: [Mailman-Users] Solaris 10 and Mailman
> 
> Hello,
> 
> Does anyone happen to have a SMF script for mailman they would care to
> share.
> 
> Thanks in advance.
> Con Wieland
> Office of Information Technology
> University of California at Irvine

Hi,

 A quick google turns up the following : https://github.com/snltd/smf/blob/master/manifest/mailman.xml

It looks (at a brief glance) like it'd work pretty much straight out of the box although you will probably have to change exec line so that it calls mailmanctrl rather than mailman.sh as it does. You'll probably also want to change the dependency 'name' for your MTA as the one you're using will probably differ from svc:/snltd/exim:default.. or you could always just drop the requirement to have mailman's operation 'dependent' on the state of your system's MTA.

I quite like this SMF xml for mailman as it lists filesystem, network, MTA and name services as 'dependencies' so in a way it should check that all the daemons needed for a healthy mailing list service are running.

Anyway it looks like a pretty good place to start. Good luck.

Steff

-----
Steff Watkins?? ??????? ??????? Natural History Museum, Cromwell Road, London,SW75BD
Systems programmer?????? ??????? Email: s.watkins at nhm.ac.uk
Systems Team???? ??????? ??????? Phone: +44 (0)20 7942 6000 opt 2
========
"Many were increasingly of the opinion that they'd all made a big mistake in coming down from the trees in the first place. And some said that even the trees had been a bad move, and that no one should ever have left the oceans." - HHGTTG





From misterbhatt at gmail.com  Tue Feb 12 13:47:06 2013
From: misterbhatt at gmail.com (Amit Bhatt)
Date: Tue, 12 Feb 2013 18:17:06 +0530
Subject: [Mailman-Users] Attachment with welcome message
Message-ID: <33A60581B22F47BBBA2D2917C301EFD9@amit>

I wish to send an attached file with list guidelines via welcome message when the confirmation E-Mail reaches to the new subscriber.

How can we do this?

Thanks,

Amit Bhatt

From dap1 at bellsouth.net  Tue Feb 12 15:48:47 2013
From: dap1 at bellsouth.net (Dennis Putnam)
Date: Tue, 12 Feb 2013 09:48:47 -0500
Subject: [Mailman-Users] Change Listname Suffix Separator?
Message-ID: <511A564F.3070007@bellsouth.net>

I have a mail provider that does not allow dashes in mailbox names. I
have been forced to set up addresses of the form listname.request, etc.
Since I am using fetchmail I can easily route those addresses to the
normal mailboxes with the dashes. However, all the mailman messages and 
web addresses are wrong. I am guessing there is no easy way to fix that
but what is the best way and what files are involved? TIA.

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

From brad at fineby.me.uk  Tue Feb 12 15:37:04 2013
From: brad at fineby.me.uk (Brad Rogers)
Date: Tue, 12 Feb 2013 14:37:04 +0000
Subject: [Mailman-Users] Attachment with welcome message
In-Reply-To: <33A60581B22F47BBBA2D2917C301EFD9@amit>
References: <33A60581B22F47BBBA2D2917C301EFD9@amit>
Message-ID: <20130212143704.62dc4388@abydos.stargate.org.uk>

On Tue, 12 Feb 2013 18:17:06 +0530
"Amit Bhatt" <misterbhatt at gmail.com> wrote:

Hello Amit,

>I wish to send an attached file with list guidelines via welcome

Does it need to be an attachment?  Why not enter the guidelines into the
body of the message as plain text?

<soapbox>
Of course, 99.999% of people *don't* read the welcome message, never
mind keep a copy so they have the unsubscribe instructions.  Not that
the unsub instructions are generally needed, since they often get tacked
onto the end of every list mail anyway.  Even then, people seem to have
difficulty unsubscribing should the need arise.
</soapbox>

-- 
 Regards  _
         / )           "The blindingly obvious is
        / _)rad        never immediately apparent"
Who's a sucker now?
Edward The Bear - The Damned
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20130212/e28923e0/attachment.pgp>

From cnulk at scu.edu  Tue Feb 12 17:26:46 2013
From: cnulk at scu.edu (Chris Nulk)
Date: Tue, 12 Feb 2013 08:26:46 -0800
Subject: [Mailman-Users] Subject line message filtering
In-Reply-To: <PC1993201302111839590203f63c1d06@MSAPIRO>
References: <PC1993201302111839590203f63c1d06@MSAPIRO>
Message-ID: <511A6D46.5000004@scu.edu>

On 2/11/2013 6:40 PM, Mark Sapiro wrote:
> Chris Nulk wrote:
{SNIP}
>> The only issue I have now is the boss wants to be able to send a reject
>> message if a message is rejected when it matches a rule.  The only
>> option I have is to hold the message and let the moderator send the
>> rejection notice.  And since, the header rule is for our global lists, I
>> am the lucky moderator.
>
> If you mean you want to reject the message with something other than
> the "Message rejected by filter rule match" message, then you are
> correct unless you want to modify the message in the SpamDetect.py
> module, i.e. change the message in
>
>                      raise Errors.RejectMessage(
>                          _('Message rejected by filter rule match'))
>
> Making it something like:
>
>                      raise Errors.RejectMessage(
>                          _("""Some long winded,
>                            Multiple line
>                            Rejection message
>                            """))
>
> However, I hope these are just legitimate notifications that shouldn't
> have been sent to a list and not spam. It is a very bad idea to reject
> anything that might be spam because the rejection almost certainly
> goes to some innocent 3rd party whose address was spoofed in the
> message's headers. This is known as backscatter and is bad.
>
>
The messages I am trying to keep from getting to the list are Google 
Calendar invitations (and cancellations).  For these messages or 
specifically targeted non-spam type messages where I have to use the 
spam filters to get rid of them, I would like to send a rejection notice 
giving a reason why the posting is not allowed.  Any spam filters I set 
up for known spam and like messages, I usually just discard the 
message.  I certainly don't want to do any backscatter.

Thanks, Mark.

Chris

From cpz at tuunq.com  Tue Feb 12 17:15:05 2013
From: cpz at tuunq.com (Carl Zwanzig)
Date: Tue, 12 Feb 2013 08:15:05 -0800
Subject: [Mailman-Users] Attachment with welcome message
In-Reply-To: <20130212143704.62dc4388@abydos.stargate.org.uk>
References: <33A60581B22F47BBBA2D2917C301EFD9@amit>
	<20130212143704.62dc4388@abydos.stargate.org.uk>
Message-ID: <511A6A89.3060804@tuunq.com>

On 2/12/2013 6:37 AM, Brad Rogers wrote:
> On Tue, 12 Feb 2013 18:17:06 +0530
> "Amit Bhatt" <misterbhatt at gmail.com> wrote:

>> I wish to send an attached file with list guidelines via welcome
>
> Does it need to be an attachment?  Why not enter the guidelines into the
> body of the message as plain text?

That was my first thought. Put all the info in the main message (and make 
sure there's a readable text/plain part, too). Doesn't guarantee that it'll 
be read, but higher probability than if the user has to do something extra, 
like click on the attachment.

z!


From mark at msapiro.net  Tue Feb 12 21:00:52 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 12 Feb 2013 12:00:52 -0800
Subject: [Mailman-Users] Attachment with welcome message
In-Reply-To: <511A6A89.3060804@tuunq.com>
Message-ID: <PC1993201302121200520343004ec98b@MSAPIRO>

Carl Zwanzig wrote:
>
>That was my first thought. Put all the info in the main message (and make 
>sure there's a readable text/plain part, too).


Absolutely! (There's way too much attaching of word processing
documents and PDFs where simple plain text will do).

Just put the text of your guidelines in the list's General Options ->
welcome_msg box. See the "(Details for welcome_msg)" link for more
info.

Note that the welcome message itself is sent as a simple text/plain
message so there is no way to include HTML or attachments.

-- 
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 Feb 12 21:25:47 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 12 Feb 2013 12:25:47 -0800
Subject: [Mailman-Users] Change Listname Suffix Separator?
In-Reply-To: <511A564F.3070007@bellsouth.net>
References: <511A564F.3070007@bellsouth.net>
Message-ID: <511AA54B.1000905@msapiro.net>

On 2/12/2013 6:48 AM, Dennis Putnam wrote:
> I have a mail provider that does not allow dashes in mailbox names. I
> have been forced to set up addresses of the form listname.request, etc.
> Since I am using fetchmail I can easily route those addresses to the
> normal mailboxes with the dashes. However, all the mailman messages and 
> web addresses are wrong. I am guessing there is no easy way to fix that
> but what is the best way and what files are involved? TIA.


It *think* there are only 3 modules that need changing to do this.

1) If you are using Mailman aliases on your Mailman server (the above
seems to say you might be), there are two places in Mailman/MTA/Utils.py
where you need to change '%s-%s' to '%s.%s' although you probably aren't
using maildir delivery so only the one in the definition of
_makealiases_mailprog really needs to be changed.

2) For the site list, in the definition of get_site_email in
Mailman/Utils.py, change

    return '%s-%s@%s' % (mm_cfg.MAILMAN_SITE_LIST, extra, hostname)

to

    return '%s.%s@%s' % (mm_cfg.MAILMAN_SITE_LIST, extra, hostname)

3) For the rest, in the definition of getListAddress in
Mailman/MailList.py, change

        return '%s-%s@%s' % (self.internal_name(), extra, ...

to

        return '%s.%s@%s' % (self.internal_name(), extra, ...

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


From tanstaafl at libertytrek.org  Tue Feb 12 22:56:38 2013
From: tanstaafl at libertytrek.org (Tanstaafl)
Date: Tue, 12 Feb 2013 16:56:38 -0500
Subject: [Mailman-Users] Attachment with welcome message
In-Reply-To: <PC1993201302121200520343004ec98b@MSAPIRO>
References: <PC1993201302121200520343004ec98b@MSAPIRO>
Message-ID: <511ABA96.2010504@libertytrek.org>

On 2013-02-12 3:00 PM, Mark Sapiro <mark at msapiro.net> wrote:
> Carl Zwanzig wrote:
>>
>> That was my first thought. Put all the info in the main message (and make
>> sure there's a readable text/plain part, too).

> Absolutely! (There's way too much attaching of word processing
> documents and PDFs where simple plain text will do).

Not to mention the fact that someone who neglects to read the email body 
is even more likely to ignore an attachment...

From dap1 at bellsouth.net  Wed Feb 13 15:11:49 2013
From: dap1 at bellsouth.net (Dennis Putnam)
Date: Wed, 13 Feb 2013 09:11:49 -0500
Subject: [Mailman-Users] From Header Changed
Message-ID: <511B9F25.8090001@bellsouth.net>

I have not made any changes (intentionally) to mailman in many months
but suddenly mail from the list has listname-bounces as the from header
rather then the original poster. I have to assume that one of my CentOS
updates changed something, although I don't recall seeing any automatic
updates to mailman. I can't seem to find where to set that header. In
any case wherever I set it before must have been wrong for an update to
overwrite it (assuming that is what caused this).

Also, I'm guessing this is related, bounced messages are now being
handled as uncaught bounces.

The attached message was received as a bounce, but either the bounce
format was not recognized, or no member addresses could be extracted
from it.  This mailing list has been configured to send all
unrecognized bounce messages to the list administrator(s).

This is in spite of the fact that the reason for the bounce and the bad address are quite clear in the bounced message (sanitized).

Sorry, we were unable to deliver your message to the following address.

<******@aol.com>:
Remote host said: 550 5.1.1 <*******@aol.com>: Recipient address rejected: aol.com [RCPT_TO]

If the reason is because that address is not a recognized member address, then how did it get sent there in the first place? The content was indeed a list message.

Can someone help sort out what is wrong and how to prevent it in the future? Thanks.



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

From mark at msapiro.net  Wed Feb 13 16:50:28 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 13 Feb 2013 07:50:28 -0800
Subject: [Mailman-Users] From Header Changed
In-Reply-To: <511B9F25.8090001@bellsouth.net>
References: <511B9F25.8090001@bellsouth.net>
Message-ID: <511BB644.9000002@msapiro.net>

On 2/13/2013 6:11 AM, Dennis Putnam wrote:
> I have not made any changes (intentionally) to mailman in many months
> but suddenly mail from the list has listname-bounces as the from header
> rather then the original poster.


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

What does the sender look like in the archived messages?


> Also, I'm guessing this is related, bounced messages are now being
> handled as uncaught bounces.
> 
> The attached message was received as a bounce, but either the bounce
> format was not recognized, or no member addresses could be extracted
> from it.  This mailing list has been configured to send all
> unrecognized bounce messages to the list administrator(s).
> 
> This is in spite of the fact that the reason for the bounce and the bad address are quite clear in the bounced message (sanitized).
> 
> Sorry, we were unable to deliver your message to the following address.
> 
> <******@aol.com>:
> Remote host said: 550 5.1.1 <*******@aol.com>: Recipient address rejected: aol.com [RCPT_TO]
> 
> If the reason is because that address is not a recognized member address, then how did it get sent there in the first place? The content was indeed a list message.


The reason is no address can be parsed from the message. It has nothing
to do with whether or not the address is that of a list member.

This could be something broken in Mailman (not likely related to the
From: issue), or it could be some new bounce format not currently
recognized.

Please send me a copy of the raw unrecognized bounce attachment and tell
me what Mailman version this is.

Also, if the FAQ linked above doesn't explain the From: issue, send me a
copy of a complete, raw message 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 rick at blaisedrake.com  Wed Feb 13 16:47:33 2013
From: rick at blaisedrake.com (rick at blaisedrake.com)
Date: Wed, 13 Feb 2013 10:47:33 -0500
Subject: [Mailman-Users] Keyword Filtering
Message-ID: <01b601ce0a01$70fa73f0$52ef5bd0$@blaisedrake.com>

Hello,

Is there a way to configure Mailman to have messages with a specific Keyword
included in the Subject and/or the Body of the email bounced to moderation?
We have searched and couldn't find a solid solution.  

Quick Note: 
- Our list is currently unmoderated and we are trying to keep it that way.
- Example:  a member sends  an email with the word TEST in the body of the
email, the message would not be approved and sent to moderation.

Can't imagine this functionality is not available, we must be missing
something.

Any help or guidance would be greatly appreciated!

Thanks,

Rick



From mark at msapiro.net  Thu Feb 14 17:07:37 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 14 Feb 2013 08:07:37 -0800
Subject: [Mailman-Users] Keyword Filtering
In-Reply-To: <01b601ce0a01$70fa73f0$52ef5bd0$@blaisedrake.com>
Message-ID: <PC19932013021408073707814678f732@MSAPIRO>

<rick at blaisedrake.com> wrote:
>
>Is there a way to configure Mailman to have messages with a specific Keyword
>included in the Subject and/or the Body of the email bounced to moderation?
>We have searched and couldn't find a solid solution.  


Subject:, yes; body, no.

To filter on Subject:, see Privacy options... -> Spam filters ->
header_filter_rules in the web admin interface.

Filtering on body content requires a custom handler. See the FAQ at
<http://wiki.list.org/x/l4A9>.

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


From lummoxx at gmail.com  Thu Feb 14 19:15:40 2013
From: lummoxx at gmail.com (Lummoxx)
Date: Thu, 14 Feb 2013 13:15:40 -0500
Subject: [Mailman-Users] ImportError: cannot import name _C
Message-ID: <CAF_HfKP-xoSFp67uouR+REz+Gine9BqdSmUJ6c_PAN6cMTpwcA@mail.gmail.com>

Running mailman 2.1.12 on RHEL6.  Imported lists from a RHEL5 server
running mailman 2.1.9.

Mailman itself seems to be running fine.  It's a fairly large installation
with over 760 lists, and messages sent to lists I subscribe to on the
server are sent and received as expected.

I need to reset a list password, but when I run ./reset_pw.py, I get a
python error:

Traceback (most recent call last):

  File "./reset_pw.py", line 41, in <module>

    from Mailman.i18n import _C
ImportError: cannot import name _C

I ran python interactively from the bin/ directory, and manually importing
path, Mailman, and Mailman.i18n worked fine, but then trying "from
Mailman.i18n import _C" interactively fails.

Thanks!

From mark at msapiro.net  Fri Feb 15 02:11:06 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 14 Feb 2013 17:11:06 -0800
Subject: [Mailman-Users] ImportError: cannot import name _C
In-Reply-To: <CAF_HfKP-xoSFp67uouR+REz+Gine9BqdSmUJ6c_PAN6cMTpwcA@mail.gmail.com>
Message-ID: <PC1993201302141711060156cf3d44a2@MSAPIRO>

Lummoxx wrote:
>
>I need to reset a list password, but when I run ./reset_pw.py, I get a
>python error:


This is not the way to run reset_pw.py.

You run it with 'withlist', but there is some issue with your copy of
reset_pw.py. Running it via ./reset_pw.py hould produce usage
instructions, not a traceback.


>Traceback (most recent call last):
>
>  File "./reset_pw.py", line 41, in <module>
>
>    from Mailman.i18n import _C
>ImportError: cannot import name _C


Your copy of reset_pw.py is corrupted somehow. Line 41 in the file
should be

from Mailman.i18n import _

(no C at the end). Get a clean copy at
<http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/bin/reset_pw.py>.
Note this is an 'unconfigured' file. replace @PYTHON@ on the first
line with /usr/bin/python or whatever the path to the python used by
Mailman is.

-- 
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  Fri Feb 15 14:56:52 2013
From: es at fruitcom.com (Eric Smith)
Date: Fri, 15 Feb 2013 14:56:52 +0100
Subject: [Mailman-Users] mult-site installation - virtual domains and postfix
Message-ID: <20130215135652.GA32437@trustfood.org>

I could not find the documentation that I read previously on how
to install mailman so that each virtual domain has distinct lists.
For example they may have the same listname ad are distinct by
the fact that they are in another domain.

Would someone please point me to the instructions.

-- 
Eric Smith

From mark at msapiro.net  Fri Feb 15 15:14:22 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 15 Feb 2013 06:14:22 -0800
Subject: [Mailman-Users] mult-site installation - virtual domains and
	postfix
In-Reply-To: <20130215135652.GA32437@trustfood.org>
Message-ID: <PC1993201302150614220906503653a0@MSAPIRO>


Eric Smith wrote:

>I could not find the documentation that I read previously on how
>to install mailman so that each virtual domain has distinct lists.
>For example they may have the same listname ad are distinct by
>the fact that they are in another domain.


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

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


From tanstaafl at libertytrek.org  Fri Feb 15 15:41:14 2013
From: tanstaafl at libertytrek.org (Tanstaafl)
Date: Fri, 15 Feb 2013 09:41:14 -0500
Subject: [Mailman-Users] OT - Regex help (was: Re: About Spam Filtering
Message-ID: <511E490A.2080202@libertytrek.org>

Hello,

Apologies for the OT post, but I've been struggling with a regex for a 
long time, trying to get it to work with my postfixadmin vacation.pl, 
and for the life of me, I can't seem to get it right. I've asked 
numerous times on the postfixadmin list, but no one there has been able 
to help.

If this is too OT or no one can help, that is ok, but I just thought 
maybe someone here might be able to see why this line isn't working...

Here is the line with the regex in it:

> elsif (/^from:.*+(bounce|do-not-reply|facebook|linkedin|list-|myspace|twitter)/i) { $logger->debug("Multi-string From header matching $1: $2 found; exiting"); exit (0); }

What I want is for it to match any 'From' header that contains any one 
of the strings in it (ie, bounce, do-not-reply, etc). We get a lot of 
list related stuff that the vacation.pl responds to that I don't want it 
to respond to, so I want a one-liner that I can manually add these 
strings too whenever I see one go out that shouldn't, so we don't 
respond to things that shouldn't be responded to.

Does anything jump out at you as to why it isn't catching anything?

Thanks in advance (to Mark or anyone who might be able to help)...


On 2013-02-12 1:37 AM, Mark Sapiro <mark at msapiro.net> wrote:> METU 
E-List Admin wrote:
 >>
 >> --------------------------------------------
 >> $ bin/config_list -o - REGISTER | grep -A20 header_filter_rules
 >> header_filter_rules = [('^X-Mailer: (?!Microsoft Outlook .*)$', 7,
 >
 >
 > This regexp won't work. The negative lookahead does not advance the
 > current position so your regexp says look for 'X-Mailer: ' at the
 > beginning of the line not followed by 'Microsoft Outlook .*' but
 > followed immediately by the end of the line, so it will only match a
 > header like 'X-Mailer: ' not followed by anything.
 >
 > What you want is
 >
 > ^X-Mailer: (?!Microsoft Outlook .*).*$
 >
 > or just
 >
 > ^X-Mailer: (?!Microsoft Outlook .*)
 >
 > or maybe even just
 >
 > ^X-Mailer: (?!Microsoft Outlook )
 >


From tanstaafl at libertytrek.org  Fri Feb 15 15:53:56 2013
From: tanstaafl at libertytrek.org (Tanstaafl)
Date: Fri, 15 Feb 2013 09:53:56 -0500
Subject: [Mailman-Users] OT - Regex help (was: Re: About Spam Filtering
In-Reply-To: <511E490A.2080202@libertytrek.org>
References: <511E490A.2080202@libertytrek.org>
Message-ID: <511E4C04.7000206@libertytrek.org>

On 2013-02-15 9:41 AM, Tanstaafl <tanstaafl at libertytrek.org> wrote:
> We get a lot of list related stuff that the vacation.pl responds to that
> I don't want it to respond to,

To clarify - by 'list-related', I mean announce/newsletter type junk 
that our users subscribe to, not necessarily mailman list posts...

Also, I want not respond to *any* social networking messages at all, I 
just want a single custom line that I can add any string that I want to 
test for.

I would never use anything like this to reject or otherwise interfere 
with *receiving* mail, but I have a much lower bar when it comes to 
stuff I don't want my vacation.pl to reply to, so false positives are 
not a real concern for me here.

From brennan at columbia.edu  Fri Feb 15 16:25:38 2013
From: brennan at columbia.edu (Joseph Brennan)
Date: Fri, 15 Feb 2013 10:25:38 -0500
Subject: [Mailman-Users] OT - Regex help (was: Re: About Spam Filtering
In-Reply-To: <511E490A.2080202@libertytrek.org>
References: <511E490A.2080202@libertytrek.org>
Message-ID: <BE5572BB7FACB8AFB2A14237@sodor.cc.columbia.edu>



elsif 
(/^from:.*+(bounce|do-not-reply|facebook|linkedin|list-|myspace|twitter)/i) 
{ $logger->debug("Multi-string From header matching $1: $2 found; 
exiting"); exit (0); }


Examine the logic of the 'if' and any 'elsif' above this line.

I am uncertain what /.*+/ would do. Remove either * or +.

Otherwise this looks reasonable to me.

Joseph Brennan
Columbia University Information Technology




From stephen at xemacs.org  Fri Feb 15 17:34:22 2013
From: stephen at xemacs.org (Stephen J. Turnbull)
Date: Sat, 16 Feb 2013 01:34:22 +0900
Subject: [Mailman-Users]  OT - Regex help (was: Re: About Spam Filtering
In-Reply-To: <511E490A.2080202@libertytrek.org>
References: <511E490A.2080202@libertytrek.org>
Message-ID: <87wqu9wn75.fsf@uwakimon.sk.tsukuba.ac.jp>

Like Joseph, I don't know what /.*+/ does, but this

$ echo 'From bounce' | perl -ane 'print if /From.*bounce/;'
>From bounce
$ echo 'From bounce' | perl -ane 'print if /From.*+bounce/;'
$ 

shows what it doesn't do.


From lummoxx at gmail.com  Fri Feb 15 23:16:46 2013
From: lummoxx at gmail.com (Lummoxx)
Date: Fri, 15 Feb 2013 17:16:46 -0500
Subject: [Mailman-Users] ImportError: cannot import name _C
In-Reply-To: <PC1993201302141711060156cf3d44a2@MSAPIRO>
References: <PC1993201302141711060156cf3d44a2@MSAPIRO>
Message-ID: <511EB3CE.3090109@gmail.com>

On 02/14/2013 08:11 PM, Mark Sapiro wrote:
> Lummoxx wrote:
>> I need to reset a list password, but when I run ./reset_pw.py, I get a
>> python error:
>
> This is not the way to run reset_pw.py.
After I saw it wasn't working the usual way, I was just doing it that 
way to generate the error.
>> Traceback (most recent call last):
>>
>>   File "./reset_pw.py", line 41, in <module>
>>
>>     from Mailman.i18n import _C
>> ImportError: cannot import name _C
>
> Your copy of reset_pw.py is corrupted somehow. Line 41 in the file
> should be
I downloaded a new copy, and all seems to be well.  I'll keep an eye out 
and see if that happened elsewhere, as well.

This was a yum package install in RHEL 6.2, so no idea how it happened.

Thanks for the quick response!


From hawat.thufir at gmail.com  Sat Feb 16 07:58:38 2013
From: hawat.thufir at gmail.com (Thufir)
Date: Fri, 15 Feb 2013 22:58:38 -0800
Subject: [Mailman-Users] rmlist results
Message-ID: <511F2E1E.3080705@gmail.com>

It seems like thunderbird has some difficulty with maildir:

https://wiki.mozilla.org/Thunderbird:Pluggable_Mail_Stores

so I'm still using mbox.  Are the below errors simply because I wasn't 
running rmlist as sudo?  It should be run as sudo?


thufir at dur:~$
thufir at dur:~$ rmlist alpha
Not removing archives.  Reinvoke with -a to remove them.
Traceback (most recent call last):
   File "/usr/sbin/rmlist", line 161, in <module>
     main()
   File "/usr/sbin/rmlist", line 116, in main
     mlist = MailList.MailList(listname, lock=0)
   File "/var/lib/mailman/Mailman/MailList.py", line 130, in __init__
     self.Load()
   File "/var/lib/mailman/Mailman/MailList.py", line 650, in Load
     dict, e = self.__load(file)
   File "/var/lib/mailman/Mailman/MailList.py", line 615, in __load
     fp = open(dbfile)
IOError: [Errno 13] Permission denied: 
'/var/lib/mailman/lists/alpha/config.pck'
thufir at dur:~$
thufir at dur:~$ sudo rmlist -a alpha
[sudo] password for thufir:
Removing list info
Removing private archives
Removing private archives
Removing public archives
alpha public archives not found as 
/var/lib/mailman/archives/public/alpha.mbox
thufir at dur:~$


thanks,

Thufir

From tanstaafl at libertytrek.org  Sat Feb 16 14:08:50 2013
From: tanstaafl at libertytrek.org (Tanstaafl)
Date: Sat, 16 Feb 2013 08:08:50 -0500
Subject: [Mailman-Users] OT - Regex help (was: Re: About Spam Filtering
In-Reply-To: <BE5572BB7FACB8AFB2A14237@sodor.cc.columbia.edu>
References: <511E490A.2080202@libertytrek.org>
	<BE5572BB7FACB8AFB2A14237@sodor.cc.columbia.edu>
Message-ID: <511F84E2.9000109@libertytrek.org>

On 2013-02-15 10:25 AM, Joseph Brennan <brennan at columbia.edu> wrote:
>
> elsif
> (/^from:.*+(bounce|do-not-reply|facebook|linkedin|list-|myspace|twitter)/i)
> { $logger->debug("Multi-string From header matching $1: $2 found;
> exiting"); exit (0); }
>
>
> Examine the logic of the 'if' and any 'elsif' above this line.
>
> I am uncertain what /.*+/ would do. Remove either * or +.

Thanks for the help Joseph (and Stephen)...

This 'if' block is just a bunch of separate one line tests that, if any 
of them match, result in the vacation response not being sent, so it 
doesn't really matter what is above them (they are all the defaults, 
this is the only line I am modifying)...

This line should simply examine any from header, and if any of the 
included strings are found *anywhere* in the from address, local or 
domain part, so, either side of the '@' sign, and regardless of any dots 
anywhere in the string.

I imagine that is why the guys from postfixadmin used the * and maybe 
the +? Like I said, I've got no experience with regex at all - guess its 
time to learn eh? ;)

Anyway, I want the regex such that any/all of the following from 
addresses would match (along with all of the other strings):

bounce-anything at example.com
anything at bounce.example.com
anything at bounce-reply.example.com
facebook at example.com
anything.facebook at example.com
anything-facebook at example.com
anything at something.facebook.com

Hopefully that is enough examples...

Basically, if *any* of the strings I might specify inside the 
parenthesis match individually anywhere in the from address, then don't 
send the response (ie, positive match).

Thanks again, it is really appreciated...

From mark at msapiro.net  Sat Feb 16 15:28:19 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 16 Feb 2013 06:28:19 -0800
Subject: [Mailman-Users] rmlist results
In-Reply-To: <511F2E1E.3080705@gmail.com>
Message-ID: <PC1993201302160628190500fb0c8607@MSAPIRO>

Thufir wrote:

>Are the below errors simply because I wasn't 
>running rmlist as sudo?  It should be run as sudo?


Yes. All Mailman's command line scripts need to run as root or
(preferably) as a user in Mailman's group (usually group mailman).

-- 
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  Sat Feb 16 15:42:04 2013
From: stephen at xemacs.org (Stephen J. Turnbull)
Date: Sat, 16 Feb 2013 23:42:04 +0900
Subject: [Mailman-Users] OT - Regex help (was: Re: About Spam Filtering
In-Reply-To: <511F84E2.9000109@libertytrek.org>
References: <511E490A.2080202@libertytrek.org>
	<BE5572BB7FACB8AFB2A14237@sodor.cc.columbia.edu>
	<511F84E2.9000109@libertytrek.org>
Message-ID: <87pq00wcar.fsf@uwakimon.sk.tsukuba.ac.jp>

Tanstaafl writes:
 > On 2013-02-15 10:25 AM, Joseph Brennan <brennan at columbia.edu> wrote:

 > > I am uncertain what /.*+/ would do. Remove either * or +.

As Joseph says, change the first part of your regexp from "^From:.*+"
to "^from:.*" or "^from:.+" (I would choose the former because it's
more inclusive, thus less backscatter to those addresses).

 > Like I said, I've got no experience with regex at all - guess its
 > time to learn eh? ;)

Yes.  I don't know specifically about Perl/Python, but there are
definitely tools out there which will help you build regexps from such
lists of strings.


From brennan at columbia.edu  Sat Feb 16 15:54:07 2013
From: brennan at columbia.edu (Joseph Brennan)
Date: Sat, 16 Feb 2013 09:54:07 -0500
Subject: [Mailman-Users] OT - Regex help (was: Re: About Spam Filtering
In-Reply-To: <511F84E2.9000109@libertytrek.org>
References: <511E490A.2080202@libertytrek.org>
	<BE5572BB7FACB8AFB2A14237@sodor.cc.columbia.edu>
	<511F84E2.9000109@libertytrek.org>
Message-ID: <EA986C10E4C5471AFA6521ED@[10.0.1.8]>



--On Saturday, February 16, 2013 8:08 AM -0500 Tanstaafl 
<tanstaafl at libertytrek.org> wrote:

> On 2013-02-15 10:25 AM, Joseph Brennan <brennan at columbia.edu> wrote:
>>
>> elsif
>> (/^from:.*+(bounce|do-not-reply|facebook|linkedin|list-|myspace|twitter)
>> /i) { $logger->debug("Multi-string From header matching $1: $2 found;
>> exiting"); exit (0); }


> This 'if' block is just a bunch of separate one line tests that, if any
> of them match, result in the vacation response not being sent, so it
> doesn't really matter what is above them (they are all the defaults, this
> is the only line I am modifying)...

Not exactly. If you chain them with elsif then the conditions are tested
in order until one matches, and any after that are not tested. If one of
the earlier conditions matched then your rule would never match.

Remove the + mark (and learn what .* means) and you're probably done.

In the debug statement, $1 will be the string in ( ) that matched, but
$2 is not defined since there is no other ( ) string.


Joe Brennan


From tanstaafl at libertytrek.org  Sat Feb 16 16:56:07 2013
From: tanstaafl at libertytrek.org (Tanstaafl)
Date: Sat, 16 Feb 2013 10:56:07 -0500
Subject: [Mailman-Users] OT - Regex help (was: Re: About Spam Filtering
In-Reply-To: <EA986C10E4C5471AFA6521ED@[10.0.1.8]>
References: <511E490A.2080202@libertytrek.org>
	<BE5572BB7FACB8AFB2A14237@sodor.cc.columbia.edu>
	<511F84E2.9000109@libertytrek.org>
	<EA986C10E4C5471AFA6521ED@[10.0.1.8]>
Message-ID: <511FAC17.2080004@libertytrek.org>

On 2013-02-16 9:54 AM, Joseph Brennan <brennan at columbia.edu> wrote:
>> This 'if' block is just a bunch of separate one line tests that, if any
>> of them match, result in the vacation response not being sent, so it
>> doesn't really matter what is above them (they are all the defaults, this
>> is the only line I am modifying)...
>
> Not exactly. If you chain them with elsif then the conditions are tested
> in order until one matches, and any after that are not tested. If one of
> the earlier conditions matched then your rule would never match.

Correct... what I meant was, if one of the prior tests match, then the 
vacation message will NOT be sent, so my test is irrelevant, since it 
only has the potential to do the same thing (prevent the message from 
being generated).

None of these tests are used to send the message, only prevent it from 
being sent...

> Remove the + mark (and learn what .* means) and you're probably done.

Done... hopefully this will fix things up... thanks again!

> In the debug statement, $1 will be the string in ( ) that matched, but
> $2 is not defined since there is no other ( ) string.

Ok, fixed that too...

Thanks again! If this works as expected I should be able to get the 
postfixadmin guys to add this to the default vacation.pl, with a 
description of how to use it...

From tanstaafl at libertytrek.org  Sun Feb 17 18:51:33 2013
From: tanstaafl at libertytrek.org (Tanstaafl)
Date: Sun, 17 Feb 2013 12:51:33 -0500
Subject: [Mailman-Users] SMTP_MAX_RCPTS setting
Message-ID: <512118A5.7090707@libertytrek.org>

Hi all,

I'm looking to add some rate limiting to my postfix, but need to know 
how postfix's smtpd_recipient_limit interacts with mailman...

After thinking about this, I just don't really see any rational reason 
that normal users should be sending to 100 recipients at one time. If 
they need a list, they can ask me to set one up for them.

So, my understanding is that if I send an email to one of my lists, and 
it has 50 people who are at the same destination domain (ie 
'example.com'), then mailman will generate a single message with 50 
recipients to this one domain (and separate messages for other domains) 
- is this correct?

If so, and if I reduce postfix's smtpd_recipient_limit to, say, 20, then 
I would also need to set SMTP_MAX_RCPTS to to 20 (or something lower 
maybe?), correct?

Thanks

From msmith13337 at gmail.com  Mon Feb 18 21:53:37 2013
From: msmith13337 at gmail.com (Michael Smith)
Date: Mon, 18 Feb 2013 21:53:37 +0100
Subject: [Mailman-Users] Odd replacement of the sender address
Message-ID: <CALwt-oksQkQR5-vPnkpYJpKxc52xzDFP54HH32pu_n1chRDV+w@mail.gmail.com>

Hey everybody!


I have a strange problem using mailman 2.1.13: Every time, a mail is sent
to one of the lists, the real sender address is replaced by
somelocaluser at example.com (somelocaluser being a unix user on the server
and example.com being the domain). This is very inconvenient since some of
the addresses doesn't even exist. Interestingly only the address is
changed; the name is unaltered. For example "John Doe <john at thedoefamily.com>"
might become "John Doe <root at example.com>".

In all the logs that I checked, the sender address was the correct one.
Even in the pipermail archives the address is correct but not in the
various MUAs of the subscribers. In every case the header information
itself was wrong in the source code of the mail. Sending e-mails to the
recipient directly through the mail server worked fine in every case (this
is why I assume the problem lies with mailman).

This problem is driving me crazy...


Cheers
Michael

From mark at msapiro.net  Tue Feb 19 06:16:40 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 18 Feb 2013 21:16:40 -0800
Subject: [Mailman-Users] Odd replacement of the sender address
In-Reply-To: <CALwt-oksQkQR5-vPnkpYJpKxc52xzDFP54HH32pu_n1chRDV+w@mail.gmail.com>
Message-ID: <PC199320130218211640065646b698b8@MSAPIRO>

Michael Smith wrote:
>
>I have a strange problem using mailman 2.1.13: Every time, a mail is sent
>to one of the lists, the real sender address is replaced by
>somelocaluser at example.com (somelocaluser being a unix user on the server
>and example.com being the domain). This is very inconvenient since some of
>the addresses doesn't even exist. Interestingly only the address is
>changed; the name is unaltered. For example "John Doe <john at thedoefamily.com>"
>might become "John Doe <root at example.com>".


I have been working a similar but not identical problem (From: header
replaced with one containing Sender: or the envelope sender). See the
thread at
<http://mail.python.org/pipermail/mailman-users/2013-February/074709.html>
for the start of this.

I gave him the attached patch to Mailman/Handlers/SMTPDirect.py, which
logs the content of the messages From: and Message-ID: headers upon
entry to SMTPDirect.py and after delivery to the outgoing MTA. The
From: is unchanged in these log messages, and the ultimate, erroneous
From: has been added after (above in the message headers) the
Received: header added by the outgoing MTA.

Thus, it seems that the header must be munged or removed after initial
SMTP delivery to the outgoing MTA. You might try the patch and see if
the same appears true in your case.

The instructions I provided with the patch (his MTA is Postfix) are:

SMTPDirect.patch.txt is a patch you can apply to
Mailman/Handlers/SMTPDirect.py via the command

patch /path/to/Mailman/Handlers/SMTPDirect.py
/path/to/SMTPDirect.patch.txt

(all on one line). This adds two statements to log to Mailman's 'debug'
log the values of each message's From: header and Message-ID: header
upon entry and after sending the message. Apply this patch and restart
Mailman and then look at Mailman's 'debug' log after a post.

Then you can remove the patch via

patch -R /path/to/Mailman/Handlers/SMTPDirect.py
/path/to/SMTPDirect.patch.txt

(again, all on one line) and restart Mailman. The information in the
debug log will tell us whether the message had a good From: upon entry
to SMTPDirect and whether it had a good From: upon delivery to Postfix.

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

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: SMTPDirect.patch.txt
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20130218/5b366868/attachment.txt>

From msmith13337 at gmail.com  Tue Feb 19 15:22:21 2013
From: msmith13337 at gmail.com (Michael Smith)
Date: Tue, 19 Feb 2013 15:22:21 +0100
Subject: [Mailman-Users] Odd replacement of the sender address
In-Reply-To: <PC199320130218211640065646b698b8@MSAPIRO>
References: <CALwt-oksQkQR5-vPnkpYJpKxc52xzDFP54HH32pu_n1chRDV+w@mail.gmail.com>
	<PC199320130218211640065646b698b8@MSAPIRO>
Message-ID: <CALwt-ok4O23b73RPeDSn8WA6yxq=kL-UfFzbZmjykN5q5gmXgw@mail.gmail.com>

Hi,


thanks Mark.

I applied the patch and both the incoming as well as the outgoing mail
addresses are correct according to the debug log. So does the problem lie
with postfix?


Cheers
Michael


On 19 February 2013 06:16, Mark Sapiro <mark at msapiro.net> wrote:

> Michael Smith wrote:
> >
> >I have a strange problem using mailman 2.1.13: Every time, a mail is sent
> >to one of the lists, the real sender address is replaced by
> >somelocaluser at example.com (somelocaluser being a unix user on the server
> >and example.com being the domain). This is very inconvenient since some
> of
> >the addresses doesn't even exist. Interestingly only the address is
> >changed; the name is unaltered. For example "John Doe <
> john at thedoefamily.com>"
> >might become "John Doe <root at example.com>".
>
>
> I have been working a similar but not identical problem (From: header
> replaced with one containing Sender: or the envelope sender). See the
> thread at
> <http://mail.python.org/pipermail/mailman-users/2013-February/074709.html>
> for the start of this.
>
> I gave him the attached patch to Mailman/Handlers/SMTPDirect.py, which
> logs the content of the messages From: and Message-ID: headers upon
> entry to SMTPDirect.py and after delivery to the outgoing MTA. The
> From: is unchanged in these log messages, and the ultimate, erroneous
> From: has been added after (above in the message headers) the
> Received: header added by the outgoing MTA.
>
> Thus, it seems that the header must be munged or removed after initial
> SMTP delivery to the outgoing MTA. You might try the patch and see if
> the same appears true in your case.
>
> The instructions I provided with the patch (his MTA is Postfix) are:
>
> SMTPDirect.patch.txt is a patch you can apply to
> Mailman/Handlers/SMTPDirect.py via the command
>
> patch /path/to/Mailman/Handlers/SMTPDirect.py
> /path/to/SMTPDirect.patch.txt
>
> (all on one line). This adds two statements to log to Mailman's 'debug'
> log the values of each message's From: header and Message-ID: header
> upon entry and after sending the message. Apply this patch and restart
> Mailman and then look at Mailman's 'debug' log after a post.
>
> Then you can remove the patch via
>
> patch -R /path/to/Mailman/Handlers/SMTPDirect.py
> /path/to/SMTPDirect.patch.txt
>
> (again, all on one line) and restart Mailman. The information in the
> debug log will tell us whether the message had a good From: upon entry
> to SMTPDirect and whether it had a good From: upon delivery to Postfix.
>
> --
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
>
>

From Ralf.Hildebrandt at charite.de  Tue Feb 19 15:31:06 2013
From: Ralf.Hildebrandt at charite.de (Ralf Hildebrandt)
Date: Tue, 19 Feb 2013 15:31:06 +0100
Subject: [Mailman-Users] Odd replacement of the sender address
In-Reply-To: <CALwt-ok4O23b73RPeDSn8WA6yxq=kL-UfFzbZmjykN5q5gmXgw@mail.gmail.com>
References: <CALwt-oksQkQR5-vPnkpYJpKxc52xzDFP54HH32pu_n1chRDV+w@mail.gmail.com>
	<PC199320130218211640065646b698b8@MSAPIRO>
	<CALwt-ok4O23b73RPeDSn8WA6yxq=kL-UfFzbZmjykN5q5gmXgw@mail.gmail.com>
Message-ID: <20130219143106.GG12761@charite.de>

* Michael Smith <msmith13337 at gmail.com>:
> Hi,
> 
> 
> thanks Mark.
> 
> I applied the patch and both the incoming as well as the outgoing mail
> addresses are correct according to the debug log. So does the problem lie
> with postfix?

I missed the patch... Could you send it to me and I can comment on
that :)

> > I gave him the attached patch to Mailman/Handlers/SMTPDirect.py, which
> > logs the content of the messages From: and Message-ID: headers upon
> > entry to SMTPDirect.py and after delivery to the outgoing MTA. The
> > From: is unchanged in these log messages, and the ultimate, erroneous
> > From: has been added after (above in the message headers) the
> > Received: header added by the outgoing MTA.

Could you share the log-lines (in private, won't disclose them).

The culprit COULD be the Postfix settings:
local_header_rewrite_clients
remote_header_rewrite_domain

Their defaults are:
local_header_rewrite_clients = permit_inet_interfaces
remote_header_rewrite_domain =

Personally, I'm using
local_header_rewrite_clients =
remote_header_rewrite_domain =
(never ever rewrite)

-- 
Ralf Hildebrandt                   Charite Universit?tsmedizin Berlin
ralf.hildebrandt at charite.de        Campus Benjamin Franklin
http://www.charite.de              Hindenburgdamm 30, 12203 Berlin
Gesch?ftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155

From Ralf.Hildebrandt at charite.de  Tue Feb 19 15:36:58 2013
From: Ralf.Hildebrandt at charite.de (Ralf Hildebrandt)
Date: Tue, 19 Feb 2013 15:36:58 +0100
Subject: [Mailman-Users] Odd replacement of the sender address
In-Reply-To: <20130219143106.GG12761@charite.de>
References: <CALwt-oksQkQR5-vPnkpYJpKxc52xzDFP54HH32pu_n1chRDV+w@mail.gmail.com>
	<PC199320130218211640065646b698b8@MSAPIRO>
	<CALwt-ok4O23b73RPeDSn8WA6yxq=kL-UfFzbZmjykN5q5gmXgw@mail.gmail.com>
	<20130219143106.GG12761@charite.de>
Message-ID: <20130219143658.GH12761@charite.de>

* Ralf Hildebrandt <Ralf.Hildebrandt at charite.de>:

> I missed the patch... Could you send it to me and I can comment on
> that :)

Found it. Hm. Postfix definitely logs rewrite operations.

-- 
Ralf Hildebrandt                   Charite Universit?tsmedizin Berlin
ralf.hildebrandt at charite.de        Campus Benjamin Franklin
http://www.charite.de              Hindenburgdamm 30, 12203 Berlin
Gesch?ftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155

From es at fruitcom.com  Wed Feb 20 13:06:03 2013
From: es at fruitcom.com (Eric Smith)
Date: Wed, 20 Feb 2013 13:06:03 +0100
Subject: [Mailman-Users] Multiple mailman domains
Message-ID: <20130220120603.GA5313@trustfood.org>

I want to configure postfix and mailman so that I have multiple
mailman domains. That means for each (postfix virtual) domain, 
the same listname may be used.

Here is the description form the docs;
http://www.list.org/mailman-install/postfix-virtual.html

and here is a mailpost answered by Mark Sapiro
http://mail.python.org/pipermail/mailman-users/2008-November/063886.html.

Is there sufficient informationn here to guide me in this configuration?


-- 
Eric Smith

From Maire.Jones at scss.tcd.ie  Tue Feb 19 13:40:12 2013
From: Maire.Jones at scss.tcd.ie (=?UTF-8?Q?M=C3=A1ire_Jones?=)
Date: Tue, 19 Feb 2013 12:40:12 +0000
Subject: [Mailman-Users] =?utf-8?q?modifying_accept=5Fnon=5Fmembers__via_c?=
 =?utf-8?q?ommand_line?=
Message-ID: <9dfd4a0dcb7ac4b4f272e2031dae2452@scss.tcd.ie>

Hi

Is it possible to add  @whitelist to accept_non_members for a mailman 
list from the command line?
Thanks in advance for your help.

-- 
M?ire Jones
Systems Administrator
School of Computer Science and Statistics
Trinity College Dublin
Ireland

From Maire.Jones at scss.tcd.ie  Tue Feb 19 14:06:45 2013
From: Maire.Jones at scss.tcd.ie (=?UTF-8?Q?M=C3=A1ire_Jones?=)
Date: Tue, 19 Feb 2013 13:06:45 +0000
Subject: [Mailman-Users] white listing
Message-ID: <c094ea16dde88b4e1b6fe6f46c7fc9a3@scss.tcd.ie>

Is it possible to configure mailman so that any email from any address 
from site @domain will be accepted by the mailman server without 
moderation?

Is it possible to configure accept_non_members so that ANY address from 
@domain can be added without having to specify each address separately?

-- 
M?ire Jones
Systems Administrator
School of Computer Science and Statistics
Trinity College Dublin
Ireland

From mark at msapiro.net  Wed Feb 20 20:13:33 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 20 Feb 2013 11:13:33 -0800
Subject: [Mailman-Users] Multiple mailman domains
In-Reply-To: <20130220120603.GA5313@trustfood.org>
Message-ID: <PC19932013022011133307966657e93d@MSAPIRO>

Eric Smith wrote:

>I want to configure postfix and mailman so that I have multiple
>mailman domains. That means for each (postfix virtual) domain, 
>the same listname may be used.
>
>Here is the description form the docs;
>http://www.list.org/mailman-install/postfix-virtual.html
>
>and here is a mailpost answered by Mark Sapiro
>http://mail.python.org/pipermail/mailman-users/2008-November/063886.html.
>
>Is there sufficient informationn here to guide me in this configuration?


No. These will result in a configuration which will not allow two lists
with the same name even if they are in different domains.

See the FAQ at <http://wiki.list.org/x/jIA9> for work around advice.

-- 
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 Feb 20 21:05:08 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 20 Feb 2013 12:05:08 -0800
Subject: [Mailman-Users] modifying accept_non_members  via command line
In-Reply-To: <9dfd4a0dcb7ac4b4f272e2031dae2452@scss.tcd.ie>
References: <9dfd4a0dcb7ac4b4f272e2031dae2452@scss.tcd.ie>
Message-ID: <51252C74.3020606@msapiro.net>

On 2/19/2013 4:40 AM, M?ire Jones wrote:
> 
> Is it possible to add  @whitelist to accept_non_members for a mailman
> list from the command line?


See <http://www.msapiro.net/scripts/non_members>.

-- 
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 Feb 20 21:18:15 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 20 Feb 2013 12:18:15 -0800
Subject: [Mailman-Users] white listing
In-Reply-To: <c094ea16dde88b4e1b6fe6f46c7fc9a3@scss.tcd.ie>
References: <c094ea16dde88b4e1b6fe6f46c7fc9a3@scss.tcd.ie>
Message-ID: <51252F87.7040406@msapiro.net>

On 2/19/2013 5:06 AM, M?ire Jones wrote:
> Is it possible to configure mailman so that any email from any address
> from site @domain will be accepted by the mailman server without
> moderation?


If this is a different question from the next question, please clarify
what you want.


> Is it possible to configure accept_non_members so that ANY address from
> @domain can be added without having to specify each address separately?


Put

^.*@domain

or, e.g.

^.*[@.]example\.com$

to accept any address in example.com or a sub-domain thereof in
accept_these_non-members. Entries that begin with ^ are regular
expression matches as mentioned in the (Details for
accept_these_nonmembers) help.

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


From tanstaafl at libertytrek.org  Thu Feb 21 15:27:31 2013
From: tanstaafl at libertytrek.org (Tanstaafl)
Date: Thu, 21 Feb 2013 09:27:31 -0500
Subject: [Mailman-Users] white listing
In-Reply-To: <51252F87.7040406@msapiro.net>
References: <c094ea16dde88b4e1b6fe6f46c7fc9a3@scss.tcd.ie>
	<51252F87.7040406@msapiro.net>
Message-ID: <51262ED3.2020705@libertytrek.org>

On 2013-02-20 3:18 PM, Mark Sapiro <mark at msapiro.net> wrote:
> On 2/19/2013 5:06 AM, M?ire Jones wrote:
>> Is it possible to configure accept_non_members so that ANY address from
>> @domain can be added without having to specify each address separately?

> Put
>
> ^.*@domain
>
> or, e.g.
>
> ^.*[@.]example\.com$
>
> to accept any address in example.com or a sub-domain thereof in
> accept_these_non-members. Entries that begin with ^ are regular
> expression matches as mentioned in the (Details for
> accept_these_nonmembers) help.

But it would still be much better to create a 'whitelist' and add 
specific addresses to it and use that...

Blindly accepting all addresses to a domain is bad in the same way that 
catchall accounts are bad... at least imho...

From mark at msapiro.net  Thu Feb 21 16:44:53 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 21 Feb 2013 07:44:53 -0800
Subject: [Mailman-Users] white listing
In-Reply-To: <ea6a0a5db8c631a89650548372a18081@scss.tcd.ie>
References: <c094ea16dde88b4e1b6fe6f46c7fc9a3@scss.tcd.ie>
	<51252F87.7040406@msapiro.net>
	<ea6a0a5db8c631a89650548372a18081@scss.tcd.ie>
Message-ID: <512640F5.5060809@msapiro.net>

On 2/21/2013 2:35 AM, M?ire Jones wrote:
> 
> Yes, these are two different questions. In the first I was wondering if
> it is possible to allow any address from @domain post to each and every
> mailman list on our mailman server. \\


Assuming you don't want to just add a regexp to accept_these_nonmembers
to all lists which is easy to do, at least for existing lists, with the
script at <http://www.msapiro.net/scripts/non_members>, you would need
to do this with a custom handler which would set approved=True in the
message's metadata if the sender was from the white listed domain.

The problem with this approach is that the custom handler would have to
be in the pipeline prior to Moderate to avoid list membership tests, and
this would also then bypass all the miscellaneous holds such as too many
recipients, implicit destination, too big, administrivia, etc.

See the FAQ at <http://wiki.list.org/x/l4A9> for info on 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 msmith13337 at gmail.com  Fri Feb 22 00:12:26 2013
From: msmith13337 at gmail.com (Michael Smith)
Date: Fri, 22 Feb 2013 00:12:26 +0100
Subject: [Mailman-Users] Odd replacement of the sender address
In-Reply-To: <20130219143658.GH12761@charite.de>
References: <CALwt-oksQkQR5-vPnkpYJpKxc52xzDFP54HH32pu_n1chRDV+w@mail.gmail.com>
	<PC199320130218211640065646b698b8@MSAPIRO>
	<CALwt-ok4O23b73RPeDSn8WA6yxq=kL-UfFzbZmjykN5q5gmXgw@mail.gmail.com>
	<20130219143106.GG12761@charite.de>
	<20130219143658.GH12761@charite.de>
Message-ID: <CALwt-ok0giDJH=L1q10ywnoNNfq+tjFe+BO1NEWz+fVPXLGf-Q@mail.gmail.com>

Hey there.


After a while, I found out that this problem only occurred with some
addresses. I found out that all addresses in the postfix sender-table were
replaced by (v)username at domain.tld . This is very bad, because the mail
domain for real (unix) users has to differ from the one for virtual users
in postfix (of course forwarding could be used; but because I didn't, the
addresses didn't exist). I still don't know, why this started to happen
from one day to another, but the solution suggested by Ralf omits the
issue: just set

local_header_rewrite_clients =

in the postfix config.


Cheers and thanks for the help
Michael


On 19 February 2013 15:36, Ralf Hildebrandt <Ralf.Hildebrandt at charite.de>wrote:

> * Ralf Hildebrandt <Ralf.Hildebrandt at charite.de>:
>
> > I missed the patch... Could you send it to me and I can comment on
> > that :)
>
> Found it. Hm. Postfix definitely logs rewrite operations.
>
> --
> Ralf Hildebrandt                   Charite Universit?tsmedizin Berlin
> ralf.hildebrandt at charite.de        Campus Benjamin Franklin
> http://www.charite.de              Hindenburgdamm 30, 12203 Berlin
> Gesch?ftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at python.org
> http://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:
> http://mail.python.org/mailman/options/mailman-users/msmith13337%40gmail.com
>

From phanh at canby.k12.or.us  Sat Feb 23 01:08:40 2013
From: phanh at canby.k12.or.us (Hung Phan)
Date: Fri, 22 Feb 2013 16:08:40 -0800
Subject: [Mailman-Users] Mailman error log file
Message-ID: <735A52FB-E8CB-4040-A7CC-27D68D5C39DB@canby.k12.or.us>

We receive an error "We're sorry, we hit a bug!" Upon inspection, we found that we run out of space on the server. We found that the error log file in /usr/local/mailman/logs grows rapidly. We delete one a couple days ago at 33GB in size. 3 days pass and it grows to 11GB. 

How do we check if verbose logging is on? 

Thank you,


From mark at msapiro.net  Sat Feb 23 03:18:22 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 22 Feb 2013 18:18:22 -0800
Subject: [Mailman-Users] Mailman error log file
In-Reply-To: <735A52FB-E8CB-4040-A7CC-27D68D5C39DB@canby.k12.or.us>
Message-ID: <PC19932013022218182206096b37e877@MSAPIRO>

Hung Phan wrote:
>
>How do we check if verbose logging is on? 


Unless you have enabled SMTP debugging as discussed in the FAQ at
<http://wiki.list.org/x/-IA9> (adding "       
self.__conn.set_debuglevel(1)" to the definition of the _connect
method in Mailman/Handlers/SMTPDirect.py) or installed some other
local modification to log stuff to Mailman's error log, the only
things logged there are actual errors and exceptions that need to be
addressed. If you need help understanding these, post some typical,
complete log messages including traceback and and other information.

There is no 'verbose' logging switch.

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


From beyerg at bellsouth.net  Sat Feb 23 04:47:50 2013
From: beyerg at bellsouth.net (Gregory Beyer)
Date: Fri, 22 Feb 2013 22:47:50 -0500
Subject: [Mailman-Users] Need to see sender of post to my list
Message-ID: <51283BE6.40903@bellsouth.net>

Hello,

I've been using Mailman for years and have a situation that I can't find
in docs  & FAQs.  I have the reply to address set to "list" and I have
senders email addresses hidden to protect privacy and prevent spam abuse.

Occasionally, I - as the administrator - need to see the actual poster
of a message sent by a member.  They sent an inappropriate message, or
perhaps their email is spam virus infected and they are unknowingly
spamming.  When I go to archives, all I can find in the emails is the
obfuscated information about a message, but not the actual senders email
address.   If they don't sig the email, I have no way to know who they
are. 

How can I find out, while maintaining privacy so that addresses are not
exposed to the list at large?

Here is a sample message header from my archives

>From jam at australianbakery.com  Fri Feb 22 13:54:16 2013
From: jam at australianbakery.com (Aussie Bakery Jam)
Date: Fri, 22 Feb 2013 15:54:16 -0500
Subject: [Aussie BG Jam] Musicians needed
Message-ID: <mailman.7.1361566462.28962.jam_australianbakery.com at host414.hostmonster.com>

Thanks very much, and if I've overlooked the answer already posted, sorry.

regards,

Greg

-- 
Protect your privacy <http://donttrack.us/> & break out of the bubble
<http://dontbubble.us/> - Search with DuckDuckGo <https://duckduckgo.com/>

From mark at msapiro.net  Sat Feb 23 19:27:20 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 23 Feb 2013 10:27:20 -0800
Subject: [Mailman-Users] Need to see sender of post to my list
In-Reply-To: <51283BE6.40903@bellsouth.net>
Message-ID: <PC199320130223102720035964c20d7b@MSAPIRO>

Gregory Beyer wrote:
>
> I have
>senders email addresses hidden to protect privacy and prevent spam abuse.
>
>Occasionally, I - as the administrator - need to see the actual poster
>of a message sent by a member.  They sent an inappropriate message, or
>perhaps their email is spam virus infected and they are unknowingly
>spamming.  When I go to archives, all I can find in the emails is the
>obfuscated information about a message, but not the actual senders email
>address.   If they don't sig the email, I have no way to know who they
>are. 


That's why the setting is called anonymous_list. You arenn't supposed
to be able to determine who sent a post from the received post or the
archives.


>How can I find out, while maintaining privacy so that addresses are not
>exposed to the list at large?


The only place you can find this information is in mailman's 'post'
log. For each post, there will be an entry like "post to <LISTNAME>
from <contents of original From: header> anonymized".

If you don't have access to the Mailman logs on the server, you will
have to get this information from someone who does.

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


From brennan at columbia.edu  Sat Feb 23 19:58:47 2013
From: brennan at columbia.edu (Joseph Brennan)
Date: Sat, 23 Feb 2013 13:58:47 -0500
Subject: [Mailman-Users] Need to see sender of post to my list
In-Reply-To: <51283BE6.40903@bellsouth.net>
References: <51283BE6.40903@bellsouth.net>
Message-ID: <9ADFFB397AFF8A9B38EF318A@[10.0.1.6]>



> How can I find out, while maintaining privacy so that addresses are not
> exposed to the list at large?


The system administrator can see it in /var/log/maillog or syslog.

Joseph Brennan





From mark at msapiro.net  Sun Feb 24 21:01:29 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 24 Feb 2013 12:01:29 -0800
Subject: [Mailman-Users] From Header Changed
In-Reply-To: <511BB644.9000002@msapiro.net>
References: <511BB644.9000002@msapiro.net>
Message-ID: <512A7199.3010708@msapiro.net>

Mark Sapiro wrote:

> On 2/13/2013 6:11 AM, Dennis Putnam wrote:
>> I have not made any changes (intentionally) to mailman in many months
>> but suddenly mail from the list has listname-bounces as the from header
>> rather then the original poster.


It turns out that the OP is using a Yahoo server as a smarthost to relay
Mailman's mail. It is Yahoo that is rewriting the From: header.

I finally did some experimentation with sending via a Yahoo server. This
is what I found

I connect to smtp.mail.yahoo.com:465 (SSL) and authenticate with my
Yahoo address.

I issue a MAIL FROM. If the address is not a verified address on my
Yahoo account, the MAIL FROM is rejected with '553 From address not
verified - see
http://help.yahoo.com/l/us/yahoo/mail/original/manage/sendfrom-07.html'
(note, this URL doesn't exist, but other help indicates you have to send
from addresses which are verified for your account. It seems the OP has
realized this and has verified the listname-bounces address on his Yahoo
account so Mailman's mail will be accepted.

If the address is verified, I can proceed and send the mail. The result
depends on whether the From: address in the mail is or is not a verified
address on my Yahoo account.

If the From: is a verified address, the From: header is not rewritten,
but the envelope sender address is rewritten to the From: header
address. In the case of Mailman, this will break bounce processing as
bounces will return to the poster and not to Mailman.

If the From: is not a verified address, the entire From: is replaced
with one containing only the verified envelope sender address, i.e., the
listname-bounces address in the Mailman case. This is what is apparently
happening in the OP's case and appears to be a change at Yahoo.

The implication of this is that Yahoo is simply not viable as a
smarthost relay for Mailman's outgoing mail.

Note that Gmail/googlemail is not a viable alternative either as
Gmail/googlemail always rewrites both the envelope sender address and
the From: header address to the Gmail/googlemail address used to
authenticate to the server. Gmail/googlemail at least leaves the
original display name in the From: header, but that's all.


>> Also, I'm guessing this is related, bounced messages are now being
>> handled as uncaught bounces.
>> 
>> The attached message was received as a bounce, but either the bounce
>> format was not recognized, or no member addresses could be extracted
>> from it.  This mailing list has been configured to send all
>> unrecognized bounce messages to the list administrator(s).


This turned out to be a bounce format from Yahoo that wasn't recognized
by Mailman. The recognizer will be updated for this.

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


From dap1 at bellsouth.net  Sun Feb 24 21:48:07 2013
From: dap1 at bellsouth.net (Dennis Putnam)
Date: Sun, 24 Feb 2013 15:48:07 -0500
Subject: [Mailman-Users] From Header Changed
In-Reply-To: <512A7199.3010708@msapiro.net>
References: <511BB644.9000002@msapiro.net> <512A7199.3010708@msapiro.net>
Message-ID: <512A7C87.3000704@bellsouth.net>

It appears that hotmail offers a free relay. Is that a viable alternative?

On 2/24/2013 3:01 PM, Mark Sapiro wrote:
> Mark Sapiro wrote:
>
>> On 2/13/2013 6:11 AM, Dennis Putnam wrote:
>>> I have not made any changes (intentionally) to mailman in many months
>>> but suddenly mail from the list has listname-bounces as the from header
>>> rather then the original poster.
>
> It turns out that the OP is using a Yahoo server as a smarthost to relay
> Mailman's mail. It is Yahoo that is rewriting the From: header.
>
> I finally did some experimentation with sending via a Yahoo server. This
> is what I found
>
> I connect to smtp.mail.yahoo.com:465 (SSL) and authenticate with my
> Yahoo address.
>
> I issue a MAIL FROM. If the address is not a verified address on my
> Yahoo account, the MAIL FROM is rejected with '553 From address not
> verified - see
> http://help.yahoo.com/l/us/yahoo/mail/original/manage/sendfrom-07.html'
> (note, this URL doesn't exist, but other help indicates you have to send
> from addresses which are verified for your account. It seems the OP has
> realized this and has verified the listname-bounces address on his Yahoo
> account so Mailman's mail will be accepted.
>
> If the address is verified, I can proceed and send the mail. The result
> depends on whether the From: address in the mail is or is not a verified
> address on my Yahoo account.
>
> If the From: is a verified address, the From: header is not rewritten,
> but the envelope sender address is rewritten to the From: header
> address. In the case of Mailman, this will break bounce processing as
> bounces will return to the poster and not to Mailman.
>
> If the From: is not a verified address, the entire From: is replaced
> with one containing only the verified envelope sender address, i.e., the
> listname-bounces address in the Mailman case. This is what is apparently
> happening in the OP's case and appears to be a change at Yahoo.
>
> The implication of this is that Yahoo is simply not viable as a
> smarthost relay for Mailman's outgoing mail.
>
> Note that Gmail/googlemail is not a viable alternative either as
> Gmail/googlemail always rewrites both the envelope sender address and
> the From: header address to the Gmail/googlemail address used to
> authenticate to the server. Gmail/googlemail at least leaves the
> original display name in the From: header, but that's all.
>
>
>>> Also, I'm guessing this is related, bounced messages are now being
>>> handled as uncaught bounces.
>>>
>>> The attached message was received as a bounce, but either the bounce
>>> format was not recognized, or no member addresses could be extracted
>>> from it.  This mailing list has been configured to send all
>>> unrecognized bounce messages to the list administrator(s).
>
> This turned out to be a bounce format from Yahoo that wasn't recognized
> by Mailman. The recognizer will be updated for this.
>


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

From mark at msapiro.net  Mon Feb 25 02:45:24 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 24 Feb 2013 17:45:24 -0800
Subject: [Mailman-Users] From Header Changed
In-Reply-To: <512A7C87.3000704@bellsouth.net>
References: <511BB644.9000002@msapiro.net> <512A7199.3010708@msapiro.net>
	<512A7C87.3000704@bellsouth.net>
Message-ID: <512AC234.8060505@msapiro.net>

On 2/24/2013 12:48 PM, Dennis Putnam wrote:
> It appears that hotmail offers a free relay. Is that a viable alternative?


I tested two more freemail servers, AOL (smtp.aim.com) and Hotmail
(smtp.live.com). Neither of these is viable as a Mailman outbound relay.

AOL refuses to accept the mail unless both the envelope sender and the
From: header address are addresses associated with the authenticating
AOL/AIM account. In addition, AOL's server says this in it's reply to
the connect:

220-mtaout-ma03.r1000.mx.aol.com ESMTP MUA/Third Party Client Interface
220-AOL and its affiliated companies do not
220-authorize the use of its proprietary computers and computer
220-networks to accept, transmit, or distribute unsolicited bulk
220-e-mail sent from the internet.
220-Effective immediately:
220-AOL may no longer accept connections from IP addresses
220 which no reverse-DNS (PTR record) assigned.

If you have an appropriate reverse-DNS, you probably should just be
sending directly and not through a smarthost.

Hotmail is a bit worse than Gmail. It accepts the mail but rewrites both
the envelope sender and the From: including display name to the address
and display name associated with the authenticating Hotmail/Live
Mail/Outlook.com account. This differs from Gmail in that Gmail rewrites
only the address in From: and not the display name.

None of this is surprising to me. I think all large ISPs take similar
measures in an attempt to avoid relaying spam with spoofed senders.

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


From dap1 at bellsouth.net  Mon Feb 25 14:26:57 2013
From: dap1 at bellsouth.net (Dennis Putnam)
Date: Mon, 25 Feb 2013 08:26:57 -0500
Subject: [Mailman-Users] From Header Changed
In-Reply-To: <512AC234.8060505@msapiro.net>
References: <511BB644.9000002@msapiro.net> <512A7199.3010708@msapiro.net>
	<512A7C87.3000704@bellsouth.net> <512AC234.8060505@msapiro.net>
Message-ID: <512B66A1.9040504@bellsouth.net>

I guess I'm not surprised either. Unfortunately with ISPs blocking
outgoing SMTP there are few alternatives. I wonder if any of the pay
SMTP servers would work any better.

On 2/24/2013 8:45 PM, Mark Sapiro wrote:
> On 2/24/2013 12:48 PM, Dennis Putnam wrote:
>> It appears that hotmail offers a free relay. Is that a viable alternative?
>
> I tested two more freemail servers, AOL (smtp.aim.com) and Hotmail
> (smtp.live.com). Neither of these is viable as a Mailman outbound relay.
>
> AOL refuses to accept the mail unless both the envelope sender and the
> From: header address are addresses associated with the authenticating
> AOL/AIM account. In addition, AOL's server says this in it's reply to
> the connect:
>
> 220-mtaout-ma03.r1000.mx.aol.com ESMTP MUA/Third Party Client Interface
> 220-AOL and its affiliated companies do not
> 220-authorize the use of its proprietary computers and computer
> 220-networks to accept, transmit, or distribute unsolicited bulk
> 220-e-mail sent from the internet.
> 220-Effective immediately:
> 220-AOL may no longer accept connections from IP addresses
> 220 which no reverse-DNS (PTR record) assigned.
>
> If you have an appropriate reverse-DNS, you probably should just be
> sending directly and not through a smarthost.
>
> Hotmail is a bit worse than Gmail. It accepts the mail but rewrites both
> the envelope sender and the From: including display name to the address
> and display name associated with the authenticating Hotmail/Live
> Mail/Outlook.com account. This differs from Gmail in that Gmail rewrites
> only the address in From: and not the display name.
>
> None of this is surprising to me. I think all large ISPs take similar
> measures in an attempt to avoid relaying spam with spoofed senders.
>


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

From mailmanu-20100705 at billmail.scconsult.com  Mon Feb 25 16:41:08 2013
From: mailmanu-20100705 at billmail.scconsult.com (Bill Cole)
Date: Mon, 25 Feb 2013 10:41:08 -0500
Subject: [Mailman-Users] From Header Changed
In-Reply-To: <512B66A1.9040504@bellsouth.net>
References: <511BB644.9000002@msapiro.net> <512A7199.3010708@msapiro.net>
	<512A7C87.3000704@bellsouth.net> <512AC234.8060505@msapiro.net>
	<512B66A1.9040504@bellsouth.net>
Message-ID: <85DD1CD1-83EB-4246-9353-90DBB210BC21@billmail.scconsult.com>

On 25 Feb 2013, at 8:26, Dennis Putnam wrote:

> I guess I'm not surprised either. Unfortunately with ISPs blocking
> outgoing SMTP there are few alternatives.

That is generally a function of what sort of access you buy. The sad 
reality is that blocking port 25 helps limit the scale & cost of abuse 
desk and retail tech support operations, so ISPs block port 25 by 
default on their cheapest access accounts. Depending on your provider, 
you may be able to get port 25 unblocked just by asking for it or by 
paying a premium for a "business grade" account, but it can be difficult 
to run a mailing list from anywhere in the address space of a "consumer" 
ISP because of receiver-side filtering.

> I wonder if any of the pay
> SMTP servers would work any better.

Intentional providers of paid SMTP smarthost service do exist in the 
market. Freemail operations exist to muster users for operations that 
sell their aggregated eyeballs or for "upselling" into revenue-producing 
services. Mail smarthost service, especially for anything of a "bulk" 
nature, is a costly and risky service to provide which doesn't provide 
much opportunity for a freemail operator to resell eyeballs or lead 
users to paid services, so it is natural that they are intentionally 
closing off the ability to use them as smarthosts for free.

If you're willing & able to be a small-scale sysadmin, it may be worth 
the trouble to forget about buying SMTP smarthost service and instead 
get a small virtual private server with a reputable provider. Just as 
being on a consumer ISP network can mean that you share the aggregate 
reputation of everyone else on that network, routing mail through a 
shared smarthost (even one charging for service) throws your lot in with 
all of the customers of that service and buying a VPS on the cheap (e.g. 
Amazon EC2) means you end up at least partially sharing the reputation 
of everyone else using the same low-rent provider. It's unfortunate, but 
as the net has matured it has taken on some of the same features as the 
real world; the market value your home (real or presumed) is a source of 
prejudices made tangible in how likely strangers are to trust you.

From admin at cpcnw.co.uk  Mon Feb 25 16:17:58 2013
From: admin at cpcnw.co.uk (Graham Bentley)
Date: Mon, 25 Feb 2013 15:17:58 -0000
Subject: [Mailman-Users] Different From field between digest and non digest
Message-ID: <9526FB809FD94C5696D7292A0D05E0B3@admin>

Hi all,

I have just got started with mailman and have noticed that
in non digest mode subscribers recieve posts from ie in
their mail client FROM: field

listname at domain

but in digest mode from;

listname-request at domain

I would prefer the former for both but cant seem to find how 
to change this?

Thanks!

From phanh at canby.k12.or.us  Wed Feb 27 00:02:02 2013
From: phanh at canby.k12.or.us (Hung Phan)
Date: Tue, 26 Feb 2013 15:02:02 -0800
Subject: [Mailman-Users] Mailman error log file
In-Reply-To: <PC19932013022218182206096b37e877@MSAPIRO>
References: <PC19932013022218182206096b37e877@MSAPIRO>
Message-ID: <2A294542-AB60-4D66-9E25-EE89C2CB2945@canby.k12.or.us>

That's it! The set_debuglevel(1) commend is left over from when we debugged an issue previously. 
We, however, have a different issue. We use logrotate to rotate the error log daily. After we implemented that, the new error log file stays at 0. Is it normal? Posts mention other services also write entries in this log file besides exim so should the file stay at 0 after 2 days?

Thank you very much for all the help,



On Feb 22, 2013, at 6:18 PM, Mark Sapiro wrote:

> Hung Phan wrote:
>> 
>> How do we check if verbose logging is on? 
> 
> 
> Unless you have enabled SMTP debugging as discussed in the FAQ at
> <http://wiki.list.org/x/-IA9> (adding "       
> self.__conn.set_debuglevel(1)" to the definition of the _connect
> method in Mailman/Handlers/SMTPDirect.py) or installed some other
> local modification to log stuff to Mailman's error log, the only
> things logged there are actual errors and exceptions that need to be
> addressed. If you need help understanding these, post some typical,
> complete log messages including traceback and and other information.
> 
> There is no 'verbose' logging switch.
> 
> -- 
> 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 Feb 27 01:00:30 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 26 Feb 2013 16:00:30 -0800
Subject: [Mailman-Users] Different From field between digest and non
	digest
In-Reply-To: <9526FB809FD94C5696D7292A0D05E0B3@admin>
Message-ID: <PC1993201302261600300718815c22ec@MSAPIRO>

Graham Bentley wrote:
>
>I have just got started with mailman and have noticed that
>in non digest mode subscribers recieve posts from ie in
>their mail client FROM: field
>
>listname at domain


Presumably this behavior is what you want. It occurs because the list
admin General Options -> anonymous_list setting is Yes. This causes to
the extent possible any information in the original message headers
that could be used to help identify the original sender to be removed
or replaced. In the case of the From: header, the original poster's
From: is replaces with one containing the list's description and
posting address. If anonymous_list is No, the original From: is left
in the message sent to list members.


>but in digest mode from;
>
>listname-request at domain
>
>I would prefer the former for both but cant seem to find how 
>to change this?


This may be a historical artifact, but it's been that way 'forever'.
There is no configuration setting to change it. You would have to
change the code in the definition of send_i18n_digests() in
Mailman/Handlers/ToDigest.py.

Note that there is a Reply-To: header in the digest with the list
posting address so a 'reply' to a digest should be addressed to the
list by default.

-- 
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 Feb 27 01:16:14 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 26 Feb 2013 16:16:14 -0800
Subject: [Mailman-Users] Mailman error log file
In-Reply-To: <2A294542-AB60-4D66-9E25-EE89C2CB2945@canby.k12.or.us>
References: <PC19932013022218182206096b37e877@MSAPIRO>
	<2A294542-AB60-4D66-9E25-EE89C2CB2945@canby.k12.or.us>
Message-ID: <512D504E.4070001@msapiro.net>

On 2/26/2013 3:02 PM, Hung Phan wrote:
> We, however, have a different issue. We use logrotate to rotate the error log daily. After we implemented that, the new error log file stays at 0. Is it normal? Posts mention other services also write entries in this log file besides exim so should the file stay at 0 after 2 days?


Almost everything written to Mailman's error log is the result of some
kind of error or exception that should not normally occur. Some of these
can result from user errors such as an invalid list name in a URL to
access a web admin page or an invalid private archive URL, but most
indicate some kind of Mailman internal error, so yes, it is normal for
this log to be empty and when it isn't, the messages should be examined
to see if there is some error condition that should be attended to.

Note: exim writes its own logs. It does not write to Mailman's logs. The
'error' log messages from set_debuglevel(1) are written by Python's
smtplib module used by Mailman/Handlers/SMTPDirect.py

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

From beyerg at bellsouth.net  Wed Feb 27 23:04:31 2013
From: beyerg at bellsouth.net (Gregory Beyer)
Date: Wed, 27 Feb 2013 17:04:31 -0500
Subject: [Mailman-Users] Need to see sender of post to my list
In-Reply-To: <9ADFFB397AFF8A9B38EF318A@[10.0.1.6]>
References: <51283BE6.40903@bellsouth.net>
	<9ADFFB397AFF8A9B38EF318A@[10.0.1.6]>
Message-ID: <512E82EF.1080603@bellsouth.net>

Thanks Joseph and Mark Sapiro,

I will contact my hosting provider for access to the logs for my list.

Greg

-------- Original Message --------
Subject: Re: [Mailman-Users] Need to see sender of post to my list
From: Joseph Brennan <brennan at columbia.edu>
To: mailman-users at python.org
Date: 02/23/2013 01:58 PM

> 
> 
>> How can I find out, while maintaining privacy so that addresses are not
>> exposed to the list at large?
> 
> 
> The system administrator can see it in /var/log/maillog or syslog.
> 
> Joseph Brennan
> 
> 
> 
> 
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at python.org
> http://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:
> http://mail.python.org/mailman/options/mailman-users/beyerg%40bellsouth.net
> 

-- 
Protect your privacy <http://donttrack.us/> & break out of the bubble
<http://dontbubble.us/> - Search with DuckDuckGo <https://duckduckgo.com/>

From bhoward at fsu.edu  Wed Feb 27 22:04:10 2013
From: bhoward at fsu.edu (Breeze Howard)
Date: Wed, 27 Feb 2013 16:04:10 -0500
Subject: [Mailman-Users] Cannot complete actions on held msgs
Message-ID: <512E74CA.1020603@fsu.edu>

We recently upgraded Mailman from 2.1.13 on Solaris 10 to 2.1.15 on 
RHEL6.  We are seeing an issue now where when posts are held for 
moderator approval, they show up in the pending requests webpage, but 
you can't take any action on them. Defer/Reject/Allow/Discard... no 
matter what you choose, the page just refreshes without anything 
actually happening.  The kicker is that this only occurs on lists that 
were created in the new environment, the lists that we transferred over 
from 2.1.13 work just fine.

When I delete the heldmsg-<LISTNAME>-##.pck manually, the held message 
disappears from the "held for approval" page.  However, new held 
messages exhibit the same problems.  Other messages sent to the listserv 
that don't ever get held, are delivered to the members just fine.

We've compared config.pck files between an old and new lists and the 
only difference we have seen is that all of the 0's are now "False" and 
the 1's are now "True".
There have not been any HTML changes to the files in question.  We have 
run check_perms and it has come back with NO errors.

Mailman Version: 2.1.15
Python Version: 2.6.6
RHEL Version: 6.2
Kernel Version: 2.6.32-220.13.1.el6.x86_64
Apache Version: 2.2.15

Thank you in advance for your assistance,
Breeze

--
Breeze P. Howard                 bhoward at fsu.edu          (850)645-8008
Email and Linux Administrators   its-unixadmins at fsu.edu   (850)644-2591
Information Technology Services  The Florida State University



From mark at msapiro.net  Thu Feb 28 17:32:27 2013
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 28 Feb 2013 08:32:27 -0800
Subject: [Mailman-Users] Cannot complete actions on held msgs
In-Reply-To: <512E74CA.1020603@fsu.edu>
Message-ID: <PC1993201302280832270390828381a1@MSAPIRO>

Breeze Howard wrote:

>We recently upgraded Mailman from 2.1.13 on Solaris 10 to 2.1.15 on 
>RHEL6.  We are seeing an issue now where when posts are held for 
>moderator approval, they show up in the pending requests webpage, but 
>you can't take any action on them. Defer/Reject/Allow/Discard... no 
>matter what you choose, the page just refreshes without anything 
>actually happening.  The kicker is that this only occurs on lists that 
>were created in the new environment, the lists that we transferred over 
>from 2.1.13 work just fine.


There is probably some issue with DEFAULT_URL_HOST or
DEFAULT_URL_PATTERN causing the web_page_url attribute on new lists to
be wrong. Possibly, new lists are created with http scheme instead of
https and the web server is redirecting http to https and losing the
post data.

See the FAQs at <http://wiki.list.org/x/ioA9> and
<http://wiki.list.org/x/7oA9>.

Also look at the source of the admindb page - in particular the action=
URL in the form tag.


>When I delete the heldmsg-<LISTNAME>-##.pck manually, the held message 
>disappears from the "held for approval" page.


You shouldn't delete (rm) these files. You should use Mailman's
bin/discard tool or possibly the script at
<http://www.msapiro.net/scripts/list_requests> to remove them.

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


From bhoward at fsu.edu  Thu Feb 28 19:44:04 2013
From: bhoward at fsu.edu (Breeze Howard)
Date: Thu, 28 Feb 2013 13:44:04 -0500
Subject: [Mailman-Users] Cannot complete actions on held msgs
In-Reply-To: <PC1993201302280832270390828381a1@MSAPIRO>
References: <PC1993201302280832270390828381a1@MSAPIRO>
Message-ID: <512FA574.3040108@fsu.edu>

Thank you so much.

That was exactly the problem.  The new lists were being created with
web_page_url': 'http://<DOMAIN>/mailman/ instead of
web_page_url': 'https://<DOMAIN>/mailman/

We fixed the mm_cfg.py file, ran the withlist to fix the ones that had 
already been created and it's all good now.

Again thank you!!
-Breeze

--
Breeze P. Howard                 bhoward at fsu.edu          (850)645-8008
Email and Linux Administrators   its-unixadmins at fsu.edu   (850)644-2591
Information Technology Services  The Florida State University

On 02/28/2013 11:32 AM, Mark Sapiro wrote:
> Breeze Howard wrote:
>
>> We recently upgraded Mailman from 2.1.13 on Solaris 10 to 2.1.15 on
>> RHEL6.  We are seeing an issue now where when posts are held for
>> moderator approval, they show up in the pending requests webpage, but
>> you can't take any action on them. Defer/Reject/Allow/Discard... no
>> matter what you choose, the page just refreshes without anything
>> actually happening.  The kicker is that this only occurs on lists that
>> were created in the new environment, the lists that we transferred over
> >from 2.1.13 work just fine.
>
>
> There is probably some issue with DEFAULT_URL_HOST or
> DEFAULT_URL_PATTERN causing the web_page_url attribute on new lists to
> be wrong. Possibly, new lists are created with http scheme instead of
> https and the web server is redirecting http to https and losing the
> post data.
>
> See the FAQs at <http://wiki.list.org/x/ioA9> and
> <http://wiki.list.org/x/7oA9>.
>
> Also look at the source of the admindb page - in particular the action=
> URL in the form tag.
>
>
>> When I delete the heldmsg-<LISTNAME>-##.pck manually, the held message
>> disappears from the "held for approval" page.
>
> You shouldn't delete (rm) these files. You should use Mailman's
> bin/discard tool or possibly the script at
> <http://www.msapiro.net/scripts/list_requests> to remove them.
>