On Sun, Mar 11, 2001 at 02:36:46PM -0600, [EMAIL PROTECTED] wrote:
> You can probably find your loop with some variant on the following shell
> script. (Note that the address being tested is in both the subject and the
> body of the message, which improves the chance that it will be included
> in any bounce or loop.)
> ...
> for name in `cat $LIST1 $LIST2 $LIST3`
> do
> /bin/mailx -s "Path Check to $name" $name <<EOT
> This is a test of addresses on the foo.bar mailing list, performed
> periodically. No response is necessary.
Actually, this may be a more subtle way to do it. This is what I
do when tracking down a particularly vexing bounce.
for dom in `sed -e 's/.*@// dist | sort -u`;
do
nslookup -query=mx $dom >> /tmp/mxlist
done
`dist' is the name of the file where SmartList keeps the subscriber
list. This script looks up the MX record for each domain on your
mailing list and stores it in /tmp/mxlist.
Mitch's bounces are getting sent from leben.com to sm4.texas.rr.com.
If he can identify which domain on his list has sm4.texas.rr.com
as an MX, he may be able to identify the problem user.
--
Regards,
Tim Pierce
RootsWeb.com lead system admonsterator
and Chief Hacking Officer
