Re: [Mailman-Users] Is there a patch which improves bulk mailing?

2003-09-30 Thread Jim Littlefield
Wayne Spivak wrote:

I have two lists, each with 20,000 names on them.  The algorithm Mailman
uses, to create the list e-mail output, is to say the least inefficient.
There was a program that was used in conjunction with Majordomo called
Bulk-mailer which did a tremendous job.  

In effect, it bundled addresses based on domain name, and let you limit
how many domain names were sent in the same e-mail.  This way, on a 20K
list, maybe 500 e-mails would go out, but they would do it in a fraction
of the time Mailman currently does it (it takes about 6 - 10 hours).
Thanks.
 

Rather than modifying Mailman, you may want to consider another MTA. 
What are you using today?

--
Jim Littlefield"I'm writing a book. I've got the page
   numbers done, so now I just have to fill
   in the rest." - Steven Wright


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Global blacklist?

2003-08-25 Thread Jim Littlefield
Gerard Beekmans wrote:

Hi guys,

I've been looking for a global blacklist or spam filter. I know how to
add addresses and regexes on a per list basis, but this gets real
tedious if I want to ban something from all the lists I'm running on the
server. Is there a global list?
I found this KNOWN_SPAMMERS variable but it doesn't work for me. Maybe
I'm using it the wrong way. Here's what I've added to Mailman/mm_cfg.py:
KNOWN_SPAMMERS = [('subject', 'test')]

I send an email with subject 'test' to any of the lists and they aren't
blocked. What am I doing wrong?
 

Block the spam with your mail server, not within Mailman.

--
Jim Littlefield "Right now I'm having amnesia and deja
vu at the same time. I think I've 
forgotten this before." - Steven Wright



--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Digest message header filtering

2003-01-30 Thread Jim Littlefield
On Thu, Jan 30, 2003 at 04:04:14PM +, Simon White wrote:
> 30-Jan-03 at 10:56, Jim Littlefield ([EMAIL PROTECTED]) wrote :
> > A number of the subscribers to my lists have complained about the
> > "unimportant" headers (Message-ID, In-Reply-To, etc.) included with
> > each post when receiving a plain digest. I am talking about headers
> > within the digest. Has anyone figured out a good way to strip these
> > out?
> 
> If you have Postfix as an MTA, then you can do body_checks on the email
> *body* only to silently ignore any lines with extraneous headers by
> using a regexp to ignore them. However, this is best done on a server
> which is not also an all-purpose MTA in case people forward full headers
> to others for analysis.
> 
> Other solutions from your MTA of choice are possible, in Mailman itself
> you'd have to hack Digester.py. At first glance, it looks like it pretty
> much forwards plaintext mbox style, to Handlers/ToDigest.py. This
> handles MIME conversion where necessary.

I guess my question wasn't very clear...I was referring to headers
*within* the body of the digest; not the digest's headers. So this isn't
an MTA issue, just a message content one.

> Interesting part of ToDigest.py
> 
> # rfc1153 says we should keep only these headers, and present them in
> # this
> # exact order.
> KEEP = ['Date', 'From', 'To', 'Cc', 'Subject', 'Message-ID', 'Keywords',
> # I believe we should also keep these headers though.
> 'In-Reply-To', 'References', 'Content-Type', 'MIME-Version',
> 'Content-Transfer-Encoding', 'Precedence', 'Reply-To',
> # Mailman 2.0 adds these headers, but they don't need to be kept
> # from
> # the original message: Message
> ]

Hmmm, I'll have to take a look at that file. Thanks for pointing it out.

> Hacking that might allow you to get rid of those headers quite simply,
> breaking RFC1153 in the process, perhaps.
> 
> (I think I should stop promoting Postfix on the Mailman list now...)

Why? Postfix is a great MTA :)

-- 
Jim Littlefield "All those who believe in psychokinesis
 raise my hand." - Steven Wright

--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org



[Mailman-Users] Digest message header filtering

2003-01-30 Thread Jim Littlefield
A number of the subscribers to my lists have complained about the
"unimportant" headers (Message-ID, In-Reply-To, etc.) included with each
post when receiving a plain digest. I am talking about headers within
the digest. Has anyone figured out a good way to strip these out?

-- 
Jim Littlefield "All those who believe in psychokinesis
 raise my hand." - Steven Wright

--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org