On Tue, 12 Sep 1995 08:44, Peter Laws said: <[log in to unmask]> wrote:
>I got a dozen or so messages from CompuServe like this today:
>
>? Invalid receiver address: [log in to unmask]
>
>Thing is, None of my subscribers are using addresses of the above form,
>only "standard" CompuServe addresses (ie. [log in to unmask]).
>Anybody else getting this?
 
Using the NSLOOKUP utility, I find that there are one MX (mail-exchanger)
record for the name 'COMPUSERVE.COM', and that host has ten IP-addresses,
namely:
 
compuserve.com     preference = 10, mail exchanger = mailgate.compuserve.com
 
mailgate.compuserve.com inet address = 198.4.7.1
mailgate.compuserve.com inet address = 198.4.7.2
mailgate.compuserve.com inet address = 198.4.7.3
mailgate.compuserve.com inet address = 198.4.7.4
mailgate.compuserve.com inet address = 198.4.7.5
mailgate.compuserve.com inet address = 198.4.9.1
mailgate.compuserve.com inet address = 198.4.9.2
mailgate.compuserve.com inet address = 198.4.9.3
mailgate.compuserve.com inet address = 198.4.9.4
mailgate.compuserve.com inet address = 198.4.9.5
 
Using NSLOOKUP to do "reverse" lookups, i.e., starting with the IP-addresses,
and requesting the names, I find names similar to those which you reported:
 
Name: arl-img-1.compuserve.com       Address: 198.4.7.1
Name: arl-img-2.compuserve.com       Address: 198.4.7.2
Name: arl-img-3.compuserve.com       Address: 198.4.7.3
Name: arl-img-4.compuserve.com       Address: 198.4.7.4
Name: arl-img-5.compuserve.com       Address: 198.4.7.5
Name: dub-img-1.compuserve.com       Address: 198.4.9.1
Name: dub-img-2.compuserve.com       Address: 198.4.9.2
Name: dub-img-3.compuserve.com       Address: 198.4.9.3
Name: dub-img-4.compuserve.com       Address: 198.4.9.4
Name: dub-img-5.compuserve.com       Address: 198.4.9.5
 
So, my conclusion is that you're just getting messages
from one of the mail-exchanger hosts within the CompuServe domain,
and that you should treat it just like any other "unknown-user" situation.
 
You could try a "test" E-mail to the ID, and see if that also "bounces",
before you do a 'SET NOMAIL NOFILE' or 'DELETE' the ID.