How to force retry queue to try again?
I'm trying to find some documentation on how to force my retry ("RetryRunner") queue to try delivery again. I'll keep searching but thought I'd toss a quick note here as well. Anyone?
Thanks for any help you can provide!
/raj
On 08/06/2018 07:22 PM, Richard Johnson wrote:
I'm trying to find some documentation on how to force my retry ("RetryRunner") queue to try delivery again. I'll keep searching but thought I'd toss a quick note here as well. Anyone?
Prior to Mailman 2.1.26, it processes the queue, sleeps for 15 minutes and repeats. There has always been a DELIVERY_RETRY_WAIT setting that defaulted to 1 hour, but prior to 2.1.26, it was ineffective. The current doc for that setting in Defaults.py is
# How long should we wait before we retry a temporary delivery failure? # Because RetryRunner sleeps for 15 minutes between processes of its queue, # whatever is put here is effectively rounded up to the next integer multiple # of 15 minutes. DELIVERY_RETRY_WAIT = hours(1)
The way this works is when a delivery fails for a temp failure, the current time + DELIVERY_RETRY_WAIT is placed in the message's metadata and the message won't be retried before that time.
If your Mailman is pre 2.1.26, or if DELIVERY_RETRY_WAIT has been set to a very low value, you can restart RetryRunner by sending it SIGINT. That should wake it up to process its queue.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks, I'll keep this information around for future reference! In the meantime, the queue was automatically retried and the changes I made to postfix configuration were correct, so the mail was delivered just fine!
(Mailman seems to deliver outgoing list messages to the local SMTP server via "::1". I was expecting 127.0.0.1. I wasn't expecting ipv6! ["Nobody expects ipv6!"]) :)
/raj
On Aug 6, 2018, at 9:16 PM, Mark Sapiro mark@msapiro.net wrote:
On 08/06/2018 07:22 PM, Richard Johnson wrote:
I'm trying to find some documentation on how to force my retry ("RetryRunner") queue to try delivery again. I'll keep searching but thought I'd toss a quick note here as well. Anyone?
Prior to Mailman 2.1.26, it processes the queue, sleeps for 15 minutes and repeats. There has always been a DELIVERY_RETRY_WAIT setting that defaulted to 1 hour, but prior to 2.1.26, it was ineffective. The current doc for that setting in Defaults.py is
# How long should we wait before we retry a temporary delivery failure? # Because RetryRunner sleeps for 15 minutes between processes of its queue, # whatever is put here is effectively rounded up to the next integer multiple # of 15 minutes. DELIVERY_RETRY_WAIT = hours(1)
The way this works is when a delivery fails for a temp failure, the current time + DELIVERY_RETRY_WAIT is placed in the message's metadata and the message won't be retried before that time.
If your Mailman is pre 2.1.26, or if DELIVERY_RETRY_WAIT has been set to a very low value, you can restart RetryRunner by sending it SIGINT. That should wake it up to process its queue.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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/raj%40mischievous.us
On 08/06/2018 09:58 PM, Richard Johnson wrote:
(Mailman seems to deliver outgoing list messages to the local SMTP server via "::1". I was expecting 127.0.0.1. I wasn't expecting ipv6! ["Nobody expects ipv6!"]) :)
Mailman delivers by default to localhost. That's ::1 because that's what localhost resolves to in your /etc/hosts. If that's not what you want, change /etc/hosts.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Interesting. Ok. Thanks!
/raj
On Aug 6, 2018, at 10:12 PM, Mark Sapiro mark@msapiro.net wrote:
On 08/06/2018 09:58 PM, Richard Johnson wrote:
(Mailman seems to deliver outgoing list messages to the local SMTP server via "::1". I was expecting 127.0.0.1. I wasn't expecting ipv6! ["Nobody expects ipv6!"]) :)
Mailman delivers by default to localhost. That's ::1 because that's what localhost resolves to in your /etc/hosts. If that's not what you want, change /etc/hosts.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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/raj%40mischievous.us
participants (2)
-
Mark Sapiro -
Richard Johnson