At 05:53 PM 3/30/2001 -0800, Dave Melton wrote:
>Let's develop the analogy here...
>An airport security system can be likened to restricting posts
>to list subscribers. Sure, we all have to stand in line and
>occasionally empty our pockets before we can get on a plane.
>This is a minor inconvenience, but a lot less annoying than
>getting blown out of the sky.
>If only subscribers could post to the list, then people would
>have to take the extra two minutes to subscribe before they post
>their questions. They could easily unsub or select nomail after
>they get what they need. This doesn't seem like much of a
>"penalty" to get the great support (for a free product!) that
>this list provides.
Also, *VOLUNTEER* list administrators could sort the
wheat from the chaff and allow legitimate posts from non-members
onto the list, removing the subscription requirement completely!
>While we're on the subject...spammers, hackers and terrorists
>should all be shot on sight.
To quote from the "Cult of father Darwin" list...
Let us prey...
On Fri, 30 Mar 2001 19:24:30 -0500
reb <Phydeaux> wrote:
> At 03:29 PM 3/30/2001 -0800, J C Lawrence wrote:
>> Without questioning the boundaries of topic or religion on this
>> one, there's also the argument that allowing spammers to control
>> and alter our behaviour, and thereby granting them that power and
>> influence over us is fundamentally WRONG and that doing so is
>> tantamount to kowtowing to terrorists.
> I think putting bombs on airplanes is WRONG! Allowing terrorists
> to make us scared and control and alter our behaviour, thereby
> granting them power and influence over us is fundamentally WRONG!
> So, we should ignore them and ban all airport security systems
> because that's just part of caving in to the terrorists'
Being cognizant of one's environment is one thing; thus awareness of
terrorist situations and methods of control for them is not an
unreasonable action. Allowing terrorist threat to modify an
otherwise desirable and reasonable action is another. Not looking
both ways when crossing the street is simply silly. Not crossing
the street because the possiblity exists that one may be struck by a
vehicle is also silly.
J C Lawrence claw(a)kanga.nu
--=| A man is as sane as he is dangerous to his environment |=--
At 05:14 PM 3/30/2001 -0500, Robert V. MacQuarrie wrote:
>Absolutely the best mailing list manager I have ever used! Thanks!
>One feature I'd love to see added would be an option to allow new list
>members to only view archives from there joining date. For example, if
>user joins or is added on 3.30.2001 then they should only be able to view
>archives dated from that date and not before.
I fail to see why this would be at all useful. I find it's great when users
peruse the archives because it at least offers some slim hope that
the same question is not brought up again and again and again...
>[...] 3 of the discussion forms I maintain require a discussion on if said
>user should be added on not and members get to voice their opinions and
>concerns before the new user is added (if everyone agrees). I'm sure there
>could be other reasons for an option such as this aswell.
Hey -- it's ancient history... if the data is there and the new list member
wants to see it he is *going* to find a way (like ask a friend who is
also on the list but who has been there longer) ... from my experience
the best thing to do is to let everyone know that what they say will
be "on record."
IMHO this is likely to be much more trouble than it is worth.
>Again, thanks for a great list manager!
> I have 2 outstanding questions about mailman configuration options:
> 1) Does mailman have a configuration setting such that everyone who is
> subscribed to a list can post unmoderated, but email from a non-subscriber
> will be sent to a moderator for approval?
> Yes or No?
> To let some non-subscribers post without moderation (a practice that I
> personally feel has dubious value, since their question might be answered
> in a post to the list, perhaps in response to someone else asking the same
> question, but they won't see it because they aren't subscribed), how about
> implementing simple filter so that if a non-subscriber's post mentions one
> or more keywords, let it through to the list unmoderated, otherwise it goes
> to the moderator?
> Is this currently available, or not?
No (at least not without hacking SpamDetect.py or something similar)
> 2) Is [content filtering on the headers or body, to block messages that
> are in reply to an entire digest] possible with mailman? Before I move my
> majordomo list to a new server with new mailing list software (mailman is
> the software I'm considering, obviously), it is a requirement that I can
> configure that software to do the same things I can currently easily do
> with majordomo. I don't want to waste my time trying to futz around with
> installing and configuring mailman before I learn that it won't let me do
> some of the critical things I need it to do.
> Is this available, or not?
Yes. Automagically, the messages get held for moderation. With
hacking of SpamDetect.py (in this case, just adding entries to a
table), the messages can be rejected without commentary or further
Here is the error I'm recieving... any ideas?:
The original message was received at Fri, 30 Mar 2001 15:27:49 -0600
----- The following addresses had permanent fatal errors -----
"|/var/lib/mailman/mail/wrapper mailowner testing"
(expanded from: testing-admin)
----- Transcript of session follows -----
|/var/lib/mailman/mail/wrapper mailowner testing: Mailbox does not exist
550 "|/var/lib/mailman/mail/wrapper mailowner testing"... User unknown
Rich De Jong
Computer Systems Analyst
Trinity Christian College
Phone: 708.239.4828 Fax: 708.239.3989 Email: rich.dejong(a)trnty.edu
i'm positive the email is going through the new machine, cause i checked the
queue on the new machine. when i first moved everything, i cleared the queue,
so there wouldn't be any ambiguity. all of the aliases are set up correctly on
the new machine.
as far as i know, mailman is still running on the old machine... i never
turned it off, in any case.
On Fri, Mar 30, 2001 at 11:04:28AM -0800, JC Dill wrote:
> On 10:48 AM 3/30/01, Noah Cantor wrote:
> >Hi all.
> >Last night i moved my mailman files from one server to another. I made a tar
> >of all the old files, did an scp to the new machine, untarred it, added the
> >appropriate users (mailman, apache) with the same uid and gids that they had
> >previously. whe i run check_list <listname> it tells me that the list is set
> >up correctly, and that the database is working. however, when i send mail to
> >that list, it gets stuck in the mailman queue,
> Is mailman still running on the old machine? Are you SURE the email you
> are sending is going to (and being returned by) the new machine? Did you
> look at the logs of the new machine to see the mail stuck in the queue, and
> then bounced back?
> and eventually bounces back to
> >me telling me that the list doesn't exist. eventually i bandaided the problem
> >by NFS mounting the mailman directory onto the machine that it used to
> run on,
> >which solved the problem, but slowed down the mailing lists a considerable
> >amount, because now they have to go across an NFS mounted drive. what i was
> >wondering is if anybody has seen this before and has some idea of what i need
> >to do to get mailman working on the new server. personally, i suspect that
> >there's something wrong with the way apache is set up, but i can't find
> >anything wrong with it.
> >Mailman-Users maillist - Mailman-Users(a)python.org
Last night i moved my mailman files from one server to another. I made a tar
of all the old files, did an scp to the new machine, untarred it, added the
appropriate users (mailman, apache) with the same uid and gids that they had
previously. whe i run check_list <listname> it tells me that the list is set
up correctly, and that the database is working. however, when i send mail to
that list, it gets stuck in the mailman queue, and eventually bounces back to
me telling me that the list doesn't exist. eventually i bandaided the problem
by NFS mounting the mailman directory onto the machine that it used to run on,
which solved the problem, but slowed down the mailing lists a considerable
amount, because now they have to go across an NFS mounted drive. what i was
wondering is if anybody has seen this before and has some idea of what i need
to do to get mailman working on the new server. personally, i suspect that
there's something wrong with the way apache is set up, but i can't find
anything wrong with it.
To whom it may concern:
Our company is looking for a software solution to manage an e-mail
newsletter to our clients and other interested parties on a regular basis.
The letter will be fairly straight forward and go out in tens or possibly
hundreds, but certainly no bigger volume than that. We also want to be able
to manage the whole process internally once it has been set up.
Are you able to come up with a proposal in terms of price, time-line,
technical requirements etc, please?
Thanks in advance.
Online Media Consultant
53 Corsica Street
London N5 1JT
t: +44 (0)20 7354 5666
f: +44 (0)20 7354 1235
This email and any files transmitted with it are confidential and solely for
the use of the intended recipient.
Hi, how can I set Mail man to configure it under web interface !
The software is already running over SCO platform....
Thanks in advance....
Marcelo S. Bitulka
Gerente de Soporte Técnico
Unisel Argentina S.A.
First, I would like to thank all Mailman developers. It is a great piece of
software and I appreciate it. (Of course, I would also like to thank the
Academy. But that is another story entirely.)
Is Mailman I18Ned? Has French localization been written yet? The webpage does
not mention this: I have looked in the FAQ. I have also looked at the
features list and the to-do list... And in my mind, I18N belongs in one of
those two places. :-)
Any information would be greatly appreciated. Thanks again!
Lévinux: GNU/Linux dans les communautés à Lévis