Lines Matching refs:MX
454 a variant on SMTP) is used. WARNING: if you have a wildcard MX
962 lists us as the best possible MX record. This generates
968 WILDCARD MX RECORDS!!! If you have a wildcard MX record
1008 Turns on the ability to allow relaying based on the MX
1010 is, if an MX record for host foo.com points to your site,
1059 MX record in DNS). If you are inside a firewall that has
1276 e-mails to. Note that MX records will be used if the
1402 resolves to a "bad" MX record. By default these are
1403 MX records which resolve to A records that match the
1534 via MX records. For example, you might have:
1539 You would use this if you had installed an MX record for cnmat.Berkeley.EDU
2101 the mail to MX records listed for the host eng.example.com (unless the
2110 This would relay mail for harry@example.com to the MX records listed for
2121 the machine server.example.com's MX servers and deliver to the address
2168 You can also allow relaying based on the MX records of the host
2174 and domain.com lists your server in its MX records, the mail will be
2176 if MX lookups for the recipient domain are slow or time out. In that
2181 as a relay for their site (that is, they set up an MX record pointing
2887 If the domain has multiple MX servers, e.g.,
2889 secure.domain. IN MX 10 mail.secure.domain.
2890 secure.domain. IN MX 50 mail.other.domain.
3177 In some cases you may want to temporarily turn off MX records,
3178 particularly on gateways. For example, you may want to MX
3182 *.domain. IN MX 0 relay.machine
3188 The [square brackets] turn off MX records for this host only.
3189 If you didn't do this, the mailertable would use the MX record
3190 again, which would give you an MX loop. Note that the use of
3191 wildcard MX records is almost always a bad idea. Please avoid
3610 confFALLBACK_MX FallbackMXhost [undefined] Fallback MX host.
3613 confTRY_NULL_MX_LIST TryNullMXList [False] If this host is the best MX
3942 zero, the initial MX lookups on