[exim-dev] [Bug 2638] New: retry database / first failed doe…

Page principale
Supprimer ce message
Répondre à ce message
Auteur: admin
Date:  
À: exim-dev
Nouveaux-sujets: [exim-dev] [Bug 2638] retry database / first failed doesn't correlate with logs: success recorded as failure, result retry times exceeded, [exim-dev] [Bug 2638] retry database / first failed doesn't correlate with logs: success recorded as failure, result retry times exceeded, [exim-dev] [Bug 2638] retry database / first failed doesn't correlate with logs: success recorded as failure, result retry times exceeded
Sujet: [exim-dev] [Bug 2638] New: retry database / first failed doesn't correlate with logs: success recorded as failure, result retry times exceeded
https://bugs.exim.org/show_bug.cgi?id=2638

            Bug ID: 2638
           Summary: retry database / first failed doesn't correlate with
                    logs: success recorded as failure, result retry times
                    exceeded
           Product: Exim
           Version: 4.92
          Hardware: x86
                OS: Linux
            Status: NEW
          Severity: bug
          Priority: medium
         Component: Routing
          Assignee: unallocated@???
          Reporter: grin@???
                CC: exim-dev@???


Similar to (but not the same as) #463 or #636.

The main difference is that I have a difference between the logs and the hints,
also I have no special retry rules.

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


However the specific logs tell me:
  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


So it does not seem to be failed at "first failed" time.


On "last tried" it was showing my reported problem: exim tried to deliver,
again, and 5 MX responded 451 for all the recipients (5x4=20 times in total),
and then I got what I didn't want to:
  2020-08-25 15:26:47 1kAYy7-00B0GU-8s ** xxx@???: retry timeout exceeded
  2020-08-25 15:26:47 1kAYy7-00B0GU-8s ** yyy@???: retry timeout exceeded
  2020-08-25 15:26:47 1kAYy7-00B0GU-8s ** ppp@???: retry timeout exceeded
  2020-08-25 15:26:47 1kAYy7-00B0GU-8s ** xxx@???: retry timeout exceeded
  2020-08-25 15:26:47 1kAYyN-00B0ok-Im <= <> R=1kAYy7-00B0GU-8s U=Debian-exim
P=local S=4708 T="Mail delivery failed/A level nem kezbesitheto : returning
message to sender/vissza a feladonak"                                           
  2020-08-25 15:26:47 1kAYy7-00B0GU-8s Completed QT=16s


Clearly "first failed" was long time ago, but since it was a success there
weren't any non-failed deliveries (nor retries) since, so the current 4xx
immediately got cutoff and bounced.


I have no special retry rules (apart from changed times):
exim4 -brt xxx@???
Retry rule: * * F,12h,15m; G,16h,1h,1.5; F,4d,6h;

--
You are receiving this mail because:
You are on the CC list for the bug.