On 2015-10-05, Ian Eiloart <i...@sussex.ac.uk> wrote: > >> On 5 Oct 2015, at 13:19, Yan Seiner <y...@seiner.com> wrote: >> >> On 10/5/2015 7:53 AM, Ian Eiloart wrote: >>> Yes, but it may not be the filters that are at fault. It looks like your >>> router isn’t being inspected. If an earlier router handles the message, >>> then your filter won’t be run. Pipe a known message into Exim, and use >>> -d+all >> Hers's a dump of -d+all: >> >> http://seiner.com/exim_debug.log >> >> Thanks. > > Hmm, well not many clues here, except that the router is completely bypassed: > > 05:07:13 22126 --------> userforward router <-------- > 05:07:13 22126 local_part=yan domain=seiner.com > 05:07:13 22126 userforward router skipped: verify 2 0 0 > > It looks to me like there may be two problems in your router: > > require_files = $local_part:$home/.forward > > Which might be intended to say require_files = $home/.forward or > require_files = /home/$local_part/.forward > > Also, > "syntax_errors_to = real-$local_part@$domain" > > I know that’s directly from the docs, but I think that should NOT point to > your email address: you’ll get a warning for every warning message that’s > sent. Recursively, I think. And that will soon add up. The warning should > probably go to postmaster, or some such address. Perhaps the "real-" was > added to the docs to stop people shooting themselves in the foot by copying > directly!
No, it's safe - by that path you end up at the real_local router and then at transport which has errors-to turned off. -- \_(ツ)_ -- ## List details at https://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/
