Daniel Griscom wrote:
>I'm using Mailman 2.1.14 on my congregation's website, hosted by
>site5.com. We use it for a couple of dozen mailing lists, and haven't
>had many troubles.
>
>Problem 1: someone noticed that all the list archives were publicly
>viewable, and even Googleable, which is a Ba
I'm using Mailman 2.1.14 on my congregation's website, hosted by
site5.com. We use it for a couple of dozen mailing lists, and haven't
had many troubles.
Problem 1: someone noticed that all the list archives were publicly
viewable, and even Googleable, which is a Bad Thing. So, I went into
th
Christopher Adams wrote:
>
>A list owner of one of our 500+ mailing lists notified me that
>postings from their non-archived list was being harvested by
>archiveorange.com and could be found via Google. I found that many of
>our lists are archived on this site, and this is not something that we
>re
Jack G F Hill wrote:
>I searched and looked, but am unable to find where the text for the
>message that is sent to a rejected moderation from a non-member
>("Non-members are not allowed to post messages to this list") is stored
>so I can change it to something a tad less cryptic.
The default
Hello all,
A list owner of one of our 500+ mailing lists notified me that
postings from their non-archived list was being harvested by
archiveorange.com and could be found via Google. I found that many of
our lists are archived on this site, and this is not something that we
really want. I am jus
I searched and looked, but am unable to find where the text for the
message that is sent to a rejected moderation from a non-member
("Non-members are not allowed to post messages to this list") is stored
so I can change it to something a tad less cryptic.
Situation:
Members of our list are als
Hi Richard Haas
On 2011-11-22 15:14, Richard Haas wrote:
< ... >
>
> The original address that led to the bounce was accepted outbound for
> delivery, and then came back about 17 seconds later, after remote
> translation of
>
> @someresearch.com to @telecdyne.com
>
> ... but cam back only once
On Tue, Nov 22, 2011 at 2:54 AM, Mark Sapiro wrote:
> Richard Haas wrote:
> >
> >Last week, we ran into a rather odd event (first time we've seen it in a
> >decade or so of Mailman ops), where a bounced message kept writing to its
> >/var/mailman/data/bounce-events-PID.pck file, until it filled t
