On Feb 20, 2010, at 4:15 PM, Stefan Foerster wrote:
> What is a "smaller sub-list"? The list in question does only hold 11k
> recipients, which is not exactly large. Some off my SVN announce lists
> are much larger.
Yeah, but an announce-only list that is larger doesn't really compare to a
discu
Mailman's pipermail archives are threaded based on In-Reply-To: and
maybe References: headers. It turns out the code always had a fallback
to thread by Subject: if there were no In-Reply-To: or References:
headers, but this fallback never worked due to a bug.
I have recently committed a fix to the
Hi!
...[very slow list]...
Seen from a very abstract standpoint, is there some pattern in
the adresses to send? Some sorting algorithms go completely
bonkers if fed with the wrong kind of pre-sorted or patterned
input list. I did NOT look into this (not knowing enough python
yet), but having st
* Brad Knowles :
> On Feb 20, 2010, at 3:27 PM, Mark Sapiro wrote:
>
> > As I said, I think it would just be the config.pck. Everything
> > else is open source software, but I don't think I want it. It's
> > not that I'm not curious because I definitely am, but I don't want
> > to accidentally sen
* Mark Sapiro :
> On 2/20/2010 12:56 PM, Stefan Foerster wrote:
> > So, if you are personally interested in this, I would talk to a lawyer
> > to find a way how I can legally provide you with a copy of every file
> > that is in any way related to this list.
>
> As I said, I think it would just be
* Barry Warsaw :
> On Feb 20, 2010, at 09:56 PM, Stefan Foerster wrote:
> >So, if you are personally interested in this, I would talk to a lawyer
> >to find a way how I can legally provide you with a copy of every file
> >that is in any way related to this list.
> >
> >If you are not _that_ interes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/20/2010 1:38 PM, Barry Warsaw wrote:
>
> Take a look at lazr.smtptest, which is what MM3 uses in its test framework.
>
> https://edge.launchpad.net/lazr.smtptest
Thanks Barry,
That's helpful.
- --
Mark Sapiro The highway is for gamb
On Feb 20, 2010, at 01:27 PM, Mark Sapiro wrote:
>As I said, I think it would just be the config.pck. Everything else is
>open source software, but I don't think I want it. It's not that I'm not
>curious because I definitely am, but I don't want to accidentally send
>mail to any of the list member
On Feb 20, 2010, at 3:27 PM, Mark Sapiro wrote:
> As I said, I think it would just be the config.pck. Everything else is
> open source software, but I don't think I want it. It's not that I'm not
> curious because I definitely am, but I don't want to accidentally send
> mail to any of the list mem
On 2/20/2010 12:56 PM, Stefan Foerster wrote:
>
> I fear I've got a decision to make here: To "fix" that problem, I'd
> normally simply export the recipient list and recreate the mailing
> list thereafter. But since we don't know what causes this behaviour, I
> can't be sure that my backups includ
On Feb 20, 2010, at 10:17 PM, Ralf Hildebrandt wrote:
>> Have you tried any of the Postfix debugging strategies?
>>
>> http://www.postfix.org/DEBUG_README.html
>
>Yes he did.
>Stefan usually knows what he's doing :)
Ah, sorry about that!
culling-inbox-during-pycon-talk-ly y'rs,
-Barry
signatu
* Barry Warsaw :
> Have you tried any of the Postfix debugging strategies?
>
> http://www.postfix.org/DEBUG_README.html
Yes he did.
Stefan usually knows what he's doing :)
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Fr
On Feb 20, 2010, at 09:56 PM, Stefan Foerster wrote:
>I fear I've got a decision to make here: To "fix" that problem, I'd
>normally simply export the recipient list and recreate the mailing
>list thereafter. But since we don't know what causes this behaviour, I
>can't be sure that my backups inclu
* Stefan Foerster :
> I fear I've got a decision to make here: To "fix" that problem, I'd
> normally simply export the recipient list and recreate the mailing list
> thereafter.
Is this guaranteed to help?
Have you tried this?
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Ch
* Mark Sapiro :
> Does this delay occur uniformly over the entire list, or only within
> some group of recipients?
It occurs for all recipients, more or less - sometimes, it gets about
5 recipients done per second, but that's still far too slow.
> You could try running OutgoingRunner with Python'
On 2/20/2010 10:27 AM, Stefan Foerster wrote:
>
> Yes. From debuglevel(1) logs:
>
> Feb 20 19:03:15 2010 qrunner(7551): send: 'rcpt
> TO:\r\n'
> Feb 20 19:03:15 2010 qrunner(7551): reply: '250 2.1.5 Ok\r\n'
> Feb 20 19:03:15 2010 qrunner(7551): reply: retcode (250); Msg: 2.1.5 Ok
> Feb 20
* Mark Sapiro :
> On 2/20/2010 4:21 AM, Stefan Foerster wrote:
> So, without VERP or personalization, you should be seeing SMTP
> transactions that look like
>
> HELO
> response
> MAIL FROM
> response
> RCPT TO
> response
> (repeated for up to SMTP_MAX_RCPTS recipients)
> DATA
> response
>
On 2/20/2010 4:21 AM, Stefan Foerster wrote:
>
> For all other lists on this server, the conversation between Postfix
> and Mailman is very fast paced, but for that one list, it takes almost
> one second for a recipient to be specified (which is then acknowledged
> immediately by Postfix).
So, w
Hello world,
I have a very strange performance problem which only affects one small
announce-only list with approximately 11000 recipients: The smtp
logfile shows that it takes Mailman about 8400 seconds to deliver the
mails, which just doesn't make sense.
Setup: Mailman is configured to deliver
19 matches
Mail list logo
