Thomas Waters wrote:
>
>Maybe the mm_cfg.py file is not being used- or there is something
>wrong with it, so Mailman is using the default.py file.
I told you the correct way to fix this in mm_cfg.py in my first reply
to your original post. You even quoted it back in your response.
Here's the i
On Apr 13, 2006, at 1:25 PM, Brad Knowles wrote:
>
> The mm_cfg.py file should over-ride any conflicting values that
> are found in Defaults.py. That's the whole purpose of this file --
> we provide a set of defaults for you in Defaults.py, and then if
> you want anything different yo
At 9:41 AM -0400 2006-04-13, Thomas Waters wrote:
> Our mm_cfg.py file listed the correct values for Default URL and
> Default host, so I don't understand how/why the default.py file was
> 1) wrong,
It wasn't wrong. Or, at least it shouldn't have been "wrong",
since that file is only
rad,
I understand the "why" of this, but don't understand the problem or
fix to the problem.
Our mm_cfg.py file listed the correct values for Default URL and
Default host, so I don't understand how/why the default.py file was
1) wrong, and 2) over-riding the mm_cfg.py file. I guess I don't
At 5:09 PM -0400 2006-04-12, Thomas Waters wrote:
> Default.py had different values than mm_cfg.py for default url host.
> I correcterd it, and the link from the web admin is now correct and
> functioning. Thx.
You should leave Defaults.py alone, and make all your
corrections/changes
Thomas Waters wrote:
>
>I will go over all of this more thoroughly, however, I ran check
>perms and it fixed much. I also ran bin/arch and it appeared to do a
>lot. However, when I hit the archives the shown list is just the
>same as it was before running these two things.
It is likely, th
On Apr 12, 2006, at 11:36 AM, Mark Sapiro wrote:
> This latter means that if you have an incorrect value for
> DEFAULT_URL_HOST in Defaults.py, and you don't clear it in mm_cfg.py,
> you can get the incorrect host. What you want in mm_cfg.py is:
>
> DEFAULT_EMAIL_HOST = ...
> DEFAULT_URL_HOST = .
Thomas Waters <[EMAIL PROTECTED]>
Date: Wed, 12 Apr 2006 10:28:55 -0400
To: mailman-users@python.org
>I'm having two problems concerning list archives.
>
>Server: Apple XServe, OS X Server 10.4.5, Mailman 2.1.5
>
>1) In the web interface for Admin, link to list archives does not
>have co
I'm having two problems concerning list archives.
Server: Apple XServe, OS X Server 10.4.5, Mailman 2.1.5
1) In the web interface for Admin, link to list archives does not
have correct path.
I ran bin/fix_url, but that didn't fix the problem
the mm_cfg.py file lists correct default mail host a
While I have no problems accessing the archive-page of my lists this
page always states that there are currently no archives. The full
raw-archive which is donwloadable on tht same page contains all
messages like supposed.
Whats my problem or - more realistic to get an answer - where should I
sta
I just got a clue about my MailMan archiving problems in the form of an
error message traceback. Here's the key line:
OSError: [Errno 2] No such file or
directory: '/opt/mailman/archives/private/ba-b5.mbox/ba-b5.mbox'
Can anyone tell me what would be likely to cause this incorrect path to be
ge
11 matches
Mail list logo
