Hank:
Just thought I'd let you know that recent updates to Firefox and
extensions (and maybe something else) solved the problem of FF
crashing on Mm admin pages. I can again access those pages without
problems ...
Thanks for your ideas to fix it as well!
-Kenneth
jwb> Did you install a new plugin (or update one) about the time the
jwb> problem started?
No.
-Kenneth
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.py
I appreciate both Mark and Barry's informative and prompt replies.
Let me do a little more investigating ... maybe there's some conflict
with one of my FF plugins ...
Thanks for the help,
-Kenneth
--
Mailman-Users mailing list
Mailman-Users@p
I'm using firefox-1.5.0.9 on an up-to-date Kubuntu system with
mailman-2.1.5-9.
Suddenly (maybe a week or so ago), 'firefox' began and continues
*crashing* immediately after I enter the "admin page" URL for all of
my lists ...
I've searched around and found some alleged "work arounds" (removing
c
[Debian/sarge, mailman-2.1.4-5]
I swear that earlier versions (e.g., 2.1b3+) would use "https:" for
all pages when I came into an admin page using "https:". Now, the
initial page does, in fact, use SSL, but the later pages revert to
"http:".
I've changed,
DEFAULT_URL_PATTERN = 'http://%s/mai
jonc> On Thu, 2003-09-04 at 22:11, Kenneth Jacker wrote:
>> (Mailman-2.1b3+)
>>
>> I must be really stupid! Though I've used regexprs for years, I
>> can't seem to create one that will show *all* members. I thought
>> that ".*"
(Mailman-2.1b3+)
I must be really stupid! Though I've used regexprs for years, I can't
seem to create one that will show *all* members. I thought that ".*"
would work, but it doesn't.
Why do I need to use this in the "Find Member" entry box?
For some reason, sometimes I go to the membership pa
Currently, I have some Mailman mailing lists where the list email
address and the Mailman webpages are both on the same machine.
I'd like to have a couple of new lists that would use two machines.
Something like:
o Machine0
[EMAIL PROTECTED] - the list address
o Machine1
http:/
Most of the "upgrading" suggestions relate to previous, non-CVS releases.
Any different/special procedures/"gotchas" to be aware of when
upgrading from a CVS (2.1b3+) distribution?
Thanks,
-Kenneth
--
Prof Kenneth H Jacker [EMAIL PROTECTED]
Computer Science Dept www.cs.appstate.ed
fredrik> I don't want to change it's hostname. The mail.domain.tld
fredrik> is what I want it to be called. When I send mail out as
fredrik> local users it gets [EMAIL PROTECTED] And as said when I
fredrik> manually act mailman, connect to port 25 and send mail from
fredrik> [EMAIL PROTE
Mike's suggested "/etc/logrotate.d/mailman" contents is apparently
just what I needed!
Thanks to him and all the others that responded ...
-Kenneth
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailm
[RH7.3, mailman-2.0.11-1]
Looking in my /var/log/mailman directory, I see file names such as:
error
error.1
error.1.1
error.1.1.1
error.1.1.1.1
error.1.1.1.1.1
This occurs for the other error files as well (subscribe, post,
digest, ...). Also, mo
Just a quick note to thank all of those who replied to my query.
A lot of good ideas!
Once I get through final exams, I'll try your suggestions.
In addition, I'll send a summary to the mailing list.
Thanks again,
--
Prof Kenneth H Jacker [EMAIL PROTECTED]
Computer Science Dept www
This is the *third* letter I have written on the same topic. Before I
give up and return to using Majordomo for certain lists, I am trying
one last time.
Is there a way to prohibit local users (with some knowledge of
Mailman's archive directory structure and naming conventions) from
seeing the c
I posted the following a few weeks ago, but saw no responses:
|I have a hunch I'm just being dense/stupid, but I'm not sure how to
|make (at least some) list archives unreadable on the 'Mailman' host.
|
|It appears everything under ~mailman has at least `--x' permissions
|for the world/
marc> On Tue, Dec 26, 2000 at 02:11:25PM -0500, Kenneth Jacker
marc> wrote:
>> I'd like to use "config_list" to transfer list ALPHA's
>> configuration to a new list BETA. Is this the recommended
>> procedure?
>>
>>
>
I have a hunch I'm just being dense/stupid, but I'm not sure how to
make (a least some) list archives unreadable on the 'Mailman' host.
It appears everything under ~mailman has at least `--x' permissions
for the world/others and many have 'r-x' or just 'r--'.
What do I do to make certain list ar
I'd like to use "config_list" to transfer list ALPHA's configuration
to a new list BETA. Is this the recommended procedure?
1) bin/config_list -o config.ALPHA ALPHA
2) cp config.ALPHA config.BETA
3) Use an editor to change all occurrences of "ALPHA" in
"config.BETA" to "BETA"
4
18 matches
Mail list logo
