>> Nope, because messages are processed for the two digests in the same
>> fell swoop. I don't think it's ever come up before that you might
>> want different processing for the different digests, but that /does/
>> make sense. ("Oh, TODO, please come here for a moment")
Yup. they really serve
At 17:25 -0400 10/14/2002, Barry A. Warsaw wrote:
>CVR> What I'd like to be able to do (but can't) is allow M/A,
>CVR> t/plain and t/html, and use the lynx to defang HTML going
>CVR> into the text (but not MIME) digests. That seems the most
>CVR> reasonable set of compromises to al
Okay, looking at the headers of a personalized message. is this really
right?
Here's the problem. From points to the author. To points to me. In this
case, they're both the same, but...
If you reply -- it goes to the author.
If you reply-to-all -- it goes to the author, because nowhere in th
On Mon, 14 Oct 2002 19:58:14 -0400
Barry A Warsaw <[EMAIL PROTECTED]> wrote:
>> "JCL" == J C Lawrence <[EMAIL PROTECTED]> writes:
>> Would you like to have the Exim/TMDA/Mailman HOW-TO as a rider on
>> that, or should we tuck it in as a separate README (Barry?).
> Is the document Exim spec
> "BAW" == Barry A Warsaw <[EMAIL PROTECTED]> writes:
BAW> 2) the logs/vette message needs to be improved.
On second though, I'm inclined to just remove the log message. It was
mostly just helpful for debugging.
pep-282-ly y'rs,
-Barry
___
> "CVR" == Chuq Von Rospach <[EMAIL PROTECTED]> writes:
CVR> why is mailman sending the unsub to -request here? and
CVR> throwing it out?
Oh this is twisted! Note that this only happens when you have
admin_notify_mchanges enabled.
So, when you remove the address, the user gets a n
Okay, here we go. I added an address to one of my lists, and then
deleted it again. Here are the log entries.
plaidworks.com 99# remove_members --fromall [EMAIL PROTECTED]
User `[EMAIL PROTECTED]' removed from list: sharks.
plaidworks.com 100#
*** subscribe ***
Oct 14 20:16:13 2002 (7041) sharks
to my last. It looks like mailman is generating THREE messages to the
unsubscribe now. One to the subscriber, one to the list admin and one
-- where? I dunno. Or maybe I'm misreading the logs. but I definitely
got the one to the list owner on this latest unsubscribe, which I
didn't previous to
personalization works! Even better, it let me nail a bounce that was
being forwarded through bigfoot to a place that was stripping all
headers.
User `[EMAIL PROTECTED]' removed from list: ahl.
the bounce was coming back from:
Your message
To: [EMAIL PROTECTED]
Subject: sorry, a q
> "BAW" == Barry A Warsaw <[EMAIL PROTECTED]> writes:
BAW> Yikes. Ok, simple bug. Let me test a few things and then
BAW> check in a patch. Should be should a few minutes.
Try it now.
-Barry
___
Mailman-Developers mailing list
[EMAIL PR
Yikes. Ok, simple bug. Let me test a few things and then check in a
patch. Should be should a few minutes.
-Barry
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers
On Monday, October 14, 2002, at 06:52 PM, Barry A. Warsaw wrote:
>
> S'ok, I often forget myself. Wanna see the bald spot where I scratch
> my head too often? ;)
>
looks like mine...
Okay, updated to cvs. ran config.status. make, mailmanctl stop, make
install, mailmanctl start, and went on
> "CVR" == Chuq Von Rospach <[EMAIL PROTECTED]> writes:
CVR> On Monday, October 14, 2002, at 05:05 PM, Barry A. Warsaw
CVR> wrote:
>> But the architecture really doesn't, unfortunately.
CVR> Yeah, I had that feeling. so we'll do without HTML for the
CVR> time being. Hon
> "CVR" == Chuq Von Rospach <[EMAIL PROTECTED]> writes:
>> You know that whenever you cvs up, you should always run
>> "./config.status" to update the generated files.
CVR> hmm. I thought I had. But you're right. I went and looked,
CVR> and it's clear I didn't. oops.
S'ok,
On Monday, October 14, 2002, at 05:05 PM, Barry A. Warsaw wrote:
> But the architecture really doesn't, unfortunately.
Yeah, I had that feeling. so we'll do without HTML for the time being.
Honestly, not a huge loss, but I need functional text digests more.
("you don't always get what you wa
On Monday, October 14, 2002, at 05:11 PM, Barry A. Warsaw wrote:
> You know that whenever you cvs up, you should always run
> "./config.status" to update the generated files.
hmm. I thought I had. But you're right. I went and looked, and it's
clear I didn't. oops.
> Another thing you always
> "MM" == Marc MERLIN <[EMAIL PROTECTED]> writes:
MM> I took the document from Nigel, modified it, and gave you my
MM> version for CVS (and gave it to Nigel too) Greg took my
MM> version from your CVS and further updated it, so he has the up
MM> to date version, so feel free
> "GM" == Gustavo M <[EMAIL PROTECTED]> writes:
GM> I manage a mailing list site with mailman, and I recently had
GM> the following problem:
GM> Lets say I have a list called [EMAIL PROTECTED] with 3 members:
GM> [EMAIL PROTECTED], [EMAIL PROTECTED] and [EMAIL PROTECTED] m3
On Mon, Oct 14, 2002 at 08:18:28PM -0400, Barry A. Warsaw wrote:
>
> > "MM" == Marc MERLIN <[EMAIL PROTECTED]> writes:
>
> MM> That'd be nice, but I think Nigel is a bit too busy, I sent
> MM> him my new version too, but he never had the time to post it
> MM> on exim.org
>
> Ok.
On 11 October 2002, Marc MERLIN said:
> I've been meaning to add this:
Hmmm, good point. Hadn't thought about it because SMTP callbacks seem a
little *too* powerful to me.
I think it's more important to add something about disabling recipient
verification for 127.0.0.1 first, but I wanted to ge
> "MM" == Marc MERLIN <[EMAIL PROTECTED]> writes:
MM> That'd be nice, but I think Nigel is a bit too busy, I sent
MM> him my new version too, but he never had the time to post it
MM> on exim.org
Ok. Can you and Greg get together and agree on a new version for
Mailman's README.E
> "CVR" == Chuq Von Rospach <[EMAIL PROTECTED]> writes:
CVR> Looks like a couple of Defaults.py variables got added but
CVR> weren't added to Defaults.py on the update.
You know that whenever you cvs up, you should always run
"./config.status" to update the generated files. When ne
> "CVR" == Chuq Von Rospach <[EMAIL PROTECTED]> writes:
CVR> But it seems to me that one way to allow that but protect the
CVR> text digests was to use that lynx filtering, but only on the
CVR> content sent to the text digest. Yes, I know, another
CVR> @#$@%@#$ configuration
On Mon, Oct 14, 2002 at 07:56:47PM -0400, Barry A. Warsaw wrote:
> Speeaking of Mailman's README.EXIM, do we want to continue to
> distribute a copy of the exim.org doc, or should we zap that and just
> include a pointer to the canonical location on the web? Which, I'm
> assuming, will be http://
> "JCL" == J C Lawrence <[EMAIL PROTECTED]> writes:
JCL> Would you like to have the Exim/TMDA/Mailman HOW-TO as a
JCL> rider on that, or should we tuck it in as a separate README
JCL> (Barry?).
Is the document Exim specific, or can you write it to be somewhat
agnostic towards th
> "GW" == Greg Ward <[EMAIL PROTECTED]> writes:
GW> I've just spent the last couple of hours beating the
GW> README.EXIM document from Mailman's current CVS tree into
GW> shape. (This is derived from Nigel Metheringham's "HOWTO -
GW> Using exim and Mailman together" document
> "TK" == Tokio Kikuchi <[EMAIL PROTECTED]> writes:
TK> While testing MimeDel with i18n Japanese configuration,
TK> message delivery error occured when forwarding the filetered
TK> message to the list administrator. Here is a quick patch:
Thanks, applied.
-Barry
___
> "MS" == Mikhail Sobolev <[EMAIL PROTECTED]> writes:
MS> It's not a _problem_. It's just a feeling about a "right
MS> thing". :(
MS> What I feel is not right that the resulting _file_ is
MS> assembled from other _files_. I believe, this is not how the
MS> rest of Mail
> "CVR" == Chuq Von Rospach <[EMAIL PROTECTED]> writes:
CVR> I'm finding that if someone sends a M/A message with a plain
CVR> and an html part, it's getting processed, and I'm getting a
CVR> message going out with two t/p parts, one the original, and
CVR> one empty. Since th
On Monday, October 14, 2002, at 09:25 AM, Michael Meltzer wrote:
> unless that was a typo, that 2 months old, you might want to grab the
> latest and greatest.
god, yes. I just wish it was a typo. I updated saturday night, then
installed the update and started tweaking...
> The black list I
unless that was a typo, that 2 months old, you might want to grab the latest and
greatest.
The black list I use:
application
audio
video
model
image
White list:
text/plain
text/richtext
text/enriched
text/html
text/rfc822-headers
multipart/mixed
multipart/alternative
multipart/digest
multipart/
On Monday, October 14, 2002, at 09:00 AM, Michael Meltzer wrote:
> thier was a fix in Mimedel.py about 1 week ago with
> multipart/alternative that soulds pretty close to this bug,
> How old is the CVS update you are using?
>
8/12 -- saturday night...
--
Chuq Von Rospach, Architech
[EMAIL
thier was a fix in Mimedel.py about 1 week ago with multipart/alternative that soulds
pretty close to this bug,
How old is the CVS update you are using?
MJM
- Original Message -
From: "Chuq Von Rospach" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, October 13, 2002 3:40 PM
S
Patches item #444884, was opened at 2001-07-26 18:27
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103
Category: None
Group: None
Status: Open
Resolution: None
Priority: 7
Submitted By: Richard Barrett (ppsys)
Assigned to: Barry A. Wars
34 matches
Mail list logo
