[opensuse] How to allow more delay in postfix?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I send mails from one internal machine to another. Ocassionally, this destination could be off for a week or more; still I would like Postfix to not give up after five days and keep trying, say, for a month. How could I do it? Preferably for one destination. - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEUEARECAAYFAlkMZrMACgkQtTMYHG2NR9VE0wCgiXF2FusfzAPv6FpgcSROegJ2 424AmOqvUu3wT0f0kkGdK4lgr5mwBTk= =zqnt -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Carlos E. R.
I send mails from one internal machine to another. Ocassionally, this destination could be off for a week or more; still I would like Postfix to not give up after five days and keep trying, say, for a month.
How could I do it?
Preferably for one destination.
don't know about "one destination", but look at: maximal_queue_lifetime (default: 5d) Consider a message as undeliverable, when delivery fails with a temporary error, and the time in the queue has reached the maximal_queue_lifetime limit. Time units: s (seconds), m (minutes), h (hours), d (days), w (weeks). The default time unit is d (days). Specify 0 when mail delivery should be tried only once. config is /etc/postfix/bounce.cf and possibly: transport_destination_concurrency_failed_cohort_limit (default: $default_destination_concurrency_failed_cohort_limit) A transport-specific override for the default_destination_concurrency_failed_cohort_limit parameter value, where transport is the master.cf name of the message delivery transport. Note: some transport_destination_concurrency_failed_cohort_limit parameters will not show up in "postconf" command output before Postfix version 2.9. This limitation applies to many parameters whose name is a combination of a master.cf service name and a built-in suffix (in this case: "_destination_concurrency_failed_cohort_limit"). This feature is available in Postfix 2.5 and later. default_destination_concurrency_failed_cohort_limit (default: 1) How many pseudo-cohorts must suffer connection or handshake failure before a specific destination is considered unavailable (and further delivery is suspended). Specify zero to disable this feature. A destination's pseudo-cohort failure count is reset each time a delivery completes without connection or handshake failure for that specific destination. A pseudo-cohort is the number of deliveries equal to a destination's delivery concurrency. Use transport_destination_concurrency_failed_cohort_limit to specify a transport-specific override, where transport is the master.cf name of the message delivery transport. This feature is available in Postfix 2.5. The default setting is compatible with earlier Postfix versions. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-05-05 14:02, Patrick Shanahan wrote:
* Carlos E. R. <> [05-05-17 07:51]:
I send mails from one internal machine to another. Ocassionally, this destination could be off for a week or more; still I would like Postfix to not give up after five days and keep trying, say, for a month.
How could I do it?
Preferably for one destination.
don't know about "one destination", but look at:
maximal_queue_lifetime (default: 5d) Consider a message as undeliverable, when delivery fails with a temporary error, and the time in the queue has reached the maximal_queue_lifetime limit.
Time units: s (seconds), m (minutes), h (hours), d (days), w (weeks). The default time unit is d (days).
Specify 0 when mail delivery should be tried only once. config is /etc/postfix/bounce.cf
I'll try this one the others seem too complex, because "transport is the master.cf name of the message delivery transport", not a destination. I will keep thinking (low priority), but meanwhile I'll set it to 100d. Thanks. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
participants (2)
-
Carlos E. R.
-
Patrick Shanahan