[Mailman-Users] Mailman-Users Digest, Vol 34, Issue 65
AMBROSE CHRISTOPHER
ambrose_christopher at yahoo.com
Wed Dec 27 17:03:08 CET 2006
when migrating archive did twice on accident,we used
to call a sink hole.
--- mailman-users-request at python.org wrote:
> Send Mailman-Users mailing list submissions to
> mailman-users at python.org
>
> To subscribe or unsubscribe via the World Wide Web,
> visit
>
>
http://mail.python.org/mailman/listinfo/mailman-users
> or, via email, send a message with subject or body
> 'help' to
> mailman-users-request at python.org
>
> You can reach the person managing the list at
> mailman-users-owner at python.org
>
> When replying, please edit your Subject line so it
> is more specific
> than "Re: Contents of Mailman-Users digest..."
> > Today's Topics:
>
> 1. Re: Mailman-Users Digest, Vol 34, Issue 64
> (AMBROSE CHRISTOPHER)
> 2. Re: Mailman-Users Digest, Vol 34, Issue 64
> (AMBROSE CHRISTOPHER)
> > From: AMBROSE CHRISTOPHER
> <ambrose_christopher at yahoo.com>
> To: mailman-users at python.org
> Date: Wed, 27 Dec 2006 04:59:05 -0800 (PST)
> Subject: Re: [Mailman-Users] Mailman-Users Digest,
> Vol 34, Issue 64
>
>
> --- mailman-users-request at python.org wrote:
>
> > Send Mailman-Users mailing list submissions to
> > mailman-users at python.org
> >
> > To subscribe or unsubscribe via the World Wide
> Web,
> > visit
> >
> >
>
http://mail.python.org/mailman/listinfo/mailman-users
> > or, via email, send a message with subject or body
> > 'help' to
> > mailman-users-request at python.org
> > check last couple days mail,you have answer,is
> double up.
> > You can reach the person managing the list at
> > mailman-users-owner at python.org
> >
> > When replying, please edit your Subject line so it
> > is more specific
> > than "Re: Contents of Mailman-Users digest..."
> > > Today's Topics:
> >
> > 1. mailman not sending post (Noah)
> > 2. BoundaryError: No terminating boundary and
> no
> > trailing empty
> > line (Noah)
> > 3. OS X Permissions Help. (Chris Florio)
> > 4. mailman not sending post (Noah)
> > 5. BoundaryError: No terminating boundary and
> no
> > trailing empty
> > line (Noah)
> > 6. BoundaryError: No terminating boundary and
> no
> > trailing empty
> > line (Stephen J. Turnbull)
> > 7. Re: BoundaryError: No terminating boundary
> and
> > no trailing
> > empty line (Brad Knowles)
> > 8. Re: mailman not sending post (Brad Knowles)
> > > From: Noah <admin2 at enabled.com>
> > To: Mailman Users <mailman-users at python.org>
> > Date: Tue, 26 Dec 2006 07:28:07 -0800
> > Subject: [Mailman-Users] mailman not sending post
> >
> > Hi there,
> >
> > mailman-2.1.9
> > sendmail 8.13.8
> > python-2.4.3
> > freebsd-4.11
> >
> >
> > Mailman has been running on my machine for years.
>
> > I host about 50 or
> > so lists with virtual hostnames being sued for
> some
> > of them.
> >
> > recently mailman has not mailed posts to a
> specific
> > list, and I cant
> > figure out why.
> > I see the mailman post mail being accepted by
> > sendmail and piped to
> > mailman but mailman does nothing with the post.
> No
> > trace of the post in
> > the /usr/local/mailman/logs/smtp or the
> > /usr/local/mailman/logs/post
> >
> > I cant find a related trace dumped in the mailman
> > error logs.
> >
> > subscribes and unsubscribes piped to mailman work
> > fine
> > like mail sent to <listname>-subscribe at domain.com
> > gets piped
> > |/usr/local/mailman/mail/mailman subscribe
> > <listname> just fine by sendmail
> > mailman sends a confirmation mail just fine as
> well.
> >
> > there is one file in the
> > /usr/local/mailman/qfiles/shunt directory from
> > october 7th 2006.
> >
> > Mailman properly handles and delivers posts to all
> > other lists. I
> > really am not sure what else to check.
> >
> > cheers,
> >
> > Noah
> >
> >
> >
> >
> > > From: Noah <admin2 at enabled.com>
> > To: Mailman Users <mailman-users at python.org>
> > Date: Tue, 26 Dec 2006 08:52:52 -0800
> > Subject: [Mailman-Users] BoundaryError: No
> > terminating boundary and no
> > trailing empty line
> >
> > freebsd-4.11
> > sendmail-8.13.8
> > mailman-2.1.9_1
> > python-2.4.3
> >
> >
> > any clues why mailman keeps dumping the following
> > error trace in
> > /usr/local/mailman/logs/error ? Happens about
> every
> > hour or so or
> > sometimes minutes apart.
> >
> >
> > --- snip ---
> >
> > Dec 26 08:27:28 2006 (75889) Ignoring unparseable
> > message:
> >
>
1166121349.6141329+c811d30798575d4ca57b9a0552a1d394a95c8ff1
> > Dec 26 08:27:28 2006 (75889) Uncaught runner
> > exception: No terminating
> > boundary and no trailing empty line
> > Dec 26 08:27:28 2006 (75889) Traceback (most
> recent
> > call last):
> > File
> "/usr/local/mailman/Mailman/Queue/Runner.py",
> > line 100, in _oneloop
> > msg, msgdata =
> > self._switchboard.dequeue(filebase)
> > File
> > "/usr/local/mailman/Mailman/Queue/Switchboard.py",
> > line 164, in
> > dequeue
> > msg = email.message_from_string(msg,
> > Message.Message)
> > File
> > "/usr/local/mailman/pythonlib/email/__init__.py",
> > line 51, in
> > message_from_string
> > return Parser(_class,
> strict=strict).parsestr(s)
> > File
> > "/usr/local/mailman/pythonlib/email/Parser.py",
> line
> > 75, in parsestr
> > return self.parse(StringIO(text),
> > headersonly=headersonly)
> > File
> > "/usr/local/mailman/pythonlib/email/Parser.py",
> line
> > 64, in parse
> > self._parsebody(root, fp, firstbodyline)
> > File
> > "/usr/local/mailman/pythonlib/email/Parser.py",
> line
> > 240, in
> > _parsebody
> > msgobj = self.parsestr(part)
> > File
> > "/usr/local/mailman/pythonlib/email/Parser.py",
> line
> > 75, in parsestr
> > return self.parse(StringIO(text),
> > headersonly=headersonly)
> > File
> > "/usr/local/mailman/pythonlib/email/Parser.py",
> line
> > 64, in parse
> > self._parsebody(root, fp, firstbodyline)
> > File
> > "/usr/local/mailman/pythonlib/email/Parser.py",
> line
> > 265, in
> > _parsebody
> > msg = self.parse(fp)
> > File
> > "/usr/local/mailman/pythonlib/email/Parser.py",
> line
> > 64, in parse
> > self._parsebody(root, fp, firstbodyline)
> > File
> > "/usr/local/mailman/pythonlib/email/Parser.py",
> line
> > 206, in
> > _parsebody
> > raise Errors.BoundaryError(
> > BoundaryError: No terminating boundary and no
> > trailing empty line
>
=== message truncated ===> From: AMBROSE CHRISTOPHER
> <ambrose_christopher at yahoo.com>
> To: mailman-users at python.org
> Date: Wed, 27 Dec 2006 05:02:57 -0800 (PST)
> Subject: Re: [Mailman-Users] Mailman-Users Digest,
> Vol 34, Issue 64
>
> they created ghost log over weekend then were
> corrected by teacher or w/ever admin is.
> --- mailman-users-request at python.org wrote:
>
> > Send Mailman-Users mailing list submissions to
> > mailman-users at python.org
> >
> > To subscribe or unsubscribe via the World Wide
> Web,
> > visit
> >
> >
>
http://mail.python.org/mailman/listinfo/mailman-users
> > or, via email, send a message with subject or body
> > 'help' to
> > mailman-users-request at python.org
> >
> > You can reach the person managing the list at
> > mailman-users-owner at python.org
> >
> > When replying, please edit your Subject line so it
> > is more specific
> > than "Re: Contents of Mailman-Users digest..."
> > > Today's Topics:
> >
> > 1. mailman not sending post (Noah)
> > 2. BoundaryError: No terminating boundary and
> no
> > trailing empty
> > line (Noah)
> > 3. OS X Permissions Help. (Chris Florio)
> > 4. mailman not sending post (Noah)
> > 5. BoundaryError: No terminating boundary and
> no
> > trailing empty
> > line (Noah)
> > 6. BoundaryError: No terminating boundary and
> no
> > trailing empty
> > line (Stephen J. Turnbull)
> > 7. Re: BoundaryError: No terminating boundary
> and
> > no trailing
> > empty line (Brad Knowles)
> > 8. Re: mailman not sending post (Brad Knowles)
> > > From: Noah <admin2 at enabled.com>
> > To: Mailman Users <mailman-users at python.org>
> > Date: Tue, 26 Dec 2006 07:28:07 -0800
> > Subject: [Mailman-Users] mailman not sending post
> >
> > Hi there,
> >
> > mailman-2.1.9
> > sendmail 8.13.8
> > python-2.4.3
> > freebsd-4.11
> >
> >
> > Mailman has been running on my machine for years.
>
> > I host about 50 or
> > so lists with virtual hostnames being sued for
> some
> > of them.
> >
> > recently mailman has not mailed posts to a
> specific
> > list, and I cant
> > figure out why.
> > I see the mailman post mail being accepted by
> > sendmail and piped to
> > mailman but mailman does nothing with the post.
> No
> > trace of the post in
> > the /usr/local/mailman/logs/smtp or the
> > /usr/local/mailman/logs/post
> >
> > I cant find a related trace dumped in the mailman
> > error logs.
> >
> > subscribes and unsubscribes piped to mailman work
> > fine
> > like mail sent to <listname>-subscribe at domain.com
> > gets piped
> > |/usr/local/mailman/mail/mailman subscribe
> > <listname> just fine by sendmail
> > mailman sends a confirmation mail just fine as
> well.
> >
> > there is one file in the
> > /usr/local/mailman/qfiles/shunt directory from
> > october 7th 2006.
> >
> > Mailman properly handles and delivers posts to all
> > other lists. I
> > really am not sure what else to check.
> >
> > cheers,
> >
> > Noah
> >
> >
> >
> >
> > > From: Noah <admin2 at enabled.com>
> > To: Mailman Users <mailman-users at python.org>
> > Date: Tue, 26 Dec 2006 08:52:52 -0800
> > Subject: [Mailman-Users] BoundaryError: No
> > terminating boundary and no
> > trailing empty line
> >
> > freebsd-4.11
> > sendmail-8.13.8
> > mailman-2.1.9_1
> > python-2.4.3
> >
> >
> > any clues why mailman keeps dumping the following
> > error trace in
> > /usr/local/mailman/logs/error ? Happens about
> every
> > hour or so or
> > sometimes minutes apart.
> >
> >
> > --- snip ---
> >
> > Dec 26 08:27:28 2006 (75889) Ignoring unparseable
> > message:
> >
>
1166121349.6141329+c811d30798575d4ca57b9a0552a1d394a95c8ff1
> > Dec 26 08:27:28 2006 (75889) Uncaught runner
> > exception: No terminating
> > boundary and no trailing empty line
> > Dec 26 08:27:28 2006 (75889) Traceback (most
> recent
> > call last):
> > File
> "/usr/local/mailman/Mailman/Queue/Runner.py",
> > line 100, in _oneloop
> > msg, msgdata =
> > self._switchboard.dequeue(filebase)
> > File
> > "/usr/local/mailman/Mailman/Queue/Switchboard.py",
> > line 164, in
> > dequeue
> > msg = email.message_from_string(msg,
> > Message.Message)
> > File
> > "/usr/local/mailman/pythonlib/email/__init__.py",
> > line 51, in
> > message_from_string
> > return Parser(_class,
> strict=strict).parsestr(s)
> > File
> > "/usr/local/mailman/pythonlib/email/Parser.py",
> line
> > 75, in parsestr
> > return self.parse(StringIO(text),
> > headersonly=headersonly)
> > File
> > "/usr/local/mailman/pythonlib/email/Parser.py",
> line
> > 64, in parse
> > self._parsebody(root, fp, firstbodyline)
> > File
> > "/usr/local/mailman/pythonlib/email/Parser.py",
> line
> > 240, in
> > _parsebody
> > msgobj = self.parsestr(part)
> > File
> > "/usr/local/mailman/pythonlib/email/Parser.py",
> line
> > 75, in parsestr
> > return self.parse(StringIO(text),
> > headersonly=headersonly)
> > File
> > "/usr/local/mailman/pythonlib/email/Parser.py",
> line
> > 64, in parse
> > self._parsebody(root, fp, firstbodyline)
> > File
> > "/usr/local/mailman/pythonlib/email/Parser.py",
> line
> > 265, in
> > _parsebody
> > msg = self.parse(fp)
> > File
> > "/usr/local/mailman/pythonlib/email/Parser.py",
> line
> > 64, in parse
> > self._parsebody(root, fp, firstbodyline)
> > File
> > "/usr/local/mailman/pythonlib/email/Parser.py",
> line
> > 206, in
> > _parsebody
> > raise Errors.BoundaryError(
> > BoundaryError: No terminating boundary and no
> > trailing empty line
>
=== message truncated ===>
------------------------------------------------------
> Mailman-Users mailing list
> Mailman-Users at python.org
>
http://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ:
> http://www.python.org/cgi-bin/faqw-mm.py
> Searchable Archives:
http://www.mail-archive.com/mailman-users%40python.org/
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
More information about the Mailman-Users
mailing list