Wez Furlong
b2887cb7b8
data_processing_timeout: increase default to 5 minutes
...
I worry that 1 minute might be too short to be universally good,
particularly as a change in behavior from an earlier build: going from
no timeout to 1 minute could be super surprising and un-welcome.
Let's bump this up to 5 minutes which more closely matches the
default for DATA in the base SMTP RFC.
2025-03-04 16:23:16 -07:00
..
2024-11-08 10:37:08 -07:00
2025-03-04 16:23:14 -07:00
2025-02-21 14:32:36 -07:00
2024-08-18 19:40:47 -07:00
2024-08-18 19:47:35 -07:00
2024-08-18 19:19:30 -07:00
2025-02-21 17:15:52 -07:00
2025-03-04 16:23:16 -07:00
2024-08-18 22:18:59 -07:00
2023-03-14 10:17:55 -07:00
2025-01-08 16:00:17 -07:00
2024-11-12 12:25:53 -07:00
2023-11-29 12:08:34 -07:00
2024-09-02 07:27:50 -07:00
2025-02-08 07:29:41 -07:00
2024-10-08 13:39:07 -07:00
2024-11-12 12:25:53 -07:00
2024-06-10 09:30:17 -07:00
2024-09-02 07:27:50 -07:00
2024-09-02 07:27:50 -07:00
2024-09-02 07:27:50 -07:00
2024-09-02 07:27:50 -07:00
2025-01-29 17:05:37 -07:00
2025-02-06 11:06:25 -07:00
2023-02-25 14:59:20 -07:00
2024-06-10 09:30:17 -07:00
2023-02-25 14:59:20 -07:00
2024-11-12 12:25:53 -07:00
2023-03-24 09:02:10 -07:00
2024-11-12 12:25:53 -07:00
2025-01-08 15:52:06 -07:00
2025-01-08 15:54:05 -07:00
2023-06-16 10:03:49 -07:00
2023-06-16 10:03:49 -07:00
2023-06-16 10:03:49 -07:00
2025-02-20 12:06:12 -07:00
2025-02-20 12:06:12 -07:00
2025-02-20 12:06:12 -07:00
2025-01-08 15:52:06 -07:00
2025-01-08 15:52:06 -07:00
2025-01-08 15:52:06 -07:00
2025-01-08 15:52:06 -07:00
2025-01-23 13:49:35 -07:00
2024-06-10 09:30:17 -07:00
2024-09-02 07:27:50 -07:00
2024-09-02 07:27:50 -07:00
2024-09-02 07:27:50 -07:00
2024-09-02 07:27:50 -07:00
2024-06-10 09:30:17 -07:00