On 8/13/07, Thomas Anderson wrote:
> I want to enable piping in /etc/aliases. GNU/Debian Etch has piping
> disabled by default and that makes Mailman not work with Exim4.
This is a Debian/Etch or Exim problem, and has nothing to do with
Mailman, except that Mailman gets caught by the fallout.
On 8/13/07, Brian Carpenter wrote:
> I have a client who has some members that use a translation software to
> translate list messages. The client has the list configured to convert html
> to plain text. However certain characters still make it through the
> conversion process:
The actual con
On 8/13/07, Chris Waltham wrote:
> Is there a relatively straightforward mechanism to protecting list
> archives from prying eyes? From what I can tell, anyone that can
> guess the URL of the archives (e.g. www.foo.org/pipermail/listname)
> can view the archives of the list, even if they're no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I want to enable piping in /etc/aliases. GNU/Debian Etch has piping
disabled by default and that makes Mailman not work with Exim4.
- --
Regards,
Thomas Anderson
"Quidquid latine dictum sit, altum sonatur"
OpenPGP fingerprint: ED7E 1E98 225A 3FCC 45
Hi All:
I have a client who has some members that use a translation software to
translate list messages. The client has the list configured to convert html
to plain text. However certain characters still make it through the
conversion process:
<
>
"
Is this normal or is there a mis-co
Is there a relatively straightforward mechanism to protecting list
archives from prying eyes? From what I can tell, anyone that can
guess the URL of the archives (e.g. www.foo.org/pipermail/listname)
can view the archives of the list, even if they're not a subscriber
to the list.
Rather th
It doesn't really matter if the list name is in any particular case,
but I'd like the DEFAULT_SUBJECT_PREFIX
to keep the original case of the list name. Because we have
lists named after course names, it would look a little odd for
only the first char to be upper case (e.g. [Srmk4563a1] rather tha
