In news:local.mailman-d> on Sun 10 Mar, Ben Gertzfield wrote:
> > "Colin" == Colin Mackinlay <[EMAIL PROTECTED]> writes:
>
> Colin> Hi, I seem to have lost the ability to add a customised
> Colin> footer and header to messages. The FAQ says it was a
> Colin> problem in 2.0 and fix
> "Colin" == Colin Mackinlay <[EMAIL PROTECTED]> writes:
Colin> That's strange then, I only use plain text and the same
Colin> format has had a footer added to it by this list :-)
Sure. "plain text" messages can have Content-Type: headers
specifying any charset, so make sure you look
On Sun 10 Mar, Ben Gertzfield wrote:
>
> > "Colin" == Colin Mackinlay <[EMAIL PROTECTED]> writes:
>
> Colin> That's strange then, I only use plain text and the same
> Colin> format has had a footer added to it by this list :-)
>
> Sure. "plain text" messages can have Content-Type: h
At 10:59 + 3/10/2002, Colin Mackinlay wrote:
>In news:local.mailman-d> on Sun 10 Mar, Ben Gertzfield wrote:
>> > "Colin" == Colin Mackinlay <[EMAIL PROTECTED]> writes:
>>
>> Colin> Hi, I seem to have lost the ability to add a customised
>> Colin> footer and header to messages. The
Hi,
after a few more tests, I am confronted to a problem: the BounceRunner seems
to load the list in its memory when it receives a bounce (in order to
process that bounce). But it does this:
1- regardless of whether it's going to need the list or not
2- without releasing the memory afterwards
I
> "BAW" == Barry A Warsaw <[EMAIL PROTECTED]> writes:
BAW> Think of shunt as a safety net. If Mailman has a bug that
BAW> causes an uncaught exception to occur while handling the
BAW> message, it gets shuffled off to shunt, so that once the bug
BAW> is fixed, you ought to be
> "F" == Fil <[EMAIL PROTECTED]> writes:
F> I think I've got it: the French translation of
F> "This is a multi-part message in MIME format.
F> "
F> lacks the trailing linefeeds. Hence mutt (at least mutt) does
F> not detect the part of the multipart message and shows
> "BAW" == Barry A Warsaw <[EMAIL PROTECTED]> writes:
> "F" == Fil <[EMAIL PROTECTED]> writes:
F> I think I've got it: the French translation of "This is a
F> multi-part message in MIME format."
I didn't find the offending string anywhere in the current Mailman
source tree. Perhaps
> "John" == John W Baxter writes:
John> You're posting as
John> Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
John> Question for the gurus: could the upper case content type
John> description be causing problems here?
It very well could be. The problem is that *some* headers
> "BG" == Ben Gertzfield <[EMAIL PROTECTED]> writes:
> "John" == John W Baxter writes:
John> You're posting as
John> Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
John> Question for the gurus: could the upper case content type
John> description be causing problems here?
> "F" == Fil <[EMAIL PROTECTED]> writes:
F> after a few more tests, I am confronted to a problem: the
F> BounceRunner seems to load the list in its memory when it
F> receives a bounce (in order to process that bounce). But it
F> does this: 1- regardless of whether it's going
On Sat, Mar 09, 2002 at 08:30:03PM -0800, Marc MERLIN wrote:
> However, I just realized that when I prepared my updated patch that I fed to
> Barry last week, I forgot this:
>
> --- mailman-wp/Mailman/versions.py Fri Aug 17 14:40:28 2001
> +++ mailman/Mailman/versions.py Thu Sep 6 12:55:00
> "F" == Fil <[EMAIL PROTECTED]> writes:
F> Hi,
F> when you upgrade Mailman to 2.1a3 from 2.0, moderated lists
F> correctly take on the attributes
| generic_nonmember_action = Hold
| default_member_moderation = Yes
F> However the latter is valid only for NE
On my test list, which doesn't have reply-to munging enabled, if I send a
test post with a reply-to header, it doesn't make it to the list (or to
ToOutgoing for that matter)
Before I look into this deeper, is this just me?
Marc
--
Microsoft is to operating systems & security
> "BG" == Ben Gertzfield <[EMAIL PROTECTED]> writes:
BG> I'm not at all sure why this is, but on a completely fresh
BG> install of CVS mailman, even though DEFAULT_NEW_MEMBER_OPTIONS
BG> = 256, all my new list members are created with the
BG> 'moderated' flag on.
For new mem
> "MM" == Marc MERLIN <[EMAIL PROTECTED]> writes:
MM> On my test list, which doesn't have reply-to munging enabled,
MM> if I send a test post with a reply-to header, it doesn't make
MM> it to the list (or to ToOutgoing for that matter)
MM> Before I look into this deeper, is
> "BAW" == Barry A Warsaw <[EMAIL PROTECTED]> writes:
BAW> For 2) That's a valid point. Please try the following patch
BAW> (untested). I'll try to test it and if it looks good, I'll
BAW> commit this change tomorrow.
If you apply the patch, you'll also have to fix the __in
On Mon, Mar 11, 2002 at 12:49:05AM -0500, Barry A. Warsaw wrote:
>
> > "MM" == Marc MERLIN <[EMAIL PROTECTED]> writes:
>
> MM> On my test list, which doesn't have reply-to munging enabled,
> MM> if I send a test post with a reply-to header, it doesn't make
> MM> it to the list (o
> "BAW" == Barry A Warsaw <[EMAIL PROTECTED]> writes:
> "BG" == Ben Gertzfield <[EMAIL PROTECTED]> writes:
BG> I'm not at all sure why this is, but on a completely fresh
BG> install of CVS mailman, even though DEFAULT_NEW_MEMBER_OPTIONS
BG> = 256, all my new list members are c
@ Barry A. Warsaw <[EMAIL PROTECTED]> :
> For 2) That's a valid point. Please try the following patch
> (untested). I'll try to test it and if it looks good, I'll commit
> this change tomorrow.
There must be something missing:
Traceback (most recent call last):
File "/home/mailman/bin/qrunne
@ Ousmane Wilane <[EMAIL PROTECTED]> :
> > "F" == Fil <[EMAIL PROTECTED]> writes:
> F> I think I've got it: the French translation of "This is a
> F> multi-part message in MIME format."
I was wrong, sorry Ousmane.
It's something in the way the multi-part message is formed, but I can't f
21 matches
Mail list logo
