Here's why I want to know:
We're getting ready to jack up our environment and drag out two (tired,
weak) machines running Solaris on SPARC, replacing them with two (strong,
healthy) Red Hat boxes, runing on Intel hardware.
Unfortunately, we're not going to swap them at the same time.
At 12:25 PM -0500 3/11/07, Steve Burling wrote:
From what I've been able to figure out, there are two parts of mailman that
are platform-dependent:
$MAILMAN_HOME/mail/mailman (the wrapper that mail is piped to)
$MAILMAN_HOME/cgi-bin/* (which get used by the web server)
That's
Hi all,
Through some finger incontinence on my part (trying to do list admin
w too late at night when I should have been in bed asleep) I have
managed to add an illegally-named user whom I now cannot unsubscribe ...
It is also possible I've discovered a bug, in which case the
--On March 11, 2007 11:34:02 AM -0500 Brad Knowles [EMAIL PROTECTED]
wrote:
That's not really platform-dependant. Mailman itself is pure Python,
so should run anywhere that Python does. These kinds of things are
installation-dependant, and if you were to install Mailman in a
different
Steve Burling wrote:
Unless I'm missing something (which is entirely possible), it's not true
that Mailman is pure Python. There is a bunch of C code in
$MAILMAN_SRC/src, which gets compiled into platform-specific executable
files. These end up as $MAILMAN_HOME/mail/mailman, and
Mike Maughan wrote:
It is also possible I've discovered a bug, in which case the circumstances
were a mass subscribe exercise where (in this case) I forgot to add a space
between the username and the email address, so the input line looked like
this User[EMAIL PROTECTED] and the list added them
On 3/8/07 10:44 PM, Herman Privyhum [EMAIL PROTECTED] wrote:
--- Brad Knowles [EMAIL PROTECTED] wrote:
I'd be willing to bet you're waiting on DNS timeouts
at the remote end for one or more of your users
-- their MTA is slowing you down, maybe as a
result of trying to do a reverse DNS
Mark Sapiro wrote:
However, I can add User[EMAIL PROTECTED] or User[EMAIL PROTECTED],
and the address User[EMAIL PROTECTED] gets added with no real name.
This too is what I would expect (I don't know if we should disallow
in an email address).
Quoted local parts are allowed in email addresses,
Mark Sapiro sent the message below at 12:41 PM 3/11/2007:
It's as I suspected. The various input tags on the Membership list look
like
INPUT name=[EMAIL PROTECTED] type=CHECKBOX value=off
where [EMAIL PROTECTED] is the email address. Clearly, if the address
contains double quotes, the field
At 1:53 PM -0500 3/11/07, Steve Burling wrote:
I apologize in advance if I'm being particular stupid about this, but the
day is fast approaching when we cut over to the new web server hardware,
and I'd rather think about this ahead of time than sit there that day,
saying, Well, sh*t,
The esteemed Barry Warsaw has said:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 27, 2007, at 10:44 PM, [EMAIL PROTECTED] wrote:
Since you guys aren't working with either Sendmail or Solaris, I think
it would be best for me to walk through and record the entire process,
and
Mailman, in its default configuration, readily integrates with a
properly-configured sendmail installation.
The discussion below gives specific file locations for a Solaris 9
installation. Solaris 10 locates the sendmail control file sources in
/etc/mail/cf rather than /usr/lib/mail/cf.
Dragon wrote:
Mark Sapiro sent the message below at 12:41 PM 3/11/2007:
It's as I suspected. The various input tags on the Membership list look
like
INPUT name=[EMAIL PROTECTED] type=CHECKBOX value=off
where [EMAIL PROTECTED] is the email address. Clearly, if the address
contains double
Mark Sapiro writes:
I understand the point about good practice, and we do try to validate
user input in Mailman to avoid possible XSS attacks via the web
interface. What we're dealing with here are syntactically validated
email addresses so the really nasty stuff has already been caught.
14 matches
Mail list logo
