Noel,
Thanks for the quick reply. I tracked down the problem.
In processor "root" I had:
<mailet match="RemoteAddrInNetwork=127.0.0.1" class="ToProcessor">
<processor> transport </processor>
</mailet>
before the list-handling code. I solved the problem by moving the
list-handling code from the "root" processor to the "transport" processor. [just my 2
cents] I think we should do this by
default.
The reason I had "RemoteAddrInNetwork=127.0.0.1" in the root processor is
because I'm experiencing slow spooling problems with the spammer-blacklist so I wanted
to bypass it for local
to local mail deliveries. It is for this same reason I suggest we move all
mail-delivery code (mailing lists included) into "transport" instead of handling it in
"root".
Anyway, thanks again for your help! I hope to resolve my spammer-blacklist
problem soon. It is the last problem I've got left to solve.
Thanks,
Gili
On Sun, 19 Oct 2003 21:42:10 -0400, Noel J. Bergman wrote:
>> I configured a mailing list in the latest nightly build and
>> sent an email to a list I was not a member on. It replied
>> with the following text:
>> To subscribe to the list, send a message to:
>> <[EMAIL PROTECTED]>
>Seems correct.
>> But when I email "soen-subscribe", the mail gets dumped due
>> to "local-address-error".
>Enable DEBUG for the spoolmanager, and watch the message flow. See why the
>message is not going to CommandListservManager.
> --- Noel
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
