Barry Finkel wrote:
>
>The patch appears to be calling
>
> check_caller
>
>only if the group is over 99 and not 65534, and it is calling that
>routine with a different parent group. But the mail-wrapper.c code has
>
> #define LEGAL_PARENT_GROUP MAIL_GROUP
> const char* parentgroup = LE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 12, 2007, at 2:14 PM, Brad Knowles wrote:
> At 1:03 PM -0600 2/12/07, Brad Knowles wrote:
>
>> Use the latest version of 2.4.x. As you've demonstrated, the 2.5
>> stuff is not yet fully baked, and Mailman 2.1.8 and earlier are not
>> compat
Greg Sims wrote:
>
>I installed mailman on a system that is running Qmail and virtual domains.
>I sent an email to [EMAIL PROTECTED] which was rejected with the following:
>
>
>
><[EMAIL PROTECTED]>:
>
>xx.xx.xx.xx does not like recipient.
>
>Remote host said: 550 sorry, no mailbox here by that
Mark Sapiro replied to my posting about group-id mismatches, in part:
>>My questions are these:
>>
>>1) Where is this group test being made?
>In the wrapper /usr/lib/mailman/mail/mailman.
>
>...
>
>In a 'package' installation, the expected group is determined by what
>ever magic the packager has
Hi There,
I installed mailman on a system that is running Qmail and virtual domains.
The Mailman GUIs from the web and the command line seem to be working
correctly. I created a list "testing" and performed a mass subscribe of a
single email address -- mine. Membership management from the web
Thanks Mark,
indeed you found the exact problem.
A person before me installed mailman but didn't complete the task.
I re-installed with a clean setup but I didn't/don't fully understand all the
settings.
in the mm_cfg.py file the setting for public archives was set to "/pipermail/"
This unfortuna
Hi There,
I installed mailman on a system that is running Qmail and virtual domains.
The Mailman GUIs from the web and the command line seem to be working
correctly. I created a list "testing" and performed a mass subscribe of a
single email address -- mine. Membership management from the web
kamalakannan wrote:
> I have mailman 2.1.9, some of the mails stuck in shunt folder.
>these mails are not delivered even
>after using unshunt command.
That's because unshunt requeues the message in it's original queue, and
the same error occurs again because you haven't fixed the underlyi
I have mailman 2.1.9, some of the mails stuck in shunt folder.
these mails are not delivered even
after using unshunt command.
Below are the errors in mailman log.
Feb 14 13:36:46 2007 (1196) SHUNTING:
1171438347.6975739+4557e8bc5545704d99fed8f512cd2de377b05e2e
Feb 14 13:36:47 2007 (1196
