forward files.
This last example underscores a weakness in this FEATURE(compat_check). Because
eachenvelope recipient undergoes aliases translation, and ~/.forward translation
before the lookup, the entry in the access database must correctly represent the translated
address. For example, consider a pseudouser named nill who has an aliases file
entry such as this:
# deep six mail to nill
nill: /dev/null
Here, the intention is to have all mail to nill delivered to the /dev/null file. If you
wanted selected mail to nill to be rejected, do not do this:
Compat:user@other.domain<@>nill@your.site ERROR:553 Don't mail to nill
?†‘
note
The nill@your.site will never be found because by the time this lookup happens, nill
has been transformed into /dev/null. The correct way to set up your access database
to handle this situation would look like this:
Compat:user@other.domain<@>/dev/null ERROR:553 Don't mail to nill
?†‘
note
Also note that when the recipient is an actual user (as, for example, bob):
Compat:user@other.domain<@>bob@your.site ERROR:553 Don't mail to bob
bob can alter his ~/.forward file at any time, thus rendering his recipient entry useless.
This is the Title of the Book, eMatter Edition
Copyright ?© 2007 O??™Reilly & Associates, Inc. All rights reserved.
290 | Chapter 7: How to Handle Spam
7.5.8 Screen by domain and .
Pages:
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537