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've installed Mailman on my Linux PC.
I've compiled the source with the following options:
./configure --with-cgi-gid=mailman --with-mail-gid=mailman
When i try to create a newlist (mailman/bin/newlist) as mailman user,
the directory /mailman/admin is not created. Then I don't see the list
in my web pages.Why???
Okay, we're really close now! I've put together Mailman 2.0 release
candidate 1 and uploaded it to SourceForge. You can grab the tarball
from the file release page at
http://sourceforge.net/project/shownotes.php?release_id=14446www.list.org and www.gnu.org should be updated soon. This release
contains a bunch of bug fixes and a few local security patches. The
source code is essentially frozen, modulo any last minute show stopper
bugs. I will probably make a pass at the documentation before the
final release. Expect 2.0 final hopefully by the weekend.
Sorry to bring the subject up again, but what is the best
currently recommended way to strip mime attachments from
email before it is sent?
I have a user who gets the KAK virus about once a month and
*always* passes it on to all our friends.
I'm using 2.0beta1 on RedHat 6.2 .
sylvia nicole wrote:
> Is it possible to modify Mailman without too much work to do the following:
> 1. users can unsubscribe by email and email confirmation, without password and
> without webpage
> 2. users can subscribe by email and email confirmation, without password and
> without webpage
sub/unsub by email already works.
"no passwords" is an often-requested feature that has not yet been added.
> 3. only the admin can post to the list. List members cannot post to the list.
Read 'Details' on the last item in Privacy/General posting filters.
Is it possible to modify Mailman without too much work to do the following:
1. users can unsubscribe by email and email confirmation, without password and
2. users can subscribe by email and email confirmation, without password and
3. only the admin can post to the list. List members cannot post to the list.
Get your own FREE, personal Netscape WebMail account today at http://home.netscape.com/webmail
Three things I'd love to see implemented:
Attachment stripping, for when stupid twits send images through
the list (Yup, I know about the size limiting, it'd still be a
nice feature by itself).
The ability to put members on moderation individually, as well as
putting the whole list on moderation.
Persistant cookies, so I don't have to log into the damm
thing every time I start the browser. I look after about a
million lists (okay, thirty-ish) and logging onto every list
every morning to process the bounces is a MAJOR pain. This would
obviously be something to make optional, as it could be a
secrurity prob, but still ... it'd be nice to have the option.
Thanks to the developers for a GREAT program, BTW. I just
upgraded from 1.1 to 2.whateveritis with NO problems at all. I
was anticipating major nightmares and hiccups and it just dropped
in brilliantly. I am VERY impressed!
: gossamer(a)tertius.net.au http://www.tertius.net.au/~gossamer/
: When you reach the end of your rope, tie a knot in it and hang
: on. -- Thomas Jefferson
Suppse I set up a list so that a list so that it requires email
confirmation. A user sends mail to list-request. They get their
conformation email and then they follow the instructions. Ok... all is
good so far. Now if they try to mail list-request with an unsubscribe
command it complains about a lack of a password. The point is that the
user may not even have a password, so how do they get off the list
without using the web interface?
I have tried to migrate a medium (795 users) list from majordomo to mailman
with small success. I have tried:
- from the administrative interface I get an error, this is what I get on
the log: Note that there is not quota for mailman user
Oct 31 18:13:25 2000 (10519) Failed config.db write, retaining old state.
[Errno 122] Disk quota exceeded
Oct 31 18:13:25 2000 (10519) Delivery exception:
Oct 31 18:13:25 2000 (10519) Traceback (innermost last):
File "/home/mailman//Mailman/Handlers/HandlerAPI.py", line 82, in
func(mlist, msg, msgdata)
File "/home/mailman//Mailman/Handlers/SMTPDirect.py", line 77, in process
File "/home/mailman//Mailman/MailList.py", line 1322, in Lock
File "/home/mailman//Mailman/LockFile.py", line 266, in lock
After that I continously get errors, so I remove manually every lock and
restart the machine. From that point, /bin utilities seem to recognize the
config.db file, I am able to list members, to dump the database, and even
remove all users with remove_members. But the administrative interface
after putting the first screen of membership management (the one with
members) is not able to get another page of members.
So, I see the sync_members utility (BUG: the -a is incorrectly listed as
--a) so I try to update from the command line, everything seems to work but
it stops (I have lost the screen) but I have been able to see that the last
address had this form (Which I don't know if is legal)
asdvb+(a)asdasda.com Yes, there is a + before the @.
Could this be the reason of the clash? I did hope so... but after a try I
noticed this works...
Should I try to add this users
BTW: in the remove_members it would be nice to add an option (as in
sync_members) for not sending messages on unsubscribing.
Eduardo Jacob - Area de Ingenieria Telematica
Departamento de Electronica y Telecomunicaciones
ETSII y de IT Tel: +34 94 601 4214
UPV / EHU Fax: +34 94 601 4259
Alda Urquijo s/n E-mail: jtpjatae(a)bi.ehu.es
E-48013 - Bilbao (Spain)
PGP Key available: Send email w/subject: PGPKEY
fingerprint : D8 FA 54 49 F7 40 BA AA 09 1A 73 40 A4 26 ED BD