I can't get to the pending request page for a mailing list.
(My web clients just say "waiting for response" and finally give up.)
I think it is because there are too many pending requests after some
problems. (config.db is almost 10MB.)
How can I do this some other way?
I have a list that I'd like to enforce a set of headers on. In other words, each message subject must start with a certain word in order be posted. Has anybody found a way to do this? I know I can block messages with certain headers, but I want to block all messages and only allow those with the approved headers. If anybody has a great idea how to accomplish this, please pass it on ...
A quick scan of the archives and the FAQ didn't turn anything up, so I
thought I'd ask this here.
Is anyone known to be using Mailman with thttpd? If so, are there any
known gotchas or things to look out for? I can't think of a reason
why it wouldn't work, but since the Mailman docs seem to assume
Apache, I figured that it was worth asking before I went ahead and set
up a listserver using thttpd/Mailman.
I just ended up with a nasty loop... just when starting up a list.
Use Mailman 2.0.5.
Turn on the anonymous_list option, so mail seems to come from the list.
Have someone on the list have a vacation notice setup.
The notice loops... in this case up to 600 times, overnight, before I caught
Is there any way of maintaining the anonymous_list feature without the
I've turned the anonymous_list feature off, but if it can't handle vacation
notices, what's the use?
I'm running a server that hosts a few domains. I already have mailman
running for lists.mydomain.com, and it is working great.
However, now i want to give users that host domains the ability to use
lists.userdomain.com too, and each user has it's own mailman setup under his
What's the best tactic for this?
I'm using Qmail and latest Mailman.
Thanks for the info on how 2.1's "cron" works... So does it still wait until the next minute to check for messages if it isn't currently processing any, or do they get processed immediately?
Hello dear list members!
We were running mailman 2.02beta and moved to new a new server (FreeBSD
4.3-STABLE, sendmail 8.11.4 and mailman 2.03). all lists are working fine.
Whenever a members email address is wrong, e.g. bla@.bla.org or whenever a local
email adress has no mailbox qrunner tries to deliver x-times to all members,
which it has reached until the wrong email address. It obviously stops when we
delete the files in $MAILMANHOME/qfiles. But this cannot be the solution since
nobody is sitting there watching postmaster mails every second ;)
Anyway: this is very annoying since lots of members unsubscribed after this
has happened ... uhm, and: yes, we have bounce options activated on every list
with the options: "5","3","5","disable and notify me". Secound uhm: yes, I
searched the archive, but have not found anything similar.
Is this a bug in mailman 2.03 or did i make some configuration errors?
If the latter is the case, I added the servers configuration below, hope that's
not to much ...
DEFAULT_HOST_NAME = 'mailman.domain.bla'
DEFAULT_URL = 'http://mailman.domain.bla/mailman/'
MAILMAN_OWNER = 'mailman-owner(a)xxx.xxx'
PUBLIC_ARCHIVE_URL = '/pipermail'
PRIVATE_ARCHIVE_URL = '/mailman/private'
MAX_SPAWNS = 100
SMTP_MAX_RCPTS = 100
DELIVERY_MODULE = 'Sendmail'
SENDMAIL_CMD = '/usr/sbin/sendmail'
First looks up the virtusertable and maps then to aliases. All local users
have a virtusertable entry and for every domain we have we put a
@domain.bla error:nouser User unknown
We have cyrus as the local delivery agent.
VERSIONID(`$Id: generic-bsd4.4.mc,v 8.11 2001/04/04 16:26:02 mic Exp $')dnl
define(`confCW_FILE', `-o /etc/mail/sendmail.cw')dnl
define(`confAUTH_MECHANISMS',`CRAM-MD5 DIGEST-MD5 LOGIN PLAIN')dnl
R$=N $: $#local $: $1
R$=N < @ $=w . > $: $#local $: $1
Rbb + $+ < @ $=w . > $#cyrusbb $: $1
Any help would be appreciated!
Thx in advance,mic
My mailman setup, which has been running fine for months now, suddenly
stopped working on the 13th.
That is to say, I had all the directors, etc., set up in exim already,
and everything was working fine. Suddenly, it has all stopped. It seems
at first glance like an exim problem, but exim is handling all mail
fine-- including unsubscribe messages!
When I send a message to a list, I get this in /var/log/exim/mainlog:
2001-06-19 21:54:25 15CY8P-0008Sd-00 <= moacir(a)zuikis.uchicago.edu H=zuikis.uchi
cago.edu [126.96.36.199] U=moacir P=esmtp S=982 id=20010619214935.A11301@zuikis
2001-06-19 21:54:28 15CY8P-0008Sd-00 => test <test(a)mydomain.com> D=list_director
2001-06-19 21:54:28 15CY8P-0008Sd-00 Completed
It never goes from there to actually funnel the messages.
My one hint that I've already got is this:
> exim -v -bt test
user "test" for file existence test not found
deliver to test in domain mydomain.com
director = list_director, transport = list_transport
yet ~mailman/lists/test/config.db exists, which is, I think, how exim tells
if a list exists.
This has me completely stumped, and I don't even know where to look on
the mailman side of things for help. Error logs end on the 13th--the
same day the lists stopped working ;)
I upgraded from 2.0.3 to 2.0.5 and nothing changed. I made a completely
new installation of mailman (and changed the web and exim.confs
accordingly) and nothing changed. In short, and to repeat, I'm stumped.
So I have mailman 2.0.5, exim 3.22 (built Apr 10) and debian (though the
mailman install was done by hand).
I'm not a QMail user and so can't verify or confirm the truth of
this. However, we have enough performance and scalability
discussions here that it may help someone:
Subject: Qmail - huge performance increase
From: "Jason Lim" <maillist(a)jasonlim.com>
Date: Thu, 21 Jun 2001 01:45:23 +0800
Reply-To: "Jason Lim" <maillist(a)jasonlim.com>
Anyone that has followed this list knows I've been trying to boost Qmail's
outgoing mail performance greatly.
Just thought I'd let everyone know that increasing the number in the
"conf-split" drastically improves performance.
One of the problems I was having earlier was that the customer's server
had a HUGE number of emails, and even just doing "ls" in each directory in
the qmail queue directories would take ages, as there were so many
individual emails queued.
SO... by increasing conf-split to 97 (from the default of 20 something
afaik), each directory ends up only having a hundred or so files. Doing
"ls" now is far speedier.
I couldn't find any documentation anywhere stating this, so I'll share it
with you all :-)
J C Lawrence claw(a)kanga.nu
The pressure to survive and rhetoric may make strange bedfellows