-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 07.09.2014 um 13:22 schrieb Jeremy Harris: >> The mainlog shows delivery of the mail: > > >> >> 2014-09-04 03:23:10 1XPLlL-0001GW-6S >> [email protected] >> R=domain_smart_route T=remote_smtp H=remote.domain.de [XXX] >> C="250 2.6.0 >> <d5c8f9b36700c60b7c929bb4cf95d6528f5f1a629288305f-74616e87f3c647681c024ad865706...@email.xxx.cl> >> >> > >> >> [InternalId=458] Queued mail for delivery" >> 2014-09-04 03:23:10 1XPLlL-0001GW-6S <= [email protected] >> H=XXX.domain.cl [XXX] P=esmtp S=6566 >> id=d5c8f9b36700c60b7c929bb4cf95d6528f5f1a629288305f-74616e87f3c647681c024ad865706...@domain.cl >> >> > >> >> for [email protected] >> 2014-09-04 03:23:10 1XPLlL-0001GW-6S Completed >> >> +++ 1XPLlL-0001GW-6S has not completed +++ 2014-09-04 03:23:11 >> 1XPLlL-0001GW-6S => [email protected] R=domain_smart_route >> T=remote_smtp H=remote.domain.de [XXX] C="250 2.6.0 >> <d5c8f9b36700c60b7c929bb4cf95d6528f5f1a629288305f-74616e87f3c647681c024ad865706...@email.domain.cl> >> >> > >> >> [InternalId=459] Queued mail for delivery" >> 2014-09-04 03:23:11 1XPLlL-0001GW-6S failed to unlink >> /var/spool/exim4/msglog/L/1XPLlL-0001GW-6S: No such file or >> directory > > To clarify - this was all in mainlog?
Yes, it is. In paniclog are only these two lines: # exigrep 1XPLlL-0001GW-6S paniclog* +++ 1XPLlL-0001GW-6S has not completed +++ 2014-09-04 03:23:11 1XPLlL-0001GW-6S failed to unlink /var/spool/exim4/msglog/L/1XPLlL-0001GW-6S: No such file or directory > If so, you also got a duplicate delivery, done within a couple of > seconds. How often are your queue-runners ticking? Are you doing > anything nonstandard to run the queue? The customer did not complain about double delivery.:-) The queue runner is only startet from the deamonized exim process: /usr/local/bin/exim -bd -q30m No start from cron. > > I'm having trouble tracing the source that produces "+++ > 1XPLlL-0001GW-6S has not completed +++" > We have round about 150-300 cutthrough-deliveries per day, but only 1-3 "failed to unlink" messages in paniclog. Until now, I have no idea how to reproduce the error. - -- Regards, Kerstin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iNwEAQECAAYFAlQOt3AACgkQPPx5/A6Q3ckfrAX/Xuon66r/HXWY85FS51EQzJel swPPMY8/9yrLZMk9ZxJ8NCBxfXtFFa6MAcU/9LyNnShQC0qHEuPoDFbxmV7CVuiz HKLHioBh63mu7r+FlPK5iJ2TTPn/ITi3aQ7kK1JAaJDcylbzerMZ0ShaGrvrqWKD wq2pqKD/d69eSnWd/LED3O1RKZYbNNfw8qce2dokLSKpFnbCGBx0LPT8UZbqxxT1 YEMnqtrDrC32lDGV+vhejYRyl6RlCB7YU7hqjhfx =uYSu -----END PGP 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/
