Marc...If you are trying to accuse me of not reading documentation...You are
just wrong...get over it...I read all of the documentation that I knew
existed...
I did not realize that you could "man" each section...that would be some
helpfull information...that is a great example of what you could have said
from the beginning...
"Wes...take a look at what comes up when you run this from the console:
man hubbed_hosts"
2 lines, and this could have been over...I think you need some anger
management.
The README.Debian that I READ pointed me to section 20 of the spec...THAT I
READ, and it talked all about adding a route-list, or route_data...WHICH I
TRIED...when it didn't work, I asked a question...which, according to you is
the beginning of wisdom.
Now...for anyone else who is interested, I added this to the (working!)
default config:
dnslookup_relay_to_domains:
debug_print = \
"R: dnslookup_relay_to_domains for
$local_part@$domain(Nowmanualroute...Wes Carver 12_21_06)"
driver = manualroute
domains = +relay_to_domains
route_list = * 10.10.5.21
transport = remote_smtp
same_domain_copy_routing = yes
no_more
I did it this way because it seemed to more accurately match the situation I
am setting up, since these are the only domains I want to relay. (Debian box
inside of firewall)
This worked like a charm...Thanks Ian, and everyone else for your time.
On 12/21/06, Marc Haber <mh+exim-users@???> wrote:
>
> On Thu, 21 Dec 2006 10:42:27 -0500, "Wes Carver" <shadwsrch@???>
> wrote:
> >In the "domain" section of the hubbed_host router, it looks like there is
> a
> >test for a hubbed_hosts file...the test fails...
> >in output:
> >expansion of "${if
>
> >exists{/etc/exim4/hubbed_hosts}{partial-lsearch;/etc/exim4/hubbed_hosts}fail}"
> >forced failure: assume not in this list
> >
> >Why did this fail...there is no hubbed_hosts file in that folder...do I
> need
> >one?
>
> Yes, you do.
>
> Quoting from the man page:
> |/etc/exim4/hubbed_hosts
> | is an optional file containing a list of route_data records
> which can
> | be used to override or augment MX information
> from the DNS. This is
> | particularly useful for mail hubs which are highest-priority MX
> for a
> | domain in the DNS but are not final destination of the
> messages, pass-
> | ing them on to a host which is not publicly reachable, or to
> temporar-
> | ily fix mail routing in case of broken DNS setups.
> |
> | The file should contain key-value pairs
> of domain pattern and route
> | data of the form
> |
> | domain: host-list options
> | dict.ref.example: mail-1.ref.example:mail-2.ref.example
> | foo.example: internal.mail.example.com
> | bar.example: 192.168.183.3
> |
> | which will cause mail for foo.example to be sent to the host
> inter-
> | nal.mail.example (IP address derived from A
> record only), and mailto
> | bar.example to be sent to 192.168.183.3.
> |
> | See spec.txt chapter 20.3 through 20.7 for a more detailed
> explanation
> | of host list format and available options.
>
> If I understand your problem right, this is exactly what you need. And
> it is already there.
>
> Greetings
> Marc
>
> --
> -------------------------------------- !! No courtesy copies, please !!
> -----
> Marc Haber | " Questions are the | Mailadresse im Header
> Mannheim, Germany | Beginning of Wisdom " |
> http://www.zugschlus.de/
> Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834
>
> --
> ## List details at http://www.exim.org/mailman/listinfo/exim-users
> ## Exim details at http://www.exim.org/
> ## Please use the Wiki with this list - http://www.exim.org/eximwiki/
>
