Re: exim4 bearbeitet Mails zweimal
Hallo Clemens,
Dr. Clemens Hardewig, 30.10.2006 (d.m.y):
> Am Montag, 30. Oktober 2006 10:53 schrieb Christian Schmidt:
> > Dr. Clemens Hardewig, 29.10.2006 (d.m.y):
> >
> > Was sagt ein "exim4 -brt user1@localhost"?
> > Wie genau sieht Dein spamcheck_router aus?
> >
> > Gruss/Regards,
> > Christian Schmidt
>
> Hm - schon die Frage, was die Retry Rules damit zu tun haben könnten
Grmpff. Vergiss das "r". Ich meinte "exim -bt ...".
Aber hier geht es los:
> --------> spamcheck_router router <--------
> local_part=user1 domain=localhost
> checking for local user
> finduser used cached passwd data for user1
> checking "condition"
> calling spamcheck_router router
> spamcheck_router router called for user1@localhost
> domain = localhost
> set transport spamcheck
> queued for spamcheck transport: local_part = user1
> domain = localhost
> errors_to=NULL
> domain_data=NULL localpart_data=NULL
> routed by spamcheck_router router
> envelope to: user1@localhost
> transport: spamcheck
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> After routing:
> Local deliveries:
> user1@localhost
> Remote deliveries:
> Failed addresses:
> Deferred addresses:
> search_tidyup called
> >>>>>>>>>>>>>>>> Local deliveries >>>>>>>>>>>>>>>>
> --------> user1@localhost <--------
> locking /var/spool/exim4/db/retry.lockfile
> locked /var/spool/exim4/db/retry.lockfile
> opened hints database /var/spool/exim4/db/retry: flags=0
> dbfn_read: key=T:user1@localhost
> no retry record exists
> search_tidyup called
> changed uid/gid: local delivery to user1 <user1@localhost> transport=spamcheck
> uid=102 gid=102 pid=16952
> auxiliary group list: <none>
> home=/tmp current=/tmp
> set_process_info: 16952 delivering 1GecpX-0004J7-VY to user1 using spamcheck
> direct command:
> argv[0] = /usr/bin/spamc
> direct command after expansion:
> argv[0] = /usr/bin/spamc
> T: spamassassin_pipe for user1@localhost
> spamcheck transport entered
> direct command:
> argv[0] = /usr/sbin/exim4
> argv[1] = -oMr
> argv[2] = spam-scanned
> argv[3] = -bS
> direct command after expansion:
> argv[0] = /usr/sbin/exim4
> argv[1] = -oMr
> argv[2] = spam-scanned
> argv[3] = -bS
> set_process_info: 16954 reading output from |/usr/sbin/exim4 -oMr
> spam-scanned -
OK, hier bekommt Dein exim gesagt, dass der Spam-Check schon durch
ist.
> bS
> Writing message to pipe
> writing data block fd=9 size=0 timeout=3600
> writing data block fd=9 size=35 timeout=3600
> writing data block fd=9 size=28 timeout=3600
> writing data block fd=9 size=5 timeout=3600
> process 16955 running as transport filter: write=10 read=11
> process 16956 writing to transport filter
> writing data block fd=10 size=246 timeout=3600
> copying from the filter
> waiting for filter process
> waiting for writing process
> writing data block fd=9 size=520 timeout=3600
> end of filtering transport writing: yield=1
> writing data block fd=9 size=0 timeout=3600
> writing data block fd=9 size=2 timeout=3600
> spamcheck transport yielded 0
> search_tidyup called
> journalling user1@localhost
> spamcheck transport returned OK for user1@localhost
> post-process user1@localhost (0)
> user1@localhost delivered
> LOG: MAIN
> => user1 <user1@localhost> R=spamcheck_router T=spamcheck
> >>>>>>>>>>>>>>>> deliveries are done >>>>>>>>>>>>>>>>
> changed uid/gid: post-delivery tidying
> uid=102 gid=102 pid=16951
> auxiliary group list: <none>
> set_process_info: 16951 tidying up after delivering 1GecpX-0004J7-VY
> Processing retry items
> Succeeded addresses:
> user1@localhost: no retry items
> Failed addresses:
> Deferred addresses:
> end of retry processing
> LOG: MAIN
> Completed
> end delivery of 1GecpX-0004J7-VY
> search_tidyup called
> search_tidyup called
> >>>>>>>>>>>>>>>> Exim pid=16951 terminating with rc=0 >>>>>>>>>>>>>>>>
Bisher sehe ich aber nur einen Durchlauf des SpamAssassin...
> und nun wirds interessant: im /var/log/exim4/mainlog (=LOG: MAIN) steht
> wieder:
> 2006-10-30 20:31:14 1GecpX-0004J7-VY <= root@domain.com U=root P=local S=246
> 2006-10-30 20:31:19 1Gecqo-0004PR-Vh <= root@domain.com U=Debian-exim
> P=spam-scanned S=664 id=E1GecpX-0004J7-VY@server.domain.com
> 2006-10-30 20:31:19 1Gecqo-0004PR-Vh => user1 <user1@localhost> R=local_user
> T=cyrus_delivery
> 2006-10-30 20:31:19 1Gecqo-0004PR-Vh Completed
> 2006-10-30 20:31:19 1GecpX-0004J7-VY => user1 <user1@localhost> R=spamcheck_
> router T=spamcheck
> 2006-10-30 20:31:19 1GecpX-0004J7-VY Completed
>
> und da sinds dann wieder zwei: 1GecpX-0004J7-VY und 1Gecqo-0004PR-Vh. Die -Vh
> taucht aber in den debug infos von exim4 gar nicht auf! Wo kann die also
> herkommen?
Keine Ahnung. Ist da irgendwo eine "unseen"-Option in den Routern
definiert?
Gruss,
Christian Schmidt
--
Christian Schmidt | Germany
No HTML Mails, please!
Reply to: