> Date: Thu, 27 Nov 2014 12:06:46 -0800
> From: m...@msapiro.net
>> Is there anything else I ought to do?
>
>
> Yes. Completely uninstall the a.com/mailman instance including any cron
> jobs that run a.com/mailman/cron.* scripts.
>
>
>> Will having installed Mailman twice have caused any confusion/
On 11/27/2014 02:39 AM, Jon 1234 wrote:
>> Date: Wed, 26 Nov 2014 21:01:36 -0800
>> From: m...@msapiro.net
...
>>
>> What exactly is the situation in your case?
>
> At the very beginning I wrongly installed the files in a.com/mailman
>
> So the aliases are:
>
> ScriptAlias /mailman/ /path/a_com
> Date: Wed, 26 Nov 2014 21:01:36 -0800
> From: m...@msapiro.net
>
>> I currently have Mailman 2.1.14 installed in the website directory of a.com
>
>
> What does this mean? Normally, Mailman is installed in it's own
> directory or directories which are not in the space served by default by
> the
On 11/26/2014 08:05 AM, Jon 1234 wrote:
> I currently have Mailman 2.1.14 installed in the website directory of a.com
What does this mean? Normally, Mailman is installed in it's own
directory or directories which are not in the space served by default by
the web server. Then Mailman's CGI wrapper
I currently have Mailman 2.1.14 installed in the website directory of a.com
I would like to:
1. Upgrade it to 2.1.18-1.2. Have it outside the website directory.3. Use it
not only for a.com but also b.com (I will not need to have the same list names
for both domains).
If I were to install from scr
