9.13 on page 809).
If you wishto add your own rules to the tls_rcpt rule set, you can do so withth e following
mc configuration command:
LOCAL_TLS_RCPT
?†? additional rules for tls_rcpt here
If your rules return a #error or #discard delivery agent, the connection is rejected. If
they return a $#OK,* the connection is accepted and subsequent tls_rcpt rule set rules
are skipped (the access database lookups are not performed):
R $* $# OK skip subsequent tls_rcpt rule set rules
But if they return a $@OK, further tls_rcpt rule set rules are allowed, and the access
database lookups are performed, which might subsequently reject the connection:
R $* $@ OK allow subsequent tls_rcpt rule set rules
Your rules, if any, will be called first. That is, for example, if you add rules to tls_
rcpt, those rules will be called before those that were already in the tls_rcpt rule set.
You need not restore the workspace at the end of your rules, however, because that
restoration is taken care of for you.
5.3.8.4 Disable STARTTLS with the try_tls rule set
By default, STARTTLS is used whenever possible. Unfortunately, some hosts on the
Internet do not properly implement STARTTLS, so even though they offer STARTTLS,
they don??™t use it properly and the connection fails. If you know ahead of time
which hosts have this problem, you can list them in the access database and cause
STARTTLS to be skipped for them.
Pages:
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413