Hi Marc
>> Exim sees them@??? as being a local address so ignores the
>> acme.org.uk zone
>> file which specifies
>> @ IN MX 10 ibmr.btconnect.com.
>> and instead tries to expand to expand "${lookup{$local_part}
>> lsearch*{/etc/
>> domianmailredirects/$domain}}"
>
> Is acme.org.uk the real domain you're talking about? If not,
> please read:
> http://www.exim.org/eximwiki/MailingListEtiquette#head-
> a6f7fb5ce8816568569a321f783315207ec38063
acme.org.uk is our client, and the domain we can't send to,
embarrassingly enough...
> Regardless, virtual domains aren't part of the default config, and
> the solution to your problem really depends on how you've
> configured them. So we'll need to see the routers involved.
>
> If you have trouble figuring out what those are, you can send your
> entire config file.
>
> You should also take a look at how Exim thinks it should route your
> message; this might give you some insight into what the problem
> is. To look at that, run:
>
> exim -d -bt them@???
I ran this without the -d which got me as far working out it was a
local vs external problem, then got stuck...
lookup yielded:
acme.org.uk in "lsearch;/etc/smtp_relay_from_domains"? yes (matched
"lsearch;/etc/smtp_relay_from_domains")
This is a LOT more informative, reading through the double dutch I
spotted that the domain was on my relay from domains list (I
automatically add new domains to this without thinking since we
normally handle sending client's domain mail to pop accounts). So I
simply removed the domain and everything worked!
Thank you! Simple solution in the end.
Also thanks to Magnus for responding, you either of you are ever in
London I'll stand ya a pint...
J
