Mark:
Is there a patch available for this?
david
On Wed, Oct 20, 2021 at 3:06 PM Mark Sapiro wrote:
>
> On 10/20/21 11:43 AM, Mark Sapiro wrote:
> > On 10/19/21 6:28 PM, Mark Sapiro wrote:
> >>
> >> Mailman 2.1.35 can be downloaded from
> >>
> >> https://launchpad.net/mailman/2.1/
> >> https://
Bill Moseley wrote:
I'd like a subscription mode where someone will receive all messages,
but when they post their message is only delivered back to them.
I'm on 2.1.4 and using the "moderate on subscription" ... thus new
subscribers are moderated initially ... but once they post a good
message,
"Tokio Kikuchi" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Use of Latin-1 character in english list is a different matter.
> If the subscribers use these character in your list, then see
> http://mail.python.org/pipermail/mailman-users/2003-February/026558.html
I don't think tha
At 01:20 AM 2/18/2003, Tokio Kikuchi wrote:
Will you please send me the offending subject line.
As to the other case, the problem you stated did not reproduce.
Tokio:
Sorry it took so long to get back to you on this ... work got kind of
hectic ...
And example of a subject line that caused the pr
man/pythonlib/email/Header.py", line 447, in
_encode_chunks
if len(chunks) >0 and chunks[-1][-1] in ' \t':
IndexError: string index out of range
"David Gibbs" <[EMAIL PROTECTED]> wrote in message
b2o3mm$mur$[EMAIL PROTECTED]">news:b2o3mm$mur$[EMAI
atching in the install dir would be OK because the installer
> doesn't seem to overwrite it in the next make install of mailman.
Ah, that didn't seem to help ... in fact, it seems to have made it somewhat
worse.
Here's what I would get BEFORE the patch ...
--
From:
"Robby Griffin" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> But wait, there's more. Mailman's wrapping the line _after_ a
> whitespace character instead of before. If you look closely, you'll see
> there's a space dangling at the end of the first line of the
"David Gibbs" <[EMAIL PROTECTED]> wrote in message
b2165s$209$[EMAIL PROTECTED]">news:b2165s$209$[EMAIL PROTECTED]...
> I've noticed some odd behavior in the latest CVS that I updated to ... the
> subject line is being treated as if it's blank.
I have been
"Nick Arnett" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> One of my list moderators accidentally approved a bit of spam to a list.
> The message that went to the subscribers contained nothing other than the
> line "/root/8e8Ta4: Permission denied" and the foo
At 08:53 PM 2/9/2003, Tokio Kikuchi wrote:
MUA developers should take care the RFC. In RFC-2822,
So, any MUA which treat the folding CR/LF as a meaningful line
separation is not RFC compliant.
I know it's weired but will take a lot of hacking because this is
caused by email package on which mailma
At 11:32 AM 2/9/2003, Robby Griffin wrote:
Didn't help ... it seems to have something to do with the length of the
subject line. A long subject gets wrapped around to the next line of the
message.
Hmm. Yes, it does. Perhaps you should have a look at RFC2822, section
2.2.3, and then try to iden
Tokio:
Didn't help ... it seems to have something to do with the length of the
subject line. A long subject gets wrapped around to the next line of the
message.
david
At 12:45 AM 2/9/2003, Tokio Kikuchi wrote:
David,
Try this patch.
Tokio
--- CookHeaders.py.orig Sun Feb 9 15:13:27 2003
++
It happens on lists with subject prefixes also.
Hmm, could you show me an example?
Here's one ...
Sensitivity:
To: [EMAIL PROTECTED]
X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001
Message-ID:
From: "Jennifer Alten"
Date: Fri, 7 Feb 2003 10:06:50 -0600
X-MIMETrack: Serialize by Router o
Tokio Kikuchi said:
>> Notice that the subject is on a seperate line.
>> This list does NOT have a prefix configured.
> Make sure your prefix is blank. Invisible space may cause this
> effect, I suspect.
It happens on lists with subject prefixes also.
david
--
"Who said I couldn't have it all?"
Folks:
I've noticed some odd behavior in the latest CVS that I updated to ... the
subject line is being treated as if it's blank.
Here's an example of a message that was processed by one of my lists ...
> Content-Type: text/plain; charset="US-ASCII"
> X-Content-Filtered-By: Mailman/MimeDel 2.1+
I recently updated to the latest CVS (based on Tokio Kikuchi's advice) to
fix some digest issues ... most things are working fine, but some messages
are coming through as attachments instead of plain text.
Any ideas why this would be?
Thanks!
david
"Rodolfo Pilas" <[EMAIL PROTECTED]> wrote in message
1042071119.1373.76.camel@localhost">news:1042071119.1373.76.camel@localhost...
> Today when I send a message to a mailinglist of users of my server I
> have the problem that the AnomySanitizer and AntiVirus scan each copy of
> message for each us
"David Gibbs" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> I sent a message to a test list and it got sent out properly ... but the
> reply-to munging isn't set to the correct host.
I just installed beta 6
6/8.11.6) with ESMTP id gB8FtLi02900
for <[EMAIL PROTECTED]>;
Sun, 8 Dec 2002 09:55:21 -0600
Message-Id: <[EMAIL PROTECTED]>
X-Sender: [EMAIL PROTECTED] (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Sun, 08 Dec 2002 09:55:17 -0600
To: [EMAIL PR
"Barry A. Warsaw" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Better yet, post it on the SF patch manager, so it doesn't get lost in
> my inbox! ;)
Ok, I posted it on sf. It's patch #563686.
david
___
Mai
At 06:54 PM 6/2/2002, Marc MERLIN wrote:
> > cvs diff -u :-)
>Mmmh, no, that'd make your patch inversed.
You sure? I just ran a diff on my patch and it looks right to me...
Line I replace has a "-" in front of it, line I replaced it with as a "+"
in front.
>Make two dirs:
>mailman-cvs mai
At 06:29 PM 6/2/2002, Barry A. Warsaw wrote:
>Better yet, post it on the SF patch manager, so it doesn't get lost in
>my inbox! ;)
Ok. What's the prescribed method of preparing a good diff?
cvs diff?
david
--
| Internet: [EMAIL PROTECTED]
| WWW: http://david.fallingrock.net
| AIM: MidrangeMan
Folks:
How does one go about contributing code?
I've made some small changes in my cvs sandbox that I think would be useful
for the core code. Do I mail them to someone (Barry?) for consideration,
post them here, what?
The mods I made are fairly simple ... when the admlogin, options, and
priva
"Barry A. Warsaw" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> | Python 2.1.1
> Try upgrading to Python 2.1.3. It should go smoothly as it's only a
> bug fix release.
Got 2.2.1 ... seems to work fine so far.
david
___
At 01:53 PM 5/25/2002, Barry A. Warsaw wrote:
>You must use at least Python 2.1 (with 2.1.3 or 2.2.1 recommended).
>Still, something's weird because unittest came with Python 2.0 IIRC.
Gah! My bad. I have two pythons installed ... python, which a 1.x, and
python2, which is 2.1.
Here's the rea
"Barry A. Warsaw" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Yup, it's part of the (in)compatibility hacks to make the email
> package work with both python2.1 and python2.2.
Ok
> Question: why did you "kill it at this point"? Did the installation
> proc
I just updated cvs and ran 'make install', and got the following error ...
make[1]: Entering directory `/root/mailman-2.1-beta/mailman/misc'
for p in email-2.0.4 JapaneseCodecs-1.4.5 KoreanCodecs-2.0.4; \
do \
gunzip -c $p.tar.gz | tar xf -; \
(cd $p ; PYTHONPATH=/usr/local/mailman/python
> I updated to CVS a few days ago and I'm now getting this:
> Traceback (most recent call last):
> File "/var/local/mailman/bin/config_list", line 270, in ?
> main()
> File "/var/local/mailman/bin/config_list", line 262, in main
> do_output(listname, outfile)
> File "/var/local/mailman/bin/config
Folks:
I just resynced my mailman sandbox, reconfigured, and got the following
message ...
configure: warning:
* Python Unicode codecs for Chinese not found.
* Chinese emails generated by or manipulated in Mailman will not
* be sent in the correct encoding and may be unreadable.
***
Folks:
I finally figured out what was causing my database error, a patch I had
applied modified the version field in the database and was causing Mailman
to not perform the necessary updates to the files.
After I got past that, I started playing around with it in earnest... and
noticed something
"Chuq Von Rospach" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> I'm sorry, but I'll take a hard line here. If you're filtering messages
THE
> WRONG WAY (using Sender instead of List-ID), then you shouldn't complain
> that it breaks because you're using a head
At 12:36 AM 5/7/2002, Barry A. Warsaw wrote:
>What happens when you do
>
> % bin/withlist list-owners
> >>> m.topics
/usr/local/mailman $bin/withlist list-owners
Loading list list-owners (unlocked)
Traceback (most recent call last):
File "bin/withlist", line 271, in ?
main()
Fi
At 08:09 PM 5/6/2002, Barry A. Warsaw wrote:
> DG> I'm trying to give MM 2.1b2 a few tests, but cannot get any of
> DG> my existing mailing lists converted (I'm just trying to
> DG> convert some test and internal lists).
>I just migrated mailman-developers to MM2.1b2 and hit the same
>
Folks:
I'm trying to give MM 2.1b2 a few tests, but cannot get any of my existing
mailing lists converted (I'm just trying to convert some test and internal
lists).
Whenever I copy the list files over from the 2.0.10 install directory, and
run bin/update -f, I get the following results ...
[roo
Ok, sorry if this question falls in the 'well duh' category, but I couldn't
find anything obvious in the docs. Since this relates to the beta, I
figured this would be the right place to post it.
I was planning on experimenting with MM 2.1b1, including converting one of
my lists over to for ex
35 matches
Mail list logo
