Tom Neff wrote,
| If absolutely all else fails, you can take your current roster and send
| (directly, not via listserv/majordomo) a set of SERIALIZED "This is a list
| test - please ignore" messages to the addresses. I once hacked some
| scripts for this, but looking just now I don't know what I did with them --
| it's not hard anyway. Then when "TEST 0001347" bounces with that IBM
| message, you look at your list and bingo, [EMAIL PROTECTED] is the culprit.
Probe messages work only if the refusing site sends you back the text, or
sends you back your outgoing subject, or at least returns something that
distinguishes one probe message from the others. Prodigy tells you only that
such-and-such a user ID is not valid: no text, no Received: headers for the
trip from your site to Prodigy, no trace of your Subject:, nothing. You're
not going to know that it is probe #0001347 that one of your subscribers
forwarded to the invalid address if you put the identifier in the subject
or the text. (If the bouncing site returns headers, it will also return
your outgoing To:, which should also tell you. Of course your list distri-
butions won't show To: each subscriber, but your probe messges will.)
The only way to deal with mail forwarded to invalid Prodigy ID's is with
VERPs or suffixing on your envelope sending address. If you don't have
that facility, you're up a creek. (Well, unless you have limitless pa-
tience to send a probe to one subscriber, give Prodigy an hour to return the
bounce, see if nothing happens, send the next subscriber a probe, etc.)
