For example, consider the following abstract from an access database:
To:postmaster@ OK
From:larry@ REJECT
Connect:spammer.domain REJECT
Withth e FEATURE(delay_checks) enabled, the first check will come as part of the
SMTP RCPT To: command, and that address will be looked up in the access database.
In this example, if the user part of the recipient address is postmaster, the message
will be accepted* by the current calling rule set. Subsequent rule sets can still reject it.
If the user part of the envelope-sender address is not postmaster, the address given to
the earlier SMTP MAIL From: command will be looked up. If that envelope-sender
address has a user part that is larry (in our example) the message will be rejected, but
because it is too late to reject the SMTP MAIL From:, the rejection will be given to the
SMTP RCPT To: command.
If the envelope sender is OK, the name of the connecting host will be looked up. If
the host is found in the access database, and if the righthand side is REJECT, the
message is rejected and the error will be reported in reply to the SMTP RCPT To: command.
If the host is found in the access database, and if the righthand side is RELAY,
the message is allowed to be relayed. If the host is not found, and if no other relaying
is allowed, the message will not be allowed to be relayed and the denial-of-relay
error, if any, will be reported in reply to the SMTP RCPT To: command.
Pages:
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529