[Mailman-Users] Mailman-Users Digest, Vol 34, Issue 64
AMBROSE CHRISTOPHER
ambrose_christopher at yahoo.com
Wed Dec 27 14:02:57 CET 2006
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
>
> --- snip ---
>
> > From: Chris Florio <cflorio at citadel97.com>
> To: mailman-users at python.org
> Date: Tue, 26 Dec 2006 17:13:45 -0500
> Subject: [Mailman-Users] OS X Permissions Help.
>
> Hello all,
>
> I'm trying to get mailman working on my intel based
> Mac Mini running
> 10.4.8 (NOT OS X Server). I'm running Postfix
> configured using
> http://cutedgesystems.com/software/MailServe/
>
> I have configured and installed mailman using some
> instructions I
> found here:
>
>
http://mail.python.org/pipermail/mailman-users/2005-July/045697.html
>
> The problem is, it looks like i have a group or
> ownership problem
> somewhere.
>
> As the instructions said, I configured using:
>
> sudo ./configure --prefix=/Applications/mailman
> --with-cgi-gid=www --
> with-mail-gid=mailman
>
>
> Using the instructions from the list I found, I am
> getting this error
> posting to a list I created:
>
> ...
>
> The Postfix program
>
> <alumni at citadel97.com>: Command died with status 2:
> "/Applications/mailman/mail/mailman post
> alumni". Command
> output: Group
> mismatch error. Mailman expected the mail
> wrapper script to be
> executed as
> group "mailman", but the system's mail server
> executed the mail
> script as
> group "www". Try tweaking the mail server to
> run the script as
> group
> "mailman", or re-run configure, providing the
> command line option
> `--with-mail-gid=www'.
>
>
> ...
>
> So, I tried again using:
>
> sudo ./configure --prefix=/Applications/mailman
> --with-cgi-gid=www --
> with-mail-gid=www
>
> And then I get this error:
>
> The Postfix program
>
> <alumni at citadel97.com>: Command died with status 2:
> "/Applications/mailman/mail/mailman post
> alumni". Command
> output: Group
> mismatch error. Mailman expected the mail
> wrapper script to be
> executed as
> group "www", but the system's mail server
> executed the mail
> script as group
> "mailman". Try tweaking the mail server to run
> the script as
> group "www",
> or re-run configure, providing the command
> line option
> `--with-mail-gid=mailman'.
>
> ....
>
>
> Any ideas?
>
> Thanks!
>
>
>
>
> > From: Noah <admin2 at enabled.com>
> To: Mailman Users <mailman-users at python.org>
> Date: Tue, 26 Dec 2006 16:01:59 -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 16:02:06 -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
>
> --- snip ---
>
>
> > From: "Stephen J. Turnbull" <stephen at xemacs.org>
> CC: Mailman Users <mailman-users at python.org>
> To: Noah <admin2 at enabled.com>
> Date: Wed, 27 Dec 2006 12:21:17 +0900
> Subject: [Mailman-Users] BoundaryError: No
> terminating boundary and
> no trailing empty line
>
> Noah writes:
>
> > 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.
>
> Probably for the same reason you repeatedly post to
> Mailman Users: it
> wants attention to its pain.
>
> For future reference, the folks (not me! I show up
> when I feel like
> it) who monitor this list are knowledgeable and
> conscientious, in the
> extreme, and it is *very* rare that posts get
> dropped on the floor.
> Typical response times are in the range 30 minutes
> to 36 hours,
> depending on random factors.
>
> Check that your post has appeared in the archives,
> and if so, give it
> a day at least. Don't waste the interval; read the
> FAQ[1], search the
> list archives (a search for the error message, in
> this case "Ignoring
> unparseable message", is strongly recommended),
> collect more log data,
> etc. If your post doesn't appear within a day, you
> may wish to send
> mail to the list administrator. It's possible that
> your post got
> inadvertantly snagged by a spam filter, and you'll
> need help getting
> past that.
>
> > Dec 26 08:27:28 2006 (75889) Ignoring unparseable
> message:
> >
>
1166121349.6141329+c811d30798575d4ca57b9a0552a1d394a95c8ff1
>
> The hash code above identified the problem message.
> I believe you
> will find a file by that name (with extension .pck)
> in the "qfiles"
> directory of your Mailman data area, and if you move
> it somewhere
> else, Mailman will stop complaining. It happens
> regularly because
> Mailman tries to process the files in that directory
> on a regular
> basis, until all deliveries scheduled for it are
> complete.
>
> It's possible that you are the target of a spambot,
> in which case you
> may not find the file (because it's been shunted to
> the "shunt"
> directory), and you will see that all the message
> IDs are different in
> the logs, because the spambot is sending a new copy
> at hourly
> intervals.
>
> > Dec 26 08:27:28 2006 (75889) Uncaught runner
> exception: No terminating
> > boundary and no trailing empty line
>
> You've got a badly-formed MIME message in the queue.
> It could be
> spam, it could simply be the product of a Microsoft
> mail client, it
> could be broken by a relay MTA, or it could be that
> you ran out of
> diskspace and it got truncated (seems unlikely,
> given the care that
> Postfix and Mailman take to not do such things).
>
> Use the bin/show_qfiles script to examine the
> contents of that file.
> Simply changing to the mailman data area (on my
> Debian system it's
> /var/lib/mailman, YMMV) running bin/show_qfiles
> without arguments will
> give you a usage message.
>
>
> Footnotes:
> [1] The whole thing, both the static one and the
> FAQ Wizard. If it's
> not important enough to read the whole FAQ, which
> isn't as much fun as
> a Sidney Sheldon novel but is also much shorter, it
> probably can wait
> a day or a week.
>
>
> > From: Brad Knowles <brad at shub-internet.org>
> CC: Mailman Users <mailman-users at python.org>
> To: Noah <admin2 at enabled.com>
> Date: Tue, 26 Dec 2006 22:23:47 -0600
> Subject: Re: [Mailman-Users] BoundaryError: No
> terminating boundary and
> no trailing empty line
>
> At 12:21 PM +0900 12/27/06, Stephen J. Turnbull
> wrote:
>
> > For future reference, the folks (not me! I show
> up when I feel like
> > it) who monitor this list are knowledgeable and
> conscientious, in the
> > extreme, and it is *very* rare that posts get
> dropped on the floor.
> > Typical response times are in the range 30
> minutes to 36 hours,
> > depending on random factors.
>
> This is the day after Christmas. Any time anyone is
> posting to any
> mailing list for the two to three week period of
> time starting a few
> days before Christmas and ending a few days after
> the first of
> January, it's going to be slow. During these times,
> people who post
> to the list can count on replies taking a lot longer
> to be posted.
>
> --
> Brad Knowles, <brad at shub-internet.org>
>
> Trend Micro has announced that they will cancel the
> stop.mail-abuse.org
> mail forwarding service as of 15 November 2006. If
> you have an old
> e-mail account for me at this domain, please make
> sure you correct that
> with the current address.
>
> > From: Brad Knowles <brad at shub-internet.org>
> To: Noah <admin2 at enabled.com>,
> Mailman Users <mailman-users at python.org>
> Date: Tue, 26 Dec 2006 22:29:02 -0600
> Subject: Re: [Mailman-Users] mailman not sending
> post
>
> At 4:01 PM -0800 12/26/06, Noah wrote:
>
> > recently mailman has not mailed posts to a
> specific list, and I cant
> > figure out why.
>
> You've recently posted a few times to this list, on
> two separate
> subjects. I strongly suspect that these two issues
> are actually
> related -- what you're not finding in this
> particular case is likely
> to be the stuff you are finding in the other case.
>
> > Mailman properly handles and delivers posts to
> all other lists. I
> > really am not sure what else to check.
>
> Check all other unusual activity. Look in all the
> logs that Mailman
> creates, and all the system log files that may be
> created by your MTA.
>
> Make sure to take a look in the FAQ wizard --
> there's lots of good
> troubleshooting tips in there. In fact, I recommend
> that you search
> on the word "troubleshooting", among other things.
>
> --
> Brad Knowles, <brad at shub-internet.org>
>
> Trend Micro has announced that they will cancel the
> stop.mail-abuse.org
> mail forwarding service as of 15 November 2006. If
> you have an old
> e-mail account for me at this domain, please make
> sure you correct that
> with the current address.
>
> >
------------------------------------------------------
> 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