I know this might be simplistic, and I cannot get it to work, but the Defaults.py say
the following:
# These variables controls how headers must be cleansed in order to be
# accepted by your NNTP server. Some servers like INN reject messages
# containing prohibited headers, or duplicate head
On Sun, 4 Apr 2004, Brad Knowles wrote:
> Give Mailman the same kind of development resources, and maybe we
> can reasonably hope to take over all their best features, at some
> point in the hopefully not-too-distant future.
To put it politely, I suggest that the condescending tone of your
On Sun, 4 Apr 2004 16:02:38 +0200
Brad Knowles <[EMAIL PROTECTED]> wrote:
> As I said, this is a slippery slope. Once you start down the path of
> "But program XYZZY does this, why can't you?!?", it becomes very
> difficult to get back to the real issue of what features truly are
> needed, for w
On Sun, 04 Apr 2004 18:54:55 +0200
Andrzej Kasperowicz <[EMAIL PROTECTED]> wrote:
>> I don't. I assume that everyone can learn python should their
>> interest/need for a particular feature be large enough. After all,
> Bad assumption. Time is not from rubber, your advice might be good for
> co
On Sun, 04 Apr 2004 17:32:55 +0200
Andrzej Kasperowicz <[EMAIL PROTECTED]> wrote:
>> Past an early point an easy distinguishing factor is:
>> Are you interested in it enough to write a patch?
>> Are you interested in it enough to maintain a patch?
> To whom you address these questions?
Ho
> Is there any way to setup mailman to stop distributing X-Confirm-Reading-
> To requests sent by some list users?
I would do it inside postfix header_checks filters, with a line like
/^X-Confirm-Reading-To: / IGNORE
If you're using some other MTA, or want this setting to be only for Mailma
At 6:53 PM -0600 2004/03/21, Andrzej Kasperowicz wrote:
Is there any way to setup mailman to stop distributing X-Confirm-Reading-
To requests sent by some list users?
Depending on your MTA, you could configure it to remove various
types of headers on incoming messages. However, I'm not aware
At 6:57 PM -0800 2004/04/02, Lloyd F. Tennison wrote:
What makes you think it is Mailman? It does not exist on any of my
lists, nor does it exist on the lists I receive from others - including
this list. (View this source.) Check you MTA. Maybe that is what is
doing it. If Mailman is doing
> No. The critical point is "large enough". If their need is large
> enough they either will themselves, or will arrange for someone else to
> as their proxy.
I don't think so. If they ask for that on the list, that already means
that their need is large enough.
List-owners needn't to know any
Guys --
Can we please drop this? It's been beaten into the ground. I don't
think the mailman development crew has shown itself well here, either,
especially Brad, who seems to be grumpy beyond the needs of the
discussion for some reason. I don't think we as a team managing an open
source proje
> I don't. I assume that everyone can learn python should their
> interest/need for a particular feature be large enough. After all,
Bad assumption. Time is not from rubber, your advice might be good for
computer science students, but might not be for others.
I suggest you never say again to so
> If you want something done, and there isn't anyone who has the time,
> skills or inclination to do it for you, then you either knuckle down and
And how could I know that there isn't anyone, huh?
> do it yourself, or forget about it. You don't keep hounding someone else
> to do it.
You are
Andrzej Kasperowicz wrote:
To whom you address these questions?
Why do you assume that everyone knows Python?
I assist Mailman community as I can, i.e. by giving my advice and my
ideas how things could be improved.
So you'd rather tell people what to do, rather than do it yourself,
because you m
> > To whom you address these questions?
> > Why do you assume that everyone knows Python?
> > I assist Mailman community as I can, i.e. by giving my advice and my
> > ideas how things could be improved.
>
> So you'd rather tell people what to do, rather than do it yourself,
> because you might
Andrzej Kasperowicz wrote:
Past an early point an easy distinguishing factor is:
Are you interested in it enough to write a patch?
Are you interested in it enough to maintain a patch?
To whom you address these questions?
Why do you assume that everyone knows Python?
I assist Mailman communit
> Past an early point an easy distinguishing factor is:
>
> Are you interested in it enough to write a patch?
>
> Are you interested in it enough to maintain a patch?
To whom you address these questions?
Why do you assume that everyone knows Python?
I assist Mailman community as I can, i.e.
> At 2:41 PM +0200 2004/04/04, Andrzej Kasperowicz wrote:
>
> > I know, but I shouldn't be condemned for recommending such features. And
> > it seems that I was just for daring to compare it to ecarits.
>
> As I said, this is a slippery slope. Once you start down the
> path of "But prog
At 2:41 PM +0200 2004/04/04, Andrzej Kasperowicz wrote:
I know, but I shouldn't be condemned for recommending such features. And
it seems that I was just for daring to compare it to ecarits.
As I said, this is a slippery slope. Once you start down the
path of "But program XYZZY does this, why
> As I told you in private e-mail, I'm not interested in whatever
> he might have to say. I've been in this business long enough to know
> what the capabilities are of the various types of programs, and
> there's nothing he could possibly say that could change my mind.
But there is a lot
At 10:15 AM +0200 2004/04/04, Thomas Hochstein wrote:
| This program is free software; you can redistribute it and/or modify
| it under the terms of the GNU General Public License as published by
| the Free Software Foundation; either version 2 of the License, or (at
| your option) any lat
Brad Knowles schrieb:
> But asking someone to re-create a commercial product and then
> give that away for free, well that's quite a different matter.
If you're referring to ecartis - last time I looked at it, it said:
| Ecartis - Modular Mailing List Manager is Copyright ©1998-2002 by
|
At 1:23 AM +0200 2004/04/04, Andrzej Kasperowicz wrote:
I'd be glad if you could explain it to him, as he apparently was
offended, because I didn't do it, and he's not a newbe in internet, I've
seen him on-line for about 9-10 years.
As I told you in private e-mail, I'm not interested in whatev
> I disagree. I've been running mailing lists for more than ten
> years. This is not a basic task for any mailing list administrator.
> This is an advanced issue that very few mailing list administrators
> (should) need to have to deal with. This is part of why very few
> mailing lists
At 3:01 PM +0200 2004/04/03, Andrzej Kasperowicz wrote:
He claimed that
list-owners should configure their mailing list programs to remove that
kind of headers, that it should be within their basic tasks to do when
configuring a list.
> the common MUA that recognizes this header, and are not computer
> savvy-enough to know how to turn this "feature" off. That would tend
The person who complained about it to me, was able to turn it off, but he
didn't want to do so, claiming that he needs it sometimes to inform
people writin
: normal
Copies to: Subject: [Mailman-Users] Re:
[Mailman-Developers] How to remove
X-Confirm-Reading requests from mail headers distributed by Mailman?
> > At 6:53 PM -0600 2004/03/21, Andrzej Kasperowicz wrote:
> >
> > >
> At 6:53 PM -0600 2004/03/21, Andrzej Kasperowicz wrote:
>
> > Is there any way to setup mailman to stop distributing X-Confirm-Reading-
> > To requests sent by some list users?
>
> Depending on your MTA, you could configure it to remove various
> types of headers on incoming messages.
27 matches
Mail list logo
