We've had several instances lately where Mailman 2.1 just dies silently and
no more mail goes out. I've resorted to putting a cron job in that
restarts mailmanctl but when that happens I get the following returned...
Shutting down Mailman's master qrunner
PID unreadable in:
Correct me if I'm wrong, but I thought that MAILMAN_SITE_LIST in
~mailman/Mailman/.. referred to a mailing list name. In this case the
mailing list name that is used as the From address for such things as
password reminders.
The list defaults to mailman. It's format is simple, simply create a
Yesterday I got reminders from lists that I am a member of,
but am not an administrator. However, the box that I
administer (for the past 3 days) didn't send out any reminder.
Does it do it automatically on the first day of the month, or rather a month after
being setup?
Also, is there a way
I suppose I may have created this problem by commenting out the
inclusion of all but from, to, cc and subject in
/mailman/handlers/ToDigest.py, but it hasn't created problems for any
other lists, or previous digests. This error message came today:
Traceback (most recent call last):
File
hi !
i want to have a htaccess file for the archive and for the page to
subscribe...
but where do i have to place this htaccess file??? i have tried in
/usr/lib/mailman/cgi-bin/
and
/var/lib/mailman/archives/public/
but without any success ...
i am using mailman 2.0.13
thanks for any help
What are your system resources while running Mailmanctl? How much
memory do you have in use? How much swap are you using? How much drive
space do you have on each volume?
And for an off-beat question: Are your archives updating properly?
On Sun, 2003-02-02 at 12:26, VLists.Net Support wrote:
VLists.Net Support [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
We've had several instances lately where Mailman 2.1 just dies silently
and
no more mail goes out. I've resorted to putting a cron job in that
restarts mailmanctl but when that happens I get the
Check out the crontab for Mailman. During the install you should have
put several entries into the cron for the local user that runs Mailman
(usually the user is mailman).
The cron entries can be found in:
~mailman/cron/crontab.in
One of these entries handles the sending out of monthly list
Would it be useful to look at the logs to see the bounces?
As an example I run a script to look for members who have been knocked
off the list by excessive bouncing...
MONTH=`date -dlast month +%b`
echo $MONTH
grep -hs disabled /home/mailman/logs/bounce.1 \
/home/mailman/logs/bounce
Any idea where this error is coming from? This error is coming from
only one list; a manual running of senddigests -l on other lists
functions perfectly. /lists/problemlist/digest.mbox appears to be
fine. Any ideas? anyone? what else should I be checking?
Traceback (most recent call last):
Greetings,
I installed Mailman with the standard install scripts and followed the
docs. Is there anything else I need to do to access the web-based admin
site for Mailman ?
What is the URL needed to access it ?
Regards,
Peter
--
Greetings Mailman,
My name is Shirley Marshall of Perfect Sites Web Design, and I have just recently
partnered with Web4Designer to host my clients' sites, and they use Mailman for their
mailing needs.
Now I've gotten the whole mailing list set up for my client, and it seems to be
functioning
I recently re-installed my Linux Mandrake 8.2 server, I had located some
data corruption in the OS Binaries. Anyway, I've been using Mailman for
quite awhile, the server has been running LM 8.1 and was upgraded to
8.2. Mailman has received several upgrades while in place on the system.
I'm
On 31/01, Barry A. Warsaw wrote:
|
| ST == Samuel Tardieu [EMAIL PROTECTED] writes:
|
| ST I was going to add this FAQ entry, but I realize that I don't
| ST have a password to do that and I have to leave for a meeting
| ST right now.
|
| Folks, remember that the FAQwiz is on the
Hello,
I have closely followed install instructions for mailman.
But when I try to send something I get this error:
[EMAIL PROTECTED]: Command died with status 8:
/usr/local/mailman/mail/mailman post mailman. Command output: Failure
to find group name mailman
Try adding this group to
On Fri, 31 Jan 2003, Simon White wrote:
SW31-Jan-03 at 14:39, Gareth Hopkins ([EMAIL PROTECTED]) wrote :
SWIs there a way to get mailman to deliver messages to the same
SW domain in one smtp connection.
SW
SWExample
SW
SW[EMAIL PROTECTED]
SW[EMAIL PROTECTED]
SW[EMAIL
I recently installed Mailman at our school. It is fantastic. Thank you
very much for a fine software package.
This morning I receive and email saying Site list is missing: mailman
Picking through the /usr/local/mailman/cron/mailpasswords script I see a
mm.cfg.MAILMAN_SITE_LIST is required.
irc.freenode.net with channel #mailman (but it seems that I'm the only person there at
the moment).
On Sat, 01 Feb 2003 07:57:18 -0500
Jim LaSalle [EMAIL PROTECTED] wrote:
Is there an IRC for users of this mail list?
--
Mailman-Users
Hello
As a lot of qmail+vpopmail+mailman users, I get the famous
Sorry,_no_mailbox_here_by_that_name._(#5.1.1) error message.
I have gathered here the 3 alias creation methods i found reading the archives, in the
hope one of a goodwill soul to help.
Here is my setup:
FreeBSD 4.7_Stable -
On Fri, 31 Jan 2003, Barry A. Warsaw wrote:
BAW
BAW SW == Simon White [EMAIL PROTECTED] writes:
BAW
BAWSW Chunking like this means that you're actually sending RCPT TO:
BAWSW based on TLD, and then only US TLDs, right? So SMTP_MAX_RCPTS
BAWSW set to 50 could mean several different
Hello!
I have a problem with setting up the language(in my case it's
Russian). I can set the Russian language through Language
Options for a particular List, but some general admin pages,
like http://www.myhost/mailman/admin (it contains the text
Welcome!
Below
In my attempts to get qmail-to-mailman.py to work with mailman_2.1/qmail/vpopmail on
FreeBSD 4.7_stable..
-All the previous softwares were installed from port tree-
---
Note, for further references:
domain.com = mydomain
ml.domain.com = virtual domain used for mailman
host.domain.com = my qmail
Hi All--
Jon Carnes wrote:
Correct me if I'm wrong, but I thought that MAILMAN_SITE_LIST in
~mailman/Mailman/.. referred to a mailing list name. In this case the
mailing list name that is used as the From address for such things as
password reminders.
The list defaults to mailman. It's
Are you remembering to setup the Virtual domains inside
~mailman/Mailman/mm_cfg.py? If Mailman does not see the virtual domain
defined in mm_cfg.py then it will only attempt local mailing via the
default domain.
On Sun, 2003-02-02 at 18:25, [EMAIL PROTECTED] wrote:
In my attempts to get
Tried that and it reported no problems. The problem definitely seems to
be in digest.mbox, although I can't see anything wrong. I renamed it
and sent a test message to create a new one, the ran cron/senddigests
-l, and it went out fine. when I moved the original mbox back it
generated the same
On Sun, 2003-02-02 at 18:32, Ivan Van Laningham wrote:
Hi All--
Jon Carnes wrote:
Correct me if I'm wrong, but I thought that MAILMAN_SITE_LIST in
~mailman/Mailman/.. referred to a mailing list name. In this case the
mailing list name that is used as the From address for such things
I've had to go into Mbox before and delete a few messages that were
gumming up the works. What I normally do is simply look at the last
message to be processed and then delete the next message from the Mbox.
At that point it normally becomes obvious what the problem with the
offending mail
Thanks. I've done that once before, and as you said, the problem was
obvious. My difficulty this time is that every message in the box went
out just fine as individual emails. There were a couple that were
content-transfer-encoding: quoted-printable, which on my old system
caused multiple
Dan,
Incidentally, as I mentioned in the first message, I cleaned up the
headers within digests by commenting out some lines in
/handlers/ToDigest.py, excluding everything but date, to, from and
subject. Is that likely to gum up the works somewhere along the line? I
suppose that breaks
Hello,
I've been using Mailman for a while now for a single, low-traffic,
low-membership list. I'm now launching a service that's going to use
mailman for quite a few more low-traffic, low-membership lists, and I'm
trying to set up some customizations for the membership and
administrative
I'm trying to install mailman-2.1 on a FreeBSD virtual private server
enviroment. I've used --with-cgi-gid, --with-username,
--with-groupname, and the DIRSETGID=: and so forth. I've successfully
gotten through the check_perms and created the newlist mailman - with
the notification message. I'm
My problem is all the ones that Mailman *isn't* knocking off the list, but
sending to me as an uncaught bounce notification, or even it's not even
going through mailman and just coming right to the list owner.
Can I get them to be marked as bad, so that Mailman will then disable them
and then
Hmmm, your best bet might be to modify your Bounce handlers so that
these errant bounces are captured by Mailman.
I would be happy to take a whack at the ones it's missing if you want to
forward them on. No guarantees, but at least I'll do no harm!
The rest of what you want will have to wait
I'm guessing that you are using Postfix as the MTA. Have you run
~mailman/bin/genaliases yet? If so, what are the rights on the files:
~mailman/data/aliases
~mailman/data/aliases.db
-rw-rw-r--1 mailman mailman 4210 Feb 1 22:52 aliases
-rw-rw-r--1 mailman mailman 12288
Dear Jon,
I've got MTA = 'Manual', so I don't think that's the problem.
Thanks
On Sunday, February 2, 2003, at 09:28 PM, Jon Carnes wrote:
I'm guessing that you are using Postfix as the MTA. Have you run
~mailman/bin/genaliases yet? If so, what are the rights on the files:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adam wrote:
Does it do it automatically on the first day of the month, or rather a
month after being setup?
The default is the first of each month. This is done via cron so you might
want to make sure your mailman crontab is setup right.
There
first of the month, and my password sending errored out again. I've
been spending some time debugging.
it boiled down to problems with some of the language codecs, the
multi-byte languages. So evidently that isn't really fixed on OS X, but
I'll deal with that later.
debugging this is tough,
Hi Paul,
It looks fine if you only have a few messages, but gets hard to scan through
when you have 50+ messages per digest. MM 2.0.x's lists were very nice.
Bob
-- Original Message
From: Paul H Byerly [EMAIL PROTECTED]
Subject: [Mailman-Users] Re: Digest Topic Lists
Date: Sat,
Hi All,
Have a situation where in the lists' folder the file 'config.db' and config.db.last'
are missing. I get this when I run the check_db command, and I get a bounce whenever I
send mail to the list.
su-2.05a$ check_db -av
List: mailman
/usr/local/mailman/lists/mailman/config.pck: okay
* Joseph Okech [EMAIL PROTECTED] [20030203 10:28]: wrote:
Hi All,
Have a situation where in the lists' folder the file 'config.db' and config.db.last'
are missing. I get this when I run the check_db command, and I get a bounce whenever
I send mail to the list.
su-2.05a$ check_db -av
40 matches
Mail list logo
