[exim] [bug2638] retry database / first failed doesn't corre…

Αρχική Σελίδα
Delete this message
Reply to this message
Συντάκτης: grin
Ημερομηνία:  
Προς: exim-users
Αντικείμενο: [exim] [bug2638] retry database / first failed doesn't correlate with logs: success recorded as failure, result retry times exceeded
Hello!

Is there anyone with a good idea about bug#2638?

Basically retry thinks there was a failure a week ago, while according
to log ther was one failure and later a succes, multiplied by
reicipients and MXes.

exinext says:
  Route: xxx@???:<xxx@???> error -44: H=secure500.t-systems.com [94.100.254.155]: SMTP error from remote mail server after RCPT TO:<xxx@???>: 451 Now greylisted - pleas                       
    first failed: 19-Aug-2020 09:24:02
    last tried:   28-Aug-2020 12:53:30
    next try at:  28-Aug-2020 18:53:30
    past final cutoff time


Log says:
  2020-08-19 09:21:46 1k8IPn-005VSw-0Y <= xxx@??? H=...
  2020-08-19 09:21:50 1k8IPn-005VSw-0Y H=secure100.t-systems.com [46.29.101.2]: SMTP error from remote mail server after RCPT TO:<xxx@???>: 451 Now greylisted - please try again in five minutes.                              
  2020-08-19 09:21:50 1k8IPn-005VSw-0Y H=secure100.t-systems.com [46.29.101.2]: SMTP error from remote mail server after RCPT TO:<yyy@???>: 451 Now greylisted - please try again in five minutes.                            
  2020-08-19 09:21:50 1k8IPn-005VSw-0Y H=secure100.t-systems.com [46.29.101.2]: SMTP error from remote mail server after RCPT TO:<zzz@???>: 451 Now greylisted - please try again in five minutes.                            
  2020-08-19 09:24:00 1k8IPn-005VSw-0Y H=secure100.t-systems.com [217.150.155.10] Connection timed out
  2020-08-19 09:24:02 1k8IPn-005VSw-0Y => xxx@??? <xxx@???> R=dnslookup T=remote_smtp H=secure100.t-systems.com [217.150.155.12] X=TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256 CV=no DN="C=DE,O=Deutsche Telekom
Security GmbH,OU=Managed AntiSpam,ST=Schleswig-Holstein,L=Kiel,CN=*.mas.t-systems-service.com" K C="250- 67663 byte chunk, total 68894\\n250 OK id=1k8IS1-0003gU-RC" QT=2m19s DT=1s
  2020-08-19 09:24:02 1k8IPn-005VSw-0Y -> yyy@??? <yyy@???> R=dnslookup T=remote_smtp H=secure100.t-systems.com [217.150.155.12] X=TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256 CV=no DN="C=DE,O=Deutsche Tele
kom Security GmbH,OU=Managed AntiSpam,ST=Schleswig-Holstein,L=Kiel,CN=*.mas.t-systems-service.com" K C="250- 67663 byte chunk, total 68894\\n250 OK id=1k8IS1-0003gU-RC" QT=2m19s DT=1s
  2020-08-19 09:24:02 1k8IPn-005VSw-0Y -> zzz@??? <zzz@???> R=dnslookup T=remote_smtp H=secure100.t-systems.com [217.150.155.12] X=TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256 CV=no DN="C=DE,O=Deutsche Tele
kom Security GmbH,OU=Managed AntiSpam,ST=Schleswig-Holstein,L=Kiel,CN=*.mas.t-systems-service.com" K C="250- 67663 byte chunk, total 68894\\n250 OK id=1k8IS1-0003gU-RC" QT=2m19s DT=1s
  2020-08-19 09:24:02 1k8IPn-005VSw-0Y Completed QT=2m19s


The result is that the next time (on 28-Aug) all the mail get bounced
by retry timeout exceeded.

Thanks,
Peter