[exim] .forward invalid-to-line problem

Etusivu
Poista viesti
Vastaa
Lähettäjä: Martin Hierling
Päiväys:  
Vastaanottaja: exim-users
Aihe: [exim] .forward invalid-to-line problem
Hi List,

some curious problem, with my vacation .forward exim stuff:

pretty easy (if personal removed) .forward

---
# Exim filter
# Autoresponder
mail
to $reply_address
#to mad@???
subject "Re: ${substr{0}{20}{$header_subject:}}..."
file $home/vacation/message
once $home/vacation/once
log $home/vacation/log
---

with that "to" line enabled i get:

gtest@??? -> invalid-to-line
  transport = address_file
gtest@???
    <-- gtest@???
  router = localmdiruser, transport = local_md_delivery


and something like this in my log:
== invalid-to-line <gtest@???> R=userforward T=address_file
defer (-1): Mandatory file or directory option missing from address_file
transport

what kind of file? Debug looks like this:
exim -bt gtest@???
...
09:54:18  5980 --------> userforward router <--------
09:54:18  5980 local_part=gtest domain=cc.fh-luh.de
09:54:18  5980 checking for local user
09:54:18  5980 calling userforward router
09:54:18  5980 rda_interpret (file): ${home}/.forward
09:54:18  5980 expanding: ${home}/.forward
09:54:18  5980    result: /home/gtest/.forward
09:54:18  5980 expanded: /home/gtest/.forward
09:54:18  5980 search_tidyup called
09:54:18  5981 changed uid/gid: userforward router (recipient is
gtest@???)
09:54:18  5981   uid=2412 gid=143 pid=5981
09:54:18  5981   auxiliary group list: <none>
09:54:18  5981 turned off address rewrite logging (not root or exim in
this process)
09:54:18  5981 346 bytes read from /home/gtest/.forward
09:54:18  5981 data is an Exim filter program
09:54:18  5981 Filter: start of processing
09:54:18  5981 expanding: 0
09:54:18  5981    result: 0
09:54:18  5981 expanding: 20
09:54:18  5981    result: 20
09:54:18  5981 expanding: $header_subject:
09:54:18  5981    result: 
09:54:18  5981 expanding: Re: ${substr{0}{20}{$header_subject:}}...
09:54:18  5981    result: Re: ...
09:54:18  5981 expanding: $home/vacation/message
09:54:18  5981    result: /home/gtest/vacation/message
09:54:18  5981 expanding: $home/vacation/log
09:54:18  5981    result: /home/gtest/vacation/log
09:54:18  5981 expanding: $home/vacation/once
09:54:18  5981    result: /home/gtest/vacation/once
09:54:18  5981 Filter: mail to: mad@???
09:54:18  5981         subject: Re: ...
09:54:18  5981            file: /home/gtest/vacation/message
09:54:18  5981             log: /home/gtest/vacation/log
09:54:18  5981            once: /home/gtest/vacation/once
09:54:18  5981 Filtering did not set up a significant delivery.
09:54:18  5981 Normal delivery will occur.
09:54:18  5981 Filter: end of processing
09:54:18  5981 search_tidyup called
09:54:18  5980 rda_interpret: subprocess yield=1 error=NULL



with the second "to" line enabled:
gtest@??? -> mail mad@???
  transport = address_reply
gtest@???
    <-- gtest@???
  router = localmdiruser, transport = local_md_delivery


everything looks fine.

This homedir (also .forward) is shared via NFS to 2 Exim Stores with
some different exim versions and configs:

1st:
09:51:52 3392 Exim version 4.34 uid=2412 gid=143 pid=3392 D=ffffffff
Probably ndbm
Support for: iconv() PAM TCPwrappers OpenSSL
Lookups: lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz dnsdb
dsearch mysql nisplus passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp
Fixed never_users: 0

.forward is working completely!

2nd:
09:52:35 5826 Exim version 4.60 uid=0 gid=1 pid=5826 D=fffdffff
Probably ndbm
Support for: crypteq iconv() PAM TCPwrappers OpenSSL Content_Scanning
Old_Demime
Lookups: lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz dnsdb
dsearch nisplus passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp
Fixed never_users: 0

.forward is NOT working, as described above.

Any help is appreciated,

regards Martin

--
----------------------------------------------------------------
He's ALIVE, Jim. Where did I go wrong?
----------------------------------------------------------------