The large number of Received headers might be exceeding some internal sieve limit. Try running the original message (and your script) through the sieve test program (sieve/test.c) and see what happens. Then try your trimmed message and see what happens. Of course, if test and lmtpd don't use the same header caching code (its been a while since I looked), then this won't prove anything.
Rob Mueller wrote: > > I'm just wondering if anyone has seen anything like this. Basically I'm > noticing (and so have a few other users) that sieve scripts are *very* > intermittently failing. > > I've captured an example, and I'm wondering if I'm missing anything obvious. > > Basically, I've got a simple sieve script here: > > http://robm.fastmail.fm/sieve/default > > I recently received the following email from the mod_perl mailing list > > http://robm.fastmail.fm/sieve/sieveproblem.eml > > Now I think this email should have ended up in my "INBOX.mod_perl" folder, > but instead it ended up in my inbox. A trimmed version of the header is > here: > > Return-Path: <[EMAIL PROTECTED]> > Received: from server3.fastmail.fm (server3.internal [10.202.2.134]) > by server2.fastmail.fm (Cyrus v2.1.9) with LMTP; Mon, 06 Jan 2003 > 10:46:31 -0500 > X-Sieve: CMU Sieve 2.2 > Received: from server3.fastmail.fm (server3.internal [10.202.2.134]) > by server3.fastmail.fm (Cyrus v2.1.9) with LMTP; Mon, 06 Jan 2003 > 10:46:35 -0500 > Received: from server3.fastmail.fm (localhost [127.0.0.1]) > by fastmail.fm (Postfix) with ESMTP id 863B72D1DA > for <[EMAIL PROTECTED]>; Mon, 6 Jan 2003 10:46:28 -0500 (EST) > Received: from 127.0.0.1 ([127.0.0.1] helo=server3.fastmail.fm) by > fastmail.fm > with SMTP; Mon, 06 Jan 2003 10:46:28 -0500 > X-Mail-from: [EMAIL PROTECTED] > X-Delivered-to: <[EMAIL PROTECTED]> > X-Spam-score: 0.8 > Received: from apache.org (daedalus.apache.org [63.251.56.142]) > by server3.fastmail.fm (Postfix) with SMTP id 07CA529A11 > for <[EMAIL PROTECTED]>; Mon, 6 Jan 2003 10:46:28 -0500 (EST) > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > > There's lots of 'Received:' headers there as we go through postfix, then an > internal content filter, then postfix again, then an lmtpproxy, then lmtp > delivery to the final machine. The postfix log suggests everything went > fine: > > Jan 6 10:46:28 server3 postfix/smtpd[30351]: 07CA529A11: > client=daedalus.apache.org[63.251.56.142] > Jan 6 10:46:28 server3 postfix/cleanup[30552]: 07CA529A11: > message-id=<[EMAIL PROTECTED]> > Jan 6 10:46:28 server3 postfix/qmgr[28413]: 07CA529A11: > from=<[EMAIL PROTECTED]>, size=5689, > nrcpt=1 (queue active) > Jan 6 10:46:28 server3 postfix/smtpd[30644]: 863B72D1DA: > client=localhost[127.0.0.1] > Jan 6 10:46:34 server3 postfix/cleanup[30453]: 863B72D1DA: > message-id=<[EMAIL PROTECTED]> > Jan 6 10:46:35 server3 postfix/qmgr[28413]: 863B72D1DA: > from=<[EMAIL PROTECTED]>, size=6114, > nrcpt=1 (queue active) > Jan 6 10:46:35 server3 postfix/smtp[30616]: 07CA529A11: > to=<[EMAIL PROTECTED]>, relay=localhost[127.0.0.1], delay=7, status=sent (250 > Ok: queued as 863B72D1DA) > Jan 6 10:46:35 server3 postfix/lmtp[30660]: 863B72D1DA: > to=<[EMAIL PROTECTED]>, relay=10.202.2.134[10.202.2.134], delay=7, > status=sent (250 2.1.5 Ok) > > I checked the IMAP log at the time of delivery, and there are no errors at > all. No DBLOCKERS or anything. > > cyrus is 2.1.9 (with some recent security patches) > > Any ideas? > > Actually, it would be nice if there was some way to get some more sieve > diagnostics, or at least a verbose logging mode for a while to help track > down any problems like this. sieve seems to be about the most silent > software I've ever seen... > > Rob -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp
