Re: [exim] .forward being ignored
On 2015-10-05, Ian Eiloart wrote: > >> On 5 Oct 2015, at 13:19, Yan Seiner 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/
Re: [exim] .forward being ignored
Yan Seiner (Mo 05 Okt 2015 14:19:00 CEST):
> 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
I may be wrong, but I think, you did the testing with 'exim … -bv
', didn't you?
Please do the testing with
exim -bt
instead(!) of using -bv, "-bv" switches Exim to address verification
mode. Your debug log indicates that the user_forward router was skipped
because Exim is in verification mode!
> userforward router <
05:07:13 22126 local_part=yan domain=seiner.com
05:07:13 22126 userforward router skipped: verify 2 0 0
Best regards from Dresden/Germany
Viele Grüße aus Dresden
Heiko Schlittermann
--
SCHLITTERMANN.de internet & unix support -
Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
gnupg encrypted messages are welcome --- key ID: F69376CE -
! key id 7CBF764A and 972EAC9F are revoked since 2015-01 -
signature.asc
Description: Digital signature
--
## 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/
Re: [exim] .forward being ignored
Ian Eiloart (Mo 05 Okt 2015 15:18:49 CEST):
> 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!
The real- prefix is used by the next router in the docs, the
real_localuser router. This avoids circulating the error messages.
Best regards from Dresden/Germany
Viele Grüße aus Dresden
Heiko Schlittermann
--
SCHLITTERMANN.de internet & unix support -
Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
gnupg encrypted messages are welcome --- key ID: F69376CE -
! key id 7CBF764A and 972EAC9F are revoked since 2015-01 -
signature.asc
Description: Digital signature
--
## 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/
Re: [exim] .forward being ignored
> On 5 Oct 2015, at 13:19, Yan Seiner 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! -- Ian Eiloart Postmaster, University of Sussex +44 (0) 1273 87-3148 -- ## 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/
Re: [exim] .forward being ignored
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. -- ## 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/
Re: [exim] .forward being ignored
> On 5 Oct 2015, at 12:30, Yan Seiner wrote: > > > On 10/5/2015 6:40 AM, Jeremy Harris wrote: >> On 05/10/15 11:31, Yan Seiner wrote: >>> I am running Exim 4.82. It works, except that my .forward file is being >>> ignored. It tests fine, and when I feed it manually it works. >> [...] >>> But exim ignores it. >> Show a debug run of a test mail, with it being ignored. > > I ran it with -d-all+filter which should just debug the filters, right? > (Sorry, I'm not that familiar with exim; it "just works" so I don't get to > work with it much. 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 -- Ian Eiloart Postmaster, University of Sussex +44 (0) 1273 87-3148 -- ## 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/
Re: [exim] .forward being ignored
On 05/10/15 12:30, Yan Seiner wrote: > > > On 10/5/2015 6:40 AM, Jeremy Harris wrote: >> On 05/10/15 11:31, Yan Seiner wrote: >>> I am running Exim 4.82. It works, except that my .forward file is being >>> ignored. It tests fine, and when I feed it manually it works. >> [...] >>> But exim ignores it. >> Show a debug run of a test mail, with it being ignored. > > I ran it with -d-all+filter which should just debug the filters, right? It does, but that's not what we want, which is to see the relationship to the routing actions. -- Cheers, Jeremy -- ## 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/
Re: [exim] .forward being ignored
On 10/5/2015 6:40 AM, Jeremy Harris wrote: On 05/10/15 11:31, Yan Seiner wrote: I am running Exim 4.82. It works, except that my .forward file is being ignored. It tests fine, and when I feed it manually it works. [...] But exim ignores it. Show a debug run of a test mail, with it being ignored. I ran it with -d-all+filter which should just debug the filters, right? (Sorry, I'm not that familiar with exim; it "just works" so I don't get to work with it much. root@selene:/etc/default# /etc/init.d/exim4 start * Starting MTA Exim version 4.82 uid=0 gid=0 pid=18323 D=200 Berkeley DB: Berkeley DB 5.3.28: (September 9, 2013) Support for: crypteq iconv() IPv6 PAM Perl Expand_dlfunc GnuTLS move_frozen_mess ages Content_Scanning DKIM Old_Demime Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz dbm nz dnsdb dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql sqlite Authenticators: cram_md5 cyrus_sasl dovecot plaintext spa Routers: accept dnslookup ipliteral iplookup manualroute queryprogram redirect Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp Fixed never_users: 0 Size of off_t: 8 Compiler: GCC [4.8.2] Library version: GnuTLS: Compile: 2.12.23 Runtime: 2.12.23 Library version: Cyrus SASL: Compile: 2.1.25 Runtime: 2.1.25 [Cyrus SASL] Library version: PCRE: Compile: 8.31 Runtime: 8.31 2012-07-06 Library version: MySQL: Compile: 5.5.35 [(Ubuntu)] Runtime: 5.5.44 Library version: SQLite: Compile: 3.8.2 Runtime: 3.8.2 WHITELIST_D_MACROS: "OUTGOING" TRUSTED_CONFIG_LIST: "/etc/exim4/trusted_configs" configuration file is /var/lib/exim4/config.autogenerated log selectors = 0ffc 00632001 cwd=/etc/default 8 args: /usr/sbin/exim4 -bd -q30m -d-all+filter -oX 25:587 -oP /var/run/exim4/exim.pid trusted user admin user 18323 daemon_smtp_port overridden by -oX: 18323 <: 25: 587 18323 listening on all interfaces (IPv6) port 25 18323 listening on all interfaces (IPv4) port 25 18323 listening on all interfaces (IPv6) port 587 18323 listening on all interfaces (IPv4) port 587 18323 pid written to /var/run/exim4/exim.pid 18323 LOG: MAIN 18323 exim 4.82 daemon started: pid=18323, -q30m, listening for SMTP on port 2 5 (IPv6 and IPv4) port 587 (IPv6 and IPv4) 18323 daemon running with uid=131 gid=139 euid=131 egid=139 18323 SIGALRM received 18323 1 queue-runner process running 18323 Listening... 18325 Starting queue-runner: pid 18325 18323 child 18325 ended: status=0x0 18323 normal exit, 0 18323 0 queue-runner processes now running 18323 Listening... 18323 Connection request from 216.16.230.210 port 61675 18323 1 SMTP accept process running 18323 Listening... 18347 Process 18347 is handling incoming connection from [216.16.230.210] 18347 Process 18347 is ready for new message 18347 trying server 127.0.0.1, port 783 18347 unspool_mbox(): unlinking '/var/spool/exim4/scan/1Zj3lC-0004lv-FY/1Zj3lC-0004lv-FY.eml' 18347 LOG: MAIN 18347 <= y...@seiner.com H=css.roadtrek.com ([10.10.31.31]) [216.16.230.210] P=esmtpsa X=TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128 A=plain_server:yan S=724 id=56125c21.7060...@seiner.com 18347 forked delivery process 18351 18347 Process 18347 is ready for new message 18351 Exim version 4.82 uid=131 gid=139 pid=18351 D=40200 Berkeley DB: Berkeley DB 5.3.28: (September 9, 2013) Support for: crypteq iconv() IPv6 PAM Perl Expand_dlfunc GnuTLS move_frozen_messages Content_Scanning DKIM Old_Demime Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz dbmnz dnsdb dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql sqlite Authenticators: cram_md5 cyrus_sasl dovecot plaintext spa Routers: accept dnslookup ipliteral iplookup manualroute queryprogram redirect Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp Fixed never_users: 0 Size of off_t: 8 Compiler: GCC [4.8.2] Library version: GnuTLS: Compile: 2.12.23 Runtime: 2.12.23 Library version: Cyrus SASL: Compile: 2.1.25 Runtime: 2.1.25 [Cyrus SASL] Library version: PCRE: Compile: 8.31 Runtime: 8.31 2012-07-06 Library version: MySQL: Compile: 5.5.35 [(Ubuntu)] Runtime: 5.5.44 Library version: SQLite: Compile: 3.8.2 Runtime: 3.8.2 WHITELIST_D_MACROS: "OUTGOING" TRUSTED_CONFIG_LIST: "/etc/exim4/trusted_configs" 18351 configuration file is /var/lib/exim4/config.autogenerated 18351 log selectors = 0ffc 00632001 18351 cwd=/var/spool/exim4 4 args: /usr/sbin/exim4 -d=0x40200 -Mc 1Zj3lC-0004lv-FY 18351 trusted user 18351 admin user 18347 LOG: smtp_connection MAIN 18347 SMTP connection from css.roadtrek.com ([10.10.31.31]) [216.16.230.210] closed by QUIT 18323 child
Re: [exim] .forward being ignored
On 05/10/15 11:31, Yan Seiner wrote: > I am running Exim 4.82. It works, except that my .forward file is being > ignored. It tests fine, and when I feed it manually it works. [...] > But exim ignores it. Show a debug run of a test mail, with it being ignored. -- Cheers, Jeremy -- ## 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/
