|
The normal way to check whether a site is in this file is to
use the Unix grep command to
search for some alphanumeric string of characters that is
part of the site's name or IP address. For best results with
alphabetic names, use the -i
option to make the search upper/lower-case-independent:
grep -i search-string
/local/mail/access
Say that a correspondent of yours complains that mail is
bouncing when they send it to you at WAM or Glue. The person
is
goodguy@seven.th.heaven.edu
You first check to see if the user or host or the domain
warrant rejection:
prompt> grep -i goodguy /local/mail/access
prompt> grep -i seven.th.heaven.edu /local/mail/access
prompt> grep -i heaven.edu /local/mail/access
|
These may get hits, but if none of them are actually the
person or host or domain in question, you then work on the
IP-address. There are two convenient commands to supply this:
host
or nslookup :
prompt> host seven.th.heaven.edu
seven.th.heaven.edu has address 123.456.78.90
or
prompt> nslookup seven.th.heaven.edu
Server: name-server-name
Address: name-server-IP
Non-authoritative answer:
Name: seven.th.heaven.edu
Address: 123.456.78.90
|
Once you have the IP-address of the sender's host machine,
you can check for both the specific IP-address
and for its domain (the first two numbers in the
IP-address):
prompt> grep -i goodguy /local/mail/access
prompt> grep 123.456.78.90 /local/mail/access
prompt> grep 123.456 /local/mail/access
123.456 550 Sorry, no access for this domain
|
This particular result would indicate that the domain from
which your correspondent sends e-mail has at some time been
the source of SPAMming against WAM/Glue. It might have
nothing to do with your particular correspondent, or may no
longer be a problem.
If you want to have this status re-considered, contact
postmaster@wam.umd.edu.
If you want help with the analysis of the problem, please
contact the Office of Information Technology (OIT) Help Desk.
|
