[EMAIL PROTECTED] wrote:
>
>I'm using Mailman 2.1.9. I've been getting reports from list owners of
>lots of unexplained automated unsubscribes. While browsing trough
>/logs/smtp-failure to look for clues, I came across many entries like
>this:
>
>Nov 09 09:31:48 2006 (2293) delivery to [EMAIL PROTE
I'm using Mailman 2.1.9. I've been getting reports from list owners of
lots of unexplained automated unsubscribes. While browsing trough
/logs/smtp-failure to look for clues, I came across many entries like
this:
Nov 09 09:31:48 2006 (2293) delivery to [EMAIL PROTECTED] failed
with code 501: Bad r
I wrote:
> Tokio Kikuchi wrote:
[...]
>> But as to the default charset is 'us-ascii' problem, if we put the
>> part together the parts, some language text (like japanese) become
>> irreversibly unreadable. It is safe to keep it in a separate file
>> if you can't archive the whole message in multip
Tokio Kikuchi wrote:
> Folks,
>
> I'm OK with changing the recomposing part in Scrubber.py:
>
> if not part or part.is_multipart():
> continue
>
> to
>
> if part.is_multipart():
> continue
>
> It looks like the email package is more robust than it was when the
> bug report was issued
Mark Sapiro wrote:
> Todd Zullinger wrote:
[...]
>>Poking in the email package (on python 2.4.4) shows:
>>
>>def get_content_charset(self, failobj=None):
>>"""Return the charset parameter of the Content-Type header.
>>
>>The returned string is always coerced to lower case. If t
Mark Sapiro wrote:
> In another reply, I suggested a simpler change
Yeah, I should have just waited a little longer before posting a
half-baked diff. :-)
> In order to fix the bug we really only need to skip parts with payload
> = None so if we want to keep the 'empty' part, the fix should be
>
Folks,
I'm OK with changing the recomposing part in Scrubber.py:
if not part or part.is_multipart():
continue
to
if part.is_multipart():
continue
It looks like the email package is more robust than it was when the bug
report was issued and the Scrubber code was patched.
But as to t
Dave Foran wrote:
>
>But the option I really do like is that every night the contents of the
>users distibution list
>is e-mailed to the list owner and the users are backed up into a 3 day
>rotation..
>
>Does mailman have a provision for backing up the users list on a daily basis
Not out of the b
At 3:31 PM -0500 12/9/06, Dave Foran wrote:
> Does mailman have a provision for backing up the users list on a daily basis
Not built-in, no. But it would be simple enough to set up a daily
cron job to run $MAILMANHOME/bin/list_members, however.
--
Brad Knowles, <[EMAIL PROTECTED]>
Trend Mic
At 9:09 AM -0800 12/9/06, Mark Sapiro wrote:
> There are other settings that could cause pipermail archiving to fail
> or be bypassed for a particular installation.
Correct. However, my understanding at the time was that the
pipermail functionality wasn't just disabled, it was never available
Paul Tomblin wrote:
>Quoting Dave Foran ([EMAIL PROTECTED]):
>> 1 How you prune old messages from the archives.. Looks like you can just
>> delete them but!!!
>
>In the past, I've deleted them from the
>archives/private/listname.mbox/listname.mbox file, and then deleted the
>entire archive and reg
Paul Tomblin wrote:
>Every time a message goes out to one person who is a member of my lists
>(who has a uchicago.edu address), I see in the Postfix log what looks like
>it should be a bounce:
>
>Dec 9 15:00:45 xen1 postfix/smtpd[3315]: connect from
>relay01.uchicago.edu[128.135.12.136]
>Dec 9
Quoting Dave Foran ([EMAIL PROTECTED]):
> 1 How you prune old messages from the archives.. Looks like you can just
> delete them but!!!
In the past, I've deleted them from the
archives/private/listname.mbox/listname.mbox file, and then deleted the
entire archive and regenerated it with bin/arch.
Disregard
I got it fixed and arrgh the system is corrupted and the user list is gone
Which now asks this question.. I have a system also using Smartlist.
While a bit of a stinker ( I took over the system from afreind who passed
away)
But the option I really do like is that every night the con
Greetings
I am not if I have the correct list to ask this, but ;-)
I host a couple of mailman lists Seem to working just fine
I have 2 questions..
1 How you prune old messages from the archives.. Looks like you can just
delete them but!!!
2 I have lost a list name on the admin page I think
Every time a message goes out to one person who is a member of my lists
(who has a uchicago.edu address), I see in the Postfix log what looks like
it should be a bounce:
Dec 9 15:00:45 xen1 postfix/smtpd[3315]: connect from
relay01.uchicago.edu[128.135.12.136]
Dec 9 15:00:47 xen1 postfix/smtpd[
On Thu, Dec 07, 2006 at 06:04:55PM -0500, Barry Warsaw wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Dec 7, 2006, at 5:22 PM, Paul Tomblin wrote:
>
> > I've just spent two days manipulating a bunch of mbox files into
> > archives.
> > Let me tell you how it goes:
>
> [Screams
Todd Zullinger wrote:
>
>Related to the second part of Werner's message being scrubbed with the
>message:
>
>An embedded and charset-unspecified text was scrubbed...
>
>Poking in the email package (on python 2.4.4) shows:
>
>def get_content_charset(self, failobj=None):
>"""Return th
Todd Zullinger wrote:
>
>--- Scrubber.py~2006-10-01 16:28:57.0 -0400
>+++ Scrubber.py 2006-12-09 11:41:25.0 -0500
>@@ -334,7 +334,12 @@
> text = []
> for part in msg.walk():
> # TK: bug-id 1099138 and multipart
>-if not part or part.is
Tokio Kikuchi wrote:
>
>This program prints out like this:
>
>multipart/mixed
>None
>text/plain
>text/plain
>Another text with a header
>
>Note that 'A message without header' is not printed out.
>
>If I remove 'If p:' and print the payload unconditionally, I get:
>
>multipart/mixed
>None
>text/pla
Related to the second part of Werner's message being scrubbed with the
message:
An embedded and charset-unspecified text was scrubbed...
Poking in the email package (on python 2.4.4) shows:
def get_content_charset(self, failobj=None):
"""Return the charset parameter of the Conten
Brad Knowles wrote:
>
>The problem is that the conversation I had with Alan up to that point
>had lead me to believe that we were talking about a standard Mailman
>installation as provided in package format by Debian, and yet Alan's
>configuration clearly lacked what I consider to be a pretty im
Tokio Kikuchi wrote:
> It looks like the problem is something to do with email package
> behavior. Here is a test code to reproduce the problem:
That's neat. I like how you can do
if not p:
print p
and it'll print out "A message without header". :)
Would an (ugly, amateurish) work-around
Help
help
This message has been scanned for viruses by BlackSpider MailControl -
www.blackspider.com
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.o
At 3:16 PM +0900 12/9/06, Stephen J. Turnbull wrote:
>The mailman package did install a
> complete Mailman on several Debian systems where I use Mailman.
Understood. At least, now I do.
The problem is that the conversation I had with Alan up to that point
had
At 1:43 AM -0500 12/9/06, John A. Martin wrote:
> Oops. The first sentence of mine above was intended to end with a
> question mark rather than an exclamation mark. Maybe that would have
> sounded better.
That would have been somewhat better, yes.
> Brad> I didn't say that Debian did.
26 matches
Mail list logo
