Mark Sapiro wrote:
>Mark Sapiro wrote:
>>
>>The problem is the upper case letters in the domain. This shouldn't
>>happen, but there may be a mailman bug. I don't see a problem in the
>>code, but there may be.
>
>
>I can duplicate the problem. I'll work up a patch. In the mean time,
>don't try to s
Mark Sapiro wrote:
>
>The problem is the upper case letters in the domain. This shouldn't
>happen, but there may be a mailman bug. I don't see a problem in the
>code, but there may be.
I can duplicate the problem. I'll work up a patch. In the mean time,
don't try to specify a new address with upp
Rick Pasotto wrote:
>On Mon, Mar 19, 2007 at 03:41:31PM -0700, Mark Sapiro wrote:
>>
>> And what is the traceback from this error in Mailman's error log.
>
>Here it is:
>
>Mar 20 12:33:53 2007 admin(13911):
>
>admin(13911): [- Mailman Version: 2.1
On Mon, Mar 19, 2007 at 03:41:31PM -0700, Mark Sapiro wrote:
> Rick Pasotto wrote:
> >
> >I tried to clone a member from the command line (something I've done
> >many times previously) but it failed with a NotAMemberError error. The
> >traceback indicated that the *new* address was the problem. Wel
Rick Pasotto wrote:
>
>I tried to clone a member from the command line (something I've done
>many times previously) but it failed with a NotAMemberError error. The
>traceback indicated that the *new* address was the problem. Well, of
>course the new address was not (yet) a member!
>
>Anyway, now wh
I'm running 2.1.9 under debian etch.
I tried to clone a member from the command line (something I've done
many times previously) but it failed with a NotAMemberError error. The
traceback indicated that the *new* address was the problem. Well, of
course the new address was not (yet) a member!
Anyw
