David Newman wrote:
>
>Thanks, Mark. Adding '-u hostname' did the trick.
>
>I'd suggest adding this to the FAQ, which currently does not mention the
>-u switch:
>
>http://wiki.list.org/display/DOC/4.27+Securing+Mailman%27s+web+GUI+by+using+Secure+HTTP-SSL
I have updated the FAQ. Thank you.
--
M
On 2/19/11 6:57 AM, Mark Sapiro wrote:
> David Newman wrote:
>>
>> With the mm.cfg config pasted below, clicking the archives link on a
>> list page for lists.domain2.tld redirects to
>>
>> https://mail.domain1.tld/pipermail/listname
>>
>> which fails because the list name is associated with doma
David Newman wrote:
>
>With the mm.cfg config pasted below, clicking the archives link on a
>list page for lists.domain2.tld redirects to
>
>https://mail.domain1.tld/pipermail/listname
>
>which fails because the list name is associated with domain2.tld and not
>domain1.tld.
Do you mean the link p
How to configure Mailman to handle https redirects to public archives
for virtual domains?
This is for a server with a canonical name of mail.domain1.tld, and
virtual names of lists.domain2.tld, lists.domain3.tld, etc.
With the mm.cfg config pasted below, clicking the archives link on a
list page
On Friday, November 7, 2003, at 02:20 pm, Paolo De Riso wrote:
On Fri November 7 2003 14:34, Richard Barrett wrote:
It seems to work but it produce no effects on some internal links
like attachment
links.
What could I do? I thought of using $prefix/arch command as I were
regenerating
the a
On Fri November 7 2003 16:12, Pablo Chamorro C. wrote:
> I think you should consider do both, regenerate the archives and also
> enforce the https conections. Another idea is, if it's suitable for your
> users, is to install a browser like Firebird or another that doesn't show
> annoying messages
I think you should consider do both, regenerate the archives and also
enforce the https conections. Another idea is, if it's suitable for your
users, is to install a browser like Firebird or another that doesn't show
annoying messages like the ones you mention. By the way, the "saving web
forms"
On Fri November 7 2003 14:34, Richard Barrett wrote:
> >> It seems to work but it produce no effects on some internal links
> >> like attachment
> >> links.
> >> What could I do? I thought of using $prefix/arch command as I were
> >> regenerating
> >> the arch
> >> ve.
> >>
> >> What do you
Leaving the list archive as it is and using Apache module mod_rewrite
was my first try.
I used exactly the same rules the you have suggested.
But it seems not work completely. I can't modify some settings in the
administration page of the lists. Nevertheless if I didn't care about the
internal l
On Friday, November 7, 2003, at 12:14 pm, Pablo Chamorro C. wrote:
I don't know if it's enough to do it to a httpd level. I have this for
Apache:
RewriteEngine on
RewriteCond %{HTTPS} !=on
RewriteRule ^//(.*) https://%{SERVER_NAME}/mailman/$1 [R,L]
and in this way it doesn't matter if the users
I don't know if it's enough to do it to a httpd level. I have this for
Apache:
RewriteEngine on
RewriteCond %{HTTPS} !=on
RewriteRule ^//(.*) https://%{SERVER_NAME}/mailman/$1 [R,L]
and in this way it doesn't matter if the users access to http or https
pages because all Mailman pages end up bee
Hallo to everyone,
I am a newbie of mailman. During this days I read many messages from this
mailing-list before writing this.
I want to use mailman under https and use the canonical name of the site
(without www).
First of all I have added the
ollowing lines in $prefix/Mailman/mm_cfg.py:
DEFAUL
Hi,
I've recently put mailman on-line, after a week or so of testing.
I like the product alot.
This is now my first day of administering the environment from a remote
location, and I realised SSL isn't being used when entering my list admin
password.
How can I force SSL (https) connectivity for
> "NB" == Norbert Bollow <[EMAIL PROTECTED]> writes:
>> You want to run the "admin" and "admindb" cgi's using https, but all the
>> other Mailman cgi's (like listinfo) using http...
>>
>> I don't think you can do that with the current versions, at least not
>> without modifying the code. Thi
> You want to run the "admin" and "admindb" cgi's using https, but all the
> other Mailman cgi's (like listinfo) using http...
>
> I don't think you can do that with the current versions, at least not
> without modifying the code. This does seem like it would be a simple
> hack to the code though
You want to run the "admin" and "admindb" cgi's using https, but all the
other Mailman cgi's (like listinfo) using http...
I don't think you can do that with the current versions, at least not
without modifying the code. This does seem like it would be a simple
hack to the code though
Yes.
Can the links and form-actions for admin pages be reset to https without
affecting the regular list (subscribers) links? I have set apache to
redirect all '/mailman/admin/' and '/mailman/admindb/' requests to the
SSL site; but all of the built-in admin links and form actions on those
pages still p
If I go to:
https://mailman.example.com/mailman/admin/listname
the links all still work via SSL (which is good); however when I go to:
https://mailman.example.com/mailman/admindb/listname
the 'Submit' button points to the insecure (non-ssl) version; since we
deny access to the non-ssl version fro
Hi all.
We set up mailman 201 and runs all right.
Three problems:
1. Server runs as https *only*. But the email messages created from
"templates" ("welcome to.." and so on) allways show
http://url instead of
https://url .
Where is the file to change this ?
2. Server is not only https, but al
19 matches
Mail list logo
