Mark Pallo wrote:
>
>Under the menu path of Membership Management...[Membership List] I am trying
>to enter a search string which will return the entire list of my members
>when using Find member (help):
>
>Can someone provide me with the proper search string? I am using 2.1.5.
>
Lots of patterns
Anne Shroeder wrote:
>I recall at one point some list members saying that it was not good to put
>one list as a member of another list. One of my colleagues has done this
>and insists that it is easier for him because this way he doesn't have to
>manage duplicate names (where names intersect list
On Oct 3, 2004, at 19:22, Heiner Lamprecht wrote:
P.S.: Is there any way to limit a list to one domain? I don't
need to have multiple lists with the same name but for
different domains. But I don't like the idea, that one can
post to one list, using every domain of the server ...
That is a functi
At 7:25 PM +0200 2004-10-02, Richard wrote:
It seems spamers can easily collect email addresses from the "user at
domain.com" text on archive web pages. It seems this is what happens even
with the latest version available. (Please correct me if I am wrong).
If this is your list, you're free to
Hi,
But the difference between public and private archives still exists.
If I define a list as being private, the link from the
listinfo-page is pointing to the correct domain the list belongs
to. As soon as I switch the list to public, the link changes to
the base name of the server (DEFAULT
On Thursday 30 September 2004 07:51, Jim Tittsler wrote:
> On Sep 29, 2004, at 04:25, Heiner Lamprecht wrote:
> > [...] And when I want to see the archive, I
> > only get "Access denied" (no matter, what domain I use).
> > Apache log says:
> >
> > "client denied by server
> > configuration: /var/l
On Oct 3, 2004, at 00:48, p e y t o n wrote:
"|/public_html/mailman/mail/mailman post test"
(reason: 1)
(expanded from: <[EMAIL PROTECTED] HIDDEN>)
- Transcript of session follows -
post script, list not found: test
554 5.3.0 unknown mailer error 1
"post script, list not found: t
On Oct 2, 2004, at 04:31, Mark Koitmaa wrote:
Is there a way to temporarily or permanently force mailman to use the
message date rather than the server date for new posts?
ARCHIVER_CLOBBER_DATE_POLICY = 0
in your mm_cfg.py will tell Pipermail to use the original Date: header.
--
Jim Tittsler
