Verisign idiocy confusion {Scanned by HJMS}

[Dan Farmer]

It's a sendmail thing, and I think the default behavior is to not allow
unresolvable domains.

Look for the rule SLocal_check_mail in your sendmail.cf file.

If it's properly working you should see lines like this in your log
files: (grep for check_mail or 553 5.1.8)

Sep 14 22:06:58 ocs2 sendmail[27101]: h8F46ws27101: ruleset=check_mail,
arg1=<rsstftrnes at rb194cc.com>, relay=verticalsmile.verticalsmiles.net
[216.15.169.214] (may be forged), reject=553 5.1.8
<rsstftrnes at rb194cc.com>... Domain of sender address
rsstftrnes at rb194cc.com does not exist

dan

On Wednesday, September 17, 2003, at 04:20  PM, Kevin Miller wrote:

> I thought I had that enabled, but I just went to double check and can't
> recall where it's set (looked in both MS and sendmail).  Where do we
> set
> that option so that when normalacy is restored it'll work again?
>
> Also, how did you quantify the amount of mail it was catching and
> rejecting?
>
> TIA...
>
> ...Kevin
> -------------------
> Kevin Miller                Registered Linux User No: 307357
> CBJ MIS Dept.               Network Systems Administrator, Mail
> Administrator
> 155 South Seward Street     ph: (907) 586-0242
> Juneau, Alaska 99801        fax: (907 586-4500
>
>
>> This change prevents you from being able to identify
>> non-existant domains
>> under .com.  Blocking mail from domains that don't have valid
>> DNS records is
>> a very effective way of reducing both spam and bounces that you cannot
>> notify anyone about.
>>
>> In fact until yesterday that one check blocked more bad email
>> on my systems
>> than mailscanner tagged as spam.  The impact is that a lot
>> more mail will
>> get through, including spam, even though that mail cannot possibly be
>> responded to electronically (since the domain has no valid dns
>> records for
>> use in returning the message or notifying the domain's admin of a
>> misconfiguration).
>>
>