Maybe I'm getting old or just more rushed by the rest of the world
these days, but without really digging into root cause, I can offer
a suggestion that may help prevent this type of event in the future.
In your wwbnews.config file, try something like this;
> # message_headers [string_array] (undef) <resend,digest>
> # These headers will be appended to the headers of the posted
> # message. The text is expanded before being used. The following
> # expansion tokens are defined: $LIST - the name of the current
> # list, $SENDER - the sender as taken from the from line, $VERSION,
> # the version of majordomo.
> message_headers << END
> X-Mailing-List: $LIST
> List-ID: $LIST mailing list <$LIST.lists.example.com>
> List-Help: <mailto:majordomo@example.com?body=help>
> List-Subscribe: <mailto:majordomo@example.com?body=subscribe%20$LIST>
> List-Unsubscribe: <mailto:majordomo@example.com?body=unsubscribe%20$LIST>
> List-Post: <mailto:$LIST@example.com>
> List-Owner: <mailto:$LIST-owner@example.com>
> List-Archive: <mailto:majordomo@example.com?body=index%20$LIST>
> END
Take or toss any of the above custom header lines, but if you keep at
least the List-ID: or X-Mailing-List: line, you can do this, assuming
the list's name is "test";
> # taboo_headers [regexp_array] (undef) <resend>
> # If any of the headers matches one of these regexps, then the
> # message will be bounced for review.
> taboo_headers << END
> /^X-Mailing-List: test/i
> /^List-ID:.*test\.lists\.example\.com/i
> END
Dan Liston
Stewart Dean wrote:
> Thanks for the quick comeback Dan!...I'll interleave my answer with your
> questions
>
> Daniel Liston wrote:
>
>> I am curious as to your sendmail settings (aliases|virtusertable)
References:
|
|
