At 07:45 AM 5/7/2005, Brad Knowles wrote:
At 11:49 PM -0400 2005-05-06, Larry Hansford wrote:
I got it working. I upgraded from Python 2.2.3 to Python 2.3.5
and reinstalled Mailman, and it began working.
Mailman 2.1.5 required Python 2.3, but in theory this was
supposed to be fixed
Did you copy the /home/mailman/scripts/mailman to /etc/rc.d/init.d/, and
then do chkconfig --add mailman?
Did you do a /etc/rc.d/init.d/mailman start? Did you get any errors when
you did the start?
At 07:41 PM 5/7/2005, James wrote:
Hrrm... what do I do now?
ps aux | grep qrunner
root
I installed the Mailman 2.1.6rc3, and it tested okay. But, messages sent
to previously existing lists all go to /home/mailman/files/shunt, and are
not delivered. Is this a rights problem? I ran check_perms, and it did
not find any errors.
Thanks!
Larry
At 04:57 PM 5/6/2005, Tokio Kikuchi wrote:
Larry Hansford wrote:
I installed the Mailman 2.1.6rc3, and it tested okay. But, messages
sent to previously existing lists all go to /home/mailman/files/shunt,
and are not delivered. Is this a rights problem? I ran check_perms,
and it did
My system (Red Hat 7.2, Mailman 2.1.2) has been running fine since it was
installed, until this past Thursday. It is now giving errors on the daily
senddigests command:
Cron [EMAIL PROTECTED] /usr/local/bin/python -S /home/mailman/cron/senddigests
Error Message:
Traceback (most recent call
At 11:29 AM 3/28/2003, Ben Ostrowsky wrote:
We've got about 20 lists, some of which have hundreds of subscribers, but it's
time to upgrade to 2.1.1. (We're planning to install Mailman 2.1.1 on a new
server.)
Am I doomed? Our usual Linux consultant is stumped. Suggestions welcomed.
Why would you
At 07:28 PM 3/26/2003, you wrote:
I am using Mailman V 2.0
I want to know how I can disable the need for a new subscriber to create
password. I think the subscribers are going to find it quite annoying that
they have to create a password for our newsletter. They should just have
subscribe and
that is not
available in 2.0.
If it is not manual how did you go about configuring it..
Thanks for your help..
John
-Original Message-
From: Larry Hansford [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 26, 2003 8:06 PM
To: Sullivan, John
Cc: [EMAIL PROTECTED]
Subject: Re: Disabling Passwords
At 11:06 AM 3/24/2003, Jan Banan wrote:
Hi,
Is it possible to set the default for a list to not send out a welcome
letter to new subscribers added under Membership Management - Mass
Subscription?
Under General Options, Send welcome message to newly subscribed
members?, with a yes or no
At 05:03 PM 3/24/2003, abid wrote:
I believe I installed mailman correctly, I can create a list and add member
from the shell. I can't seem to figure out how to use the webaccess. I did
as install notes told me. My data files are in /usr/local/mailman. The
user is in /home/mailman. What URL
At 02:54 PM 3/21/2003, you wrote:
Hi, I run a small (max 400) email group for a nonprofit organization. I
send emails to this group probably about 10 times weekly. I just need to
be able to upload the entire list of of email addresses, and manage that
list myself, and send emails to that
At 10:06 PM 3/2/2003, Todd wrote:
Larry Hansford wrote:
I removed the python2-2.2.2-11.7.3 that was installed by Red Hat 7.3,
downloaded the tarball
Python-2.2.2.tgz, and installed it. That corrected the problem.
Just for the archives, I run MM 2.1 on a few systems using the Red Hat 7.3
One of my servers crashed, and was restored, but Mailman doesn't run. I've
tried re-installing Mailman (v2.1.1), and it indicates that the
configuration completed with no problems. When I do 'make install' there
are a number of messages that scroll by indicating that 'import site' failed.
The message below is OBE
I removed the python2-2.2.2-11.7.3 that was installed by Red Hat 7.3,
downloaded the tarball
Python-2.2.2.tgz, and installed it. That corrected the problem.
Larry
At 04:13 PM 3/2/2003, you wrote:
One of my servers crashed, and was restored, but Mailman doesn't
I didn't see a reply to my previous post on this, so I may not have
explained it well.
I currently have a line This message was sent to %(user_delivered_to)s in
non-digest footer, which places a line on each received message that reads
This message was sent to [EMAIL PROTECTED].
I'd like to
At 09:35 AM 2/24/2003, Jeremy Butler wrote:
As a sendmail newbie, I was having too much trouble implementing Mailman's
aliasing system and so--at Keith Mastin's suggestion--I shifted over to
Postfix. I'm happy to say that that works like a charm! Thanks very much.
But it does bring up a new
I have a list with a little over 3,000 members, that I want to change to a
Newsletter-type list. To do this, I need to set the Moderate bit for each
subscribed member. Is there any way to bulk change the Moderate bit for
the entire list? I looked through the scripts in the bin directory,
Please disregard this previous post -- I forgot to look at the Web
interface for this option.
Larry
At 06:34 PM 2/22/2003, you wrote:
I have a list with a little over 3,000 members, that I want to change to a
Newsletter-type list. To do this, I need to set the Moderate bit for
each
I have added personalization to the lists, and have added a line in the
footer that shows:
This message was sent to: [EMAIL PROTECTED]
which the list members like, but they would like me to add a line that reads:
This message was sent by: [EMAIL PROTECTED]
Can someone tell me what variable I
At 07:13 AM 2/18/2003, David wrote:
On 13 Feb 2003, Jon Carnes wrote:
Some folks on the list have hypothesized that this is due to some spam
rules setup on hotmail servers (but not consistent across all their
servers).
Try modifying SMTP_MAX_RCPTS (in the file mm_cfg.py):
# Ceiling on
At 01:41 PM 2/17/2003, Lucas Albers wrote:
I keep on getting the following errors from mailman.
The permissions for that file are thus:
-rwxrwxr-x1 apache mailman 6023 Feb 14 10:03 config.pck
-rw-rw1 apache mailman 6023 Feb 14 10:03 config.pck.last
-rw-rw1
At 02:03 PM 2/17/2003, [EMAIL PROTECTED] wrote:
I have sent this in before but I guess the powers that be are NOT interested.
There is definitely something wrong with the bounce process with
regards to the Confirmation string.
The first time I reported this the problem occurred on the
At 11:08 PM 2/10/2003, Andy Firman wrote:
I have 3,000 emails I need to get into a new Mailman mailing list.
Do you think I can cut and paste into the admin membership-
management interface? I have no clue what it can handle.
I searched the archives but did not find anything similar to my
At 08:39 PM 2/8/2003, Barry A. Warsaw wrote:
I've released Mailman 2.1.1 which includes many bug fixes and language
updates. This release includes a fix for the cross-site scripting
vulnerability, a fix for the cookie problem, any many other bugs. I
recommend that all Mailman 2.1 users upgrade
and isolates the entries that
indicate a user has been moved over to no-mail due to excessive bounces.
Great, Jon! Not a big rush, but it would be a great benefit to list
owners that have large lists.
Larry
Jon Carnes
- Original Message -
From: Larry Hansford [EMAIL PROTECTED]
Thanks
I read the article in Linux Journal last night, and liked the description
of this software. But, it didn't appear from the article that it would
work with Mailman 2.1, which I'm running. The lines it adds to the aliases
are of the old format. I would love to have a capability such as the
For all lists you are subscribed to at
%(host_name)s
under the email address
%(user_delivered_to)s
your current password is
%(user_password)s
___
END OF HOW-TO SET UP PERSONALIZATION
==
On Sat, 2003-02-01 at 19:42, Larry Hansford wrote
Several weeks ago, I upgraded Mailman from v2.0.11 to v2.1, and have not
had any problems with it since. Both the users and me, as administrator,
love all the new features that became available.
However, the end-of-month cron job mailpasswds did not run.
The subject of the message is:
Cron
At 03:58 AM 2/1/2003, Matt Brown wrote:
On Saturday 01 February 2003 04:18 pm, Larry Hansford wrote:
However, the end-of-month cron job mailpasswds did not run.
The subject of the message is:
Cron mailman@ash /usr/local/bin/python -S /home/mailman/cron/mailpasswds
And, the body
Since I upgraded to Mailman 2.1, I want to add personalized messages in the
footer of messages, much like the ones that are included with this list. I
added these lines to the mm_cfg.py file, as indicated in the FAQ:
VERP_PASSWORD_REMINDERS = 1
VERP_PERSONALIZED_DELIVERIES = 1
I was running Red Hat 7.0, Postfix, and Mailman 2.0.6, and have been
running with that setup since 2.0.6 was released.
I upgraded the server to Red Hat 7.2, but did not change anything
else. After the upgrade, all of the exists lists continued to
work. However, I could no longer add new
At 09:57 PM 10/4/2001, you wrote:
I've been looking on the 'net, but the freeware I've found seems to be
mostly written for Unix or some other O/S, and requires more programming
ability than I have. I was looking at Mailman because it mentioned being
usable via a website page, and I have
I'm fairly new to Mailman, but am using V2.0.6 on a small network using Red
Hat 7.1. It has been working really good except for one minor problem with
PDF attachments. I want to be able to distribute a weekly member
newsletter to people that sign up for the Newsletter list, and the
At 02:01 PM 10/2/01, Greg Ward wrote:
On 02 October 2001, Larry Hansford said:
The problem is that in testing sending this newsletter as an PDF
attachment, Mailman sends it out as an embedded text message -- unreadable
50Kb of ASCII code.
Is there a setting that allows me to set it up
I've seen comments on this list that Postfix mail server is preferable to
Sendmail due to its improved speed and security. So, I'm thinking of
changing my Red Hat server over to Postfix.
Question: If I remove Sendmail and install Postfix, is the only thing
necessary for Mailman to re-run
At 04:19 PM 10/2/2001, J C Lawrence wrote:
On Tue, 02 Oct 2001 14:56:58 -0400
Larry Hansford [EMAIL PROTECTED] wrote:
Question: If I remove Sendmail and install Postfix, is the only
thing necessary for Mailman to re-run configure install to make
sure it has the right gid's?
If you
I wonder if someone changed rights to one of the directories so that the
files can't be read or executed. Did somebody do a recursive rights change
on the /home directory?
Larry
At 08:31 PM 10/2/2001, you wrote:
I'm using Mailman version 2.0.6 on Red Hat 7.1. It was working
fine before I
At 08:08 PM 10/2/2001, Greg Ward wrote:
On 02 October 2001, Larry Hansford said:
Thanks, Greg! The problem seems to be solved, but I'm not sure why. I
checked my Eudora setup, and all seemed well. I went into the TEST
group
admin page, and changed the setting for message size from
38 matches
Mail list logo
