I would also like to see this patch as part of Mailman. I tried it and it
works just fine.
thanks,
Mentorhi,
in indymedia (http://indymedia.org) and sindominio
(http://sindomino.net) we saw the necessity to protect the admin part
of mailman (above all the password transmission) with a ssl
connec
Barry,
Recently I started shopping for some web hosting service and obviously was
looking for a web hosting service that uses mailman for mailing lists
management.
Soon realized that all of these services have installed one instance of
Mailman and serve the lists for the various domains using som
With mailman 2.1, if I used https for secure access to access the admin
site, example: https://www.alb-net.com/mailman/admin/
Clicking on one of the lists brings you do that list's login page,
and the "https" stays "https"
However, in 2.1.1, the "https" changes into "http".
Was this an intention
On Fri, 29 Mar 2002, at 09:52 -0800, John W Baxter wrote:
> >This could confuse lists owners who expect (rightfully so) to see the
> >changed footers or headers on their lists as soon as they save the
> >configuration. Should the "Submit Your Changes" button do a "bin/mailmanctl
> >restart" af
With the latest CVS, whenever list's configuration changes (i.e. new headers
or footers) a bin/mailmanctl restart is needed.
This could confuse lists owners who expect (rightfully so) to see the
changed footers or headers on their lists as soon as they save the
configuration. Should the "Submit
On Thu, 21 Mar 2002, at 12:21 -0800, Dan Mick wrote:
>
> > > Is this just me?
>
> Digests are still working on my list.
>
Same here digests are working on my lists.
However, my cron/checkdbs is not working yet. Actually, it is working in my
test installation and it isn't working in my p
The "Emergency moderation of all list traffic" check-box does not stay
checked beyond the current session. If you "Logout" and login back that the
check-box is uncheck and the red-color disappears.
--
Mentor
___
Mailman-Developers mailing list
[EMAIL
I would like to report a succesful upgrade from 2.0.8 to 2.1b1. :) Besides
for some small things, the upgrade went fine; per list options and per
subscriber options migrated all fine. Obviously, I had to create the
default site list, regenerate the aliases file, make sure that qfile/ was
empty, g
Thanks for the e-mail. I have already installed 2.1b1 in a separate
location (both version 2.0.8 and 2.1b1 working just fine). However, my
current 2.1b1 installation is a test instalation only. That's where I test
my CVSs before installing in the production location.
However, my current 2.1b1 wa
Has anyone installed 2.1b1 on top of 2.0.8? I'm tempted to do so and I
would appreciate any first hand experience.
Is this recommended or is it prefered that we install 2.1b1 in another
location and than move the 2.0.8 lists to the 2.1b1 location?
thanks,
Mentor
__
All...
Here is the error logged after I send a message to a test list on the
latest mailman CVS installation. I CVSed today's set of checkings...
The message gets stuck in qfiles/shunt directory.
--
Mentor
--
Jul 05 18:54:08 2001 (23307) Uncaught runner exception: len() of unsized ob
Here is the error I get when attempting to approve subscription Request on
"confirm+approval" list.
thanks,
Mentor
---
Mar 07 17:07:00 2001 admin(15231):
admin(15231): [- Mailman Version: 2.0.2 -]
admin(15231): [- Traceback --]
admin(
I think it is true that the "reply_goes_to_list" decides(indirectly) if the
sender's e-mail is displayed in the archives or the list e-mail addresses [as
described below]. Actually, my experiment showed that if the Reply-To:
field is present in the messages it is used to set the addresses in the
13 matches
Mail list logo