This ends up just being my silliness.  The running configuration file is 
not in the default location, so the command line (in which I did not 
specify a configuration file) picked up the configuration file from the 
default location (/usr/local/exim), which off course did not have any of 
my changes in.



Sent by:        [email protected]
To:     [email protected]
cc:     [email protected], John Jetmore <[email protected]> 
Subject:        Re: [exim] forwarding router
LSN: Not Relevant - Not Privileged
User Filed as: Excl/AdminMgmt-14-4/QA:N/A

Here is some output from running the command (below).  It looks like to 
goes straight to the dnslookup router...

exim -d -M <message id>

=================================================================

recipients_count=1
body_linecount=1 message_linecount=12
Delivery address list:
  [email protected]
locking /var/spool/exim/db/retry.lockfile
locked /var/spool/exim/db/retry.lockfile
EXIM_DBOPEN(/var/spool/exim/db/retry)
returned from EXIM_DBOPEN
opened hints database /var/spool/exim/db/retry: flags=O_RDONLY
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Considering: [email protected]
unique = [email protected]
dbfn_read: key=R:ocrwm.doe.gov
dbfn_read: key=R:[email protected]
dbfn_read: key=R:[email protected]:<[email protected]>
no domain retry record
no address retry record
[email protected]: queued for routing
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
routing [email protected]
--------> dnslookup router <--------
local_part=dan.test domain=ocrwm.doe.gov
checking domains
ocrwm.doe.gov in "@"? no (end of list)
ocrwm.doe.gov in "! +local_domains"? yes (end of list)
calling dnslookup router
dnslookup router called for [email protected]
  domain = ocrwm.doe.gov
DNS lookup of ocrwm.doe.gov (MX) succeeded




Sent by:        [email protected]
To:     John Jetmore <[email protected]>
cc:     [email protected] (bcc: Dan Mitton/YD/RWDOE)
Subject:        Re: [exim] forwarding router
LSN: Not Relevant - Not Privileged
User Filed as: Excl/AdminMgmt-14-4/QA:N/A

John,

I'm running as 'root' and the file is at to rw-r--r--



Sent by:        [email protected]
To:     [email protected]
cc:     [email protected] 
Subject:        Re: [exim] forwarding router
LSN: Not Relevant - Not Privileged
User Filed as: Excl/AdminMgmt-14-4/QA:N/A

On Thu, Jul 22, 2010 at 11:14 AM,  <[email protected]> wrote:
> I am trying to forward a large number of users mails to a variety of new
> addresses.  I was thinking I could do this with a redirect router
> (below)...
>
> my_forward_router:
>        driver               = redirect
>        data                 = ${lookup{$local_p...@$domain}
> nwildlsearch{my.forward}}
>
> This seems to work, unless a delivery is deferred, for example...
>
> R=dnslookup T=remote_smtp defer (-53): retry time not reached for any 
host
>
> and then a forced retry is done using the -M <message id> or -R <string>
> command line commands.  When this happens, the message is delivered to 
the
> un-forwarded address.
>
> What am I missing?  It seems like it is skipping my redirect router the
> second time through.

Is it possible you're running the -M command as an "admin user" and
that user doesn't have the permissions to open the file containing the
forward lookups?

-- 
## 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/


-- 
## 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/


-- 
## 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/


-- 
## 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/

Reply via email to