Re: [Mailman-Users] nginx + thttpd configuration for mailman

[Manlio Perillo]

Manlio Perillo ha scritto:
> Hi.
> 
> I have successfully configured nginx to handle the mailman web interface.
> 
> CGI executions is delegated to thttpd.
> 
> If someone is interested I can post the configuration.
> 

I have posted the configuration guide in:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.023.htp



Manlio Perillo
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] programmatically managing list membership

[Scott Chapman]

Is there a way to programmatically manage th members of a list?

I am am managing a club, where we track current and former membership in 
a database. One wouldlike to b able to send an email to all the current 
members, but that requires a SQL query.

Is there a way for me to do this? Thanks in advance!

-Scott.

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] programmatically managing list membership

[Barry Finkel]

Scott Chapman <[EMAIL PROTECTED]> wrote:

>Is there a way to programmatically manage th members of a list?
>
>I am am managing a club, where we track current and former membership in 
>a database. One wouldlike to b able to send an email to all the current 
>members, but that requires a SQL query.
>
>Is there a way for me to do this? Thanks in advance!

I do it every day.  Once a day, for some of my lists, someone creates
a file of subscribers; this comes from a database.  I have cron jobs
that take each (possibly changed) file and run

 ./sync_members -w=no -g=no -d=no -a=no -f  filename  $listname

This will quietly synchronize the membership list.  I get the output
of the cron, so I can keep track of who was unsubscribed and who was
subscribed.  One problem - if an address in the database is incorrect,
then the subscriber address will be unsubscribed eventually by Mailman
at the end of its bounce processing.  If the bad address has not been
corrected, it will be re-subscribed the next time the cron job is run.

My script does some other processing, as I allow for static entries
(persons automatically subscribed to a list even though they are not
in the database).
--
Barry S. Finkel
Computing and Information Systems Division
Argonne National Laboratory  Phone:+1 (630) 252-7277
9700 South Cass Avenue   Facsimile:+1 (630) 252-4601
Building 222, Room D209  Internet: [EMAIL PROTECTED]
Argonne, IL   60439-4828 IBMMAIL:  I1004994

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] another question about invitation confirmationsubject line/VERP

[Christopher Adams]

Thanks to all for the plethora of information about VERP and how it is
used by the MTAs and Mailman. Just for clarification, I don't have a
list of 250,000 subscribers, just a site that has a total of 250,000
subscribers over 500+ lists. I think the largest is about 40,000.

So, if all I want to do (which was my original question) is to VERP
confirmations,  I only have to add this to Postfix:

default_verp_delimiters = +=
verp_delimiter_filter = -+=x

and this to mm_cfgy.py:

VERP_CONFIRMATIONS = Yes

All other VERP setting are whatever is the default in Defaults.py.

VERPing the confirmations seems to work as expectedc and I assume that
there is not much of a burden on the server without VERPing every
message or even VERPing a sample of messages.

Thanks again for the good information.


On Nov 27, 2007 8:38 PM, Brad Knowles <[EMAIL PROTECTED]> wrote:
> On 11/27/07, Mark Sapiro wrote:
>
> >  As a point of reference however, there are lots of lists on python.org
> >  and some are quite busy (e.g. [EMAIL PROTECTED]) and they are
> >  personalized and it seems to work OK. Brad has posted on this in the
> >  past
> >  
> > .
>
> I also updated FAQ 1.15 with the latest information about python.org.
> See
> .
>
>
> --
> Brad Knowles <[EMAIL PROTECTED]>
> LinkedIn Profile: 
>



-- 
Christopher Adams
[EMAIL PROTECTED]
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] another question about invitation confirmationsubject line/VERP

[Brad Knowles]

On 11/29/07, Christopher Adams wrote:

>  Thanks to all for the plethora of information about VERP and how it is
>  used by the MTAs and Mailman. Just for clarification, I don't have a
>  list of 250,000 subscribers, just a site that has a total of 250,000
>  subscribers over 500+ lists. I think the largest is about 40,000.

That would still make it one of the larger Mailman installations I know of.

>  VERPing the confirmations seems to work as expectedc and I assume that
>  there is not much of a burden on the server without VERPing every
>  message or even VERPing a sample of messages.

There shouldn't be a whole lot of load resulting from VERP'ing the 
confirmations, no.  Those should be going out, at most, once per day 
per recipient who's been identified as needing confirmation.  Even if 
all your lists were announce-only lists and you only got one 
announcement per list per month, you should probably see more 
"regular" traffic than the confirmations.

I'm not sure, but turning on verp_confirmations may result in other 
list administrative functions also being VERP'ed, but again even if 
you put all them together, they should still be a relatively small 
fraction of your overall volume.


Please let us know if you have any further questions, or if you'd be 
willing to contribute more information to be put into the FAQs.

-- 
Brad Knowles <[EMAIL PROTECTED]>
LinkedIn Profile: 
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] another question about invitation confirmationsubject line/VERP

[Mark Sapiro]

Christopher Adams wrote:
>
>So, if all I want to do (which was my original question) is to VERP
>confirmations,  I only have to add this to Postfix:
>
>default_verp_delimiters = +=
>verp_delimiter_filter = -+=x


Actually, you don't need either of these. default_verp_delimiters
specifies the default VERP delimiters to be used in the envelope
sender address, + to separate the sender from the recipient address
and = to replace the @ in the recipient address. verp_delimiter_filter
specifies the characters that a sender is allowed to specify as
replacements for the defaults.

They both relate only to 'true' VERP done by Postfix on outgoing mail
and have nothing to do with Postfix's parsing of incoming mail
addresses.

What you do need in Postfix is

recipient_delimiter = +

So that when Postfix receives the reply to a 'friendly' confirmation
addressed to [EMAIL PROTECTED] it
delivers it the same as it would if it were addressed to
[EMAIL PROTECTED] .


>and this to mm_cfgy.py:
>
>VERP_CONFIRMATIONS = Yes
>
>All other VERP setting are whatever is the default in Defaults.py.


That's correct.


>VERPing the confirmations seems to work as expectedc and I assume that
>there is not much of a burden on the server without VERPing every
>message or even VERPing a sample of messages.


There is no additional burden on anything (except maybe Postfix address
parsing on the replies) from setting VERP_CONFIRMATIONS = Yes since
the confirmations are individual messages sent one at a time to one
recipient regardless of the VERP_CONFIRMATIONS setting.

-- 
Mark Sapiro <[EMAIL PROTECTED]>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://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] HOWTO - integrating Mailman with a Swish-e search engine

[Tomasz Chmielewski]

Hi,

I just wrote a small HOWTO on integrating Mailman with Swish-e:

http://wpkg.org/Integrating_Mailman_with_a_Swish-e_search_engine


Let me know what you think about it.


-- 
Tomasz Chmielewski
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] HOWTO - integrating Mailman with a Swish-e searchengine

[Mark Sapiro]

Tomasz Chmielewski 
>
>I just wrote a small HOWTO on integrating Mailman with Swish-e:
>
>http://wpkg.org/Integrating_Mailman_with_a_Swish-e_search_engine
>


This looks great.

Is it OK if we (or you) update FAQ 1.11

to point to your page?

-- 
Mark Sapiro <[EMAIL PROTECTED]>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://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] thread-throttling (feature idea, needs more thought)

[Jim Popovitch]

On Fri, 2007-11-30 at 15:24 +0900, Stephen J. Turnbull wrote:
> Now, if you were proposing a feature where Mailman would notice that
> I've posted to a thread 3 times in fifteen minutes and mail me a
> polite notice "are you really sure you need to post to this thread
> three times in fifteen minutes?!", *that* I could really go for!  It
> wouldn't even have to work for other people.

Actually I like that idea very much.  It could cause the hot-heads to
wait a minute for a confirmation email with a URL to click to before
continuing.  Hm.

Thanks!

-Jim P.

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] thread-throttling (feature idea, needs more thought)

[Stephen J. Turnbull]

Jim Popovitch writes:

 > What if Mailman had a thread-throttling feature where after a preset
 > number of posts, further posts (with same msgid or Subject, etc.) would
 > automatically induce a queuing delay.

I think this would just lead to people mail-bombing the admins instead
of the list. :-)

The other issue I can think of is that when I think back on the cases
where in hindsight I really wish I'd had a 15 minute delay on the SEND
key mostly occurred on lists with a substantial management component.
It would be really nasty if a feature intended to keep hotheads like
me from embarrassing themselves instead suddenly slowed a discussion
of how to deal with an ongoing DDOS attack or the like.

Now, if you were proposing a feature where Mailman would notice that
I've posted to a thread 3 times in fifteen minutes and mail me a
polite notice "are you really sure you need to post to this thread
three times in fifteen minutes?!", *that* I could really go for!  It
wouldn't even have to work for other people.

Or to paraphrase an old George Carlin schtick, "Stop me before I
[post] again!"

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp