In regards to bounce processing...I noticed that all incoming bounced mail would put the bounced addr in a file called bounces/MMDDYY
Looking at the code, this happens if formail/idhash returns a 0 serial #.
A little investigation showed that for my setup, the formail -m4 needs to be changed to -m5. Why? How many other broken smartlists can there be out there?
Below is a dump of what is in tmp.request (which gets passed to) formail in procbounce.
From MAILER-DAEMON@vroc.org Tue Apr 10 01:22:33 2001
Received: from omr-r05.mx.aol.com (omr-r05.mx.aol.com [152.163.225.133]) by nomad.vroc.org (8.11.0/8.11.0) with ESMTP id f3A5MX927615 for vulcan-request@vroc.org; Tue, 10 Apr 2001 01:22:33 -0400 Received: from rly-na05.mx.aol.com (rly-na05.mail.aol.com [172.18.151.234]) by omr-r05.mx.aol.com (v77.27) with ESMTP; Tue, 10 Apr 2001 01:21:41 -0500 Received: from localhost (localhost) by rly-na05.mx.aol.com (8.8.8/8.8.8/AOL-5.0.0) with internal id BAA11479; Tue, 10 Apr 2001 01:21:39 -0400 (EDT) Date: Tue, 10 Apr 2001 01:21:39 -0400 (EDT) From: Mail Delivery Subsystem MAILER-DAEMON@aol.com Message-Id: 200104100521.BAA11479@rly-na05.mx.aol.com To: vulcan-request@vroc.org MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary="BAA11479.986880099/rly-na05.mx.aol.com" Subject: Returned mail: Service unavailable Auto-Submitted: auto-generated (failure)