On 6/15/06, Mark Sapiro [EMAIL PROTECTED] wrote:
Kaushal Shriyan wrote:
I have installed Mailman-2.1.8 by reading the mailman-install.pdf, I
am done with the web server configuration, Just out of curiosity I
checked
http://www.mydomain.com/mailman
I am not getting the mailman web
Hi there,
There is a list that I run and have a slightly political situation. It
has been requested that one user on the list is faked into thinking
they are still on the list. So that they receive their own mails and the
rest of the lists mails. And the their mail can go into the archive. But
it
Mark Sapiro wrote:
Lawrence Bowie wrote:
Mark Sapiro wrote:
Did you add import japanese to bin/paths.py or was it already there?
If you added it, you also have to add it to scripts/paths.py and
cron/path.py, and for completeness, tests/paths.py if you have a
tests/ directory, but that is
Thanks for your reply Mark. The problem was that the /etc/hosts file
was set to 600 for the permissions. Resetting to 755 worked great.
Now I've run into another problem, but I've found plenty of info on
that.
Thanks again.
- Original Message -
From: Mark Sapiro [EMAIL PROTECTED]
To:
Kaushal Shriyan wrote:
When i hit http://www.mydomain.com/mailman/admin I am getting
Mailman CGI error!!!
The Mailman CGI wrapper encountered a fatal error. This entry is being
stored in your syslog:
Group mismatch error. Mailman expected the CGI
wrapper script to be executed as group nobody,
Daniel Bartlett wrote:
There is a list that I run and have a slightly political situation. It
has been requested that one user on the list is faked into thinking
they are still on the list. So that they receive their own mails and the
rest of the lists mails. And the their mail can go into the
The following recipient(s) could not be reached:
[EMAIL PROTECTED] on 6/16/2006 10:53 AM
A configuration error in the e-mail system caused the
message to bounce between two servers or to be forwarded between two
recipients. Contact your administrator.
Lawrence Bowie wrote:
Mark Sapiro wrote:
You may have a syntax error (typo) in scripts/paths.py. Try just running
python scripts.paths.py
It should exit without printing anything. If there's an error, it will
print an exception.
No exceptions.
Actually, when I added import japanese
Dickson, Paul wrote:
The following recipient(s) could not be reached:
[EMAIL PROTECTED] on 6/16/2006 10:53 AM
A configuration error in the e-mail system caused the
message to bounce between two servers or to be forwarded between two
recipients. Contact your administrator.
Assuming that encrypted e-mail is a red watch me flag in countries which
limit political freedoms, what would be the best settings for an e-mail list
to protect the participants from retribution?
My initial thoughts:
1. Private list, invite-only.
2. No archive.
3. Replace From: Name/e-mail with
Steven Clift wrote:
Assuming that encrypted e-mail is a red watch me flag in countries which
limit political freedoms, what would be the best settings for an e-mail list
to protect the participants from retribution?
My initial thoughts:
1. Private list, invite-only.
2. No archive.
3. Replace
I am setting up a mailman server, so far it working fine.
We want to simplify thing by routing all -bounces -owner
to a single email address '[EMAIL PROTECTED]'
How do we do that?
In the mail received:
From: poster
Sender: [EMAIL PROTECTED] = how can I change it
to [EMAIL PROTECTED]
Hi
Is there any way I can amend the HTML behind the page to force a field
to be made mandatory? I'm thinking of the name field - once a user
enters their options page, I would like them not to be able to leave it
until they have filled their name in. I know it could be circumvented by
just
On 16 Jun 2006, at 20:10, Thiep Duong wrote:
I am setting up a mailman server, so far it working fine.
We want to simplify thing by routing all -bounces -owner
to a single email address '[EMAIL PROTECTED]'
How do we do that?
For -owner just set what e-mail address you want in the second
Martin Dennett wrote:
Is there any way I can amend the HTML behind the page to force a field
to be made mandatory? I'm thinking of the name field - once a user
enters their options page, I would like them not to be able to leave it
until they have filled their name in. I know it could be
Mark Sapiro wrote:
Lawrence Bowie wrote:
Mark Sapiro wrote:
You may have a syntax error (typo) in scripts/paths.py. Try just running
python scripts.paths.py
It should exit without printing anything. If there's an error, it will
print an exception.
No exceptions.
Actually, when I added
Lawrence Bowie wrote:
Mark Sapiro wrote:
What does scripts/paths.py now contain?
# -*- python -*-
# Copyright (C) 1998-2003 by the Free Software Foundation, Inc.
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
I have a problem with a mailing list where out of the office regexp
matches are sometimes failing to block emails to the list due to the
Subject actually containing a line wrap. An example from the header is
this:
Subject: Re:[list] Bobby Painintheass and Susie Givingyouhell are out
Jim Popovitch wrote:
I have a problem with a mailing list where out of the office regexp
matches are sometimes failing to block emails to the list due to the
Subject actually containing a line wrap. An example from the header is
this:
Subject: Re:[list] Bobby Painintheass and Susie
19 matches
Mail list logo
