MS/perl segfaults

Hugo van der Kooij hvdkooij at
Mon Nov 10 19:08:51 GMT 2008

Hash: SHA1

Julian Field wrote:
> One immediate thought: the only reproducible instance of this problem
> was caused by the HTML parser, and I wrote a solution to that in a
> recent release, it's in the Change Log.
> But yes, your idea is a possibility, now that I'm using SQLite. Doing it
> with a dbm file is not really practical due to high contention for the
> exclusive write locks on the file. SQLite may be able to do it rather
> better.
> There are quite a few routes that lead to a message leaving a batch, and
> I would have to catch all of those, time for a quick code review of a
> few chunks I think.
> If a message is more than 20 minutes old and still in the database, then
> we do a batch containing only 1 message, and log it. If we find a
> message more than 30 minutes old, then we log it and ignore it.
> How many ways could this process go wrong? All existing exclusion-locks
> would still apply, so if a message was more than 20 minutes old and is
> being re-tried and is still locked, that lock still applies.
> What are the failure modes of this scheme? I refuse to believe there
> aren't any. We need to cover as many of them as possible and come up
> with remedies for them.

I think you need these timers configurable. Not every installation can
reliably parse messages within 20 minutes.  But beyond that little point
it sounds like a good scheme.


- --
hvdkooij at     

	A: Yes.
	>Q: Are you sure?
	>>A: Because it reverses the logical flow of conversation.
	>>>Q: Why is top posting frowned upon?

Bored? Click on and rate those images.

Nid wyf yn y swyddfa ar hyn o bryd. Anfonwch unrhyw waith i'w gyfieithu.
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora -


More information about the MailScanner mailing list