Re: [Mailman-Users] Preventing Cross Posting

Thanks Mark for the good suggestions. I didn't think there was an easy solution besides the clue-by-four. I guess I be reading and contemplating a custom handler. -- Bryan Carbonnell - [EMAIL PROTECTED] Life's journey is not to arrive at the grave safely in a well preserved body, but rather to

[Mailman-Users] senddigests cron error.

Folks, Has anyone seen this error before? I just started receiving this error message on my list server. This is only happening to one of my lists and keeping users from receiving mail. All mails sent to the list is queued in the list/digest.mbox file. I will appreciate any feedback on this

[Mailman-Users] Uncaught bounce notification - Out-of-Office

I, as co-owner of a Mailman 2.1.9 list, received this message: Subject: Uncaught bounce notification The attached message was received as a bounce, but either the bounce format was not recognized, or no member addresses could be extracted from it. This mailing list has been

Re: [Mailman-Users] Uncaught bounce notification - Out-of-Office

On Tue, 2007-07-24 at 08:12 -0500, Barry Finkel wrote: Or is the format of the text too variable to be able to parse the OOO message? Bingo! No Standard, and even if there was one most wouldn't follow it. The 2 biggest offenders I see are Outlook/Exchange and Lotus Notes, of which neither

[Mailman-Users] Uncaught bounce notification - Out-of-Office

Barry Finkel writes: The attached message was received as a bounce, but either the bounce format was not recognized, This is the relevant case here. If the message doesn't look like an MTA bounce, it's probably a bad idea to treat it as a bounce. ML admin addresses get a fair

Re: [Mailman-Users] Uncaught bounce notification - Out-of-Office

On Tue, 24 Jul 2007, Barry Finkel wrote: Are there plans for Mailman to be able to intercept out-of-office replies and ignore them? Or is the format of the text too variable to be able to parse the OOO message? I've solved this problem locally using a procmail rule, and I think the method

[Mailman-Users] Sanity-checking individual lists for health?

Hi folks, I have been tasked with moving a Mailman 2.0.12 installation from a Solaris (SPARC) server to a Linux (x86) server. The Linux server will be receiving a copy of Mailman 2.1.9, so obviously I am making the 2.0.x - 2.1.x jump in there. Also, on Solaris, Mailman lives in /

[Mailman-Users] Unmoderated Posts Not Allowed

I have run into an odd problem with one mailing list belonging to a client. The client has many lists but we have not seen this behavior before. I have also set up a test list with them and have duplicated their settings and cannot reproduce the behavior. Details: Mailman ver. 2.1.5. Installation

Re: [Mailman-Users] senddigests cron error.

Daniel Ojo wrote: Has anyone seen this error before? I just started receiving this error message on my list server. This is only happening to one of my lists and keeping users from receiving mail. All mails sent to the list is queued in the list/digest.mbox file. I will appreciate any feedback on

Re: [Mailman-Users] Unmoderated Posts Not Allowed

Janis Neville wrote: Recently she made another announcement post to the list and it was again held for approval. We have looked through the settings in the admin panel and can find no reason why it would be held for approval. So why don't you look at the held message in the admindb interface or

Re: [Mailman-Users] Sanity-checking individual lists for health?

Chris Waltham wrote: I have been tasked with moving a Mailman 2.0.12 installation from a Solaris (SPARC) server to a Linux (x86) server. The Linux server will be receiving a copy of Mailman 2.1.9, so obviously I am making the 2.0.x - 2.1.x jump in there. Also, on Solaris, Mailman lives in /