Anne Ramey wrote:
>
>Mark Sapiro wrote:
>>
>> Well then is your site list named 'mailman-admin' (I assumed it was
>> 'mailman')?
>>
>No, it's names mailman. I can only assume the admin address is left
>over after upgrade.
I've looked more deeply and found it is a bug in pre-Mailman 2.1.6
bin
Mark Sapiro wrote:
> Anne Ramey wrote:
>
>> Mark Sapiro wrote:
>>
>>
> Please address all questions to [EMAIL PROTECTED]
>
>>> This makes no sense. It shouldn't be -admin because that's a Mailman
>>> 2.0.x artifact, but the 'mailman' site list di
Anne Ramey wrote:
>
>Mark Sapiro wrote:
>
>>> >
>>> >Please address all questions to [EMAIL PROTECTED]
>>>
>> This makes no sense. It shouldn't be -admin because that's a Mailman
>> 2.0.x artifact, but the 'mailman' site list didn't appear until 2.1.
>>
>You are incorrect. That is not a ty
Mark Sapiro wrote:
>> >
>> >Please address all questions to [EMAIL PROTECTED]
>>
> This makes no sense. It shouldn't be -admin because that's a Mailman
> 2.0.x artifact, but the 'mailman' site list didn't appear until 2.1.
>
> Assuming this is a typo and is really [EMAIL PROTECTED], I
> proc
Anne Ramey wrote:
>Not too long ago, we switched out domain from wwwadm.mydomain.com to
>lists.mydomain.com. I used fix-url on all the lists, and when we create
>all lists now, we create then as
>./newlist [EMAIL PROTECTED]
>
>
>you can get info about using it by sending a message
>with just t
Not too long ago, we switched out domain from wwwadm.mydomain.com to
lists.mydomain.com. I used fix-url on all the lists, and when we create
all lists now, we create then as
./newlist [EMAIL PROTECTED]
But when the email is sent to the administrator for these new lists it
has wwwadm.mydomain.c
