| 1 |
# The "mailer table" can be used to override routing for particular domains |
| 2 |
# (which are not in class {w}, i.e. local host names). |
| 3 |
# |
| 4 |
# hash /etc/mail/mailertable |
| 5 |
# |
| 6 |
# Keys in this database are fully qualified domain names or partial domains |
| 7 |
# preceded by a dot -- for example, "vangogh.CS.Berkeley.EDU" or |
| 8 |
# ".CS.Berkeley.EDU". As a special case of the latter, "." matches any domain |
| 9 |
# not covered by other keys. Values must be of the form: |
| 10 |
# |
| 11 |
# mailer:domain |
| 12 |
# |
| 13 |
# where "mailer" is the internal mailer name, and "domain" is where to send |
| 14 |
# the message. These maps are not reflected into the message header. As a |
| 15 |
# special case, the forms: |
| 16 |
# |
| 17 |
# local:user |
| 18 |
# |
| 19 |
# will forward to the indicated user using the local mailer, |
| 20 |
# |
| 21 |
# local: |
| 22 |
# |
| 23 |
# will forward to the original user in the e-mail address using the local |
| 24 |
# mailer, and |
| 25 |
# |
| 26 |
# error:code message |
| 27 |
# error:D.S.N:code message |
| 28 |
# |
| 29 |
# will give an error message with the indicated SMTP reply code and message, |
| 30 |
# where D.S.N is an RFC 1893 compliant error code. |