Re: [Mailman-Users] [ext] Messages delivered out of order and delayed
Ralf Hildebrandt writes: > That's [do you mean 4 hours?] quite a lot. I know that postfx for > example would rescan the queue after 300s (5m) and probably retry > the message then (after an initial failure). Well, I wouldn't be surprised if nowadays defaults are like that. I haven't changed mine ever (the series of Debian servers that have hosted my domain have been continuously serving mail for almost 25 years). > Maybe they "tweaked" something :) I suspect that as soon as greylisting became common, they did. On the other hand, if they retry after 5 minutes, they'd get caught again by every greylister I know (all 10 min or more). So the question is how much do they back off? I guess if I worried about getting my mail delivered a few minutes faster (which I don't :-), I would set the retry schedule every 5m or 10m up to a total of 30m, then back off sort of exponentially 4h, 8h, 16h, then 24h for a total of maybe 5 days. Steve -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] [ext] Messages delivered out of order and delayed
* Stephen J. Turnbull : > That's mostly true. However, traditionally the first retry was set > for 4 hours after the initial send. If Dreamhost has such a long > retry delay, that could cause hours of out-of-order and certainly cut > someone out of a hot and heavy discussion. That's quite a lot. I know that postfx for example would rescan the queue after 300s (5m) and probably retry the message then (after an initial failure). Maybe they "tweaked" something :) Ralf Hildebrandt Charité - Universitätsmedizin Berlin Geschäftsbereich IT | Abteilung Netzwerk Campus Benjamin Franklin (CBF) Haus I | 1. OG | Raum 105 Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 ralf.hildebra...@charite.de https://www.charite.de -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Messages delivered out of order and delayed
Jim Ziobro writes: > Indeed email is not a synchronous messaging channel. But most > email clients will sort incoming messages by header Date thus undo > the effects of out-of-order delivery. That's mostly true. However, traditionally the first retry was set for 4 hours after the initial send. If Dreamhost has such a long retry delay, that could cause hours of out-of-order and certainly cut someone out of a hot and heavy discussion. The problem is that the first message from a particular sender will be rejected temporarily and retried after 4 hours, but everything from that sender sent after 15 minutes (typical greylisting delay) will go through the list. Of course anybody the sender CC'd will get it immediately, and may reply. It can be a mess. Steve Footnotes: [1] For those who don't know the term: this is an antiabuse device where the recipient rejects the message with a temporary failure, then sets a timer for a few minutes, say 15. If the message is received again after that, it is accepted. -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
