On Nov 30, 2003, at 5:54 PM, Damar Thapa, ICT Technician wrote:
I am planning to use mailman simply to inform the website update to
the members, so that the members should not be able to send mail to
the list address.
Can I do this?
yes
--
"Experience is that marvelous thing that enables you t
Hi,
I am planning to use mailman simply to inform the website update to the members, so
that the members should not be able to send mail to the list address.
Can I do this?
Regards,
Damar Thapa
ICT Technician, Kennedy School
_
-
If someone are usin more than my archives in out of law .. so please be a
simple person and write to me ok.
At 12:01 p.m. 29/11/03 -0500, you wrote:
Send Mailman-Users mailing list submissions to
[EMAIL PROTECTED]
To subscribe or unsubscribe via the World Wide Web, visit
http://m
Is 'bin/update -f' required, for an upgrade from 2.0.8 -> 2.1.3? It's not
mentioned as needed in the INSTALL or UPGRADING docs, except for 1.0 or 1.1
-> 2.0.
Morgan
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/l
Morgan Fletcher <[EMAIL PROTECTED]> writes:
> I've got a netbsd server which has a working 2.0.8 installation in
> /home/mailman. Python is 2.3. MTA is postfix. I've installed mailman
> 2.1.3 in /usr/local/mailman. The /usr/local/mailman is basically owned by
> root.mailman. I've copied the lists a
I've got a netbsd server which has a working 2.0.8 installation in
/home/mailman. Python is 2.3. MTA is postfix. I've installed mailman 2.1.3
in /usr/local/mailman. The /usr/local/mailman is basically owned by
root.mailman. I've copied the lists and archives files over to the new
tree, but I've hit
On Sun, 30 Nov 2003 12:54 , Peter Jaros <[EMAIL PROTECTED]> sent:
>
>How does one properly migrate lists from one installation of Mailman to
>another on another box? What are the permissions caveats?
>
>Could someone put this in the FAQ? The question is there, but not the
>answer...
>
>http:
My apologies if this is always asked, but I've been searching for the
answer for a while.
How does one properly migrate lists from one installation of Mailman to
another on another box? What are the permissions caveats?
Could someone put this in the FAQ? The question is there, but not the
an
Success. It's always the simple permissions issues! Considering that
most who run mailman with postfix would face this, I'm suprised that a 0 B
aliases file and db were included with the fedora rpm - it would prevent
users from getting the perms wrong on a system where you, by default,
cannot
On Sat, 29 Nov 2003 [EMAIL PROTECTED] wrote:
> RuntimeError: command failed: /usr/sbin/postalias
> /var/mailman/data/aliases (status: 1, Operation not permitted)
>
> The file perms:
>
> /var/mailman/data
> [EMAIL PROTECTED] $ ls -la
> total 64
> drwxrwsr-x2 root mailman 4096 Nov 2
At 12:22 PM + 2003/11/30, John Poltorak wrote:
Is there any alternative to running qrunner via cron?
In mailman 2.1.x, qrunner is not run via cron. The qrunner
processes are left continually running, separate from system
facilities such as cron.
I am used to Majordomo which just sends o
Is there any alternative to running qrunner via cron?
I am used to Majordomo which just sends outgoing mail straight through to
Sendmail and it gets sent out automatically as and when necessary.
Can I get Mailman to do this?
What I would like to do is avoid mail from being queued, or at least
I'm new to this list - working on a solaris install.
I struggled for a while with the same symptoms as you on 2.1.3 .
What clinched it for me was creating the list mailman - my test list only
worked after doing this.
Look at the section Create a "site-wide" mailing list in INSTALL
hth
ac
13 matches
Mail list logo
