while using ./configure command in user login it shows
error
./configure: ./config.log: Permission denied
./configure: 5: Bad file descriptor
./configure: confdefs.h: Permission denied
creating cache ./config.cache
./configure: ./config.cache: Permission denied
checking for --with-python... ./conf
On Fri, 16 Feb 2001 22:30:20 +
Mark Barratt <[EMAIL PROTECTED]> wrote:
> My users want to have plain text messages - no attachments, no
> html formatting, no 'visiting cards' and the like. But some of
> them don't know how to switch off formatting and cards. A few
> forget and send attachmen
On Fri, 16 Feb 2001, Jerry Adlersfluegel wrote:
> I have followed your instructions and (think I) have it working on my
> site. But I noticed swish-e is s l o w to index my archives. Have you or
> anyone been able to get swish++ doing the same thing? I don't see a quick
> cgi available for swish+
On Fri, 16 Feb 2001, Mark Barratt wrote:
> >"Peter Hutnick" <[EMAIL PROTECTED]> wrote
(snip)
> >It might be better just to have your MTA strip attachmnets on incoming
> >messages to the list, before Mailman ever sees them.
>
> This sounds like good advice, but it's not very meaningful to me,
> u
> None of my lists are subscription lists they are information
> lists where my boss and the other administrators are sending
> information to a preset list of users. The headers are stupid
> and confusing, there is no reason for them on these lists.
Why don't you also get similar complaints abo
I'm a new Mailman user, and a pretty non-expert Linux operator, so
Mailman is great - not half the problems I had trying to persuade
Majordomo to work (I'm sure it's a fine product in the right hands).
So here's my problem:
My users want to have plain text messages - no attachments, no html
form
>Again feel free to modify your copy. Or fork if you are so sure this
>is the right thing to do.
It's the nature of projects like this to get used in ways that the authors didn't
exactly anticipate. Often these variations can be accommodated with simple options,
which seems like a way better c
Ok; looks like my first problem was more of a bug in Solaris cron (I
suppose deny-everything-including-root-by-default is a "feature", but
hey...)
Now, the mailing list seems to be working fine, except messages are sent
out sans "From:" header (making a reply rather difficult to do easily
from th
Email is working just fine, but the archives are going to the wrong location
(the location of the previous installation). 2.0b4 was compiled to use
/usr/share/mailman while the new installation is using /var/mailman. When I
create a new list, the correct archive directories are created under
/va
I have a mailing list for which I said the archive should be private.
We have a mailing list with a public archive where the link that is given
is http://foo.com/pipermail/listname/ and that works fine. (/pipermail/ is
an alias to /var/lib/mailman/archives/public/.)
That form of URL doesn't give
>Jeez. Time for the asbestos suits.
This was not a fire storm I started but I got irritated at.
>Mr. Hillson, Ed, and others should realize that honey catches more
>flies than vinegar. And that the majority of Mailman developers
>aren't being paid for this work. Don't try to fire volunteers.
New to the list, and I come bearing questions! *grin*
I recently finished setting up Mailman for a small, non-crucial,
inter-office mailing list (a when-does-the-coffee-lady-get-here type of
thing). Everything works fine via the web interface, and I can send
mail to the host it is running on (a
On Fri, Feb 16, 2001 at 10:22:33AM -0800, Ed Lazor wrote:
> I'm not just running announcement lists, but I think I may have
> an idea on this. I believe people use Mailman for ease of use. In
> the case of announcement lists, it provides easy administration,
> easily viewable archives, and easy
>Mr. Hillson, Ed, and others should realize that honey catches more
>flies than vinegar. And that the majority of Mailman developers
>aren't being paid for this work. Don't try to fire volunteers.
>They're hard to find.
Trust me. I certainly don't want to fire anyone. I also tried to
suppres
Let me start this by saying that I am not a developer, I don't know
any of the developers, and I have no personal interest in this whole
thing.
I am sure that there are people on this list who's methods of personal
interaction are distasteful to some others on the list. I think that
this has bee
I run several lists on a server and every once in a while when I
check on the directory where mailman resides, I see that some of the
lists have their config.db and request.db owned by the Apache daemon,
while others have theirs owned by mailman.
list_1, all files owned mailman.mailman, EXCE
Jeez. Time for the asbestos suits.
Mr. Hillson, Ed, and others should realize that honey catches more
flies than vinegar. And that the majority of Mailman developers
aren't being paid for this work. Don't try to fire volunteers.
They're hard to find.
A question to Mr. Hillson and others, thou
On Feb 16, 2001 at 10:31, David Miner wrote:
>I use mailman to manage about 20 lists. I only have two (really one) wish.
> In both add_members and remove_members have an option to search ALL lists
>and remove the individual from them, rather than one at a time.
How about a script that will run
>I do disagree with Ed it is not a matter of freedom, it is a matter of
>respect, and some of you having not shown any respect for Ed and his
>opinions. He started out being very respectful of you and he had been
>very considerate until some of you started getting nasty about him
>requesting for
There are probably lots of people out there who would like to
get rid of the stupid headers. But unlike Ed Lazor, they are not
willing to take the crap you have been throwing at him.
None of my lists are subscription lists they are information
lists where my boss and the other administrators are
Craig McPherson wrote:
> I need to set up about 25 mailing lists that are all going to be
> identical to each other except for name, description, and member list.
Create a basic list with all configurations. Once you're done
/home/mailman/bin/config_list -o filename basiclist
create newslist
an
I wonder if anyone has experience of using XML
to keep info, including names and email addresses, for mailman?
I find that for long lists it is quite difficult to keep track
of who exactly the people on the list are, just from their email addresses.
--
Timothy Murphy
e-mail: [EMAIL PROTECTED]
I use mailman to manage about 20 lists. I only have two (really one) wish.
In both add_members and remove_members have an option to search ALL lists
and remove the individual from them, rather than one at a time.
Thanks for all of your hard work. It has eased mine greatly. Now I can
let other
I need to set up about 25 mailing lists that are all going to be
identical to each other except for name, description, and member list.
What would be the most efficient way to go about doing this?
Thanks for any suggestions.
--
Mailman-Users
Kedves Kat.egyház!
Szeretném ha
Válaszolnának
I wish to know the details of my last
account
[EMAIL PROTECTED]
26 matches
Mail list logo
