Phil:
Thanks for your reply. The following router is present in my default
exim.conf:
# This router routes to remote hosts over SMTP by explicit IP address,
# given as a "domain literal" in the form [nnn.nnn.nnn.nnn]. The RFCs
# require this facility, which is why it is enabled by default in Exim.
# If you want to lock it out, set forbid_domain_literals in the main
# configuration section above.
#
# Literal Transports .. ignores verisigns sitefinder service
#
literal:
driver = ipliteral
domains = ! +local_domains
headers_add = "${perl{mailtrapheaders}}"
ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8 : 64.94.110.0/24
transport = remote_smtp
According to the specs,
http://www.us.exim.org/exim-html-4.20/doc/html/spec_14.html,
section 14, "Generic Options for Routers there is the "self" option.
******************paste**************************
self
Type: string
Default: freeze
This option applies to those routers which use the address to find a list of
remote hosts. Currently, these are the dnslookup, ipliteral, and manualroute
routers. Usually such routers are configured to send the message to a remote
host via an smtp transport. The self option specifies what happens when the
first host on the list turns out to be the local host (this is checked by
comparing IP addresses), or a host whose name matches hosts_treat_as_local.
Normally this situation indicates either an error in Exim's configuration (for
example, the router should be configured not to process this domain), or an
error in the DNS (for example, the MX should not point to this host). For this
reason, the default action is to log the incident, defer the address, and
freeze the message. The following alternatives are provided for use in special
cases:
*
defer
Delivery of the message is tried again later, but the message is not
frozen.
*
reroute: <domain>
The domain is changed to the given domain, and the address is passed back
to be reprocessed by the routers. No rewriting of headers takes place. This
behaviour is essentially a redirection.
*
reroute: rewrite: <domain>
The domain is changed to the given domain, and the address is passed back
to be reprocessed by the routers. Any headers that contain the original domain
are rewritten.
*
pass
The router passes the address to the next router, or to the router named
in the pass_router option if it is set. This overrides no_more.
During subsequent routing and delivery, the variable $self_hostname
contains the name of the local host that the router encountered. This can be
used to distinguish between different cases for hosts with multiple names. The
combination
self = pass
no_more
ensures that only those addresses that routed to the local host are
passed on. Without no_more, addresses that were declined for other reasons
would also be passed to the next router.
*
fail
Delivery fails and an error report is generated.
*
send
The anomaly is ignored and the address is queued for the transport. This
setting should be used with extreme caution. For an smtp transport, it makes
sense only in cases where the program that is listening on the SMTP port is not
this version of Exim. That is, it must be some other MTA, or Exim with a
different configuration file that handles the domain in another way.
**************************end paste**************************
Since the default is "freeze", I think this is what is happening on my
server. Question is, where to write the added text and which option is
safer? Pass, or send? Add to the end of the literal router text copied
above?
My goal is to enable delivery of emails to domain literal addressed mail
to an account (IP) on the server for testing. I do not plan to keep it
in place for an extended time.
Thanks for your help.
Greg Masters <[email protected]>
--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
