From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] upas sending duplicate copies
Date: Thu, 10 Sep 2020 12:20:26 -0400 [thread overview]
Message-ID: <FD8F459E-E7C7-4625-80E4-5E42590D1E4C@stanleylieber.com> (raw)
In-Reply-To: <8C78EA4E8EDD8518FB263D8DDDE52F6B@eigenstate.org>
On September 3, 2020 11:03:35 PM EDT, ori@eigenstate.org wrote:
>> running latest code, no other recent changes to my mail setup. people
>are reporting receiving duplicate copies of mail from me. i don't see
>any obvious signs of delivery failures in my logs, but i do see what
>appear to be multiple deliveries of the same message to remote servers,
>around 3-5 minutes apart. of course, it's all intermittent, and doesn't
>happen with every recipient.
>>
>> this never used to happen before that i'm aware of.
>>
>> sl
>
>Hm. I'm not a upas expert (yet), but it looks like the only place we
>try
>to resend messages is in upas/runq. That only retries if the command it
>execs requests a retry when it exits. Presumably that command is smtp.
>
>I don't think they should be affected by recent date changes -- smtp
>treats
>dates as opaque strings, other than 'rewritezone' and upas/runq doesn't
>deal with dates at all. And I can't think why mangling dates would give
>a temp fail while *still* sending the message.
>
>If you're willing to debug, would it be too verbose to run upas/runq
>and upas/smtp with the -d (debug) flag, so we can see more clearly what
>happens when something gets resent?
>
>Does it happen every time with certain servers, or is it just random?
>
>(I'm hoping that it's got something to do with the recent centurylink
>outage, rather than my changes... this date stuff is proving to be
>pretty painful)
as far as i can tell it hasn't happened since i complained.
sl
prev parent reply other threads:[~2020-09-10 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 15:23 Stanley Lieber
2020-09-04 3:03 ` [9front] " ori
2020-09-10 16:20 ` Stanley Lieber [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FD8F459E-E7C7-4625-80E4-5E42590D1E4C@stanleylieber.com \
--to=sl@stanleylieber.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).