From owner-freebsd-questions Tue Jul 4 20:40:43 2000 Delivered-To: freebsd-questions@freebsd.org Received: from watson.ficsgrp.com (watson.ficsgrp.com [194.74.111.3]) by hub.freebsd.org (Postfix) with ESMTP id 995BD37B5DF for <questions@FreeBSD.ORG>; Tue, 4 Jul 2000 20:40:32 -0700 (PDT) (envelope-from harry.woodward-clarke@s1.com) Received: from mail.au.ficsgrp.com ([194.74.111.35]) by watson.ficsgrp.com (Netscape Messaging Server 3.6) with ESMTP id AAA218D for <questions@FreeBSD.ORG>; Wed, 5 Jul 2000 05:40:29 +0200 Received: from S1.com ([172.16.48.219]) by mail.au.ficsgrp.com (Netscape Messaging Server 3.6) with ESMTP id 411 for <questions@FreeBSD.ORG>; Wed, 5 Jul 2000 13:43:27 +1000 Message-ID: <3962AE26.90176952@S1.com> Date: Wed, 05 Jul 2000 13:40:22 +1000 From: Harry Woodward-Clarke <Harry.Woodward-Clarke@S1.com> X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 Cc: FreeBSD Questions List <questions@FreeBSD.ORG> Subject: Re: Repeated mail References: <NDBBLDLJFKMIDBKILPEPOEGNCIAA.pedro@hci.com.mx> <20000704202649.A325@dialin-client.earthlink.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi y'all, I've not read this whole string, but... ;') I've seen this sort of thing using fetchmail with a locally written mda (mail delivery agent), whereby fetchmail would connect correctly to the POP3 mailbox, start sucking them down & pass the data-stream to the mda (which inserts the messages into a db/2 database). Occasionally, the mda would fail, passing an 'error' status to fetchmail. Now, at this stage, fetchmail has not sent back a "mark message(s) read" status to the POP3 mailbox, so the process terminates , and the messages stay on the mailbox with an "unread" status on them. We worked around this by modifying fetchmail - gotta love that open-source stuff ;') hth, haxxa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message