Re: [Mailman-Users] unsubscribe one user from many lists

[Mark Sapiro]

Rafael Lang wrote:
>
>Now, I'm not super sure I got the command 
>line right, this is what I tried:
>
>wget --post-data="adminpw=foobar&unsubscribees=m...@somewhere.edu" 
>http://serveraddress/mailman/admin/mailinglistname/members/members/remove
>
>and I also tried to directly enter
>
>http://serveraddress/mailman/admin/mailinglistname/members/members/remove?adminpw=foobar&unsubscribees=m...@somewhere.edu
>
>into my browser. In both cases what I got back was:
>
>
>Bug in Mailman version 2.1.9
>Bug in Mailman version 2.1.9
>We're sorry, we hit a bug!
>
>Please inform the webmaster for this site of this
>problem.  Printing of traceback and other system information has been
>explicitly inhibited, but the webmaster can find this information in the
>Mailman error logs.
>
>
>and now I'm lost :-\ Can somebody help me? How can I unsubscribe a given 
>user from a couple of mailing lists at the same time without having to 
>go through the clumsy web interface for each of the mailing lists?


It appears that you don't have command line access to Mailman, so the
obvious

  bin/remove_members --fromall u...@example.com

isn't something you can do. That probably also means you don't have
access to Mailman's error log to provide the traceback, however, I can
say what the issue might be. Your URLs are wrong. There should not be
two occurrences of /members in the URL. The 'bug' however is that the
script assumes there are values for the check boxes on the form. Thus,
you need something like 

wget
--post-data="adminpw=foobar&send_unsub_notifications_to_list_owner=0&send_unsub_ack_to_this_batch=0&unsubscribees=m...@somewhere.edu"
http://serveraddress/mailman/admin/mailinglistname/members/remove

or

http://serveraddress/mailman/admin/mailinglistname/members/remove?adminpw=foobar&send_unsub_notifications_to_list_owner=0&send_unsub_ack_to_this_batch=0&unsubscribees=m...@somewhere.edu

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
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/archive%40jab.org

Re: [Mailman-Users] Basic Mailing Lists vulnerable ?

[Mark Sapiro]

Bernardo - HIT  wrote:

>Emails from a group in my "Basic Mailing List 'can be found and read
>by/from Google and other search engines. How can I do to hide these
>e-mails/group, so that others can not read them? At this way, any one can
>read the emails.


In the web admin interface, set Archiving Options -> archive_private to
Private.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
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/archive%40jab.org

[Mailman-Users] unsubscribe one user from many lists

[Rafael Lang]

Hi Mailmen and -women,

I'd like to administrate some ~20 email lists of a team of people 
working together via mailman. Once a user leaves the team, I should 
unsubscribe this user from all lists that he's on. How do I do this 
without having to click through 20 web interfaces?


First I thought, hey, I simply send an unsubscribe email, just like the 
subscribe email. Well, that doesn't work though, since unsubscription 
always requires the user password, which I don't have of course. So I 
searched around and found this thread:


http://mail.python.org/pipermail/mailman-users/2004-July/037815.html

about exactly this. Now, that suggests a global change by patching a 
python script. But since the mail server I'm using is actually for a 
whole institute, the administrator probably has little interest to 
globally change his Mailman/Commands/cmd_unsubscribe.py just because of 
my 20 mailing lists, in particular since some of his other lists may be 
more security sensitive than mine. In addition, if I try to patch this 
file rather than having some patch from somebody who actually knows 
python ;-) he probably won't like it anyway...


So I continued searching and stumbled across the possibility of doing 
this via wget:


http://mail.python.org/pipermail/mailman-users/2004-December/041214.html

and

http://mail.python.org/pipermail/mailman-users/2004-December/041220.html

Wow, that would be fantastic! :-) I could simply shell script that, not 
even worrying whether the user is subscribed to all 20 lists and just 
batch-unsubscribe (if the user wouldn't be on a given list, nothing 
would happen, so that's OK) Now, I'm not super sure I got the command 
line right, this is what I tried:


wget --post-data="adminpw=foobar&unsubscribees=m...@somewhere.edu" 
http://serveraddress/mailman/admin/mailinglistname/members/members/remove


and I also tried to directly enter

http://serveraddress/mailman/admin/mailinglistname/members/members/remove?adminpw=foobar&unsubscribees=m...@somewhere.edu

into my browser. In both cases what I got back was:


Bug in Mailman version 2.1.9
Bug in Mailman version 2.1.9
We're sorry, we hit a bug!

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


and now I'm lost :-\ Can somebody help me? How can I unsubscribe a given 
user from a couple of mailing lists at the same time without having to 
go through the clumsy web interface for each of the mailing lists?


Your help is greatly appreciated - thank you very much!

Kind regards,
Rafael




--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

[Mailman-Users] Basic Mailing Lists vulnerable ?

[Bernardo - HIT]

Emails from a group in my "Basic Mailing List 'can be found and read
by/from Google and other search engines. How can I do to hide these
e-mails/group, so that others can not read them? At this way, any one can
read the emails.

I didn't found any options about it.Some one can help me ?


Thks.
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

[Mailman-Users] Mailman 2.1.15rc1 released

[Mark Sapiro]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I am happy to announce the first release candidate for Mailman 2.1.15.

Python 2.4 is the minimum supported, but Python 2.6 is recommended.
This release should work with Python 2.7, but has not been tested with
that version.

This release includes minor security enhancements, new features and
bug fixes. See the Changelog at
 for more details.

Mailman is free software for managing email mailing lists and
e-newsletters. Mailman is used for all the python.org and
SourceForge.net mailing lists, as well as at hundreds of other sites.

For more information, please see:

http://www.list.org
http://www.gnu.org/software/mailman

Mailman 2.1.15rc1 can be downloaded from

https://launchpad.net/mailman/2.1/
http://ftp.gnu.org/gnu/mailman/

It is anticipated that the 2.1.15 final release will be on or about
June 13. Bugs found between now and then will be fixed if possible,
but I hope that most if not all changes between now and June 13 will
be i18n updates. Please send any updates to the templates and/or
message catalogs in the 2.1.15rc1 release directly to me no later than
June 11.

- -- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)

iD8DBQFPs0HiVVuXXpU7hpMRAhEfAKDHkpFORnL9a6ka3RRn4WP8m7EsHgCcCKFi
C17WrK2wc2irrXn9Gp2ju8I=
=5wvM
-END PGP SIGNATURE-
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Ubuntu release of Mailman

[David]

On Tue, May 15, 2012 at 7:31 PM, Mark Sapiro  wrote:

> Geoff Shang wrote:
> >
> >I've done several Mailman installs under Debian and Ubuntu and have had
> >minimal problems.  The key in my opinion is to look at the installation
> >guide and make sure you actually do everything that's listed there that's
> >appropriate.  It's easy enough to assume that a lot of what you need to do
> >regarding setup will be done for you when you install a package, but this
> >isn't really the case with Mailman (by necessity).
>
>
> 
> That sounds good, but evidently, judging from the number of
> Debian/Ubuntu packge users who come to this list with mail delivery
> issues because they have ended up with some Postfix configuration that
> combines Mailman aliases and postfix_to_mailman.py in incompatible
> ways, people don't look at the Debian documentation. They look at our
> installation manual or some incompatible web HowTo and wind up with a
> mess.
>
> I wish they all would read and comprehend the FAQ at
> .
>
> And, while I'm wishing, sometimes I wish I were less compulsive about
> this and could just refer them to that FAQ and forget about it.
> 
>


I'm one member of the list who is extremely grateful for your compulsion.
In my opinion, your help on this list is an invaluable asset to the Mailman
community. Without your compulsive help, the Mailman user community would
be tremendously disadvantaged compared to its current status.
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Ubuntu release of Mailman

[Mark Sapiro]

Geoff Shang wrote:
>
>I've done several Mailman installs under Debian and Ubuntu and have had 
>minimal problems.  The key in my opinion is to look at the installation 
>guide and make sure you actually do everything that's listed there that's 
>appropriate.  It's easy enough to assume that a lot of what you need to do 
>regarding setup will be done for you when you install a package, but this 
>isn't really the case with Mailman (by necessity).



That sounds good, but evidently, judging from the number of
Debian/Ubuntu packge users who come to this list with mail delivery
issues because they have ended up with some Postfix configuration that
combines Mailman aliases and postfix_to_mailman.py in incompatible
ways, people don't look at the Debian documentation. They look at our
installation manual or some incompatible web HowTo and wind up with a
mess.

I wish they all would read and comprehend the FAQ at
.

And, while I'm wishing, sometimes I wish I were less compulsive about
this and could just refer them to that FAQ and forget about it.



>ONe of the reasons why installing from source is not exactly 
>straight-forward is that Debian has conventions for things like the user 
>accounts used for specific things.  If you're going to compile Mailman 
>from source on a Debian-based system, you'll need to either undermine a 
>lot of other things, or supply the appropriate configure flags so that 
>Mailman uses the accounts that Debian uses.


Which, along with postfix_to_mailman.py, is a large part of why people
should heed the above FAQ.


>There were some other bits and pieces specific to the multiple hosts 
>aspect of it.  IN particular, there was a patch I was applying to add the 
>domain as a suffix so that the same list name could be used across 
>domains.  I'm not sure if that patch is now the virtual hosts branch or if 
>it's something else.


If the patches are those referred to at
,
the branch at  is
based on those but includes several updates and fixes.

If they are from , they
are someone elses work.


>All this was a product of many days of slavery and lots of helpful advice 
>from this list, which you can read at the following threads (don't know 
>why they split):
>
>http://mail.python.org/pipermail/mailman-users/2009-October/067354.html
>http://mail.python.org/pipermail/mailman-users/2009-October/067363.html
>http://mail.python.org/pipermail/mailman-users/2009-October/067364.html


You actually missed one:



The reason the thread is split is you were initially moderated. Your
replies to my posts were Cc'd to me, and my replies to those reached
the list before your replies were approved and reached the list.
Pipermail threading sometimes fails if the referenced message
(In-Reply-To: or References:) is not in the Pipermail archive at the
time the referencing message is archived.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
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/archive%40jab.org

Re: [Mailman-Users] Ubuntu release of Mailman

[David]

On Tue, May 15, 2012 at 4:36 PM, Geoff Shang  wrote:

> Hi,
>
> I'd like to make the case for considering the Debian etc Mailman instead
> of rolling your own.
>
> I've done several Mailman installs under Debian and Ubuntu and have had
> minimal problems.


I can't claim a lot of experience, but I did install Mailman on at least 3
Ubuntu servers recently and on the basis of that limited experience, I
agree with you. In Ubuntu 12.04 installing the Mailman deb package was very
straightforward and is working without any problems (after I ran
bin/check_perms and manually fixed anything the script didn't fix).
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Ubuntu release of Mailman

[Geoff Shang]

Hi,

I'd like to make the case for considering the Debian etc Mailman instead 
of rolling your own.


I've done several Mailman installs under Debian and Ubuntu and have had 
minimal problems.  The key in my opinion is to look at the installation 
guide and make sure you actually do everything that's listed there that's 
appropriate.  It's easy enough to assume that a lot of what you need to do 
regarding setup will be done for you when you install a package, but this 
isn't really the case with Mailman (by necessity).


ONe of the reasons why installing from source is not exactly 
straight-forward is that Debian has conventions for things like the user 
accounts used for specific things.  If you're going to compile Mailman 
from source on a Debian-based system, you'll need to either undermine a 
lot of other things, or supply the appropriate configure flags so that 
Mailman uses the accounts that Debian uses.


I had to do a number of Mailman instals on a Ubuntu box in 2009.  This is 
the command line I came up with:


./configure --with-username=list --with-groupname=list \
--with-mail-gid=list --with-cgi-gid=www-data

These flags were a product of looking at the Debian package sources and 
several rounds with the various bits of the system where it complained 
about user mismatches.


Since I was doing multiple installs for multiple virtual hosts (see other 
thread on this), I also added:


--prefix=/usr/local/mailman/example.com/ --with-mailhost=example.com
--with-urlhost=www.example.com

I also wrote the following in my file of notes at the time (since I was 
going to have to do this multiple times):


You might want to umask 002 before running make.

after make install:

cd $prefix
bin/check_perms

then
chown www-data archives/private
chmod o-x archives/private

(Do stuff specific to your webserver and MTA setup)

Run bin/genailiases from $prefix

Try check-perms again after genaliases

---CUT here ---

There were some other bits and pieces specific to the multiple hosts 
aspect of it.  IN particular, there was a patch I was applying to add the 
domain as a suffix so that the same list name could be used across 
domains.  I'm not sure if that patch is now the virtual hosts branch or if 
it's something else.


All this was a product of many days of slavery and lots of helpful advice 
from this list, which you can read at the following threads (don't know 
why they split):


http://mail.python.org/pipermail/mailman-users/2009-October/067354.html
http://mail.python.org/pipermail/mailman-users/2009-October/067363.html
http://mail.python.org/pipermail/mailman-users/2009-October/067364.html

Hope all of this is of some use to someone.

Geoff.
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Spam filters

[Mark Sapiro]

Mark J Bradakis wrote:

>But to be more general, what are some of the current
>best practices to filter out spam in a postfix mailman environment
>on Linux?


I use greylisting with Postgrey and spam/virus/other scanning via
MailScanner.

Also to increase protection against hijacked list member's accounts, on
my largest, highest traffic list I have set Privacy options... ->
Recipient filters -> max_num_recipients to 5 although this does result
in some held posts due to the recipient list growing after multiple
reply-alls.

I also hold messages with no or empty Subject: header. I happen to do
this with a custom handler that also holds messages that quote digest
boilerplate, but it can be done with header_filter_rules.

Other things I hold with header_filter_rules are these:

^Sender:.*linkedin.com>?$
^Return-Path:.*linkedin.com>?$
^Sender:.*homerunmail.com>?$
^Return-Path:.*homerunmail.com>?$
^Reply-To:.*homerunmail.com>?$
^Sender:.*facebookmail.com>?$
^Return-Path:.*facebookmail.com>?$

I also have

^.*[@.]apot(mail)?\.com$

in all my lists' ban_list.  This is not anti-spam, but is to prevent
answerpot from subscribing to lists for the purpose of archiving them.

If MailScanner seems too heavy a hammer for spam/malware filtering,
alternatives are  or simply
running spamassassin and clamav via milters.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
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/archive%40jab.org

Re: [Mailman-Users] Error accessing admin pages, AttributeError: local_name

[Mark Sapiro]

Odhiambo Washington wrote:

>I did not know of the existence of this branch of Mailman. How is it
>different from the main branch?
>I am running Mailman with vhosts in a single instance, with theonly
>limitation I have being that I cannot use the same listname more than once.
>Is there something I am/have been missing? I am on 2.1.14.


If you can accept the limitation of globally unique list names, stick
with what you have and upgrade to 2.1.15 when it is released.

If you need to use the same list name in two different domains, see
. This branch is
currently somewhere between 2.1.14 and 2.1.15 and will probably be
merged with 2.1.15 when it is released, but the patches on which it is
based are incomplete and not guaranteed. Read the description on the
above page for more information.

The recommendation for support of the same list name in two domains is
still either multiple 2.1.x instances or wait for Mailman 3.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
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/archive%40jab.org

Re: [Mailman-Users] Spam filters

[mailman]

Am Dienstag, 15. Mai 2012, 03:54:21 schrieb Mark J Bradakis:
> So my mailing lists are getting hit by spam that goes to the lists
> since it claims to be from some poor subscriber whose email got
> hijacked.  But to be more general, what are some of the current
> best practices to filter out spam in a postfix mailman environment
> on Linux?
> 
Since we are using greylisting in addition to clamav (+ clamav-unofficial-
sigs) the amount of spam decreased once more. I don't remember when the last 
customer complained about having unsolicited e-mails.

Regards,
Rainer
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Error accessing admin pages, AttributeError: local_name

[Andrew H]

On 15/05/2012 03:12, Mark Sapiro wrote:
> Andrew H wrote:
>> I'm using the mailman vhost branch (is this the 'best' thing to use to
>> do multi-domain mailing list hosting?)
>
> The recommended best practice for Mailman 2.1.x is to run a separate
> Mailman instance per domain. The vhost branch may be the second choice
> alternative.
>
>
>> When I enter /mailman/admin/2030 it first asks for the password, after
>> that I get an error page 'Bug in Mailman version 2.1.14'
>>
>> This happens on all the lists, but it did used to work but I'm not sure
>> what has happened to break it now.
>
> What broke it is setting
>
> OWNERS_CAN_DELETE_THEIR_OWN_LISTS = Yes
>
> in mm_cfg.py. It's definitely a bug in the vhost branch. It's fixed (I
> hope) in rev. 852 of the branch. See
>  for
> the fix.
>

Ah, thank you very much!

I'm looking in to mailman3 too, seems quite different :-)


a.

--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Error accessing admin pages, AttributeError: local_name

[Odhiambo Washington]

On Tue, May 15, 2012 at 5:12 AM, Mark Sapiro  wrote:

> Andrew H wrote:
> >
> >I'm using the mailman vhost branch (is this the 'best' thing to use to
> >do multi-domain mailing list hosting?)
>
>
> The recommended best practice for Mailman 2.1.x is to run a separate
> Mailman instance per domain. The vhost branch may be the second choice
> alternative.
>
>
I did not know of the existence of this branch of Mailman. How is it
different from the main branch?
I am running Mailman with vhosts in a single instance, with theonly
limitation I have being that I cannot use the same listname more than once.
Is there something I am/have been missing? I am on 2.1.14.


-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
I can't hear you -- I'm using the scrambler.
Please consider the environment before printing this email.
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org