I've continued to fiddle with this and now have different errors, so I thought
I would back up and give ya'll the big picture in case I'm approaching this
from the wrong direction. Tuesday morning I had a hardware failure on my old
Solaris 10 box. In 25 years in the business, I don't think
On 1/19/2011 3:35 PM, C Nulk wrote:
So the question is, should the listnames in the *_these_nonmembers
fields be all lowercase, all uppercase, or mixed case? So far, mixed
case does not appear to be working.
The list name in @listname entries in *_these_nonmembers must be the
internal
Here's some more information:
At step 3.1 of the installation instructions, the ./configure step appears to
run to completion, but then ends with a warning: can't change build.
I don't get this when I run as root, but the instructions pretty clearly say
that I should not be root when I run it.
Scott Race wrote:
Ah, I see what's going on. So for the particular lists were working on, all
messages to the list are held for moderation. So, it seems clicking Accept
will accept the message, even if the message size is too big.
Yes, and further, if the messages are held because the poster
Is this a fatal error for the ./configure step?
checking for --with-mailhost... no
checking for --with-urlhost... no
Traceback (most recent call last):
File conftest.py, line 2, in module
from socket import *
File /usr/local/lib/python2.6/socket.py, line 46, in module
import _socket
If I continue to make install I get the following error:
.././install-sh -c -m 755 mailman /usr/local/mailman/scripts
.././install-sh -c -m 644 sitelist.cfg /usr/local/mailman/data
for p in email-2.5.8 JapaneseCodecs-1.4.11 KoreanCodecs-2.0.5; \
do \
gunzip -c ./$p.tar.gz | (cd . ; tar xf -);
McNutt Jr, William R wrote:
If I continue to make install I get the following error:
.././install-sh -c -m 755 mailman /usr/local/mailman/scripts
.././install-sh -c -m 644 sitelist.cfg /usr/local/mailman/data
for p in email-2.5.8 JapaneseCodecs-1.4.11 KoreanCodecs-2.0.5; \
do \
gunzip -c
Richard Damon wrote:
The question comes in that the CentOS 5 distribution only has a RPM
for Mailman 2.1.9, instead of the recently released 2.1.14, so the
question comes do I use the RPM from the distribution and run a
version several years old, or is it better to install from a direct
download.
by the way, I keep deleting the following:
/var/spool/mailman/bounces/*.pck
/var/lib/mailman/data/*.pck
because they fill up all the space on my small hard drives on my VPS
servers.. is that why mailman's bounce processor removes the subscribers or
because they does actually bounce until they
Hi,
I'd like to use Mailman for a distribution list and would prefer that
the from address be of the form Foo Bar foo...@list.org ... rather
than just foo...@list.org. Is this possible? How do I need to input
this in the configuration?
Thanks
Khalil Abbas wrote:
by the way, I keep deleting the following:
/var/spool/mailman/bounces/*.pck
It looks like BounceRunner has died and is not processing the bounce
queue. Chack Mailman's qrunner and error logs for more information.
/var/lib/mailman/data/*.pck
Are these
I'm continuing to try various combinations but without any luck.
Don't see this documented either. Any ideas or confirmation that this
is not possible would really help. Thanks!
On Thu, Jan 20, 2011 at 11:23 AM, Stefan Alder twigbra...@gmail.com wrote:
Hi,
I'd like to use Mailman for a
Stefan Alder wrote:
I'm continuing to try various combinations but without any luck.
Don't see this documented either. Any ideas or confirmation that this
is not possible would really help. Thanks!
On Thu, Jan 20, 2011 at 11:23 AM, Stefan Alder twigbra...@gmail.com wrote:
Hi,
I'd like to use
Scott Race wrote:
A few final questions to figure this out:
1. Has this always been the design? The client seems to think that on his
old server the message would get kicked back before hitting the moderation
queue. If so that's cool, just want to make sure I'm not missing something.
I
14 matches
Mail list logo
