Brad == Brad Knowles [EMAIL PROTECTED] writes:
Brad Clearly, there is a benefit here to the Gmane users,
Brad potentially even a commercial benefit. But what do they
Brad contribute back to the larger Mailman community?
I don't think that's a useful question to ask. Open source is
jam == John A Martin [EMAIL PROTECTED] writes:
sjt I missed at least one of your posts, receiving Brad's reply
sjt to it almost 24 hours in advance of your post. Even today
sjt this is common for netnews.
jam Sorry, Gmane is not netnews. Gmane is not Usenet.
OK, so that's not
Matthew == Matthew Thompson [EMAIL PROTECTED] writes:
Matthew I have a mailing list with users subscribed from two
Matthew particular domains, call them nice.com and naughty.com.
Matthew The security czars are naughty.com have decided that
Matthew inbound email with naughty.com
Mark == Mark Sapiro [EMAIL PROTECTED] writes:
Mark The logical place to do all this is
Mark Mailman/Handlers/CookHeaders.py.
I don't understand this recommendation. Why not use a separate
Handler in either the global pipeline (if it's an organizational
installation) or the
Mark == Mark Sapiro [EMAIL PROTECTED] writes:
Mark Henrik wrote:
On 2/24/06, Mark Sapiro [EMAIL PROTECTED] wrote:
Then maybe someone put it in Defaults.py. Let's hope Mandrake
is not distributing its package this way.
They are, I'm afraid.
Mark :-(
With all due
Brad == Brad Knowles [EMAIL PROTECTED] writes:
Brad If anyone wants to see a more completely laid out and
Brad fully explained discussion of why Goodmail is such a bad
Brad idea, please see http://www2.dearaol.com/faq and
Brad http://www2.dearaol.com/blog.
*sigh* I see
Jeff == Jeff Donsbach [EMAIL PROTECTED] writes:
Jeff Based on the lack of traffic to the mailman3-dev mailing
Jeff list, is it a safe assumption that Mailman3 development is
Jeff stalled? (Please, devs, don't take this as criticism. It is
Jeff just a question).
No. Besides
Brad == Brad Knowles [EMAIL PROTECTED] writes:
Brad At 3:07 PM +0900 2006-03-02, Stephen J. Turnbull wrote:
*sigh* I see lots of explanation of why this is going to hurt
legitimate bulk emailers there, but ... isn't that obvious?
OTOH, very little about how it hurts
Harold == Harold Paulson [EMAIL PROTECTED] writes:
Harold Do you really have a *policy* to accept messages that you
Harold will never deliver, save them to disk, and then generate
Harold reject messages for them?
As I read his post, indeed he does. He wants legitimate posters to be
Harold == Harold Paulson [EMAIL PROTECTED] writes:
Harold The problem is that we are making net.messes by
Harold automatically replying to junk. It would be nice to see a
Harold general fix.
Well, there isn't one.[1] Take the case in point. Your solution is also
a hack in that it
Dave == Dave Crocker [EMAIL PROTECTED] writes:
You understand that and I understand that, but I don't think
it's easy to grasp from the pages whose URLs you posted. What
_is_ easy to grasp is that bulk emailers who have been getting
a certain level of QoS for free are now
Patrick == Patrick Bogen [EMAIL PROTECTED] writes:
Patrick On 3/9/06, Matt England [EMAIL PROTECTED] wrote:
...and this seems to be the trickiest part: which list becomes
the primary one. I can envision straightforward (even though
they are not easy to implement solutions)
Brad == Brad Knowles [EMAIL PROTECTED] writes:
At 7:50 PM -0400 2006-04-28, Barry Warsaw wrote:
Whatever else we decide, I don't agree, or at least, it won't
help us. $3.6.6 says that Resent-* headers are to be added by
a user. It also says that these are purely informational
William == William D Tallman [EMAIL PROTECTED] writes:
William How does the RFC, or the writers thereof, define user?
They don't. IMHO (there are those more expert than I on this list)
anything that is normally expected to touch the headers or body of a
message is a user for the purpose of
William == William D Tallman [EMAIL PROTECTED] writes:
William On Wed, May 03, 2006 at 11:11:22PM +0900, Stephen
William J. Turnbull wrote:
I don't think that is the way that RFC writers in general
think.
William Yes, so I gather.
:-)
William Which means that people
Vikram == Vikram Goyal [EMAIL PROTECTED] writes:
Vikram May 7 05:07:16 ip-68-178-242-231 sendmail[12991]:
Vikram k474oTaH027069: to=Several Emails, delay=06:48:40,
Vikram xdelay=00:00:00, mailer=relay, pri=15687906,
Vikram relay=someserver.net, dsn=4.0.0, stat=Deferred:
Brad == Brad Knowles [EMAIL PROTECTED] writes:
At 5:09 PM -0400 9/18/06, John A. Martin quoted JC Dill:
Where are those restrictions expressed. I do not see them at
http://mail.python.org/mailman/listinfo/mailman-users. I do not see
them in either the subscription challenge mail nor in
Brad Knowles writes:
One thing that would help is if your ISP was running the latest
version of Mailman -- we're now on version 2.1.9. There have been a
At 3:10 PM -0500 11/17/06, Alan McConnell wrote:
Yes. My question, addressed to you, or to any Debian
experts here is:
Bob McLeran writes:
Using Mailman 2.1.9 as a list administrator.
Trying to block posts with string test in the subject line but would
like to automatically approve certain subjects with the same string,
such as testing engine components - is this possible under either
Header
Bob McLeran writes:
We're trying to stop emails with the string test - and that works with
the filter subject: test currently. What I'd like to do is to be able to
create a rule that would allow a legitimate subject line, like testing
NMEA circuit which includes the string test to go
Paul Tomblin writes:
Is there any way to make arch smarter about ^From lines?
Yes, but it's not a good idea to put it in the distribution, at least
not without a lot of careful hedging about and making it an option
defaulting to off. You can't even being sure that From_ lines will be
Brad Knowles writes:
I've never claimed to be a Debian expert, and if they're mucking
about with packages that include certain features by default in order
to remove those features, then there's not much I can do to help the
poor souls that are stuck with that kind of stuff.
That's
Todd Zullinger writes:
Brad Knowles wrote:
We can tell you what the Mailman-standard was is to start them, but
Apple has created their own code to manage this aspect of Mailman
operations and they haven't shared that with us.
Apple does provide the source code for their mailman
Todd Zullinger writes:
Nothing wrong with that. It's why open source is so nice. I have the
choice to find vendors and projects that share more of my values than
others may. If FHS compliance is really important to you, you'll like
the Red Hat mailman packages.
The problem is that
Todd Zullinger writes:
I agree that if someone comes here with questions that are obviously
very dependent on some customization that their vendor has made that
they should be directed to check with the vendor. (Same goes for
users who need more basic help learning to use their OS of
Mark Sapiro writes:
Then, the question is why doesn't bin/check_perms -f fix it? Are you
running this as root?
This may have improved more recently, but sometimes I've had to run
check_perms -f more than once.
--
Mailman-Users mailing list
Ron Brogden writes:
The administrator gets a discard notice but there is no mention of
specifically why the message was discarded. Is there any option anyone is
aware of to make logging of discards more verbose?
Unlike the Hold exception, the Discard exception contains no
information
Noah writes:
any clues why mailman keeps dumping the following error trace in
/usr/local/mailman/logs/error ? Happens about every hour or so or
sometimes minutes apart.
Probably for the same reason you repeatedly post to Mailman Users: it
wants attention to its pain.
For future
Noah writes:
7) Logs.
The incoming post email to announce arrives and sendmail dumps a line or
two to /var/log/sendmail to acknowledge receipt of the email.
If you can post the relevant log entries, that might be helpful. (Of
course be careful that you're not revealing anything
Noah writes:
thanks for following up. we just solved the problem.
Good!
it was a misused wildcard in the mailman filter rules. I might
have missed it but it feels like there is not enough verbose output
in the mailman logs files to tell me that a message was filtered
and an entry
Brad Knowles writes:
If you have Mailman questions, we should be able to help with those.
But we can't provide support for OS-specific issues.
However, members of this list often do; eg, this thread got 3 answers.
How about starting an OS-specific section of the FAQ, similar to the
MTA
Brad Knowles writes:
However, members of this list often do; eg, this thread got 3 answers.
Of which two were We can't help you with OS-specific issues,
Of course. My point is that people do respond, not that it's very
helpful; I'm looking for ways to save some of that effort.
Brad Knowles writes:
Challenge/response is one of the most vile inventions that has ever
been applied to the concept of Internet e-mail.
*chuckle*
I wouldn't go so far, since the spam that evoked it is far worse, but
I'm steadfastly opposed to challenge-response.
If you absolutely *must*
Bob Morse writes:
The problem remains, however: How do I prevent spoofing? In this case they
have a real fear due to a board member who is soon to be ejected from the
board and have organizational membership taken away. They feel he is capable
(both emotionally and technically) of major
Mark Sapiro writes:
2. Why this message didn't get moved to shunt directory?
I don't know why it didn't shunt.
At least in earlier implementations of the email lib and Mailman, the
original parse of the message was not enclosed in the shunt mechanism,
so the exception got caught by the
heathcliff writes:
We are all set to migrate our user community to Mailman, but we are
at an impasse as to the most painless way to do this. It is not
enough to just inform them of the cut off date and send them a few
lines of instructions or guides ahead of time. Has anyone come
Mark Sapiro writes:
I understand the point about good practice, and we do try to validate
user input in Mailman to avoid possible XSS attacks via the web
interface. What we're dealing with here are syntactically validated
email addresses so the really nasty stuff has already been caught.
Krystal writes:
Has anyone here ever attempted to use EUC-JP encoding along with
digests? I recently ran into an issue with a list whom was using
Japanese as they're language, and the digest mbox file actually caused
any other list on that server to not receive digests and I have
Brad Knowles writes:
At 12:10 PM +0900 4/6/07, Stephen J. Turnbull wrote:
In the short run, you probably should disable digestible for that
list. Mailman's I18N is not very robust in this respect, and it
may take some time to fix.
More importantly, I'm not sure where
[EMAIL PROTECTED] writes:
The second is not really a problem, but a request. Is there any
way to sort the archives by date in descending order rather than
ascending order? It makes no sense for the newest posts to be at
the bottom of the list.
This is a Your Mileage May Vary king of
Bill Bedford writes:
I am getting a number of confirmations failing with SMTP errors similar
to this
Out: 220 mousa.uk.com ESMTP Postfix
Your mailer is Postfix, good ...
In: HELO smtp806.mail.ukl.yahoo.com
Out: 250 mousa.uk.com
In: MAIL FROM:[EMAIL PROTECTED]
Out: 250 Ok
Mark Sapiro writes:
It isn't AFAICT. I was going to add it, but I am looking for a specific
RFC reference. I have looked at several RFCs and I don't see anything
that talks about rewriting domains in headers. All I found was RFC
1123 (STD 3), sec 5.2.2
As Lucy van Pelt (The Doctor is
Brad Knowles writes:
| In the dot-atom form, this is interpreted as an Internet
| domain name (either a host name or a mail exchanger name) as
| described in [STD3, STD13, STD14].
In particular, note that it says host name or mail exchanger
name, and specifically
Mark Sapiro writes:
I have added FAQ 6.22
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.022.htp.
Look it over and comment/fix as appropriate.
Basic format, especially the length, looks good to me. Two
suggestions: my feeling is that the first line should mention the
*places*
Brad Knowles writes:
[[ Aside:
I was on the DRUMS working group for a while,
Thank you!
]]
The MTA needs to rewrite headers that the MTA needs to rewrite. The
question is which headers should the MTA be rewriting?
RFC 2821 section 3.8.4 (IIRC) mandates that gateways rewrite non-FQDN
Brad Knowles writes:
Two
suggestions: my feeling is that the first line should mention the
*places* where replacement has been observed (envelope address, RFC
2822 addresses, whatever).
It may be my anti-histamine-fogged
Brad Knowles writes:
At 4:25 PM +0900 4/12/07, Stephen J. Turnbull wrote:
And on which host? Ie, is it that [EMAIL PROTECTED] composes a message
To: [EMAIL PROTECTED], and the MTA at example.com is rewriting that
to To: [EMAIL PROTECTED]? If so, it's purely a DNS issue
Rick Pasotto writes:
It must be the default as I certainly haven't changed anything.
On the default archiver (pipermail) in default configuration, the
60-hyphen separators are preserved intact in this test:
http://calypso.tux.org/pipermail/xemacs-test/2007-April/04.html
Mark Sapiro writes:
I said in my first reply
A single post should be archived as one message unless it containes
lines beginning with From (*nix mbox separators), but I think the
current archiver escapes extraneous From lines, so even these won't
cause a single message to be
Brad Knowles writes:
Of course, if there isn't any other resource, then CPanel users are
welcome to try to help each other through this list.
+1
Such help might even leak into the FAQ occasionally.
Maybe it's also time we set up a separate mailman-cpanel-users list,
as well as a
[EMAIL PROTECTED] writes:
is it possible for a Server Provider to dump the cPanel version of
MM and do a source install that would work similar to the
pre-package version??
Depends on what you mean by work similarly, of course. There are
four points of view: list user, list admin, site
Andrea S. Gozzi writes:
[EMAIL PROTECTED]: mail for lists.vp44.net loops back to myself
Would somebody know how to fix this?
You probably need to tell postfix that it accepts mail addressed to
lists.vp44.net for local delivery. I would guess that the parameter
is virtual_alias_domains in
Andrea S. Gozzi writes:
'relay_domains = lists.vp44.net' fixed it.
Why is this a right way to do it? I would think that if it's all the
same host you would want something to say I'll handle it, which is
what mydestination does for real domains, and virtual_alias_domains
does for virtual
David Southwell writes:
the Mailman FAQ is a bit of a curates egg. Sometimes it seems like
an FAQ but it often seems more like a personal blog
That's a FAQ. Excerpts from mailing list posts, with those questions
that are most frequently answered gradually acquiring improved wording
and more
Dragon writes:
Actually no, those are not the best way to do this IMO. If ALL of the
web pages were template-based, it would be a simple matter of
defining the CSS you want in a CSS file and adding it to the page header.
There's no reason why the programmatically generated pages can't
Dragon writes:
Yes, it could be done now, but it requires changes to the mailman
code that generates the page.
But the header I'm talking about is an *HTTP* header. It seems
plausible that it requires only *one* change to the routine that
marshals the headers or to the httpd configuration,
Ivan Van Laningham writes:
But the head element is not being produced in one place.
I'm not talking about the HEAD element. Before the HTML, the gods
have placed the HTTP headers. It seems reasonably likely that there
is one place where an appropriate HTTP header could be inserted in all
Rolf E. Sonneveld writes:
today I have a similar (or the same?) problem. Running Mailman V2.1.9.
Symptoms in my case: a new member (added with the command line utility
add_members) is subscribed properly, the associated mail address gets a
welcome message (so far so good), but mail to
Mark Sapiro writes:
Stephen J. Turnbull wrote:
When the post is delivered,
there will be an entry in logs/smtp for each batch of deliveries
(usually one per remote host, or one per user if personalization or
VERP is being used).
Actually, if nothing goes wrong, there will be only
Mark Sapiro writes:
In header_filter_rules, put the following regexp.
^from:[EMAIL PROTECTED]
Isn't that going to lose on (1) Bogus Name [EMAIL PROTECTED] and
on (2) ... [EMAIL PROTECTED] ?
--
Mailman-Users mailing list
Mark Sapiro writes:
Yes! base64 is a standard MIME encoding which the recipient's MUAs
should recognize. Why do the recipients have difficulty reading a
base64 encoded message?
Because they use non-conforming MUAs localized to the environment.
These MUAs are typically popular with users
Dragon writes:
Mark Sapiro sent the message below at 12:20 4/27/2007:
Brandon Sussman wrote:
Can a copyright notice containing the sender's name be
automatically placed in regular mailman list messages?
However, is this even a good idea at all.
I've got to agree with Mark, I
John W Gintell writes:
Many of the web hosting services that offer mailman place a limit on
the number of messages/hour that a given domain can deliver. This is
presumably done to avoid saturating their servers. If you exceed the
limit, they just ignore some of the recipients.
If
[EMAIL PROTECTED] writes:
I do not have direct access to the list server system; I am working
through our ISP's support service. Any suggestions for what I can
tell them to look for
I'd suggest just giving them this address.
Support implies that they know what they are doing, and will do
Mark Sapiro writes:
This can be tricky. LOG_DIR is defined in Defaults.py in terms of
VAR_PREFIX. If VAR_PREFIX is redefined in mm_cfg.py, this will not
redefine LOG_DIR as LOG_DIR was already defined in Defaults.py in
terms of the Defaults.py definition of VAR_PREFIX.
2.1.9's
John Papapanos writes:
Is there a solution to the broken link ?
This is not a problem that can be solved. Mailman (or some other
mail program) here is conforming to the recommendation in the
standards that lines in mail bodies be broken at a reasonable length.
Since this behavior is
Mailman developers: I've submitted a bug on the SF tracker (what, no
Jira yet?) #1712034. What I write below is all I've got for now, and
it's on the tracker; bug/patch traffic will followup to the tracker.
Reply-To set to mailman-users.
John Papapanos writes:
Here is a URL where I created a
Wilfred Gasper writes:
Thank you for this description. So there's nothing I can do against it
like using another version of Python?
Well, another version of Python won't do. You need another version of
the Internet. According to RFC 2822,
Subject: a few words
Subject:
a few words
Deboo ^ writes:
I'm getting the above erro when I try to telnet in to my newly
installed/configured postfix with TLS.
I searched on google for this exact error but didn't get any solution.
I got the info that thsi problem is due to the certs. I double checked
the paths to the certs
Mark Sapiro writes:
case, it is done by the underlying Python email library, and all three
of the above folded subjects should unfold to essentially the same
thing (i.e., the MUA should remove the inserted crlftab)
AFAIK the standard implies but does not say that a single CRLF is to
be
Barry Warsaw writes:
I agree that the current state isn't correct, but the right place to
fix this is in the email package, so the discussion really should be
moved to Python's email-sig.
I thought about that ... but I certainly hope that people who have
opinions about this will join,
Brad Knowles writes:
The problem is that the people who can fix this problem are over on
the list that Barry identified. Any discussion anywhere else is not
likely to go anywhere, at least not as far as Python Mailman are
concerned.
So, get your experts to go have the
Lloyd F. Tennison writes:
I saw that, but it is not really an answer as te problem is that it
is inserting a TAB, not whitespace, and that is what is causing the
problem. A carriage return and spaces would be fine. The tab is
what most clients cannot handle.
Carl's reply
Leonard Jacobs writes:
delivery to [EMAIL PROTECTED] failed with code -1: (104,
'Connection reset by peer') I am also seeing many Low level smtp
error: Server not connected, msgid errors.
This seems likely to be either a Postfix problem, or maybe you've
caught a social disease (ie, a
Curtis Preston writes:
But that doesn't authenticate. On the real web side, it works if you
authenticate FIRST with another page, then call the user's options page
after you're authenticated as the admin, but I don't think I can do that
with wget.
Dunno if it will get you where you want
Juan Miscaro writes:
My MTA is rejecting with a 550 (user does not exist):
No, it would appear that it is in an error state, closing the
connection before receiving and acknowledging a QUIT command (required
by RFC 2821, section 4.1.1.10):
$ tail -600 smtp-failure | grep example
Jun 09
Mark Sapiro writes:
I don't know if there is a standard that says your MUA 'should'
recognize a single LF in the decoded text as a line break,
Since it's in UTF-8, Unicode does, Technical Annex #14. Conformance
is required by Unicode 4.0.
Of course if the MUA doesn't claim conformance to
Barry Finkel writes:
I am running Mailman 2.1.9. I have a list where one posting has a
Subject: line:
Change in Procedure for Computers on list with possible Antivirus
Problems
The next posting in the thread has:
Change in Procedure for Computers on list with
Mark Sapiro writes:
Implementation of a custom handler to take action on a message based on
pattern matches on the message body would not be difficult, but I
don't know if anyone has done it.
If you need something that's somewhat automatically extensible, the
SpamBayes package is written
Mark Sapiro writes:
But, the fact remains that there are many commonly used MUAs that drop a
whitespace character in unfolding and there's not much we can do about that.
I wonder if they're better with RFC 2047. That is, suppose we
rendered
Subject: Pretend this is a long field
as
Rich Kulawiec writes:
Any incoming mail message whose putative sender matches:
do-not-reply@
and which is directed to any of the Mailman standard aliases can
be rejected (not bounced [1]) with SMTP status 550 (extended status
5.7.1) since either:
(a) it's a forgery,
Michael Kabot writes:
I would love to help, but afraid my Python experience is non
existent.
If you have coded in any language, well, Python is very readable. Try
reading the Mailman code, starting with the email module. If you
like, then help with the code. If it leaves you cold,
Brad Knowles writes:
However, do keep in mind that spammers have recently latched onto the
fact that most people do seem to let *.PDF files through, although
I'm not sure what MIME type these messages are being tagged with.
FWIW, in a sample of 10 recent .pdf spams, all had extension
Barry Finkel writes:
The attached message was received as a bounce, but either the bounce
format was not recognized,
This is the relevant case here. If the message doesn't look like an
MTA bounce, it's probably a bad idea to treat it as a bounce. ML
admin addresses get a fair
Jewel Makda writes:
I am receiving spam from a listserv on my server and I am not even
subscribed to it. The spam is not getting through to the list members
which is a good thing. The name of the list is: maineattorneys-l and
sometimes the email will be to:
[EMAIL PROTECTED]
Julie Zbeetnoff writes:
After not getting any response and not being able to send out to my list for
over 24 hours. I decided to test the subscription option.
I did not receive confirmation to join my own list but rather I received a
confirmation to join this mailman list which I
Pál Viktor writes:
I have a problem with the mailman web interface output.
I use the hungarian translation, which should be generated as an
ISO-8859-2 html file, but it generates an UTF-8 output.
I have checked the text files which are related to the web output and
they are all in
Gary Spivey writes:
former, does somebody have a recommended way to stop them? I have a SPAM
filter running on my end system, but I am just tired of the constant
flow of SPAM.
There's no recommended way. As Mark says, only a choice of evils.
The basic problem that we face is that email
Brad Knowles writes:
On 10/1/07, Stephen J. Turnbull wrote:
If (3) interests you, I can go into more detail about my solution, but
I gotta run right now.
BTW, #1 and #2 are also issues for e-mail to Postmaster, which is
covered in the SAGE Booklet Internet Postmaster: Duties
Brad Knowles writes:
giving them some reasonable protection against loss of revenue due
to the material being freely available in an electronic form.
You may not call that proprietary, but that's precisely the definition
of proprietary that one arrives at when observing the behavior of
Brad Knowles writes:
If I had mentioned a book that I wrote or co-authored, or a book that
I had been technical reviewer of (e.g., 2nd editions of the O'Reilly
books _DNS BIND_ and _sendmail_) and I provided a link to the
publishers web page for the book, would you have done anything
J.R. Constance writes:
I have been working through the instrucitons available at http://
www.jamesh.id.au/articles/mailman-spamassassin/
I believe these instructions are pretty old, and SpamAssassin has
evolved significantly since then.
I get the following:
warn: Unknown option: a
Steve Campbell writes:
I will do my best to train the users, but for now, I have just added a
note in the footer to avoid the Reply to All. Of course, no one read
footers, but what the heck.
Note that Mailman also allows headers, which people will notice. Of
course you don't want that
Mark Sapiro writes:
Alexandros G. Fragkiadakis wrote:
He's Greek. I'll bet he has users putting raw ISO-8859-7 in the
headers.
Look for illegal character isn't ascii errors in the logs (something
like that, I forget exactly how it's spelled).
zbigniew szalbot writes:
I uploaded the script to /usr/local/mailman/bin
but when I run list_pending adwent
I get list_pending: command not found
is /usr/local/mailman/bin on your PATH?
--
Mailman-Users mailing list
Mervyn Kahn writes:
How do or what do I have to do to change the from to have less than all of
the following
[EMAIL PROTECTED]; on behalf of; Teamepasella
[EMAIL PROTECTED]
You can't; this is a bug in the user's mail program, probably Outlook.
The most straightforward approach is to tell
Jim Park writes:
My question is what does the Reason Message has implicit destination mean?
The list was BCC'd, and therefore doesn't appear in the message
headers.
There are various caveats and features that need to be accounted for,
but that's the basic idea.
Mark Sapiro writes:
Tokio Kikuchi wrote:
File /usr/local/mailman/Mailman/Archiver/HyperArch.py, line 579, in
as_text
atmark = unicode(_(' at '), Utils.GetCharSet(self._lang))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xd0 in position 1:
ordinal not in range(128)
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. :-)
Cyndi Norwitz writes:
Date: Sat, 8 Dec 2007 08:49:30 -0800
From: Mark Sapiro [EMAIL PROTECTED]
SpamAssassin is much better integrated in the MTA ahead of Mailman, but
if they want to integrate SpamAssassin with Mailman at some point,
refer them to
101 - 200 of 1551 matches
Mail list logo
