On Sat, 18 Jan 2003 15:43:06 -0500
Barry A Warsaw <[EMAIL PROTECTED]> wrote:
> I got working a prototype integration of Mailman and spambayes, and
> I'll probably be checking this into cvs when I get back . I'd
> label it as an interesting experiment, but whether it'll be useful
> remains to be s
I installed Linux 8 and it comes with mailman
but i dont know how to access this on web browser please help how to go abut
thank u,
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman F
Thanks Barry - I already got MHonArc running - just need to learn how to
customize how the screens Look. :)
Jim Hale
---
'The OS Tells The PC What To Do With Itself" - Me, 1990
---
Visit Our MIDI & Digital Audio Website at http://hale.dyndns.org
-Original Message-
From: [EMAIL PROTECTED]
On Saturday, January 18, 2003, at 10:47 PM, Bryan Fullerton wrote:
On Thursday, January 16, 2003, at 07:36 PM, Barry A. Warsaw wrote:
One of my goals for the digester was that either digest could be burst
and the individual messages would look exactly as if they had arrived
independently. Or
"Paul Kleeberg" <[EMAIL PROTECTED]> wrote in message
news:a05200f09ba4fc58a4544@[192.168.1.12]...
> A message was sent out to the subscribers with the appropriate
> subject line and list-specific header lines but this is what appeared
> in the body of the message:
>/root/hPnn4E: Permission deni
On Thursday, January 16, 2003, at 07:36 PM, Barry A. Warsaw wrote:
One of my goals for the digester was that either digest could be burst
and the individual messages would look exactly as if they had arrived
independently. Or at least, they'd be useable to do follow ups back
to the list. Maybe
Thank you all for the help on the regular expression.
Again I am probably missing the obvious but it is beyond my skill
level to decipher.
I would like only plain text messages to go out to the list,
converting non-text messages to plain text and stripping attachments.
I am not sure if that is
Hi, Barry.
Barry A. Warsaw wrote:
"BF" == Bryan Fullerton <[EMAIL PROTECTED]> writes:
BF> When I get a chance later today I'll be trying the patch Tokio
BF> Kikuchi sent to mailman-developers - hopefully it will resolve
BF> the excess headers issue.
I'm off the net at the moment
Done. Added as patch #670522
On Sat, 2003-01-18 at 12:27, Barry A. Warsaw wrote:
> > "NN" == Nathan Neulinger writes:
>
> NN> I managed to make a patch to do this based on the
> NN> "list_exploder" patch that is in the sourceforge patches area
> NN> for 2.0.
>
> NN> I've got
> "JAE" == Jeff A Earickson <[EMAIL PROTECTED]> writes:
JAE> In my study of my mailing lists today (both new in MM 2.1,
JAE> and upgraded from 2.0.13), I made the sad discovery that
JAE> generic_nonmember_action = 0
JAE> for **all** of my lists. The "bend over and take spam
> "sp" == sean pambianco <[EMAIL PROTECTED]> writes:
sp> Is there anyway to run the mailpasswds cron jobs for just one
sp> list as opposed for all lists on my mailman server?
cron/mailpasswds -l onelist
See -h for details.
-Barry
-
> "CH" == Carl Holtje <[EMAIL PROTECTED]> writes:
CH> While the power of denying a list to be specified in a BCC
CH> field is certainly undeniable, I'd like the ability to accept
CH> a post that has the list BCCd if the sender is a list member
CH> -- is this possible?
For MM2
> "JH" == Jim Hale <[EMAIL PROTECTED]> writes:
JH> I started a mailing list for 'Blinkies' and 99% of the
JH> messages that come thru are in HTML. They come thru my list
JH> just fine, but the archives are majorly ugly. Is there a way
JH> to have the HTML messages display in H
> "KW" == Kory Wheatley <[EMAIL PROTECTED]> writes:
KW> I would like to discard any email that comes from the from
KW> address "[EMAIL PROTECTED]".
In MM2.1, this is easy. Add [EMAIL PROTECTED] to your Privacy->Sender
filters->discard_these_nonmembers.
In MM2.0 the best you can do
> "NN" == Nathan Neulinger writes:
NN> I managed to make a patch to do this based on the
NN> "list_exploder" patch that is in the sourceforge patches area
NN> for 2.0.
NN> I've got a patch against 2.1 if anyone is
NN> interested. Basically lets you put:
NN> +list@th
> "EL" == Ed Leafe <[EMAIL PROTECTED]> writes:
EL> I recently received a request from a user who receives and
EL> archives the digest version of the list, and due to ISP
EL> problems he recently missed a few issues. He has used lists
EL> where you can send email to the list re
> "BF" == Bryan Fullerton <[EMAIL PROTECTED]> writes:
BF> When I get a chance later today I'll be trying the patch Tokio
BF> Kikuchi sent to mailman-developers - hopefully it will resolve
BF> the excess headers issue.
I'm off the net at the moment so I can't look at the patch, bu
> "RBP" == Richard B Pyne <[EMAIL PROTECTED]> writes:
RBP> However, the create cgi will not permit including the
RBP> @dom.ain in the list name and therefore defaults to the
RBP> default domain (which mailman appears to allow only to be the
RBP> domain listed in the PTR dns re
I don't know what the I or | or whatever that is does - I assume it
does the same thing as {0,1}. But the important difference between the
rule I use:
RewriteRule ^/(mailman[/]{0,1}){0,1}$/mailman/listinfo [L,R]
and the ones you suggested is that mine also redirects requests for /
to /m
At 14:46 18/01/2003, Greg Westin wrote:
I think what you want to do to fix this is add a carat ("^") before the
first slash:
RedirectMatch ^/mailman[/]*$ http://www.example.com/mailman/listinfo
That way, it only catches it if "/mailman" occurs at the beginning of
the string.
Personally, I use a
Can someone point me in the right direction to make a patch. I am using
Postfix virtual domains, and I need to make a patch to make newlist add
'@localhost' to the end of each entry in virtual-mailman as in:
default entry:
[EMAIL PROTECTED] mylist
needs to be:
[EMAIL PROTECTED] mylist@loc
Just in case anyone was actually thinking of using that regexp I sent,
my limited knowledge tells me that this would be a slightly better
incarnation:
RewriteRule ^/(mailman[/]{0,1}){0,1}$ /mailman/listinfo [L,R]
Greg
On Saturday, January 18, 2003, at 09:46 AM, Greg Westin wrote:
I th
I think what you want to do to fix this is add a carat ("^") before the
first slash:
RedirectMatch ^/mailman[/]*$ http://www.example.com/mailman/listinfo
That way, it only catches it if "/mailman" occurs at the beginning of
the string.
Personally, I use a little more inclusive regular express
23 matches
Mail list logo
