Hello there. How would I go about debugging mailman, by --
for example -- polluting the .py libraries with print or
assert statements? If I do that (which seems like a pretty
thoughtless idea), the output would end up .. in /dev/null?
It would probably be better to write to file in stead?
Right no
Barry Warsaw wrote:
> Other than that, we'd need a reliable standards-compliant LMTP server
> written in Python (and no, smtpd.py- or Twisted-based versions are
> not acceptable ;).
Why no smtpd.py ? There is a MailmanProxy Object in the code which was
written by you, Barry. Any SMTP serve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 29, 2006, at 9:52 AM, Tokio Kikuchi wrote:
> Barry Warsaw wrote:
>
>> Other than that, we'd need a reliable standards-compliant LMTP server
>> written in Python (and no, smtpd.py- or Twisted-based versions are
>> not acceptable ;).
>
> Why no s
Sven Ingebrigt Ulland wrote:
>Hello there. How would I go about debugging mailman, by --
>for example -- polluting the .py libraries with print or
>assert statements? If I do that (which seems like a pretty
>thoughtless idea), the output would end up .. in /dev/null?
>It would probably be better t
Barry Warsaw wrote:
> BTW, what do you think about changing the way we hold messages for
> digests? E.g. instead of putting them in an mbox file, where it's
> more difficult to skip bad messages, stick them in a queue-like
> directory and pull them from there. Any messages that can't be re
Brad Knowles wrote:
> So your assumptions about what kinds of filesystems may or may not be
> appropriate are not necessarily going to coincide with the decisions
> that other people make, or the kinds of hardware and OS they may be
> forced to live with.
I don't disagree with this assertion,
On 9/28/06 7:16 PM, "Barry Warsaw" <[EMAIL PROTECTED]> wrote:
> If you look at the source, you'll see that the #! line is actually
> @PYTHON@ which gets substituted by configure at build time. I forget
> exactly why, but the standard #! /usr/bin/env python invocation
> caused problems for people,
At 12:23 PM -0400 9/29/06, emf wrote:
> Furthermore, many MTAs *do* understand Maildir,
MTAs should be sticking to the job of transmitting e-mail between
themselves. If they're spending any time mucking about with local
mailbox formats, they're making a mistake. That's a job for a Local
Del
At 12:23 PM -0400 9/29/06, emf wrote:
>> So your assumptions about what kinds of filesystems may
>> or may not be appropriate are not necessarily going to
>> coincide with the decisions that other people make, or
>> the kinds of hardware and OS they may be forced to live
>> with.
>
> I don't
On Fri, 29 Sep 2006, Brad Knowles wrote:
> If you don't read the comments that Mark Crispin has written about
> the weaknesses in Maildir, and you haven't read the code to see what
> it's actually doing, then I don't see how you can participate in this
> discussion.
I did read through both of
--On Thursday, September 28, 2006 11:39 PM -0500 Brad Knowles
<[EMAIL PROTECTED]> wrote:
> At 11:19 PM -0400 9/28/06, emf wrote:
>
>> It seems to me like anyone likely to end up with a huge enough incoming
>> mailman queue to care about Maildir's inefficiencies would also be able
>> to put a s
At 3:37 PM -0700 9/29/06, Carson Gaspar wrote:
> Brad, if your _incoming_ queue is so big that you have to worry, your
> servers are woefully underspec'd.
That may or may not be true, but that doesn't make the problem
magically go away.
>
12 matches
Mail list logo
