Using v1.1 (the sys admin refuses to upgrade!)...
How can I defeat whatever it is that logs the list
administrator off after a period of no activity?
Thanks.
--
Mailman-Users mailing list
[EMAIL PROTECTED]
We are using mailman version 2.1.2.
It works good, but I have a question to the part of
Archives
The official layout of an archive page of a given list
hasn't any interface for looking for any strings in
archived emails.
I only sea the web tables of archived months/years, where
I can
Hi,
Under the Privacy Options one can list the people not on a list that are
allowed to post to that list. Does the list support globbing eg
[EMAIL PROTECTED]
Thanx,
-jose-
--
Mailman-Users mailing list
[EMAIL PROTECTED]
Hi
mailman 2.1.2
figured out how to globally add mailman script alias so each domain can get
to lists.domainX.com/mailman/ but pipermail always seems to use
default_url_host as the lists.domain.com to access pipermail. So the link
List_Archives is always lists.domain.com/pipermail/listname not
I'm new to Mailman and I'm having a major problem getting it to start.
I had it setup and working and then I needed to reboot the server for a
kernel upgrade.
Now when I start mailman it causes python to burn 100% CPU until mailman
is stopped.
logs show nothing out of the ordinary.
Mailman users,
I'm in the process of writing documentation geared to newbie's looking to
install an all-in-one server with RH 7.3 as the base. You can find more at
www.pfohlsolutions.com/projects/server/. I wanted the latest version of
Mailman so I packaged the rpm to work with a standard install
I searched all the archives and FAQ.
Has anyone solved the problem of getting Mailman 2.1 to run in a Virtual
Host with Apache 1.3 suEXEC?
Would it work to create a second Name-Based VirtualHost (mailman.domain.tld)
for each IP-Based Domain (www.domain.tld) with the VirtualHost User.Group
I don't think those errors mean too much (unless you upgraded and it
hasn't finished the upgrade...)
If your MTA is Postfix, be sure that you have followed all the advise in
the README.POSTFIX file. Specifically make sure that local bounces are
not set to a 4xx error code (which means retry and
Hello!
On Mit, Sep 10, 2003 at 02:35:49 -0700, Merle Reine wrote:
I am looking for the best way to backup all of mailman. I am using the
following script but is there a built in utility to do this? I am using
SuSe Open Exchange 4 with mailman.
Take a look into the mailman FAQ, AFAIk there
Hello:
I'm a developer/sysadmin at a catalog retailer. My employer sends
regular e-mail marketing campaigns to its clients (not a traditional
mailing list, but bulk advertising mail -- strictly opt-in, btw!). They
are too cheap to implement an enterprise e-mail marketing system so at the
I think I have the problem solved. Acting on a hunch from what Jon Carns
said about the postfix configuration I completely stopped postfix and
restarted it.
Previously I had simply done a postfix reload.
Just for the benefit of anyone reading this thread in the future, I
believe the setting that
On Thu, 2003-09-11 at 16:47, John Lange wrote:
my recommendation would be that mailman should report a
failed connection attempt to localhost as a serious problem and log it
in syslog, or at the very minimum it's own logs. quietly burning 100%
CPU should not be acceptable.
Quite right!
After creating the mailman list under mailman 2.1-8
on a Redhat Linux 9 system,
I find that when I try to access
http://$server/mailman/admin/mailman
it reverts back to
http://$server/mailman/admin
so I cannot edit the mailman list options.
Could I be missing an entry in the mm_cfg.py
./newlist mailman
Returns:
START QUOTE
[EMAIL PROTECTED]:/usr/local/mailman/bin$ ./newlist mailman
Enter the email of the person running the list: mailman-owner
Initial mailman-system password:
Create a new, unpopulated mailing list.
Run check_perms from ~mailman/bin/
On Thu, 2003-09-11 at 18:08, Cody Harris wrote:
./newlist mailman
Returns:
START QUOTE
[EMAIL PROTECTED]:/usr/local/mailman/bin$ ./newlist mailman
Enter the email of the person running the
[EMAIL PROTECTED]:~$ /usr/local/mailman/bin/check_perms
No problems found
[EMAIL PROTECTED]:~$
My $PREFIX is /usr/local/mailman/
On Thursday 11 September 2003 7:26 pm, you wrote:
Run check_perms from ~mailman/bin/
On Thu, 2003-09-11 at 18:08, Cody Harris wrote:
./newlist mailman
Hi,
Cody Harris wrote:
./newlist mailman
Returns:
START QUOTE
[EMAIL PROTECTED]:/usr/local/mailman/bin$ ./newlist mailman
Enter the email of the person running the list: mailman-owner
You must enter non-mailman mailbox with
It was suggested to me it would be nice to show the number of members
on the listinfo page. Getting that number was easy - I just created this
cron job:
$prefix /mailman/bin/list_members listname | wc -l
../var/www/html/mmcount/listname.html
The hard part was finding a way to
If we turn on VERP, how is mail to the unqualified -bounces@
address processed? Is it ignored?
At the moment we are frequently getting subscriptions disabled
on the webdav.org lists (which don't use VERP) by stray SoBig
bounces using a real subscriber as the return address and
-bounces@ as the
I have been told that messages cannot be edited/deleted once posted. Is
this true?
I cannot find instructions about this in the Discussion mailing list
administration
Archiving Options Section either.
Janos Abel
pp
globaljusticemovement.net
--
Is there a complete list of those MM tags for designing a template? Thanks.
Danny
-
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
--
Mailman-Users mailing list
[EMAIL
Hi,
I have the same problem of
*/*/You are not authorized to create new mailing lists/*/*
Did you find out why?
Cheers
Jong
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
I have been using Mailman successfully for 2 years now.
We are currently having a problem: Not all posts are going though. They
are not being held up for any rule violations (like size, sender,
etc). All the posts go directly into the archives, but MANY do not get
sent out as email (but some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul F. Williams wrote:
After creating the mailman list under mailman 2.1-8
on a Redhat Linux 9 system,
I find that when I try to access
http://$server/mailman/admin/mailman
it reverts back to
http://$server/mailman/admin
Do you
The order of posts shown in the author, subject and date view is NOT
the order that the post run using the next and previous links. I appears
that the next and previous always follow the thread. I assume this is a
limitation of Pipermail?
(P²-a)/(u+l) = B³/(y+e)(r-l)*y
I have full personalization on now and it seems to work fine, the to:
header is rewritten with the recipient's address. Is there a way to tell
mailman not to also include the cc: with the list address?
thanks,
Ethan
--
Mailman-Users
26 matches
Mail list logo