Searching \ for '[OT]: [ADMIN] Bounces' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page:
Search entire site for: '[ADMIN] Bounces'.

Exact match. Not showing close matches.
PICList Thread
'[OT]: [ADMIN] Bounces'
2001\03\27@125409 by jamesnewton

picon face
We are getting bounces from spam_OUTJoko.NugrohoTakeThisOuTspamINDESSO.COM probably due to
incompetence of his ISP at

Just so people understand how I know this...

...and to try to learn how to better handle this problem which has really
disrupted our list in the past...

The email headers for one of the bounces contains the section reproduced
below. There are two important things to notice.

First, the email passes through MITVMA.MIT.EDU twice. In my experience, this
is a dead giveaway that the email is a bounce. The bounce detector and
eliminator used by
looks for exactly that. I've suggested to lsoft that they also look for
that, but they are a busy lot I guess or maybe there is some reason why that
won't work for them.

Second, the first time (read from the bottom up) that is passes
MITVMA.MIT.EDU, it heads off to the ISP at and they
report delivering it to .....indesso-Joko.NugrohoKILLspamspam@spam@INDESSO.COM. If it comes back
to the list again with that first part of the header still attached, it was
after this persons machine (or their ISPs machine) touched it so that is the
root of the problem.

Now, what is "interesting" is that indesso-Joko.NugrohospamKILLspamINDESSO.COM isn't
(hasn't been) subscribed to the list! Neat huh? But the list server has a
totally cool feature that allows one to scan for any part of an email
address or name. So scanning for indesso comes up with
.....Joko.NugrohoKILLspamspam.....INDESSO.COM who IS (was) subscribed.

What I would like to have is a script that parses the headers of any message
that is detected by the postbot as being a bounce and tries to figure out
who the subscriber is that caused the bounce. So they can be automatically
deleted rather than waiting until a human is available to do the detective
work and drop them. This one was fairly easy due to the
machine adding the (not required) comment about who it delivered it to.
There is apparently an immense amount of variability in the layout of email

If anyone out there with lots of email ISP experience (I have VERY LITTLE)
knows more about this sort of thing, please comment.

         with spool id 8739 for EraseMEPICLISTspam_OUTspamTakeThisOuTMITVMA.MIT.EDU; Tue, 27 Mar 2001
         04:48:43 -0500
Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail
         V1.2c/1.8c) with BSMTP id 1059; Tue, 27 Mar 2001 04:48:03 -0500
Received: from [] by (IBM VM
         Level 320) via TCP with SMTP ; Tue, 27 Mar 2001 04:47:58 EST
X-Comment: Mail was sent by
Received: from (unknown []) by
         (Postfix) with ESMTP id 3D78D5371C for <>;
         27 Mar 2001 16:48:47 +0700 (JAVT)
Received: from jktm [] by [] with
         (MDaemon.v3.0.4.R) for <>; Tue, 27 Mar 2001
         16:45:10 +0700
Received: FROM BY jktm ; Tue Mar 27 16:45:08 2001 +0700
Received: from Pending... [] by [] with DomainPOP
         (MDaemon.v3.0.4.R) for <>; Tue, 27 Mar 2001
         16:43:01 +0700
Delivered-To: RemoveMEindesso-Joko.NugrohoTakeThisOuTspamINDESSO.COM
Received: (qmail 11772 invoked from network); 27 Mar 2001 15:16:09 +0700
Received: from unknown (HELO ( by with SMTP; 27 Mar 2001 15:16:09 +0700
Received: from PEAR.EASE.LSOFT.COM ( by
         (LSMTP for Digital Unix v1.1b) with SMTP id
         <>; Tue, 27 Mar 2001 3:14:45 -0500
         with spool id 5099 for TakeThisOuTPICLISTEraseMEspamspam_OUTMITVMA.MIT.EDU; Tue, 27 Mar 2001
         03:12:51 -0500
Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail
         V1.2c/1.8c) with BSMTP id 5271; Tue, 27 Mar 2001 03:12:45 -0500

James Newton (PICList Admin #3) 1-619-652-0593
PIC/PICList FAQ: or .org

-- hint: To leave the PICList

More... (looser matching)
- Last day of these posts
- In 2001 , 2002 only
- Today
- New search...