Import Debian changes 4.89-2+deb9u4
[hcoop/debian/exim4.git] / src / retry.c
CommitLineData
420a0d19
CE
1/*************************************************
2* Exim - an Internet mail transport agent *
3*************************************************/
4
2813c06e 5/* Copyright (c) University of Cambridge 1995 - 2015 */
420a0d19
CE
6/* See the file NOTICE for conditions of use and distribution. */
7
8/* Functions concerned with retrying unsuccessful deliveries. */
9
10
11#include "exim.h"
12
13
14
15/*************************************************
16* Check the ultimate address timeout *
17*************************************************/
18
19/* This function tests whether a message has been on the queue longer than
20the maximum retry time for a particular host or address.
21
22Arguments:
23 retry_key the key to look up a retry rule
24 domain the domain to look up a domain retry rule
25 retry_record contains error information for finding rule
26 now the time
27
28Returns: TRUE if the ultimate timeout has been reached
29*/
30
31BOOL
2813c06e 32retry_ultimate_address_timeout(uschar *retry_key, const uschar *domain,
420a0d19
CE
33 dbdata_retry *retry_record, time_t now)
34{
35BOOL address_timeout;
36
37DEBUG(D_retry)
38 {
39 debug_printf("retry time not reached: checking ultimate address timeout\n");
40 debug_printf(" now=%d first_failed=%d next_try=%d expired=%d\n",
41 (int)now, (int)retry_record->first_failed,
42 (int)retry_record->next_try, retry_record->expired);
43 }
44
45retry_config *retry =
46 retry_find_config(retry_key+2, domain,
47 retry_record->basic_errno, retry_record->more_errno);
48
49if (retry != NULL && retry->rules != NULL)
50 {
51 retry_rule *last_rule;
52 for (last_rule = retry->rules;
53 last_rule->next != NULL;
54 last_rule = last_rule->next);
55 DEBUG(D_retry)
56 debug_printf(" received_time=%d diff=%d timeout=%d\n",
57 received_time, (int)(now - received_time), last_rule->timeout);
58 address_timeout = (now - received_time > last_rule->timeout);
59 }
60else
61 {
62 DEBUG(D_retry)
63 debug_printf("no retry rule found: assume timed out\n");
64 address_timeout = TRUE;
65 }
66
67DEBUG(D_retry)
68 if (address_timeout)
69 debug_printf("on queue longer than maximum retry for address - "
70 "allowing delivery\n");
71
72return address_timeout;
73}
74
75
76
77/*************************************************
78* Set status of a host+address item *
79*************************************************/
80
81/* This function is passed a host_item which contains a host name and an
82IP address string. Its job is to set the status of the address if it is not
83already set (indicated by hstatus_unknown). The possible values are:
84
85 hstatus_usable the address is not listed in the unusable tree, and does
86 not have a retry record, OR the time is past the next
87 try time, OR the message has been on the queue for more
88 than the maximum retry time for a failing host
89
90 hstatus_unusable the address is listed in the unusable tree, or does have
91 a retry record, and the time is not yet at the next retry
92 time.
93
94 hstatus_unusable_expired as above, but also the retry time has expired
95 for this address.
96
97The reason a delivery is permitted when a message has been around for a very
98long time is to allow the ultimate address timeout to operate after a delivery
99failure. Otherwise some messages may stick around without being tried for too
100long.
101
102If a host retry record is retrieved from the hints database, the time of last
103trying is filled into the last_try field of the host block. If a host is
104generally usable, a check is made to see if there is a retry delay on this
105specific message at this host.
106
107If a non-standard port is being used, it is added to the retry key.
108
109Arguments:
110 domain the address domain
111 host pointer to a host item
112 portstring "" for standard port, ":xxxx" for a non-standard port
113 include_ip_address TRUE to include the address in the key - this is
114 usual, but sometimes is not wanted
115 retry_host_key where to put a pointer to the key for the host-specific
116 retry record, if one is read and the host is usable
117 retry_message_key where to put a pointer to the key for the message+host
118 retry record, if one is read and the host is usable
119
120Returns: TRUE if the host has expired but is usable because
121 its retry time has come
122*/
123
124BOOL
2813c06e 125retry_check_address(const uschar *domain, host_item *host, uschar *portstring,
420a0d19
CE
126 BOOL include_ip_address, uschar **retry_host_key, uschar **retry_message_key)
127{
128BOOL yield = FALSE;
129time_t now = time(NULL);
130uschar *host_key, *message_key;
131open_db dbblock;
132open_db *dbm_file;
133tree_node *node;
134dbdata_retry *host_retry_record, *message_retry_record;
135
136*retry_host_key = *retry_message_key = NULL;
137
138DEBUG(D_transport|D_retry) debug_printf("checking status of %s\n", host->name);
139
140/* Do nothing if status already set; otherwise initialize status as usable. */
141
142if (host->status != hstatus_unknown) return FALSE;
143host->status = hstatus_usable;
144
145/* Generate the host key for the unusable tree and the retry database. Ensure
146host names are lower cased (that's what %S does). */
147
148host_key = include_ip_address?
149 string_sprintf("T:%S:%s%s", host->name, host->address, portstring) :
150 string_sprintf("T:%S%s", host->name, portstring);
151
152/* Generate the message-specific key */
153
154message_key = string_sprintf("%s:%s", host_key, message_id);
155
156/* Search the tree of unusable IP addresses. This is filled in when deliveries
157fail, because the retry database itself is not updated until the end of all
158deliveries (so as to do it all in one go). The tree records addresses that have
159become unusable during this delivery process (i.e. those that will get put into
160the retry database when it is updated). */
161
162node = tree_search(tree_unusable, host_key);
163if (node != NULL)
164 {
165 DEBUG(D_transport|D_retry) debug_printf("found in tree of unusables\n");
166 host->status = (node->data.val > 255)?
167 hstatus_unusable_expired : hstatus_unusable;
168 host->why = node->data.val & 255;
169 return FALSE;
170 }
171
172/* Open the retry database, giving up if there isn't one. Otherwise, search for
173the retry records, and then close the database again. */
174
175if ((dbm_file = dbfn_open(US"retry", O_RDONLY, &dbblock, FALSE)) == NULL)
176 {
177 DEBUG(D_deliver|D_retry|D_hints_lookup)
178 debug_printf("no retry data available\n");
179 return FALSE;
180 }
181host_retry_record = dbfn_read(dbm_file, host_key);
182message_retry_record = dbfn_read(dbm_file, message_key);
183dbfn_close(dbm_file);
184
185/* Ignore the data if it is too old - too long since it was written */
186
187if (host_retry_record == NULL)
188 {
189 DEBUG(D_transport|D_retry) debug_printf("no host retry record\n");
190 }
191else if (now - host_retry_record->time_stamp > retry_data_expire)
192 {
193 host_retry_record = NULL;
194 DEBUG(D_transport|D_retry) debug_printf("host retry record too old\n");
195 }
196
197if (message_retry_record == NULL)
198 {
199 DEBUG(D_transport|D_retry) debug_printf("no message retry record\n");
200 }
201else if (now - message_retry_record->time_stamp > retry_data_expire)
202 {
203 message_retry_record = NULL;
204 DEBUG(D_transport|D_retry) debug_printf("message retry record too old\n");
205 }
206
207/* If there's a host-specific retry record, check for reaching the retry
208time (or forcing). If not, and the host is not expired, check for the message
209having been around for longer than the maximum retry time for this host or
210address. Allow the delivery if it has. Otherwise set the appropriate unusable
211flag and return FALSE. Otherwise arrange to return TRUE if this is an expired
212host. */
213
214if (host_retry_record != NULL)
215 {
216 *retry_host_key = host_key;
217
218 /* We have not reached the next try time. Check for the ultimate address
219 timeout if the host has not expired. */
220
221 if (now < host_retry_record->next_try && !deliver_force)
222 {
223 if (!host_retry_record->expired &&
224 retry_ultimate_address_timeout(host_key, domain,
225 host_retry_record, now))
226 return FALSE;
227
228 /* We have not hit the ultimate address timeout; host is unusable. */
229
230 host->status = (host_retry_record->expired)?
231 hstatus_unusable_expired : hstatus_unusable;
232 host->why = hwhy_retry;
233 host->last_try = host_retry_record->last_try;
234 return FALSE;
235 }
236
237 /* Host is usable; set return TRUE if expired. */
238
239 yield = host_retry_record->expired;
240 }
241
242/* It's OK to try the host. If there's a message-specific retry record, check
243for reaching its retry time (or forcing). If not, mark the host unusable,
244unless the ultimate address timeout has been reached. */
245
246if (message_retry_record != NULL)
247 {
248 *retry_message_key = message_key;
249 if (now < message_retry_record->next_try && !deliver_force)
250 {
251 if (!retry_ultimate_address_timeout(host_key, domain,
252 message_retry_record, now))
253 {
254 host->status = hstatus_unusable;
255 host->why = hwhy_retry;
256 }
257 return FALSE;
258 }
259 }
260
261return yield;
262}
263
264
265
266
267/*************************************************
268* Add a retry item to an address *
269*************************************************/
270
271/* Retry items are chained onto an address when it is deferred either by router
272or by a transport, or if it succeeds or fails and there was a previous retry
273item that now needs to be deleted. Sometimes there can be both kinds of item:
274for example, if routing was deferred but then succeeded, and delivery then
275deferred. In that case there is a delete item for the routing retry, and an
276updating item for the delivery.
277
278(But note that that is only visible at the outer level, because in remote
279delivery subprocesses, the address starts "clean", with no retry items carried
280in.)
281
282These items are used at the end of a delivery attempt to update the retry
283database. The keys start R: for routing delays and T: for transport delays.
284
285Arguments:
286 addr the address block onto which to hang the item
287 key the retry key
288 flags delete, host, and message flags, copied into the block
289
290Returns: nothing
291*/
292
293void
294retry_add_item(address_item *addr, uschar *key, int flags)
295{
296retry_item *rti = store_get(sizeof(retry_item));
2813c06e 297host_item * host = addr->host_used;
420a0d19
CE
298rti->next = addr->retries;
299addr->retries = rti;
300rti->key = key;
301rti->basic_errno = addr->basic_errno;
302rti->more_errno = addr->more_errno;
2813c06e
CE
303rti->message = host
304 ? string_sprintf("H=%s [%s]: %s", host->name, host->address, addr->message)
305 : addr->message;
420a0d19
CE
306rti->flags = flags;
307
308DEBUG(D_transport|D_retry)
309 {
310 int letter = rti->more_errno & 255;
311 debug_printf("added retry item for %s: errno=%d more_errno=", rti->key,
312 rti->basic_errno);
313 if (letter == 'A' || letter == 'M')
314 debug_printf("%d,%c", (rti->more_errno >> 8) & 255, letter);
315 else
316 debug_printf("%d", rti->more_errno);
317 debug_printf(" flags=%d\n", flags);
318 }
319}
320
321
322
323/*************************************************
324* Find retry configuration data *
325*************************************************/
326
327/* Search the in-store retry information for the first retry item that applies
328to a given destination. If the key contains an @ we are probably handling a
329local delivery and have a complete address to search for; this happens when
330retry_use_local_part is set on a router. Otherwise, the key is likely to be a
331host name for a remote delivery, or a domain name for a local delivery. We
332prepend *@ on the front of it so that it will match a retry item whose address
333item pattern is independent of the local part. The alternate key, if set, is
334always just a domain, so we treat it likewise.
335
336Arguments:
337 key key for which retry info is wanted
338 alternate alternative key, always just a domain
339 basic_errno specific error predicate on the retry rule, or zero
340 more_errno additional data for errno predicate
341
342Returns: pointer to retry rule, or NULL
343*/
344
345retry_config *
2813c06e 346retry_find_config(const uschar *key, const uschar *alternate, int basic_errno,
420a0d19
CE
347 int more_errno)
348{
2813c06e 349const uschar *colon = Ustrchr(key, ':');
420a0d19
CE
350retry_config *yield;
351
352/* If there's a colon in the key, there are two possibilities:
353
354(1) This is a key for a host, ip address, and possibly port, in the format
355
356 hostname:ip+port
357
2813c06e 358 In this case, we copy the host name.
420a0d19
CE
359
360(2) This is a key for a pipe, file, or autoreply delivery, in the format
361
362 pipe-or-file-or-auto:x@y
363
364 where x@y is the original address that provoked the delivery. The pipe or
365 file or auto will start with | or / or >, whereas a host name will start
366 with a letter or a digit. In this case we want to use the original address
367 to search for a retry rule. */
368
2813c06e
CE
369if (colon)
370 key = isalnum(*key)
371 ? string_copyn(key, colon-key) /* the hostname */
372 : Ustrrchr(key, ':') + 1; /* Take from the last colon */
420a0d19
CE
373
374/* Sort out the keys */
375
2813c06e
CE
376if (!Ustrchr(key, '@')) key = string_sprintf("*@%s", key);
377if (alternate) alternate = string_sprintf("*@%s", alternate);
420a0d19
CE
378
379/* Scan the configured retry items. */
380
381for (yield = retries; yield != NULL; yield = yield->next)
382 {
2813c06e
CE
383 const uschar *plist = yield->pattern;
384 const uschar *slist = yield->senders;
420a0d19
CE
385
386 /* If a specific error is set for this item, check that we are handling that
387 specific error, and if so, check any additional error information if
388 required. */
389
390 if (yield->basic_errno != 0)
391 {
392 /* Special code is required for quota errors, as these can either be system
393 quota errors, or Exim's own quota imposition, which has a different error
394 number. Full partitions are also treated in the same way as quota errors.
395 */
396
397 if (yield->basic_errno == ERRNO_EXIMQUOTA)
398 {
399 if ((basic_errno != ERRNO_EXIMQUOTA && basic_errno != errno_quota &&
400 basic_errno != ENOSPC) ||
401 (yield->more_errno != 0 && yield->more_errno > more_errno))
402 continue;
403 }
404
405 /* The TLSREQUIRED error also covers TLSFAILURE. These are subtly different
406 errors, but not worth separating at this level. */
407
408 else if (yield->basic_errno == ERRNO_TLSREQUIRED)
409 {
410 if (basic_errno != ERRNO_TLSREQUIRED && basic_errno != ERRNO_TLSFAILURE)
411 continue;
412 }
413
414 /* Handle 4xx responses to MAIL, RCPT, or DATA. The code that was received
415 is in the 2nd least significant byte of more_errno (with 400 subtracted).
416 The required value is coded in the 2nd least significant byte of the
417 yield->more_errno field as follows:
418
419 255 => any 4xx code
420 >= 100 => the decade must match the value less 100
421 < 100 => the exact value must match
422 */
423
424 else if (yield->basic_errno == ERRNO_MAIL4XX ||
425 yield->basic_errno == ERRNO_RCPT4XX ||
426 yield->basic_errno == ERRNO_DATA4XX)
427 {
428 int wanted;
429 if (basic_errno != yield->basic_errno) continue;
430 wanted = (yield->more_errno >> 8) & 255;
431 if (wanted != 255)
432 {
433 int evalue = (more_errno >> 8) & 255;
434 if (wanted >= 100)
435 {
436 if ((evalue/10)*10 != wanted - 100) continue;
437 }
438 else if (evalue != wanted) continue;
439 }
440 }
441
442 /* There are some special cases for timeouts */
443
444 else if (yield->basic_errno == ETIMEDOUT)
445 {
446 if (basic_errno != ETIMEDOUT) continue;
447
448 /* Just RTEF_CTOUT in the rule => don't care about 'A'/'M' addresses */
449 if (yield->more_errno == RTEF_CTOUT)
450 {
451 if ((more_errno & RTEF_CTOUT) == 0) continue;
452 }
453
454 else if (yield->more_errno != 0)
455 {
456 int cf_errno = more_errno;
457 if ((yield->more_errno & RTEF_CTOUT) == 0) cf_errno &= ~RTEF_CTOUT;
458 if (yield->more_errno != cf_errno) continue;
459 }
460 }
461
462 /* Default checks for exact match */
463
464 else
465 {
466 if (yield->basic_errno != basic_errno ||
467 (yield->more_errno != 0 && yield->more_errno != more_errno))
468 continue;
469 }
470 }
471
472 /* If the "senders" condition is set, check it. Note that sender_address may
473 be null during -brt checking, in which case we do not use this rule. */
474
475 if (slist != NULL && (sender_address == NULL ||
476 match_address_list(sender_address, TRUE, TRUE, &slist, NULL, -1, 0,
477 NULL) != OK))
478 continue;
479
480 /* Check for a match between the address list item at the start of this retry
481 rule and either the main or alternate keys. */
482
2813c06e 483 if (match_address_list(key, TRUE, TRUE, &plist, NULL, -1, UCHAR_MAX+1,
420a0d19 484 NULL) == OK ||
2813c06e
CE
485 (alternate != NULL &&
486 match_address_list(alternate, TRUE, TRUE, &plist, NULL, -1,
420a0d19
CE
487 UCHAR_MAX+1, NULL) == OK))
488 break;
489 }
490
420a0d19
CE
491return yield;
492}
493
494
495
496
497/*************************************************
498* Update retry database *
499*************************************************/
500
501/* Update the retry data for any directing/routing/transporting that was
502deferred, or delete it for those that succeeded after a previous defer. This is
503done all in one go to minimize opening/closing/locking of the database file.
504
505Note that, because SMTP delivery involves a list of destinations to try, there
506may be defer-type retry information for some of them even when the message was
507successfully delivered. Likewise if it eventually failed.
508
509This function may move addresses from the defer to the failed queue if the
510ultimate retry time has expired.
511
512Arguments:
513 addr_defer queue of deferred addresses
514 addr_failed queue of failed addresses
515 addr_succeed queue of successful addresses
516
517Returns: nothing
518*/
519
520void
521retry_update(address_item **addr_defer, address_item **addr_failed,
522 address_item **addr_succeed)
523{
524open_db dbblock;
525open_db *dbm_file = NULL;
526time_t now = time(NULL);
527int i;
528
529DEBUG(D_retry) debug_printf("Processing retry items\n");
530
531/* Three-times loop to handle succeeded, failed, and deferred addresses.
532Deferred addresses must be handled after failed ones, because some may be moved
533to the failed chain if they have timed out. */
534
535for (i = 0; i < 3; i++)
536 {
537 address_item *endaddr, *addr;
538 address_item *last_first = NULL;
2813c06e
CE
539 address_item **paddr = i==0 ? addr_succeed :
540 i==1 ? addr_failed : addr_defer;
420a0d19
CE
541 address_item **saved_paddr = NULL;
542
2813c06e
CE
543 DEBUG(D_retry) debug_printf("%s addresses:\n",
544 i == 0 ? "Succeeded" : i == 1 ? "Failed" : "Deferred");
420a0d19
CE
545
546 /* Loop for each address on the chain. For deferred addresses, the whole
547 address times out unless one of its retry addresses has a retry rule that
548 hasn't yet timed out. Deferred addresses should not be requesting deletion
549 of retry items, but just in case they do by accident, treat that case
550 as "not timed out".
551
552 As well as handling the addresses themselves, we must also process any
553 retry items for any parent addresses - these are typically "delete" items,
554 because the parent must have succeeded in order to generate the child. */
555
2813c06e 556 while ((endaddr = *paddr))
420a0d19
CE
557 {
558 BOOL timed_out = FALSE;
559 retry_item *rti;
560
2813c06e 561 for (addr = endaddr; addr; addr = addr->parent)
420a0d19
CE
562 {
563 int update_count = 0;
564 int timedout_count = 0;
565
2813c06e
CE
566 DEBUG(D_retry) debug_printf(" %s%s\n", addr->address,
567 addr->retries ? "" : ": no retry items");
420a0d19
CE
568
569 /* Loop for each retry item. */
570
2813c06e 571 for (rti = addr->retries; rti; rti = rti->next)
420a0d19
CE
572 {
573 uschar *message;
574 int message_length, message_space, failing_interval, next_try;
575 retry_rule *rule, *final_rule;
576 retry_config *retry;
577 dbdata_retry *retry_record;
578
579 /* Open the retry database if it is not already open; failure to open
580 the file is logged, but otherwise ignored - deferred addresses will
581 get retried at the next opportunity. Not opening earlier than this saves
582 opening if no addresses have retry items - common when none have yet
583 reached their retry next try time. */
584
2813c06e 585 if (!dbm_file)
420a0d19
CE
586 dbm_file = dbfn_open(US"retry", O_RDWR, &dbblock, TRUE);
587
2813c06e 588 if (!dbm_file)
420a0d19
CE
589 {
590 DEBUG(D_deliver|D_retry|D_hints_lookup)
591 debug_printf("retry database not available for updating\n");
592 return;
593 }
594
595 /* If there are no deferred addresses, that is, if this message is
596 completing, and the retry item is for a message-specific SMTP error,
597 force it to be deleted, because there's no point in keeping data for
598 no-longer-existing messages. This situation can occur when a domain has
599 two hosts and a message-specific error occurs for the first of them,
600 but the address gets delivered to the second one. This optimization
601 doesn't succeed in cleaning out all the dead entries, but it helps. */
602
2813c06e 603 if (!*addr_defer && rti->flags & rf_message)
420a0d19
CE
604 rti->flags |= rf_delete;
605
606 /* Handle the case of a request to delete the retry info for this
607 destination. */
608
2813c06e 609 if (rti->flags & rf_delete)
420a0d19
CE
610 {
611 (void)dbfn_delete(dbm_file, rti->key);
612 DEBUG(D_retry)
613 debug_printf("deleted retry information for %s\n", rti->key);
614 continue;
615 }
616
617 /* Count the number of non-delete retry items. This is so that we
618 can compare it to the count of timed_out ones, to check whether
619 all are timed out. */
620
621 update_count++;
622
623 /* Get the retry information for this destination and error code, if
624 any. If this item is for a remote host with ip address, then pass
625 the domain name as an alternative to search for. If no retry
626 information is found, we can't generate a retry time, so there is
627 no point updating the database. This retry item is timed out. */
628
2813c06e
CE
629 if (!(retry = retry_find_config(rti->key + 2,
630 rti->flags & rf_host ? addr->domain : NULL,
631 rti->basic_errno, rti->more_errno)))
420a0d19
CE
632 {
633 DEBUG(D_retry) debug_printf("No configured retry item for %s%s%s\n",
634 rti->key,
2813c06e
CE
635 rti->flags & rf_host ? US" or " : US"",
636 rti->flags & rf_host ? addr->domain : US"");
420a0d19
CE
637 if (addr == endaddr) timedout_count++;
638 continue;
639 }
640
641 DEBUG(D_retry)
642 {
2813c06e 643 if (rti->flags & rf_host)
420a0d19
CE
644 debug_printf("retry for %s (%s) = %s %d %d\n", rti->key,
645 addr->domain, retry->pattern, retry->basic_errno,
646 retry->more_errno);
647 else
648 debug_printf("retry for %s = %s %d %d\n", rti->key, retry->pattern,
649 retry->basic_errno, retry->more_errno);
650 }
651
652 /* Set up the message for the database retry record. Because DBM
653 records have a maximum data length, we enforce a limit. There isn't
654 much point in keeping a huge message here, anyway. */
655
2813c06e
CE
656 message = rti->basic_errno > 0
657 ? US strerror(rti->basic_errno)
658 : rti->message
659 ? US string_printing(rti->message)
660 : US"unknown error";
420a0d19
CE
661 message_length = Ustrlen(message);
662 if (message_length > 150) message_length = 150;
663
664 /* Read a retry record from the database or construct a new one.
665 Ignore an old one if it is too old since it was last updated. */
666
667 retry_record = dbfn_read(dbm_file, rti->key);
2813c06e
CE
668 if ( retry_record
669 && now - retry_record->time_stamp > retry_data_expire)
420a0d19
CE
670 retry_record = NULL;
671
2813c06e 672 if (!retry_record)
420a0d19
CE
673 {
674 retry_record = store_get(sizeof(dbdata_retry) + message_length);
675 message_space = message_length;
676 retry_record->first_failed = now;
677 retry_record->last_try = now;
678 retry_record->next_try = now;
679 retry_record->expired = FALSE;
680 retry_record->text[0] = 0; /* just in case */
681 }
682 else message_space = Ustrlen(retry_record->text);
683
684 /* Compute how long this destination has been failing */
685
686 failing_interval = now - retry_record->first_failed;
687 DEBUG(D_retry) debug_printf("failing_interval=%d message_age=%d\n",
688 failing_interval, message_age);
689
690 /* For a non-host error, if the message has been on the queue longer
691 than the recorded time of failure, use the message's age instead. This
692 can happen when some messages can be delivered and others cannot; a
693 successful delivery will reset the first_failed time, and this can lead
694 to a failing message being retried too often. */
695
2813c06e 696 if (!(rti->flags & rf_host) && message_age > failing_interval)
420a0d19
CE
697 failing_interval = message_age;
698
699 /* Search for the current retry rule. The cutoff time of the
700 last rule is handled differently to the others. The rule continues
701 to operate for ever (the global maximum interval will eventually
702 limit the gaps) but its cutoff time determines when an individual
703 destination times out. If there are no retry rules, the destination
704 always times out, but we can't compute a retry time. */
705
706 final_rule = NULL;
2813c06e 707 for (rule = retry->rules; rule; rule = rule->next)
420a0d19
CE
708 {
709 if (failing_interval <= rule->timeout) break;
710 final_rule = rule;
711 }
712
713 /* If there's an un-timed out rule, the destination has not
714 yet timed out, so the address as a whole has not timed out (but we are
715 interested in this only for the end address). Make sure the expired
716 flag is false (can be forced via fixdb from outside, but ensure it is
717 consistent with the rules whenever we go through here). */
718
2813c06e 719 if (rule)
420a0d19 720 retry_record->expired = FALSE;
420a0d19
CE
721
722 /* Otherwise, set the retry timeout expired, and set the final rule
723 as the one from which to compute the next retry time. Subsequent
724 messages will fail immediately until the retry time is reached (unless
725 there are other, still active, retries). */
726
727 else
728 {
729 rule = final_rule;
730 retry_record->expired = TRUE;
731 if (addr == endaddr) timedout_count++;
732 }
733
734 /* There is a special case to consider when some messages get through
735 to a destination and others don't. This can happen locally when a
736 large message pushes a user over quota, and it can happen remotely
737 when a machine is on a dodgy Internet connection. The messages that
738 get through wipe the retry information, causing those that don't to
739 stay on the queue longer than the final retry time. In order to
740 avoid this, we check, using the time of arrival of the message, to
741 see if it has been on the queue for more than the final cutoff time,
742 and if so, cause this retry item to time out, and the retry time to
743 be set to "now" so that any subsequent messages in the same condition
744 also get tried. We search for the last rule onwards from the one that
745 is in use. If there are no retry rules for the item, rule will be null
746 and timedout_count will already have been updated.
747
748 This implements "timeout this rule if EITHER the host (or routing or
749 directing) has been failing for more than the maximum time, OR if the
750 message has been on the queue for more than the maximum time."
751
752 February 2006: It is possible that this code is no longer needed
753 following the change to the retry calculation to use the message age if
754 it is larger than the time since first failure. It may be that the
755 expired flag is always set when the other conditions are met. However,
756 this is a small bit of code, and it does no harm to leave it in place,
757 just in case. */
758
2813c06e
CE
759 if ( received_time <= retry_record->first_failed
760 && addr == endaddr
761 && !retry_record->expired
762 && rule)
420a0d19
CE
763 {
764 retry_rule *last_rule;
2813c06e
CE
765 for (last_rule = rule; last_rule->next; last_rule = last_rule->next)
766 ;
420a0d19
CE
767 if (now - received_time > last_rule->timeout)
768 {
769 DEBUG(D_retry) debug_printf("on queue longer than maximum retry\n");
770 timedout_count++;
771 rule = NULL;
772 }
773 }
774
775 /* Compute the next try time from the rule, subject to the global
776 maximum, and update the retry database. If rule == NULL it means
777 there were no rules at all (and the timeout will be set expired),
778 or we have a message that is older than the final timeout. In this
779 case set the next retry time to now, so that one delivery attempt
780 happens for subsequent messages. */
781
2813c06e
CE
782 if (!rule)
783 next_try = now;
784 else
420a0d19 785 {
2813c06e
CE
786 if (rule->rule == 'F')
787 next_try = now + rule->p1;
420a0d19
CE
788 else /* rule = 'G' or 'H' */
789 {
790 int last_predicted_gap =
791 retry_record->next_try - retry_record->last_try;
792 int last_actual_gap = now - retry_record->last_try;
793 int lastgap = (last_predicted_gap < last_actual_gap)?
794 last_predicted_gap : last_actual_gap;
795 int next_gap = (lastgap * rule->p2)/1000;
796 if (rule->rule == 'G')
420a0d19 797 next_try = now + ((lastgap < rule->p1)? rule->p1 : next_gap);
420a0d19
CE
798 else /* The 'H' rule */
799 {
800 next_try = now + rule->p1;
801 if (next_gap > rule->p1)
802 next_try += random_number(next_gap - rule->p1)/2 +
803 (next_gap - rule->p1)/2;
804 }
805 }
806 }
807
808 /* Impose a global retry max */
809
810 if (next_try - now > retry_interval_max)
811 next_try = now + retry_interval_max;
812
813 /* If the new message length is greater than the previous one, we
814 have to copy the record first. */
815
816 if (message_length > message_space)
817 {
818 dbdata_retry *newr = store_get(sizeof(dbdata_retry) + message_length);
819 memcpy(newr, retry_record, sizeof(dbdata_retry));
820 retry_record = newr;
821 }
822
823 /* Set up the retry record; message_length may be less than the string
824 length for very long error strings. */
825
826 retry_record->last_try = now;
827 retry_record->next_try = next_try;
828 retry_record->basic_errno = rti->basic_errno;
829 retry_record->more_errno = rti->more_errno;
830 Ustrncpy(retry_record->text, message, message_length);
831 retry_record->text[message_length] = 0;
832
833 DEBUG(D_retry)
834 {
835 int letter = retry_record->more_errno & 255;
836 debug_printf("Writing retry data for %s\n", rti->key);
837 debug_printf(" first failed=%d last try=%d next try=%d expired=%d\n",
838 (int)retry_record->first_failed, (int)retry_record->last_try,
839 (int)retry_record->next_try, retry_record->expired);
840 debug_printf(" errno=%d more_errno=", retry_record->basic_errno);
841 if (letter == 'A' || letter == 'M')
842 debug_printf("%d,%c", (retry_record->more_errno >> 8) & 255,
843 letter);
844 else
845 debug_printf("%d", retry_record->more_errno);
846 debug_printf(" %s\n", retry_record->text);
847 }
848
849 (void)dbfn_write(dbm_file, rti->key, retry_record,
850 sizeof(dbdata_retry) + message_length);
851 } /* Loop for each retry item */
852
853 /* If all the non-delete retry items are timed out, the address is
854 timed out, provided that we didn't skip any hosts because their retry
855 time was not reached (or because of hosts_max_try). */
856
857 if (update_count > 0 && update_count == timedout_count)
420a0d19
CE
858 if (!testflag(endaddr, af_retry_skipped))
859 {
860 DEBUG(D_retry) debug_printf("timed out: all retries expired\n");
861 timed_out = TRUE;
862 }
863 else
864 {
865 DEBUG(D_retry)
866 debug_printf("timed out but some hosts were skipped\n");
867 }
420a0d19
CE
868 } /* Loop for an address and its parents */
869
870 /* If this is a deferred address, and retry processing was requested by
871 means of one or more retry items, and they all timed out, move the address
872 to the failed queue, and restart this loop without updating paddr.
873
874 If there were several addresses batched in the same remote delivery, only
875 the original top one will have host retry items attached to it, but we want
876 to handle all the same. Each will have a pointer back to its "top" address,
877 and they will now precede the item with the retries because addresses are
878 inverted when added to these final queues. We have saved information about
879 them in passing (below) so they can all be cut out at once. */
880
881 if (i == 2) /* Handling defers */
882 {
2813c06e 883 if (endaddr->retries && timed_out)
420a0d19
CE
884 {
885 if (last_first == endaddr) paddr = saved_paddr;
886 addr = *paddr;
887 *paddr = endaddr->next;
888
889 endaddr->next = *addr_failed;
890 *addr_failed = addr;
891
892 for (;; addr = addr->next)
893 {
894 setflag(addr, af_retry_timedout);
895 addr->message = (addr->message == NULL)? US"retry timeout exceeded" :
896 string_sprintf("%s: retry timeout exceeded", addr->message);
897 addr->user_message = (addr->user_message == NULL)?
898 US"retry timeout exceeded" :
899 string_sprintf("%s: retry timeout exceeded", addr->user_message);
900 log_write(0, LOG_MAIN, "** %s%s%s%s: retry timeout exceeded",
901 addr->address,
902 (addr->parent == NULL)? US"" : US" <",
903 (addr->parent == NULL)? US"" : addr->parent->address,
904 (addr->parent == NULL)? US"" : US">");
905
906 if (addr == endaddr) break;
907 }
908
909 continue; /* Restart from changed *paddr */
910 }
911
912 /* This address is to remain on the defer chain. If it has a "first"
913 pointer, save the pointer to it in case we want to fail the set of
914 addresses when we get to the first one. */
915
916 if (endaddr->first != last_first)
917 {
918 last_first = endaddr->first;
919 saved_paddr = paddr;
920 }
921 }
922
923 /* All cases (succeed, fail, defer left on queue) */
924
925 paddr = &(endaddr->next); /* Advance to next address */
926 } /* Loop for all addresses */
927 } /* Loop for succeed, fail, defer */
928
929/* Close and unlock the database */
930
2813c06e 931if (dbm_file) dbfn_close(dbm_file);
420a0d19
CE
932
933DEBUG(D_retry) debug_printf("end of retry processing\n");
934}
935
936/* End of retry.c */